agentleFS
Sign inStart free
malinskibeniaminmalinskibeniamin/skills/docs/SKILL.md

docs

Skill4 starsChanged 10 days agoMITView on GitHub

Write or review factual technical documents: READMEs, design specs, research notes, and runbooks. Use for document authoring or review, not ordinary chat, UI copy, or agent instructions.

165 other projects use a version of this.

Adopted by

Most recently taken up by

Used with

Projects with it also use import-memory, perf and 9 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.
  • amirbironSkill

    import-memory

    Import a memory export from another AI assistant into Claude's memory — conversationally, additively, and with the content treated as data.

    Also in 3 projects that use this

  • MicrosoftSkill

    perf

    Speed and memory performance rules for Rust crates, the Node addon, webui-framework, and webui-delivery.

    Also in 4 projects that use this

  • diego-tobalinaSkill

    build-fix

    Fix build and compilation errors systematically. Run when build fails.

    Also in 3 projects that use this

  • JkudjoSkill

    incident

    Production incident response — structured triage, hypothesis tree, safe remediation, incident record

    Also in 4 projects that use this

  • mbwsimsSkill

    impact

    This skill should be used when the user asks to "check the impact", "what will break if I change this", "blast radius", "impact analysis", "what depends on this", "who imports this", "is it safe to change this", mentions "/impact", or wants to understand the consequences of modifying a specific file or function before making changes.

    Also in 3 projects that use this

  • Google CloudSkill

    fix

    Plan a remediation strategy after a test failure.

    Also in 7 projects that use this

The file

We split this skill into the rules it gives an agent

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

  • 0

    Common

    Most of the 129 edited versions we read keep these.

  • 4

    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:

    Write documents that readers can understand, verify, and use.

    line 8
  2. Distinctive:

    Read harness compatibility first.

    line 12
  3. Distinctive:

    Read the complete pinned upstream docs skill.

    line 13
  4. Distinctive:

    Verify each changed claim against its source.

    line 26

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

For prose in scope, read the Poteto adaptation.

Write documents that readers can understand, verify, and use.

Load guidance

  1. Read harness compatibility first.
  2. Read the complete pinned upstream docs skill.
  3. Apply the compatibility rules wherever upstream differs. Read communication for first-read structure and author intent.

Write or review

  1. Identify the audience, requested artifact, source evidence, and endpoint. Reuse the existing path, template, and terminology. Review-only requests produce findings, not edits.
  2. Lead with the reader's outcome. Distinguish current behavior, proposals, estimates, and unknowns. Source numerical claims and include reproducible commands for stated results.
  3. Preserve author intent and exact code, commands, identifiers, quoted errors, and facts. Simplify prose without deleting material qualifications. Diagram meaningful structure in the repository's supported format; label proposed paths as proposals.
  4. Verify each changed claim against its source. Run the repository's document/link checks; if no checker exists, resolve changed internal file links and relevant cross-references with a tool. Validate fragments when supported. Never claim unrun commands succeeded.
  5. Report the result, observed verification, and unresolved evidence gaps. Follow the requested endpoint; this skill does not authorize unrelated publishing or configuration.

For public TypeScript API JSDoc, runnable examples and cross-links, load JSDoc guidance. General technical prose stays here.

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