agentleFS
Sign inStart free
AymanShamsAymanShams/codex-coding-os/.agents/skills/process-docs/SKILL.md

process-docs

Skill1 starsChanged 2 months agoMPL-2.0View on GitHub

Use when the user asks to document, standardize, explain, or turn a recurring internal process into a lightweight operational SOP, playbook, runbook, onboarding playbook, checklist, procedure, or team guide that helps someone execute the process consistently. Use for prompts like write a simple SOP, document this process, create a runbook, build an onboarding playbook, standardize this workflow, make this repeatable, capture tribal knowledge, define handoffs, add decision points, or write step-by-step instructions for a routine process. Prefer this for practical internal process documentation when the artifact is not legal-facing, audit-facing, board-facing, governance-controlled, or intended as a formal source of truth. Do not use for customer-facing help center content, API docs, broad artifact-system design, WBS planning, casual notes, or formal controlled SOPs, policies, operating models, governance artifacts, RACI or DACI matrices, implementation guides, legal or contract drafts, and company source-of-truth artifacts. If the primary task is a controlled or high-stakes artifact, use ssot-drafter. If the primary task is documenting the surrounding document library, folder system, metadata, or lifecycle, use artifact-system-designer. If the primary task is a delivery plan, issue tree, roadmap, or dependency plan, use wbs-artifact-planner. If the primary task is customer-facing support documentation, use support-docs.

2 other projects use a version of this, 2 of them edited.

Adopted by

Most recently taken up by

The file

We split this skill into the rules it gives an agent

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

  • ≈0

    Common · estimate

    Many files like this have a rule of this kind.

  • ≈6

    Distinctive · estimate

    This author's own choices. Worth a look.

  • 0

    Very specific

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

Licensed with conditions — read it at the source. We count its rules but don't quote them. Read them on GitHub.

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

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