Stats
Actions
Tags
From inki
Top-level write orchestrator: outline a new page, get user approval, then draft from the outline.
How this skill is triggered — by the user, by Claude, or both
Slash command
/inki:write [--yes|-y] <topic brief or path to a brief file>[--yes|-y] <topic brief or path to a brief file>The summary Claude sees in its skill listing — used to decide when to auto-load this skill
From `$ARGUMENTS`, detect `--yes` or `-y` anywhere in the list. If present, set `AUTO=true` and remove the flag. What remains is the topic brief (text or path to a `.md` file).
From $ARGUMENTS, detect --yes or -y anywhere in the list. If present, set AUTO=true and remove the flag. What remains is the topic brief (text or path to a .md file).
AUTO=false, default)/inki:outline $ARGUMENTS. Wait for user approval inside that sub-skill./inki:draft <outline-path>.If the user rejects the outline, stop. Do not draft.
AUTO=true)/inki:outline --yes $ARGUMENTS. The outline is generated and saved without an approval gate./inki:draft <outline-path> on the resulting outline.In auto mode, the user sees the outline and the draft only after both are produced. They can still discard the outputs if they don't fit — nothing is committed automatically. --yes here means "don't pause between outline and draft," not "trust the output blindly."
/inki:submit for that.npx claudepluginhub strapi/documentation --plugin inkiGenerates a documentation page from an approved outline, matching template, and authoring guide. Useful for technical writers following a structured documentation workflow.
Researches topics, generates outlines with citations, improves hooks, provides section feedback, and refines drafts for blog posts, articles, tutorials, and technical docs.
Researches topics, outlines structures, drafts sections, improves hooks, manages citations, and refines blog posts, articles, tutorials, and technical docs.