Stats
Actions
Tags
'%20stop-opacity%3D'0.16'%2F%3E%3Cstop%20offset%3D'1'%20stop-color%3D'rgb(200%2C90%2C60)'%20stop-opacity%3D'0.03'%2F%3E%3C%2FlinearGradient%3E%3C%2Fdefs%3E%3Crect%20width%3D'320'%20height%3D'200'%20fill%3D'url(%23g)'%2F%3E%3Ccircle%20cx%3D'250'%20cy%3D'56'%20r%3D'92'%20fill%3D'rgb(200%2C90%2C60)'%20fill-opacity%3D'0.06'%2F%3E%3Ccircle%20cx%3D'64'%20cy%3D'172'%20r%3D'58'%20fill%3D'rgb(200%2C90%2C60)'%20fill-opacity%3D'0.05'%2F%3E%3C%2Fsvg%3E)
From inki
Audits the pedagogical UX of documentation outlines—beginnner progression, signposting, and reading flow—using a reference prompt.
How this skill is triggered — by the user, by Claude, or both
Slash command
/inki:outline-ux-analyzer <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.
$ARGUMENTS is a relative path to a documentation page.
Read ../../references/prompts/outline-ux-analyzer.md and use it as the system prompt over the target.
Target: <path>
UX score: <1-5>
Findings:
- <section/heading>: <UX issue>: <suggestion>
npx claudepluginhub strapi/documentation --plugin inkiEvaluates documentation information architecture: navigation paths, discoverability, progressive disclosure, cross-linking, and mental model alignment. Use when restructuring docs or users report difficulty finding information.
Checks the structural outline of a documentation page against a template: heading hierarchy, section order, and completeness. Useful when reviewing docs for consistency.
Reviews end-user and product documentation for voice/tone, structure, completeness, clarity, and technical accuracy. Flags issues with prioritized findings and pass/needs-revision verdict.