Agent skill · writing content · callicrate
make-documentation
Use when writing READMEs, architecture, changelogs, release notes, runbooks, notebook docs, install docs, or security articles; produces docs. Do not trigger for API docs, AGENTS.md, or diagrams.
Why this skill is useful
Provides structured templates and specific workflows for various types of documentation that the AI wouldn't reliably generate on its own.
What it needs
About 3k tokens when loaded. Last updated 2026-06-24.
What this skill does
Make Documentation When to Use Writing or updating a README.md, architecture note, changelog, or release notes Auditing existing project docs before adding missing documentation Drafting customer-facing security guidance or partner-sensitive article prose from source material Writing live access, reproduction, lab interface, workstation/server, or operator runbooks Documenting notebooks, generated notebooks, or table-producing notebook workflows Writing WSL, local, Docker, or environment-specific install docs Writing agent operation manuals, role files, peer-status contracts, or AI-readable workflow docs Producing diagram documents only when the user explicitly asks or the project already uses them When NOT to Use Writing API reference documentation Creating or updating AGENTS.md. Use agents-md, even when the broader request also includes other docs. Generating diagram files by default when prose or tables are sufficient Workflow 1. Run scripts/auditdocumentation.py for new docs, large rewrites, doc moves, missing-doc investigations, or unclear structure. For tiny explicit edits, inspect the target file and nearby docs directly. 2. Choose only the deliverables justified by the user's request and the audit. Do not generate a fixed documentation bundle by default. 3. …
How to use it
Reference it in AdaL, Claude Code, Cursor or any coding agent — nothing to install:
@skills callicrate/make-documentation