[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M7A6569CYMBEBPHW8RMXX684":3,"skill-same:01M7A6569CYMBEBPHW8RMXX684":73},{"skillNo":4,"name":5,"nameZh":6,"description":7,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":16,"categories":17,"keywords":18,"publishedAt":19,"linkOnly":20,"markdownContent":21,"markdownBody":22,"frontMatter":23,"refName":24,"commitSha":25,"skillDirectory":26,"forksCount":27,"repositoryHtmlUrl":28,"repositoryHomepageUrl":6,"ownerHtmlUrl":29,"ownerBlogUrl":6,"ownerDescription":6,"updatedAt":30,"install":31,"resources":44},"01M7A6569CYMBEBPHW8RMXX684","skill-publisher",null,"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.","siuserxiaowei\u002Fxiaowei-ai-tools","siuserxiaowei","https:\u002F\u002Favatars.githubusercontent.com\u002Fu\u002F226641659?v=4","01M7A3SYZKS0MVRZZJQC10XSYM","siuser小伟","01M7A3SZ0735VJJQ0479SNF44J",1,"MIT","https:\u002F\u002Fgithub.com\u002Fsiuserxiaowei\u002Fxiaowei-ai-tools\u002Fblob\u002Fmain\u002Fskills\u002Fskill-publisher\u002FSKILL.md",[],[],"2026-11-15 14:19:17",false,"---\nname: skill-publisher\ndescription: 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.\n---\n\n# Skill Publisher\n\n## 案例入口\n\n先读 [references\u002Fexamples.md](references\u002Fexamples.md)：其中给出正向案例、边界案例、失败恢复和可观察的验收证据；再按下文流程执行。\n\nPublish a reviewable repository state, not an inferred collection of local files.\n\n## 1. Resolve the Release Object\n\nInspect the source before changing local or remote state:\n\n- find the repository root and all Skill entrypoints that the chosen publish command will discover;\n- distinguish the Skill name, local directory, repository name, and release tag;\n- inspect the current branch, origin, staged and unstaged changes, and repository visibility;\n- identify the exact commit or exact files intended for the release;\n- preserve existing licenses, notices, copyright, and provenance.\n\nIf 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.\n\n## 2. Establish Authority\n\nPublishing is an external write. Before the first create, push, visibility change, topic change, or release action, resolve:\n\n- exact `OWNER\u002FREPO`;\n- public, private, or internal visibility;\n- whether this is a new repository or an update;\n- the files\u002Fcommit and branch to publish;\n- license choice and required attribution;\n- release tag, if a GitHub release will be created.\n\nA 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.\n\nNever 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.\n\n## 3. Run Read-Only Preflight\n\nRun the bundled checker from this Skill directory:\n\n```bash\npython3 scripts\u002Fpreflight.py \u002Fabsolute\u002Fpath\u002Fto\u002Frepository --visibility public --target OWNER\u002FREPO\n```\n\nThe checker does not execute candidate scripts, stage files, create licenses, initialize Git, or contact GitHub. Use `--format json` for a machine-readable manifest.\n\nThen use the current official validator when available:\n\n```bash\ngh skill publish \u002Fabsolute\u002Fpath\u002Fto\u002Frepository --dry-run\n```\n\n`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\u002Fpublishing-playbook.md](references\u002Fpublishing-playbook.md) for fallback and release details.\n\nDo not publish while any of these remain unresolved:\n\n- secrets, private keys, environment files, or private user paths in the release set;\n- invalid Skill metadata or a Skill name\u002Fdirectory mismatch;\n- symlinks or archives whose target\u002Fcontent was not reviewed;\n- unknown public-license status or missing third-party attribution;\n- unrelated staged changes, an unexpected remote, or an ambiguous repository boundary;\n- placeholders or claims in public documentation that were not verified.\n\n## 4. Publish the Reviewed State\n\nUse the least surprising official operation for the resolved repository state:\n\n- create a repository only after the owner and visibility are explicit;\n- stage exact paths rather than `git add .` in a dirty worktree;\n- do not rewrite history, bypass branch protection, bypass secret protection, force-push, or change visibility unless separately authorized;\n- do not create a generic commit if the user did not ask you to commit;\n- prefer `gh skill publish` for validation and a versioned Skill release when supported;\n- if the preview command is unavailable, explain the fallback and keep repository creation, push, release creation, and installation verification as distinct observable steps.\n\nREADME 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.\n\n## 5. Verify the Remote Result\n\nRead back authoritative remote state after each external mutation:\n\n1. confirm the repository URL, visibility, default branch, and pushed commit;\n2. confirm the release tag and assets if a release was requested;\n3. preview the discovered Skill and file tree;\n4. install the intended Skill\u002Fversion into an isolated temporary directory using a supported client;\n5. verify the installed `SKILL.md` name and important file hashes against the reviewed release;\n6. report the exact install command, verified commit\u002Ftag, and any client-specific limitation.\n\nDo not copy the published Skill over a user's personal Skill directory as a side effect. Installation or local synchronization is a separate action.\n\nRead [references\u002Fresearch-basis.md](references\u002Fresearch-basis.md) when updating assumptions about the Agent Skills specification, GitHub CLI, security checks, or licensing.\n","# Skill Publisher\n\n## 案例入口\n\n先读 [references\u002Fexamples.md](references\u002Fexamples.md)：其中给出正向案例、边界案例、失败恢复和可观察的验收证据；再按下文流程执行。\n\nPublish a reviewable repository state, not an inferred collection of local files.\n\n## 1. Resolve the Release Object\n\nInspect the source before changing local or remote state:\n\n- find the repository root and all Skill entrypoints that the chosen publish command will discover;\n- distinguish the Skill name, local directory, repository name, and release tag;\n- inspect the current branch, origin, staged and unstaged changes, and repository visibility;\n- identify the exact commit or exact files intended for the release;\n- preserve existing licenses, notices, copyright, and provenance.\n\nIf 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.\n\n## 2. Establish Authority\n\nPublishing is an external write. Before the first create, push, visibility change, topic change, or release action, resolve:\n\n- exact `OWNER\u002FREPO`;\n- public, private, or internal visibility;\n- whether this is a new repository or an update;\n- the files\u002Fcommit and branch to publish;\n- license choice and required attribution;\n- release tag, if a GitHub release will be created.\n\nA 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.\n\nNever 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.\n\n## 3. Run Read-Only Preflight\n\nRun the bundled checker from this Skill directory:\n\n```bash\npython3 scripts\u002Fpreflight.py \u002Fabsolute\u002Fpath\u002Fto\u002Frepository --visibility public --target OWNER\u002FREPO\n```\n\nThe checker does not execute candidate scripts, stage files, create licenses, initialize Git, or contact GitHub. Use `--format json` for a machine-readable manifest.\n\nThen use the current official validator when available:\n\n```bash\ngh skill publish \u002Fabsolute\u002Fpath\u002Fto\u002Frepository --dry-run\n```\n\n`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\u002Fpublishing-playbook.md](references\u002Fpublishing-playbook.md) for fallback and release details.\n\nDo not publish while any of these remain unresolved:\n\n- secrets, private keys, environment files, or private user paths in the release set;\n- invalid Skill metadata or a Skill name\u002Fdirectory mismatch;\n- symlinks or archives whose target\u002Fcontent was not reviewed;\n- unknown public-license status or missing third-party attribution;\n- unrelated staged changes, an unexpected remote, or an ambiguous repository boundary;\n- placeholders or claims in public documentation that were not verified.\n\n## 4. Publish the Reviewed State\n\nUse the least surprising official operation for the resolved repository state:\n\n- create a repository only after the owner and visibility are explicit;\n- stage exact paths rather than `git add .` in a dirty worktree;\n- do not rewrite history, bypass branch protection, bypass secret protection, force-push, or change visibility unless separately authorized;\n- do not create a generic commit if the user did not ask you to commit;\n- prefer `gh skill publish` for validation and a versioned Skill release when supported;\n- if the preview command is unavailable, explain the fallback and keep repository creation, push, release creation, and installation verification as distinct observable steps.\n\nREADME 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.\n\n## 5. Verify the Remote Result\n\nRead back authoritative remote state after each external mutation:\n\n1. confirm the repository URL, visibility, default branch, and pushed commit;\n2. confirm the release tag and assets if a release was requested;\n3. preview the discovered Skill and file tree;\n4. install the intended Skill\u002Fversion into an isolated temporary directory using a supported client;\n5. verify the installed `SKILL.md` name and important file hashes against the reviewed release;\n6. report the exact install command, verified commit\u002Ftag, and any client-specific limitation.\n\nDo not copy the published Skill over a user's personal Skill directory as a side effect. Installation or local synchronization is a separate action.\n\nRead [references\u002Fresearch-basis.md](references\u002Fresearch-basis.md) when updating assumptions about the Agent Skills specification, GitHub CLI, security checks, or licensing.\n",{"name":5,"description":7},"main","ebb257363024c428d3c797cb705194b35d00cb0f","skills\u002Fskill-publisher",0,"https:\u002F\u002Fgithub.com\u002Fsiuserxiaowei\u002Fxiaowei-ai-tools","https:\u002F\u002Fgithub.com\u002Fsiuserxiaowei","2026-11-03 21:39:44",{"source":8,"skillName":5,"commands":32,"prompt":42,"zipAvailable":43},[33,36,39],{"tool":34,"command":35},"npx","npx skills add siuserxiaowei\u002Fxiaowei-ai-tools --skill skill-publisher",{"tool":37,"command":38},"bunx","bunx skills add siuserxiaowei\u002Fxiaowei-ai-tools --skill skill-publisher",{"tool":40,"command":41},"pnpm","pnpm dlx skills add siuserxiaowei\u002Fxiaowei-ai-tools --skill skill-publisher","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002Fsiuserxiaowei\u002Fxiaowei-ai-tools\u002Fblob\u002Fmain\u002Fskills\u002Fskill-publisher\u002FSKILL.md",true,[45,51,55,59,63,69],{"path":46,"resourceType":47,"resourceTypeDesc":48,"sizeBytes":49,"sourceHtmlUrl":50},"agents\u002Fopenai.yaml","REFERENCE","参考文档",277,"https:\u002F\u002Fgithub.com\u002Fsiuserxiaowei\u002Fxiaowei-ai-tools\u002Fblob\u002Fmain\u002Fskills\u002Fskill-publisher\u002Fagents\u002Fopenai.yaml",{"path":52,"resourceType":47,"resourceTypeDesc":48,"sizeBytes":53,"sourceHtmlUrl":54},"references\u002Fexamples.md",3597,"https:\u002F\u002Fgithub.com\u002Fsiuserxiaowei\u002Fxiaowei-ai-tools\u002Fblob\u002Fmain\u002Fskills\u002Fskill-publisher\u002Freferences\u002Fexamples.md",{"path":56,"resourceType":47,"resourceTypeDesc":48,"sizeBytes":57,"sourceHtmlUrl":58},"references\u002Fpublishing-playbook.md",4259,"https:\u002F\u002Fgithub.com\u002Fsiuserxiaowei\u002Fxiaowei-ai-tools\u002Fblob\u002Fmain\u002Fskills\u002Fskill-publisher\u002Freferences\u002Fpublishing-playbook.md",{"path":60,"resourceType":47,"resourceTypeDesc":48,"sizeBytes":61,"sourceHtmlUrl":62},"references\u002Fresearch-basis.md",3092,"https:\u002F\u002Fgithub.com\u002Fsiuserxiaowei\u002Fxiaowei-ai-tools\u002Fblob\u002Fmain\u002Fskills\u002Fskill-publisher\u002Freferences\u002Fresearch-basis.md",{"path":64,"resourceType":65,"resourceTypeDesc":66,"sizeBytes":67,"sourceHtmlUrl":68},"scripts\u002Fpreflight.py","SCRIPT","脚本",18215,"https:\u002F\u002Fgithub.com\u002Fsiuserxiaowei\u002Fxiaowei-ai-tools\u002Fblob\u002Fmain\u002Fskills\u002Fskill-publisher\u002Fscripts\u002Fpreflight.py",{"path":70,"resourceType":65,"resourceTypeDesc":66,"sizeBytes":71,"sourceHtmlUrl":72},"tests\u002Ftest_preflight.py",4570,"https:\u002F\u002Fgithub.com\u002Fsiuserxiaowei\u002Fxiaowei-ai-tools\u002Fblob\u002Fmain\u002Fskills\u002Fskill-publisher\u002Ftests\u002Ftest_preflight.py",[74,81,88,95,102,109],{"skillNo":75,"name":76,"nameZh":6,"description":77,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":78,"categories":79,"keywords":80,"publishedAt":19},"01M7A66TQCYTAPVGB01H6593P0","x-article-draft-uploader","把本地 Markdown 转为经核验的 X Articles 新草稿。适用于需要保留首图封面、正文图片相对位置，并在独立 Playwright 会话中复用用户已授权 Chrome 登录态的任务；不负责公开发布。","https:\u002F\u002Fgithub.com\u002Fsiuserxiaowei\u002Fxiaowei-ai-tools\u002Fblob\u002Fmain\u002Fskills\u002Fx-article-draft-uploader\u002FSKILL.md",[],[],{"skillNo":82,"name":83,"nameZh":6,"description":84,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":85,"categories":86,"keywords":87,"publishedAt":19},"01M7A66R643K97EQHY5AFBBVQ6","wecom-operations","通过用户已配置的官方 wecom-cli 管理企业微信文档、智能文档、待办、会议和日程。适合创建或查询这些云端对象、把本地 Markdown 转为智能文档，以及在明确确认后更新或取消对象；不发送消息、不控制桌面客户端。","https:\u002F\u002Fgithub.com\u002Fsiuserxiaowei\u002Fxiaowei-ai-tools\u002Fblob\u002Fmain\u002Fskills\u002Fwecom-operations\u002FSKILL.md",[],[],{"skillNo":89,"name":90,"nameZh":6,"description":91,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":92,"categories":93,"keywords":94,"publishedAt":19},"01M7A66M3AXR54FQB7B4TX5VN9","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 企业微信\u002FWeCom local data, recover a private database snapshot, inspect local contacts or sessions, search chat history, or export a bounded conversation.","https:\u002F\u002Fgithub.com\u002Fsiuserxiaowei\u002Fxiaowei-ai-tools\u002Fblob\u002Fmain\u002Fskills\u002Fwecom-local-vault\u002FSKILL.md",[],[],{"skillNo":96,"name":97,"nameZh":6,"description":98,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":99,"categories":100,"keywords":101,"publishedAt":19},"01M7A6649YFS2SQ8SKFSTBRN2Z","wechat-reading","Read and analyze WeRead\u002F微信读书 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.","https:\u002F\u002Fgithub.com\u002Fsiuserxiaowei\u002Fxiaowei-ai-tools\u002Fblob\u002Fmain\u002Fskills\u002Fwechat-reading\u002FSKILL.md",[],[],{"skillNo":103,"name":104,"nameZh":6,"description":105,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":106,"categories":107,"keywords":108,"publishedAt":19},"01M7A65QZNA4FBYV32WH9S97QG","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\u002Fcomments workflows. Do not use for a one-page summary or to automate the WeChat client.","https:\u002F\u002Fgithub.com\u002Fsiuserxiaowei\u002Fxiaowei-ai-tools\u002Fblob\u002Fmain\u002Fskills\u002Fwechat-mp-batch-exporter\u002FSKILL.md",[],[],{"skillNo":110,"name":111,"nameZh":6,"description":112,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":113,"categories":114,"keywords":115,"publishedAt":19},"01M7A65NP84R1JFFZEPVZT065P","wechat-local-vault","在 macOS 本机建立并查询私有微信数据快照。适用于盘点数据库、离线校验已有密钥候选、创建全量或增量明文快照、查会话与联系人、按时间检索消息、导出指定聊天、查看朋友圈或收藏，以及准备群聊摘要素材。所有查询只读，默认隐藏内部账号标识，不操控微信界面，也不发送任何内容。","https:\u002F\u002Fgithub.com\u002Fsiuserxiaowei\u002Fxiaowei-ai-tools\u002Fblob\u002Fmain\u002Fskills\u002Fwechat-local-vault\u002FSKILL.md",[],[]]