agentleFS
ByronScottJonesByronScottJones/Agents/skills/generate-service-documentation/SKILL.md

generate-service-documentation

Skill7 starsChanged 2 months agoMITView on GitHub

Use when creating or refreshing a service record, ownership document, runbook index, or operational documentation from repository and deployment evidence. Produces a reviewable draft and never invents owners, SLOs, or dependencies.

1 other project uses a version of this.

Adopted by

Most recently taken up by

The file

We split this skill into the rules it gives an agent

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

  • ≈0

    Common · estimate

    Many files like this have a rule of this kind.

  • ≈3

    Distinctive · estimate

    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 only with explicit permission.

    line 29
  2. Distinctive:

    Never invent an owner, contact, SLO, credential, or recovery guarantee.

    line 33
  3. Distinctive:

    Do not include secrets or private telemetry.

    line 34

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

Generate Service Documentation

Build a service record from code, deployment, ownership, and observability evidence.

Parameters

  • projectPath: service repository; default workspace root.
  • outputPath: destination document; default SERVICE.md.
  • sources: optional files or directories to inspect.
  • includeRunbook: default true.
  • format: Markdown or JSON; default Markdown.
  • failOnUnknown: default false.

Workflow

  1. Inspect repository metadata, deployment files, CI workflows, routes, manifests, dashboards, and existing documentation.
  2. Extract purpose, owners, environments, dependencies, data classification, lifecycle, SLOs, alerts, recovery procedures, and escalation paths.
  3. Mark every inferred or missing value explicitly as unknown.
  4. Generate a draft with source references and review prompts.
  5. Validate links, commands, and paths in the draft.
  6. Write only with explicit permission; otherwise return the draft in memory.

Safety

  • Never invent an owner, contact, SLO, credential, or recovery guarantee.
  • Do not include secrets or private telemetry.
  • Preserve existing service documentation unless replacement is authorized.

Output

Return the draft path or content, evidence sources, unknown fields, stale references, and required owner review.

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.