From inki
Searches llms.txt, doc files, sidebars, and GitHub PRs to check whether a topic is already covered on strapi/documentation.
How this skill is triggered — by the user, by Claude, or both
Slash command
/inki:exists <topic or keyword><topic or keyword>The summary Claude sees in its skill listing — used to decide when to auto-load this skill
`$ARGUMENTS`: a topic or keyword (e.g. `MCP server`, `hasPublishedVersion`, `openapi.json route`).
$ARGUMENTS: a topic or keyword (e.g. MCP server, hasPublishedVersion, openapi.json route).
If no argument is provided and the conversation has context (e.g. a PR was just discussed), extract the relevant keywords from context.
Read docusaurus/static/llms.txt at the repo root and find lines mentioning the topic (case-insensitive).
REPO_ROOT=$(git rev-parse --show-toplevel)
grep -i "<topic>" "$REPO_ROOT/docusaurus/static/llms.txt" | head -20
REPO_ROOT=$(git rev-parse --show-toplevel)
grep -rli "<topic>" "$REPO_ROOT/docusaurus/docs/cms" "$REPO_ROOT/docusaurus/docs/cloud" 2>/dev/null | head -20
For each match, optionally check when it was last touched:
git log -1 --format="%ai" -- "<path>"
REPO_ROOT=$(git rev-parse --show-toplevel)
grep -in "<topic>" "$REPO_ROOT/docusaurus/sidebars.js" | head -20
gh pr list --repo strapi/documentation --state all --search "<topic>" --limit 20 --json number,title,state,url
Bucket the PRs as: open (might be in progress), merged (might already cover the topic), closed-not-merged (abandoned attempts).
Report in this format:
Coverage check: "<query>"
Pages on docs.strapi.io that mention it:
- <path 1> (last updated YYYY-MM-DD, coverage: full | partial | mention)
- <path 2>
Sidebars referencing it:
- <entry>
PRs:
- Open: #<num> "<title>" — <url>
- Merged: #<num> "<title>" — <url>
- Closed: #<num> "<title>" — <url>
Verdict: COVERED | PARTIAL | IN PROGRESS | NOT DOCUMENTED
Suggested next step: <e.g. "Run /inki:route with the related strapi/strapi PR" | "Run /inki:outline to start a new page" | none>
npx claudepluginhub strapi/documentation --plugin inkiOrchestrates pre-writing research for Strapi projects by classifying input and combining sub-reports on existing coverage, feature gaps, and code change routing.
Audits repository documentation for drift, stale statements, broken references, and README mismatches before corrective PRs.
Audits documentation against source code using git-based staleness detection. Run with no args for smart check or specify a path. Supports full audit, auto-fix, and check-only modes.