GitHub Actions Supply Chain Pinning
asyncapi/generator
A skill your agent uses when editing, adding, or reviewing any file under .github/workflows/, or when a CI step installs a CLI tool (npm i -g, npx, pipx, uses: /setup-).
发布 Blockless VS Code 扩展到 Visual Studio Marketplace（含发布前测试）/ ship the Blockless extension to the VS Code Marketplace.
Install Publish Extension
$ npx skills add FreakStudioCN/mpy-hardware-extension --skill publish-extension -a claude-codeProject install by default; add -g for ~/.claude/skills/.
$ gh skill install FreakStudioCN/mpy-hardware-extension publish-extension --agent claude-codeProject scope by default; add --scope user for a personal install. Needs GitHub CLI 2.90.0 or later (public preview).
$ git clone --depth 1 https://github.com/FreakStudioCN/mpy-hardware-extension.git skills-src && mkdir -p .claude/skills && cp -r skills-src/.agents/skills/publish-extension .claude/skills/publish-extension && rm -rf skills-srcUse ~/.claude/skills/ instead of .claude/skills for a personal install. The folder must contain SKILL.md.
Claude Code skills documentation · loads skills from .claude/skills/
Install the "publish-extension" agent skill from https://github.com/FreakStudioCN/mpy-hardware-extension/tree/main/.agents/skills/publish-extension into .claude/skills/publish-extension/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "publish-extension", then confirm the skill loads.Claude Code copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$skill-installer install https://github.com/FreakStudioCN/mpy-hardware-extension/tree/main/.agents/skills/publish-extensionType this inside Codex. $skill-installer <name> installs a curated skill from openai/skills. The installer writes to $CODEX_HOME/skills (default ~/.codex/skills). Restart Codex if the skill does not show up.
$ npx skills add FreakStudioCN/mpy-hardware-extension --skill publish-extension -a codexProject install goes to .agents/skills/; add -g for ~/.codex/skills/.
$ gh skill install FreakStudioCN/mpy-hardware-extension publish-extension --agent codexProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/FreakStudioCN/mpy-hardware-extension.git skills-src && mkdir -p .agents/skills && cp -r skills-src/.agents/skills/publish-extension .agents/skills/publish-extension && rm -rf skills-srcUse ~/.agents/skills/ instead of .agents/skills for a personal install.
Codex skills documentation · loads skills from .agents/skills/
Install the "publish-extension" agent skill from https://github.com/FreakStudioCN/mpy-hardware-extension/tree/main/.agents/skills/publish-extension into .agents/skills/publish-extension/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "publish-extension", then confirm the skill loads.Codex copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ npx skills add FreakStudioCN/mpy-hardware-extension --skill publish-extension -a cursorProject install goes to .agents/skills/; add -g for ~/.cursor/skills/.
$ gh skill install FreakStudioCN/mpy-hardware-extension publish-extension --agent cursorProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/FreakStudioCN/mpy-hardware-extension.git skills-src && mkdir -p .cursor/skills && cp -r skills-src/.agents/skills/publish-extension .cursor/skills/publish-extension && rm -rf skills-srcUse ~/.cursor/skills/ instead of .cursor/skills for a personal install.
Cursor skills documentation · loads skills from .cursor/skills/, .agents/skills/, .claude/skills/, .codex/skills/
Install the "publish-extension" agent skill from https://github.com/FreakStudioCN/mpy-hardware-extension/tree/main/.agents/skills/publish-extension into .cursor/skills/publish-extension/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "publish-extension", then confirm the skill loads.Cursor copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ gemini skills install https://github.com/FreakStudioCN/mpy-hardware-extension.git --path .agents/skills/publish-extension--scope user (default) or --scope workspace; --path is the subfolder of the repo that holds the skill; --consent skips the security confirmation prompt.
$ npx skills add FreakStudioCN/mpy-hardware-extension --skill publish-extension -a gemini-cliProject install goes to .agents/skills/; add -g for ~/.gemini/skills/.
$ gh skill install FreakStudioCN/mpy-hardware-extension publish-extension --agent gemini-cliProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/FreakStudioCN/mpy-hardware-extension.git skills-src && mkdir -p .gemini/skills && cp -r skills-src/.agents/skills/publish-extension .gemini/skills/publish-extension && rm -rf skills-srcUse ~/.gemini/skills/ instead of .gemini/skills for a personal install, then run /skills reload.
Gemini CLI skills documentation · loads skills from .gemini/skills/, .agents/skills/
Install the "publish-extension" agent skill from https://github.com/FreakStudioCN/mpy-hardware-extension/tree/main/.agents/skills/publish-extension into .gemini/skills/publish-extension/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "publish-extension", then confirm the skill loads.Gemini CLI copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ gh skill install FreakStudioCN/mpy-hardware-extension publish-extensionInstalls for Copilot at project scope by default; add --scope user for a personal install. Preview a skill first with gh skill preview. Needs GitHub CLI 2.90.0 or later (public preview).
$ npx skills add FreakStudioCN/mpy-hardware-extension --skill publish-extension -a github-copilotProject install goes to .agents/skills/; add -g for ~/.copilot/skills/.
$ git clone --depth 1 https://github.com/FreakStudioCN/mpy-hardware-extension.git skills-src && mkdir -p .github/skills && cp -r skills-src/.agents/skills/publish-extension .github/skills/publish-extension && rm -rf skills-srcUse ~/.copilot/skills/ instead of .github/skills for a personal install. Commit .github/skills so cloud agent and code review can use it.
GitHub Copilot skills documentation · loads skills from .github/skills/, .claude/skills/, .agents/skills/
Install the "publish-extension" agent skill from https://github.com/FreakStudioCN/mpy-hardware-extension/tree/main/.agents/skills/publish-extension into .github/skills/publish-extension/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "publish-extension", then confirm the skill loads.GitHub Copilot copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ npx skills add FreakStudioCN/mpy-hardware-extension --skill publish-extension -a opencodeOpenCode documents no install command of its own. Project install goes to .agents/skills/; add -g for ~/.config/opencode/skills/.
$ gh skill install FreakStudioCN/mpy-hardware-extension publish-extension --agent opencodeProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/FreakStudioCN/mpy-hardware-extension.git skills-src && mkdir -p .opencode/skills && cp -r skills-src/.agents/skills/publish-extension .opencode/skills/publish-extension && rm -rf skills-srcUse ~/.config/opencode/skills/ instead of .opencode/skills for a personal install.
OpenCode skills documentation · loads skills from .opencode/skills/, .claude/skills/, .agents/skills/
Install the "publish-extension" agent skill from https://github.com/FreakStudioCN/mpy-hardware-extension/tree/main/.agents/skills/publish-extension into .opencode/skills/publish-extension/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "publish-extension", then confirm the skill loads.OpenCode copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
Facts
- Skill name
publish-extension- GitHub stars
- 154
- Token cost
- ~1.3k tokens
- SKILL.md length
- 316 words
- Files
- 1
- Skills in repo
- 8
- Repo updated
- First seen
- Licence
- Custom licence
At a glance
发布 Blockless VS Code 扩展到 Visual Studio Marketplace（含发布前测试）/ ship the Blockless extension to the VS Code Marketplace.
- Works in 4 steps: 预检（程序面，全绿才发） → 人肉内测（首版上公网前强烈建议） → 发布（local / tag，需用户确认） → …
- Tasks that involve CI/CD
- SKILL.md covers 解析参数（默认 check）, Phase 1 — 预检（程序面，全绿才发）, Phase 2 — 人肉内测（首版上公网前强烈建议） and Phase 3 — 发布（local / tag，需用户确认）, plus 2 more sections
- Calls npm, git and npx; reaches blockless.upypi.net and marketplace.visualstudio.com
What it does
Publish Extension is an agent skill from FreakStudioCN/mpy-hardware-extension. 发布 Blockless VS Code 扩展到 Visual Studio Marketplace（含发布前测试）/ ship the Blockless extension to the VS Code Marketplace. 先跑预检（Render 后端探活 + api-base-url 指向线上 + 子模块完整 + typecheck + npm test + 打包 VSIX），再二选一发布：GitHub Actions 打 v tag 自动发（仓库 secret VSCEPAT），或本地 vsce login blockless + npm run publish。publisher=blockless，Marketplace ID=blockless.mpy-hardware-extension。默认只预检、不发布；真正发布要用户在本次调用里显式确认。参数 check(默认)/local/tag。
Its SKILL.md is about 1.3k tokens, which your agent loads only when the skill is triggered. It is a single SKILL.md file with no bundled scripts.
It sits in DevOps & Cloud, covering CI/CD. It works with Visual Studio Code, GitHub Actions, npm and GitHub.
When your agent uses it
- Tasks that involve CI/CD
Example prompts
- “/publish-extension”
Requirements
- Node.js
Workflow steps
4 steps, taken from the step headings in SKILL.md.
- 预检（程序面，全绿才发）
- 人肉内测（首版上公网前强烈建议）
- 发布（local / tag，需用户确认）
- 验证已上架
What it can do on your machine
Read from SKILL.md and the folder at commit b661df6. It shows what the files ask for, not the result of running them.
Tool permissions
Pre-approves nothing: there is no allowed-tools line, so your agent's usual permission prompts apply.
From allowed-tools in the SKILL.md frontmatter.
Runs code
Shell commands in SKILL.md call:
npmgitnpx
From the folder's file list and the shell code blocks in SKILL.md.
Network
Hosts in commands or code, which the agent is likely to contact:
blockless.upypi.netmarketplace.visualstudio.com
From URLs in SKILL.md, links to its own repository left out.
Credentials
Names no API keys, tokens, secrets or passwords.
From names ending in _API_KEY, _TOKEN, _SECRET, _KEY or _PASSWORD in SKILL.md.
Context cost
Publish Extension loads about 1.3k tokens when it runs. Until then it costs about 109 tokens; SKILL.md has 316 words of instructions outside code blocks.
Estimates: characters ÷ 4, the usual rule of thumb; real counts depend on the model's tokenizer. Scripts and assets cost tokens only if the agent reads them.
Safety
Auto-check passed
The automated check found no risky patterns in SKILL.md.
Automated static check — not a guarantee. Review scripts before installing. It scans the text of SKILL.md for risky patterns (piping downloads into a shell, reading credential files, hidden Unicode, destructive commands); files beside SKILL.md are not scanned.
SKILL.md
Its licence (Custom licence) doesn't allow us to republish the file, so here is its outline and opening line. It has 316 words (~1,343 tokens).
“把 mpy-hardware-extension 打包并发布到 Visual Studio Marketplace。发布走 PAT（不是 Azure workload identity——那条试过又弃，完整步骤留在 git 历史 commit 0ed0383）。两种发布方式：”
- name
- publish-extension
- argument-hint
- [check|local|tag]
Files
Just SKILL.md in .agents/skills/publish-extension of FreakStudioCN/mpy-hardware-extension.
Open the folder on GitHubat commit b661df6
Compare with similar skills
Publish Extension next to the 5 skills that share the most tags, products or categories with it. Stars are the repository's; “used in” counts other GitHub owners with a copy.
| Skill | Stars | Used in | Tokens | Auto-check | Licence | Repo updated |
|---|---|---|---|---|---|---|
| Publish Extension this skillFreakStudioCN/mpy-hardware-extension | 154 | — | ~1.3k | Automated safety check: Pass | Custom licence | |
| GitHub Actions Supply Chain Pinningasyncapi/generator | 1.1k | — | ~1.9k | Automated safety check: Pass | Apache-2.0 | |
| npm Release Via GitHub Actionsjmfederico/pi-web | 871 | — | ~2.9k | Automated safety check: Pass | MIT | |
| Release Flowromankurnovskii/BrewMate | 300 | — | ~976 | Automated safety check: Pass | MIT | |
| Tendril ReleaseIvy-Interactive/Ivy-Tendril | 202 | — | ~2k | Automated safety check: Pass | Custom licence | |
| Publishingadeze/raindrop-mcp | 188 | — | ~398 | Automated safety check: Pass | MIT |
Similar skills
npm Release Via GitHub Actions
jmfederico/pi-web
A skill your agent uses whenever the user asks for a new npm version, npm release, package release, new release, version bump, publishing to npm, cutting a GitHub release, tagging a release, or…
Release Flow
romankurnovskii/BrewMate
Automate the full application release flow for BrewMate, including committing local changes, bumping version, waiting for GitHub Actions release build, and pushing the in-repo cask update…
Tendril Release
Ivy-Interactive/Ivy-Tendril
Updates the used Ivy NuGet packages to the latest stable versions in a branch from development, builds/verifies, merges into development, creates a PR into main, merges it, merges main back to…
Publishing
adeze/raindrop-mcp
Publishing and release workflow with semantic-release and GitHub Actions
- Official
Gating Production Deploys
PostHog/posthog
A skill your agent uses when adding or editing a GitHub Actions workflow that pushes a container image to a registry (ECR/ghcr/Docker Hub via build-push-action) or dispatches a production deploy (a…
More from FreakStudioCN/mpy-hardware-extension
All 8 skills in this repoBlockless Extension E2E
FreakStudioCN/mpy-hardware-extension
Run and debug the Blockless VS Code extension release gate: CI-equivalent API and extension tests, V0 protocol smoke, live DeepSeek full-stack e2e, VSIX packaging, local reinstall, direct…
Diagnose Cloud Session
FreakStudioCN/mpy-hardware-extension
用户报告 Blockless 扩展在云端实测时出问题（卡死/灰屏/跳步/构建失败），但本地复现不了、日志不在本地文件里时，用这个从云端托管数据库拉真实 session 定位症状与根因 / Use when a user reports an in-product Blockless bug from live cloud-backend testing and the real session…
Review PR
FreakStudioCN/mpy-hardware-extension
A skill your agent uses when reviewing the open pull requests in this repo (mpy-hardware-extension / blockless extension) — "review the PRs", "review PRs with codex", triaging open PRs, gating PRs…
Cloud Test
FreakStudioCN/mpy-hardware-extension
用本地前端插件连云端后端做端到端测试 / test the local VS Code extension against the deployed cloud backend.
Dev Up
FreakStudioCN/mpy-hardware-extension
启动 Blockless 本地开发栈 / bring up the local dev stack. An agent skill from FreakStudioCN/mpy-hardware-extension.
Publish Extension
FreakStudioCN/mpy-hardware-extension
发布 Blockless VS Code 扩展的预检 + MS Marketplace 那一半 / preflight and the MS Marketplace half of shipping the Blockless extension.
Related
Categories
Questions about Publish Extension
What does Publish Extension do?
发布 Blockless VS Code 扩展到 Visual Studio Marketplace（含发布前测试）/ ship the Blockless extension to the VS Code Marketplace. Publish Extension is an agent skill from FreakStudioCN/mpy-hardware-extension. 发布 Blockless VS Code 扩展到 Visual Studio Marketplace（含发布前测试）/ ship the Blockless extension to the VS Code Marketplace.
When should I use Publish Extension?
Publish Extension fits situations like: tasks that involve CI/CD.
How do I install Publish Extension in Claude Code?
Run `npx skills add FreakStudioCN/mpy-hardware-extension --skill publish-extension -a claude-code`. Or copy the skill folder (.agents/skills/publish-extension in FreakStudioCN/mpy-hardware-extension) into .claude/skills/publish-extension in your project. Claude Code loads it when a task matches its description.
How do I install Publish Extension in Codex?
Run `npx skills add FreakStudioCN/mpy-hardware-extension --skill publish-extension -a codex`. Or copy the skill folder (.agents/skills/publish-extension in FreakStudioCN/mpy-hardware-extension) into .agents/skills/publish-extension in your project. Codex loads it when a task matches its description.
Can I use Publish Extension in Cursor, Gemini CLI or GitHub Copilot?
Cursor, Gemini CLI, GitHub Copilot and OpenCode also load SKILL.md folders. With the skills CLI, run `npx skills add FreakStudioCN/mpy-hardware-extension --skill publish-extension -a cursor` (or -a gemini-cli, github-copilot or opencode for the others). To copy it by hand, put the folder in .cursor/skills/publish-extension, .gemini/skills/publish-extension, .github/skills/publish-extension and .opencode/skills/publish-extension in your project.
What does Publish Extension need to run?
Going by SKILL.md and its folder, Publish Extension needs the command-line tools its instructions call (npm, git and npx). Our summary lists: Node.js.
Does Publish Extension access the network?
SKILL.md names 2 domains. In commands or code: blockless.upypi.net and marketplace.visualstudio.com; the agent is likely to contact these when it follows the instructions. This is read from the text; nothing was executed.
Is Publish Extension safe to install?
Our automated static check of SKILL.md found no risky patterns, such as piping downloads into a shell, reading credential files or hidden Unicode. It is not a guarantee. Review the folder before installing.
What licence does Publish Extension use?
Publish Extension has a licence file (the repository's licence) that doesn't match a standard licence. Read it on GitHub before reusing the skill.
How many tokens does Publish Extension use?
About 1.3k tokens (SKILL.md is roughly 5.4k characters). Agents keep only the skill's name and description in context until a task matches; then they load SKILL.md in full.
What are the alternatives to Publish Extension?
Skills that share tags, products or a category with Publish Extension: GitHub Actions Supply Chain Pinning (asyncapi/generator, 1.1k stars), npm Release Via GitHub Actions (jmfederico/pi-web, 871 stars), Release Flow (romankurnovskii/BrewMate, 300 stars) and Tendril Release (Ivy-Interactive/Ivy-Tendril, 202 stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.
Who maintains Publish Extension?
FreakStudioCN (a GitHub organization) maintains it in FreakStudioCN/mpy-hardware-extension, which has 154 GitHub stars. The repository holds 8 skills in this directory. The repository was last updated on September 28, 2026.
Source: FreakStudioCN/mpy-hardware-extension on GitHub. Facts on this page come from the repository at the commit we read; the author's words are quoted as theirs.