agentleFS
Sign inStart free
syncwinsyncwin/ai-extender/skills/claude-maintainer/SKILL.md

claude-maintainer

Skill0 starsChanged 39 days agoMITView on GitHub

Updates existing Claude extensions and governs their versions: fix, extend, or refactor a plugin, skill, connector, agent, hook, or MCP server you already have; de-duplicate and shrink token use; bump semver; keep the changelog. Use for "update my agent so it only reads files", "update my skill", "split or merge my skills", "fix this plugin", "clean up", "this failed in production", "bump the version", "add a changelog entry", "migrate", or "customize this Cowork plugin".

The file

We split this skill into the rules it gives an agent

1 rule. About 0 are common, 1 is distinctive, and 0 are very specific to this project.

  • ≈0

    Common · estimate

    Many files like this have a rule of this kind.

  • ≈1

    Distinctive · estimate

    This author's own choices. Worth a look.

  • 0

    Very specific

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

  • Common
  • Distinctive
  • Very specific
  1. Distinctive:

    Not authored here (downloaded/third-party)?

    line 26

≈ “Common” is an estimate: at least 1 in 5 of the 350,495 skill files we read have a rule of the same kind, not the same words. “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

AI Extender Maintainer

  1. Read everything in the target first (all files). Identify type, current version, stable contract.
  2. Flow by target: references/updating.md.
  3. Scope: change only what was asked; confirm larger restructures.
  4. De-duplicate, version, log: references/versioning.md. Same-session iterations stay under the current changelog entry.
    • One summary → changelog entry and every version field: python ${CLAUDE_SKILL_DIR}/scripts/bump_version.py <dir> --summary-file <notes.md> (--level keep adds to the current entry without a bump).
    • What a release keeps, changes, adds, and drops: scripts/release_diff.py <old> <new> (folders or packages).
    • Shared files (scratchpad and others) live once and are copied into each skill: scripts/sync_shared.py <dir> with .claude-plugin/shared-files.json.
  5. Not authored here (downloaded/third-party)? Disclose the fork consequences first (versioning.md).
  6. Re-validate with ai-extender:claude-reviewer, repackage with ai-extender:claude-packager.

Finish with the scratchpad (ai-extender/references/scratchpad.md).

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