Stats
Actions
Tags
From inki
Checks the structural outline of a documentation page against a template: heading hierarchy, section order, and completeness. Useful when reviewing docs for consistency.
How this skill is triggered — by the user, by Claude, or both
Slash command
/inki:outline-check <file path><file path>The summary Claude sees in its skill listing — used to decide when to auto-load this skill
`$ARGUMENTS` is a relative path to a documentation page. Identify which template this page should match (feature, plugin, guide, API, configuration, breaking-change) by reading the page's frontmatter and content.
$ARGUMENTS is a relative path to a documentation page. Identify which template this page should match (feature, plugin, guide, API, configuration, breaking-change) by reading the page's frontmatter and content.
Read ../../references/prompts/outline-checker.md and use it as the system prompt. Compare the page's outline to the expected template at ../../references/templates/<template-name>.md.
Target: <path>
Expected template: <template name>
Outline issues:
- <heading missing | order wrong | extra section>: <details>
npx claudepluginhub strapi/documentation --plugin inkiAudits the pedagogical UX of documentation outlines—beginnner progression, signposting, and reading flow—using a reference prompt.
Validates marketing content structure: schema compliance, required sections, word counts, placeholder detection. Run before publication for quality gate.
Verifies a document contains all required sections: About This, Acknowledgements, Methods, Results, Conclusion, References, and a conditional Appendix.