From inki
Generates a documentation page from an approved outline, matching template, and authoring guide. Useful for technical writers following a structured documentation workflow.
How this skill is triggered — by the user, by Claude, or both
Slash command
/inki:draft <path to outline file><path to outline file>The summary Claude sees in its skill listing — used to decide when to auto-load this skill
`$ARGUMENTS` is a path to an outline file produced by `/inki:outline`.
$ARGUMENTS is a path to an outline file produced by /inki:outline.
../../references/templates/<template>-template.md../../references/authoring/AGENTS.<area>.md../../references/12-rules-of-technical-writing.mdRead ../../references/prompts/drafter.md. Use it as the system prompt. Generate the draft, section by section.
Save the draft as a .md file at the canonical path (drop the .outline.md suffix, use .md). Show the user the file path and a diff.
npx claudepluginhub strapi/documentation --plugin inkiGenerates a documentation page outline from a topic brief and a template, then saves it as a Markdown file.
Generates first-draft Reference or How-To technical documentation from code analysis, saving to docs/drafts/ for review before publishing.
Drafts READMEs, API docs, tutorials, release notes, and reviews technical docs for clarity and structure. Activates on docs/ .md files and READMEs.