agentleFS
Sign inStart free
NeplichNeplich/dev-agent-skills/.agents/skills/maintain-skills/SKILL.md

maintain-skills

Skill8 starsChanged 2 months agoMITView on GitHub

Maintain Skills, plugin registration, discovery metadata, documentation and installation consistency in this repository.

6 other projects use a version of this.

Adopted by

Most recently taken up by

  • Other versions6 projects use a version of this.

    Word for word · 1

    1. Neplich/h-level-model-skills★ 0100% same

    Edited · 0

    None found.

    Wrote their own version · 5

    1. heptameta/heptabase-cli-skills★ 158same name
    2. vic-lsh/agent-skills★ 2same name
    3. christofferbergj/agent-skills★ 1same name
    4. mamachanko/skills★ 1same name
    5. ltatarev/skills★ 0same name

    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.

  • In this repository3 other files it gives its agents.

The file

We split this skill into the rules it gives an agent

5 rules. 0 are common, 5 are distinctive, and 0 are very specific to this project.

  • 0

    Common

    Most of the 5 edited versions we read keep these.

  • 5

    Distinctive

    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:

    Update the repository's professional knowledge library within the user's authorized scope.

    line 8
  2. Distinctive:

    Use the request and current repository evidence to establish the expected result.

    line 10
  3. Distinctive:

    Keep Skill names, paths, references and discovery descriptions consistent.

    line 14
  4. Distinctive:

    Use plans and durable documents when they help readers or future maintenance.

    line 16
  5. Distinctive:

    Run relevant behavior and installation tests.

    line 27

“Common” is measured: kept by at least 6 in 10 of the 5 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

Maintain Skills

Update the repository's professional knowledge library within the user's authorized scope. Select the relevant items from change types and sync surfaces.

Use the request and current repository evidence to establish the expected result. Keep the implementation and verification proportionate to the change. Continue across documentation, metadata and code work using the same task authorization.

Implementation

Keep Skill names, paths, references and discovery descriptions consistent. Update the owning plugin's capability directory when its contents change. Refresh skills-lock.json hashes for modified Skill files, and regenerate packaged shared references from their source.

Use plans and durable documents when they help readers or future maintenance. Record concise final facts and evidence. Preserve unrelated user work and credentials.

Verification and Delivery

uv run scripts/generate_shared_contracts.py --check
uv run scripts/check_repository_contract.py
uv run scripts/check_doc_contract.py
git diff --check

Run relevant behavior and installation tests. Deliver through a PR with the final changes, verification results and material limitations. Use explicit maintainer authorization for merge and publication.

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