agentleFS
Sign inStart free
EllAchEEllAchE/skill-observability/skills/update-skill/SKILL.md

update-skill

Skill0 starsChanged 3 months agoMITView on GitHub

Revise an existing agent skill while preserving its ownership boundary, invocation intent, progressive disclosure, safety gates, and reusable resources. Use when the user asks to improve, modernize, tighten, rename, or codify new guidance in an existing skill.

12 other projects use a version of this.

Adopted by

Most recently taken up by

Used with

Projects with it also use diagnose-ci-failures, write-product-spec and 7 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

The file

We split this skill into the rules it gives an agent

8 rules. 0 are common, 7 are distinctive, and 1 is very specific to this project.

  • 0

    Common

    Most of the 11 edited versions we read keep these.

  • 7

    Distinctive

    This author's own choices. Worth a look.

  • 1

    Very specific

    Tied to their project's names, files or tools. Probably skip.

  • Common
  • Distinctive
  • Very specific
  1. Very specific:

    Read the entire SKILL.md and only the directly relevant bundled resources.

    line 14
  2. Distinctive:

    Read the source artifact for the requested change: user correction, memory, issue, trace, failure, documentation, or duplicated skill text.

    line 18
  3. Distinctive:

    Keep mechanics in the skill that performs the work.

    line 20
  4. Distinctive:

    Keep metadata triggers precise.

    line 24
  5. Distinctive:

    Test changed scripts and realistic failure paths.

    line 28
  6. Distinctive:

    Run the target repository's skill validator and check the edited skill for structural errors and broken relative links.

    line 29
  7. Distinctive:

    Treat an already-codified request as a valid no-op.

    line 33
  8. Distinctive:

    Follow the repository's review and delivery conventions.

    line 35

“Common” is measured: kept by at least 6 in 10 of the 11 edited versions of this file we could read. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.

Keep what fits and drop the rest. Your version, ready for your agents.
Files
SKILL.md

Update Skill

Preconditions

  1. Resolve the exact target and confirm its SKILL.md exists. Route missing targets through create-skill.
  2. Confirm the new information changes how the repeatable workflow triggers, decides, executes, validates, or stops. Keep one-off status outside the skill.
  3. Read the entire SKILL.md and only the directly relevant bundled resources.

Workflow

  1. Read the source artifact for the requested change: user correction, memory, issue, trace, failure, documentation, or duplicated skill text.
  2. Keep mechanics in the skill that performs the work. Other skills get a short routing pointer rather than a copied procedure.
  3. Edit narrowly. Preserve correct instructions and remove contradictions, obsolete branches, redundant prose, and unused resources.
  4. Keep metadata triggers precise. If the skill name changes, search callers, hooks, docs, configuration, and transcripts for the old name.
  5. Maintain progressive disclosure: core decisions in SKILL.md, optional detail in one-level-deep references, deterministic repeated work in scripts.
  6. Test changed scripts and realistic failure paths.
  7. Run the target repository's skill validator and check the edited skill for structural errors and broken relative links.
  8. Forward-test behavior-changing revisions when safe, using a raw representative task without leaking the desired result.
  9. Treat an already-codified request as a valid no-op. Cite the existing section rather than churning prose.
  10. Follow the repository's review and delivery conventions.

A rename is incomplete while any model-facing caller or hook still uses the old name.

Download now (ZIP)

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.

Check your setup, free