agentleFS
busybutlazybusybutlazy/skill-forge/.claude/skills/update-skill/SKILL.md

update-skill

Skill1 starsChanged 7 months agoMITView on GitHub

Canonical skill maintenance specialist for this repository. Use when a maintainer needs to revise an existing public canonical skill package.

Files
SKILL.md

Update Public Skill

用來修改 canonical-skills/regular-skills/ 中既有的公開 skill。

Use This For

  • 更新 skill workflow
  • 調整 trigger description
  • 修正 canonical package metadata
  • 升級 skill 版本
  • 視需要調整 shared tag,控制 manager install flow 是否應納入某個 regular skill

Do Not Use This For

  • 修改 .agents/skills/ 的管理者技能
  • 安裝或移除其他專案的 skills
  • 建立全新的 skill
  • 把 skill 同步到本 repo 的 .agents/ 或 .claude/

Workflow

1. Inspect the current skill

先讀:

  • canonical-skills/regular-skills/<skill-name>/instruction.md
  • canonical-skills/regular-skills/<skill-name>/package.json
  • canonical-skills/regular-skills/<skill-name>/manifest.json
  • canonical-skills/regular-skills/<skill-name>/targets/
  • 必要時對照 docs/reference/canonical-package-spec.md 與 docs/reference/adapter-contract.md

搞清楚:

  • 現在的行為是什麼
  • 哪些部分要改
  • 變更是否屬於 patch / minor / major 等級

2. Revise the skill

更新必要內容:

  • 觸發描述
  • 不適用情境
  • 流程步驟
  • 限制與輸出要求
  • target-specific frontmatter
  • 受管 asset 目錄中的引用與路徑

只改真正需要改的部分,避免把 skill 改成另一個任務。

shared instruction.md 不應混入 target-specific frontmatter、Claude tools、安裝路徑或 maintainer-only 流程。

3. Update metadata

同步調整:

  • package.json.identity.version
  • package.json.identity.updated_at
  • 必要時調整 package.json.identity.description、package.json.identity.tags
  • manifest.json
  • package.json.integrity.package_sha256

版本規則:

  • 小修正:patch
  • 新增能力或顯著流程調整:minor
  • 不相容重寫或定位改變:major

如果修改了 render-driving content,必須同步更新:

  • manifest.json.files[*].sha256
  • manifest.json.package_sha256
  • package.json.integrity.package_sha256

4. Validate publishability

確認:

  • skill 仍屬於公開可分發內容
  • 目錄名稱、identity.name、target override name 一致
  • package metadata 與 target override 沒有互相矛盾
  • 說明不依賴舊工具或已淘汰目錄
  • distribution.scope 仍符合預期
  • content.instruction_file 仍為 instruction.md
  • Codex install path 仍為 .agents/skills/{name}/
  • Claude install path 仍為 .claude/skills/{name}/

更新完 canonical source 後,下一步應提醒使用者執行 finalize-skill。

建議互動收尾:

  • 問使用者是否現在就要 finalize 這個 skill
  • 若使用者回答 yes,立即切換到 finalize-skill
  • 若使用者回答 no,明確提醒之後要執行 finalize-skill <skill-name>

如果只是要把 canonical 狀態同步到本 repo 的 agent 目錄,不用這個 skill,改用 install-manager-skill。

5. Check manager impact

如果這次修改會影響 render / install 流程,記得一起檢查:

  • Python CLI
  • README.md
  • target render output 與狀態顯示是否仍合理

若變更牽涉 canonical 結構、hash、renderer 或 installer 契約,再補做:

  • phase 3 test suite
  • 用暫時目錄 smoke-test Codex install
  • 用暫時目錄 smoke-test Claude install

Download now (ZIP)

  • Other versions11 projects use a version of this.

    Word for word · 0

    None found.

    Edited · 0

    None found.

    Wrote their own version · 11

    1. zerx-lab/warp★ 2.1ksame name
    2. zerx-lab/zap★ 2.1ksame name
    3. warpdotdev/common-skills★ 630same name
    4. tenequm/skills★ 38same name
    5. xjsongphy/skills★ 7same name
    6. openmodelingfoundation/skills★ 4same name
    7. magnusrodseth/dotfiles★ 2same name
    8. phucbm/skills★ 2same name
    9. zhouycheng/skills★ 1same name
    10. EllAchE/skill-observability★ 0same name

    1 more not listed

    How matches are found. Word for word: the exact same text. Edited: shares passages with this file (“99% same” means 99% of its five-word phrases also appear here; 10% or more counts). Their own version: similar meaning, or, weakest, the same name. We can’t tell which project had it first. Projects are counted among the 200 most-starred candidates, and mentions are links to the repository we found, up to 50 per site, so both counts are a floor.

  • Used alongsideProjects with it also use diagnose-ci-failures, write-product-spec and 6 more.

    Other files people use alongside this one.

    Files found in the same public projects as a version of this one, more often than they turn up anywhere else. Each project counts once, large collections count for less, and this file's own repository is left out.
    • zerx-labSkill

      diagnose-ci-failures

      Diagnose CI failures for a PR using the GitHub CLI, extract error logs, and generate a plan to fix them. Use when the user asks to check CI status, pull CI issues, triage test failures, or investigate PR build failures.

      Also in 3 projects that use this

    • zerx-labSkill

      write-product-spec

      Write a PRODUCT.md spec for a significant user-facing feature in Zap, focused on detailed behavior and validation. Use when the user asks for a product spec, desired behavior doc, or PRD, wants to define feature behavior before implementation, or when the feature is substantial or behaviorally ambiguous enough that a written spec would improve implementation or review.

      Also in 3 projects that use this

    • charlesmatteSkill

      write-tech-spec

      Generate a technical specification document from an existing PRD through relentless technical interview and codebase exploration. Use when user wants to write a tech spec, technical specification, technical design document, TDD (technical design doc), or go deeper on the technical details of a PRD.

      Also in 3 projects that use this

    • GitHubSkill

      resolve-merge-conflicts

      Merge a base ref and safely regenerate compiled workflow lock-file conflicts.

      Also in 3 projects that use this

    • gitpod-ioSkill

      fix-errors

      Guidelines for fixing unhandled errors from the VS Code error telemetry dashboard. Use when investigating error-telemetry issues with stack traces, error messages, and hit/user counts. Covers tracing data flow through call stacks, identifying producers of invalid data vs. consumers that crash, enriching error messages for telemetry diagnosis, and avoiding common anti-patterns like silently swallowing errors.

      Also in 3 projects that use this

    • DockerSkill

      review-pr

      Review one or more incoming Docker documentation pull requests as a maintainer. Independently validate technical claims, assess editorial fit and information architecture, choose a verdict, and draft exact inline or PR-wide feedback behind a confirmation gate. Use for requests such as "review PR 123", "is this PR correct?", "does this information belong here?", "validate this PR", or "help review backlog PRs". Do not use to maintain or fix a PR you own; use maintain-pr for that.

      Also in 4 projects that use this

    • +2 more from zerx-lab
  • In this repository18 other files it gives its agents.

Does it work?

Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.

No reviews yet

People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.

  • It worked
  • Partly
  • It didn't
What did you use it for? e.g. Reviewing pull requests in a Rails app

Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.

Your trail

Files you open will collect here, so you can find them again.

Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.

Now do this for your own.

Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.