agentleFS
Sign inStart free
saffron-healthsaffron-health/opencode-gui/.agents/skills/update-docs/SKILL.md

update-docs

Skill59 starsChanged 9 months agoMITView on GitHub

Update AGENTS.md files based on session learnings about a topic. Use when documenting patterns, commands, or conventions discovered during development.

We split this skill into the rules it gives an agent

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

  • 0

    Common

    Most of the 77 edited versions we read keep these.

  • 4

    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. Distinctive:

    Update AGENTS.md files based on what was learned in this session about: $TOPIC

    line 6
  2. Very specific:

    Read docs/updating-agents-docs.md for full guidelines before proceeding.

    line 8
  3. Distinctive:

    Check if the target AGENTS.md already has related content:

    line 23
  4. Distinctive:

    If multiple related items exist, consider extracting to a docs/ page

    line 24
  5. Distinctive:

    If adding would make the file too long (>60 lines for root), extract to docs/

    line 25

“Common” is measured: kept by at least 6 in 10 of the 77 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 AGENTS.md files based on what was learned in this session about: $TOPIC

Read docs/updating-agents-docs.md for full guidelines before proceeding.

Process

  1. Review the conversation for learnings about the specified topic:
    • Patterns or conventions discovered
    • Commands needed but not documented
    • Architectural insights
    • Common pitfalls encountered
  2. Determine where each learning belongs (lowest common ancestor):
    • Root AGENTS.md for repo-wide patterns
    • Package-level AGENTS.md for package-specific patterns
    • docs/*.md for detailed explanations
  3. Check if the target AGENTS.md already has related content:
    • If multiple related items exist, consider extracting to a docs/ page
    • If adding would make the file too long (>60 lines for root), extract to docs/
  4. Apply changes following the writing style in the guidelines
  5. List what was updated and why

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.

Reviews can't be read right now.

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