Stats
Actions
Tags
Help us improve
Share bugs, ideas, or general feedback.
From inki
Audits documentation coverage of a Strapi feature or module by enumerating its public surface and cross-referencing with the Strapi docs.
npx claudepluginhub strapi/documentation --plugin inkiHow this skill is triggered — by the user, by Claude, or both
Slash command
/inki:coverage <feature or module name><feature or module name>The summary Claude sees in its skill listing — used to decide when to auto-load this skill
This skill compares a Strapi feature's public surface against the documentation. It needs access to the Strapi codebase, in one of these forms (by preference):
Orchestrates pre-writing research for Strapi projects by classifying input and combining sub-reports on existing coverage, feature gaps, and code change routing.
Generates docstrings, OpenAPI specs, JSDoc annotations, and developer guides. Validates code examples and reports coverage.
Writes or updates documentation with code-verified accuracy for READMEs, guides, and API references. Use when creating, reviewing, or updating docs.
Share bugs, ideas, or general feedback.
This skill compares a Strapi feature's public surface against the documentation. It needs access to the Strapi codebase, in one of these forms (by preference):
strapi/strapi. Fastest and most reliable. Pass the path as input or ask the user.https://raw.githubusercontent.com/strapi/strapi/develop/<path>). Works without a local clone but rate-limited and slower.If neither is available, ask the user for a path or fall back to GitHub fetches.
$ARGUMENTS is a Strapi feature name (e.g., "Users & Permissions plugin", "Document Service API"). Resolve to a set of source files using one of the sources listed in Prerequisites.
List the public APIs, methods, hooks, configuration options, and CLI commands of the feature.
For each public element, search docusaurus/docs/cms and docusaurus/docs/cloud for mentions. Bucket as:
Feature: <name>
Documented (N/M):
- <element>: <doc path>
Partially documented:
- <element>: <doc path> (notes)
Undocumented:
- <element>: <suggested doc path>