agentleFS
Sign inStart free
ZeeshanSultanZeeshanSultan/DocGov/skills/tag/SKILL.md

tag

Skill0 starsChanged 2 months agoMITView on GitHub

Reorganize existing documentation — add missing frontmatter, split oversized documents, extract overgrown README sections, merge duplicates, and archive superseded documents. Use for "clean up the docs", oversized files, duplicate documents, or after onboarding leaves judgement calls.

2 other projects use a version of this.

Adopted by

Most recently taken up by

  • Other versions2 projects use a version of this.

    Word for word · 0

    None found.

    Edited · 0

    None found.

    Wrote their own version · 2

    1. 1756141021/tag-skill★ 20same name
    2. laodao-ai/laodao-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 repository10 other files it gives its agents.

The file

We split this skill into the rules it gives an agent

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

  • ≈0

    Common · estimate

    Many files like this have a rule of this kind.

  • ≈0

    Distinctive · estimate

    This author's own choices. Worth a look.

  • 4

    Very specific

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

  • Common
  • Distinctive
  • Very specific
  • could be automatic: a setting could enforce it
  1. Very specific:

    Create each part with docgov create <type> "<part name>" --domain <d> so it lands in the right place with the right frontmatter.

    line 28
  2. Very specific:

    Add depends_on from each part back to the parent, so the graph keeps the structure.

    line 34
  3. Very specific:

    Run docgov check to confirm no link broke.

    line 35
  4. Very specific:

    Never merge prose silently.

    line 46

≈ “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

Reorganize documentation

State

!docgov tag --json 2>&1 | head -c 8000

Mechanical work first

docgov tag --apply writes missing frontmatter for everything it can classify confidently. Run it, then report how many documents it annotated. Moves stay with docgov fix so that link repair and the move happen in one transaction.

Then the judgement calls, one at a time

Splits

A document flagged for splitting holds several independently addressable concepts. Do it like this, and only this way:

  1. Create each part with docgov create <type> "<part name>" --domain <d> so it lands in the right place with the right frontmatter.
  2. Move the content across verbatim. Rewriting while splitting is how information gets lost; if prose needs improving, that is a separate change.
  3. Turn the parent into an index: a short overview plus a link to each part. Not a stub — an overview that is useful on its own.
  4. Add depends_on from each part back to the parent, so the graph keeps the structure.
  5. Run docgov check to confirm no link broke.

README extraction

A README section that has grown past ~40 lines belongs elsewhere. Move the body to the document class DocGov names, then leave behind a summary of roughly one line per fifteen removed, plus a link. A README answers "what is this, why would I use it, how do I start, where is the depth" — it is not the project encyclopedia.

Merges

Never merge prose silently. Show the user both documents, say which content you would keep, which you would drop, and why. Then merge into the higher-authority path, point supersedes at the retired one, and archive rather than delete it.

Archiving

Superseded documents go to the archive namespace with status: superseded and a supersedes edge from their replacement. The archive is a record: do not edit it afterwards, and DocGov will block attempts to.

Report

End with the docgov health score before and after, and the single change that would raise it most.

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