skill-publisher
Prepare, validate, publish, or update Agent Skills in a GitHub repository with explicit target, visibility, license, attribution, commit, and release boundaries. Use when the user asks to publish or share a Skill, create its GitHub repository, cut a Skill release, or verify that a published Skill can be discovered and installed.
- License 许可
- MIT
- 最近更新
- 2026-11-03
- Stars
- ★ 1
- Forks
- 0
01 前言 Front Matter
- name
- skill-publisher
- description
- Prepare, validate, publish, or update Agent Skills in a GitHub repository with explicit target, visibility, license, attribution, commit, and release boundaries. Use when the user asks to publish or share a Skill, create its GitHub repository, cut a Skill release, or verify that a published Skill can be discovered and installed.
02 资源文件 6
- 参考文档agents/openai.yaml277 B
- 参考文档references/examples.md3.5 KB
- 参考文档references/publishing-playbook.md4.2 KB
- 参考文档references/research-basis.md3.0 KB
- 脚本scripts/preflight.py17.8 KB
- 脚本tests/test_preflight.py4.5 KB
03 SKILL.md 正文
Skill Publisher
案例入口
先读 references/examples.md:其中给出正向案例、边界案例、失败恢复和可观察的验收证据;再按下文流程执行。
Publish a reviewable repository state, not an inferred collection of local files.
1. Resolve the Release Object
Inspect the source before changing local or remote state:
- find the repository root and all Skill entrypoints that the chosen publish command will discover;
- distinguish the Skill name, local directory, repository name, and release tag;
- inspect the current branch, origin, staged and unstaged changes, and repository visibility;
- identify the exact commit or exact files intended for the release;
- preserve existing licenses, notices, copyright, and provenance.
If the source sits inside a larger repository, do not pretend the subdirectory can be pushed independently. Decide whether the user wants the whole repository published or a separately prepared repository.
2. Establish Authority
Publishing is an external write. Before the first create, push, visibility change, topic change, or release action, resolve:
- exact
OWNER/REPO; - public, private, or internal visibility;
- whether this is a new repository or an update;
- the files/commit and branch to publish;
- license choice and required attribution;
- release tag, if a GitHub release will be created.
A direct request to publish can authorize the resolved operation, but it does not answer missing high-impact choices. Ask when target, audience, license, ownership, or included changes remain materially ambiguous.
Never add MIT or any other license on the user's behalf. Without a license, default copyright applies; public visibility is not an open-source license.
3. Run Read-Only Preflight
Run the bundled checker from this Skill directory:
python3 scripts/preflight.py /absolute/path/to/repository --visibility public --target OWNER/REPO
The checker does not execute candidate scripts, stage files, create licenses, initialize Git, or contact GitHub. Use --format json for a machine-readable manifest.
Then use the current official validator when available:
gh skill publish /absolute/path/to/repository --dry-run
gh skill requires GitHub CLI 2.90.0 or later as of the research date and remains a preview feature. Detect support with gh skill --help; do not assume it exists and do not upgrade tools without authorization. Read references/publishing-playbook.md for fallback and release details.
Do not publish while any of these remain unresolved:
- secrets, private keys, environment files, or private user paths in the release set;
- invalid Skill metadata or a Skill name/directory mismatch;
- symlinks or archives whose target/content was not reviewed;
- unknown public-license status or missing third-party attribution;
- unrelated staged changes, an unexpected remote, or an ambiguous repository boundary;
- placeholders or claims in public documentation that were not verified.
4. Publish the Reviewed State
Use the least surprising official operation for the resolved repository state:
- create a repository only after the owner and visibility are explicit;
- stage exact paths rather than
git add .in a dirty worktree; - do not rewrite history, bypass branch protection, bypass secret protection, force-push, or change visibility unless separately authorized;
- do not create a generic commit if the user did not ask you to commit;
- prefer
gh skill publishfor validation and a versioned Skill release when supported; - if the preview command is unavailable, explain the fallback and keep repository creation, push, release creation, and installation verification as distinct observable steps.
README content should help the intended audience evaluate and install the Skill, but screenshots, badges, bilingual duplication, Star History, and marketing copy are optional—not universal gates. Never fabricate adoption metrics, compatibility, screenshots, or security claims.
5. Verify the Remote Result
Read back authoritative remote state after each external mutation:
- confirm the repository URL, visibility, default branch, and pushed commit;
- confirm the release tag and assets if a release was requested;
- preview the discovered Skill and file tree;
- install the intended Skill/version into an isolated temporary directory using a supported client;
- verify the installed
SKILL.mdname and important file hashes against the reviewed release; - report the exact install command, verified commit/tag, and any client-specific limitation.
Do not copy the published Skill over a user's personal Skill directory as a side effect. Installation or local synchronization is a separate action.
Read references/research-basis.md when updating assumptions about the Agent Skills specification, GitHub CLI, security checks, or licensing.
04 同仓库更多 Skills
x-article-draft-uploader
把本地 Markdown 转为经核验的 X Articles 新草稿。适用于需要保留首图封面、正文图片相对位置,并在独立 Playwright 会话中复用用户已授权 Chrome 登录态的任务;不负责公开发布。
wecom-operations
通过用户已配置的官方 wecom-cli 管理企业微信文档、智能文档、待办、会议和日程。适合创建或查询这些云端对象、把本地 Markdown 转为智能文档,以及在明确确认后更新或取消对象;不发送消息、不控制桌面客户端。
wecom-local-vault
Inspect authorized local WeCom databases on macOS, create private plaintext snapshots, and query or export contacts, conversations, and messages without modifying the source account store. Use when the user asks to parse 企业微信/WeCom local data, recover a private database snapshot, inspect local contacts or sessions, search chat history, or export a bounded conversation.
wechat-reading
Read and analyze WeRead/微信读书 search results, book metadata, bookshelf entries, progress, notes, highlights, public reviews, recommendations, and reading statistics through the official read-only Agent Gateway. Use for WeRead account questions or exports; do not imply that the current Gateway can add, remove, upload, rate, like, or edit content.
wechat-mp-batch-exporter
Build a bounded, private archive from known WeChat Official Account article URLs or an owner-authorized account-history export, with explicit reconciliation of article, publish-group, and platform-marked-original counts. Use for batch body capture, history normalization, or enhanced metrics/comments workflows. Do not use for a one-page summary or to automate the WeChat client.
wechat-local-vault
在 macOS 本机建立并查询私有微信数据快照。适用于盘点数据库、离线校验已有密钥候选、创建全量或增量明文快照、查会话与联系人、按时间检索消息、导出指定聊天、查看朋友圈或收藏,以及准备群聊摘要素材。所有查询只读,默认隐藏内部账号标识,不操控微信界面,也不发送任何内容。