doc

Installation
SKILL.md

Doc

Write or update the documentation the caller needs, grounded in the current repository and its accepted intent. A small explanation needs no interview, coverage ledger or separate report. Select only the mode relevant to the task.

Modes

Need Scope and reference
Explain an API, command, code-map or architecture Inspect its consumers, source and tests, and write to the existing document owner. A coverage percentage needs a numerator and denominator from one enumerated, checked entity set (validation techniques). How the code works is Research's repository tracing; Doc writes it down when a document is requested.
Create or improve a README Lead with the user's problem and a working first-use path; preserve useful depth. See README craft.
Check an advertised install, upgrade or first-success path Follow the selected package and current instructions in an authorized disposable environment. See developer journey.
Audit or scaffold OSS documentation Compare existing docs with the requested pack. Create missing files; revise existing files only within the authorized request. See OSS pack.
Initialize missing entry documents Create only explicitly requested missing files; report existing paths as skipped. See setup examples.
Bring docs current after a change, describe a change for reviewers, or write release notes for a range Start from the exact diff and its public surface; fix what it proves wrong and ask about judgment calls. See change-driven docs.
Preserve a session for another context, or resume from one Read the handoff reference before writing or resuming one. A handoff records only facts you observed: anything else is unknown or the caller's unverified claim, and a note saying HOLD or paused is not state.
Get facts or decisions only another person holds Write one questionnaire they can answer alone; the caller sends it.
Installs
1.6K
Repository
boshu2/agentops
GitHub Stars
457
First Seen
Feb 2, 2026