Stats
Actions
Tags
Help us improve
Share bugs, ideas, or general feedback.
From inki
Orchestrates pre-writing research for Strapi projects by classifying input and combining sub-reports on existing coverage, feature gaps, and code change routing.
npx claudepluginhub strapi/documentation --plugin inkiHow this skill is triggered — by the user, by Claude, or both
Slash command
/inki:research <topic, feature name, or strapi/strapi PR><topic, feature name, or strapi/strapi PR>The summary Claude sees in its skill listing — used to decide when to auto-load this skill
Given `$ARGUMENTS`, classify the input:
Audits documentation coverage of a Strapi feature or module by enumerating its public surface and cross-referencing with the Strapi docs.
Writes or updates documentation with code-verified accuracy for READMEs, guides, and API references. Use when creating, reviewing, or updating docs.
Autonomously researches feature requests or architecture documents, explores codebase patterns, identifies ambiguities and gaps, produces feature-context.md for orchestrator without making technical decisions.
Share bugs, ideas, or general feedback.
Given $ARGUMENTS, classify the input:
/inki:exists $ARGUMENTS/inki:coverage $ARGUMENTS/inki:route $ARGUMENTSIf the input is ambiguous, run more than one and label sections clearly.
Combine sub-reports under labeled sections:
=== Existing coverage ===
<output of /inki:exists, if invoked>
=== Feature gaps ===
<output of /inki:coverage, if invoked>
=== Code change routing ===
<output of /inki:route, if invoked>
Conclude with a single recommended next step (e.g., "Run /inki:write" or "Skip — already documented at ").