agentleFS
Sign inStart free
berntpoppberntpopp/stringdb-link/.claude/skills/fleet-standard-adoption/SKILL.md

fleet-standard-adoption

Skill1 starsChanged 4 months agoMITView on GitHub

Use when bringing this repo into compliance with a GeneFoundry fleet standard (tool-naming, response-envelope, container-hardening, versioning, MCP transport, or logging) or closing its tracking issue.

We split this skill into the rules it gives an agent

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

  • ≈0

    Common · estimate

    Many files like this have a rule of this kind.

  • ≈2

    Distinctive · estimate

    This author's own choices. Worth a look.

  • 2

    Very specific

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

  • Common
  • Distinctive
  • Very specific
  1. Very specific:

    Follow AGENTS.md first. The canonical standards live under ../genefoundry-router/docs/ (the sibling router repo for *-link.

    line 8
  2. Distinctive:

    Read the standard's Definition of Done.

    line 19
  3. Distinctive:

    Add or update the guard test the standard specifies so the change can't regress.

    line 21
  4. Very specific:

    Run make ci-local; note residual risk.

    line 22

≈ “Common” is an estimate: at least 1 in 5 of the 308,232 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

Fleet-Standard Adoption

Follow AGENTS.md first. The canonical standards live under ../genefoundry-router/docs/ (the sibling router repo for *-link; docs/ in the router):

  • TOOL-NAMING-STANDARD-v1.md — verb_noun snake_case, stable, collision-free names (lets the router drop any transform).
  • RESPONSE-ENVELOPE-STANDARD-v1.1.md (current; supersedes v1) — success, the payload, flat execution-error fields (error_code / message / retryable / recovery_action), and _meta (data_version). v1.1 adds untrusted-content fencing and error-message sanitation (fixed/enum error fields — never reflect caller-supplied or upstream text into caller-visible fields or logs; see the FastMCP not-found reflection guard). The nested error:{...} shape is deferred — don't use it.
  • CONTAINER-HARDENING-STANDARD-v1.md — non-root, read-only, cap-drop, digest-pin, Trivy + SBOM.
  • VERSIONING-STANDARD-v1.md — single-source metadata version; no serverInfo.version framework leak.
  • MCP-TRANSPORT-STANDARD-v1.md — single stateless /mcp (no 307 split), canonical serverInfo / health.
  • Logging & CLI Standard v1 — structured logging + CLI conventions (canonical text tracked per-repo; no router doc).

Workflow

  1. Read the standard's Definition of Done; check this repo against it.
  2. Apply the smallest change that meets the DoD; reuse the router's reference implementation rather than reinventing.
  3. Add or update the guard test the standard specifies so the change can't regress.
  4. Run make ci-local; note residual risk.
  5. Close the standard's tracking issue with a one-line CHANGELOG note.

Common mistakes

  • Adding router-side workarounds instead of fixing the backend to the standard.
  • Meeting the letter without the guard test — it regresses on the next change.

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