Menú
De forma predeterminada está seleccionado el prompt que primero revisa el origen. Puedes cambiar a un comando directo o descargar una copia local.
Lee SKILL.md y los archivos complementarios que muestra SkillsMP antes de decidir si quieres instalarlo.
Instalar con Codex o Claude Copia este prompt, pégalo en Codex, Claude u otro asistente, y deja que revise la página de la skill y la instale por ti.
Un comando directo omite el prompt de revisión. Revisa el origen antes de ejecutarlo.
npx skills add https://github.com/existential-birds/beagle --skill ensure-docsEl comando permanece en una sola línea. Desplázate horizontalmente para revisarlo antes de copiarlo.
¿Prefieres una copia local? Descarga los archivos que SkillsMP tiene disponibles ahora.
Basado en la clasificación ocupacional SOC
Mostrando SKILL.md
| name | ensure-docs |
| description | Verify documentation coverage and generate missing docs interactively |
| disable-model-invocation | true |
Verify documentation coverage across a codebase, report gaps, and generate missing docs. If the agent supports subagents, dispatch one verifier per detected language in parallel; otherwise run the same per-language verification sequentially — the output is identical either way.
Coverage has two complementary lenses, and a healthy project needs both:
Complete steps in order. Do not advance until each step’s Pass is satisfied.
Language detection — Follow Phase 1 (language detection) in references/workflow.md.
Load standards — Read the sections for your detected languages (language standards, verifier prompts, consolidation format) in the same reference file.
Verification — Verify each qualifying language using the verifier prompts and JSON output shape in the reference (Phase 2). If the agent supports subagents, run one verifier per language in parallel; otherwise run them sequentially.
language, files_scanned, and findings (array, possibly empty).Diataxis balance check — Run the Diataxis type balance check against the project's existing docs (e.g. a docs/ tree, README, or wiki).
Consolidated report — Merge results per Phase 3 (summary table, severity grouping, detailed findings if requested). Include the Diataxis balance alongside symbol coverage.
Generation — Only if --report-only is not set: offer choices per Phase 4; apply doc edits only after an explicit user choice to generate. For a missing Diataxis type, route generation through draft-docs for the relevant type rather than generating inline.
Post-edit verification — After any generation, run or offer the linter commands in Phase 5 of the reference for languages you changed, when those tools exist in the repo.
N/A with a one-line reason (e.g. tool not configured); remaining issues are listed or cleared.Survey the project's prose documentation (a docs/ tree, README, wiki, or doc site) and classify what exists into the four Diataxis types. Use the compass to classify — action or cognition? acquisition or application? — per docs-style/references/diataxis-compass.md.
Report the balance as a table:
| Type | Present? | Notes |
|---|---|---|
| Tutorial (learning) | yes / no / thin | e.g. "No getting-started / first-project guide" |
| How-To (tasks) | yes / no / thin | e.g. "Several task guides under docs/how-to/" |
| Reference (lookup) | yes / no / thin | e.g. "API reference generated, but no CLI reference" |
| Explanation (understanding) | yes / no / thin | e.g. "No architecture / design-rationale docs" |
Flag, in priority order:
Do not propose generating empty skeletons for missing types. Following the Diataxis "work by improvement" principle, recommend the single highest-value document to add or fix next, and offer to draft it via draft-docs.
--report-only to skip generation.