AC context7-cli
Use the ctx7 CLI to fetch up-to-date library documentation, API references, and code examples — always, even for well-known libraries, because training data may be outdated. Also covers managing AI coding skills, generating skills, and setting up Context7 MCP. Activate when the user mentions "ctx7" or "context7", needs current docs for any library/framework/SDK/CLI/cloud service, asks "how do I" questions mentioning a library name, wants to install/search/generate skills, or needs to set up Context7 for their AI coding agent. Triggers include: API syntax questions, configuration options, version migration issues, debugging that involves library-specific behavior, setup instructions, and CLI tool usage. Prefer this over web search for library documentation and API details.
Use the ctx7 CLI to fetch up-to-date library documentation, API references, and code examples — always, even for well-known libraries, because training data…
As a process C 61/100 · Has gaps — weak spots: result and completion, inputs and preconditions, running it twice
How to improve
- Your own cases (evals/evals.json, 4–6 real requests with expected answers): the full check would then run those instead of a model-drafted suite.
- A spec.yaml with trigger phrases and assertions — a behaviour contract for CI; `skilltest init` writes a template.
Guard findings · 0
✓ No critical or high findings
Files scanned: 5. Evidence is masked. Grey chips explain why severity was lowered.
Against the Agent Skills spec
✓ No remarks against the Agent Skills spec
Process rating: all ten parameters 61/100
- 0Result and completion. Does not say what the result is
- 0Inputs and preconditions. Does not say what the process needs to start
- 30Running it twice. 1 mutating operations with no state check
- 60Tools and files. Uses tools (bash, web) that frontmatter does not declare
- 70When it triggers. States when to use, but not when not to
- 100Steps. 26 steps
- 100Failures and branches. 1 branches, has a failure section
- 100Consistency. Name and required fields are in place
- 100Execution cost. Instruction body is 1656 tokens
- 100Progress reporting. Reports progress
Everything here is measured from the skill text rather than judged by a model, so the numbers are checkable. A parameter weighs more when it is a more common reason for the process to stall.
Quality signals
- +4Description does not say when NOT to use the skill (false activations)
- +3Output format is not stated: the model decides each time
- +1No license
- +2Single-language instructions
- +5Description quotes 2 example trigger phrases
- +3Description length 782: enough signal without eating the budget
- +4Structure: 9 headings
- +3Step-by-step instructions: 26 items
- +4Has examples (7 code blocks)
- +4Reference files are cited in the instructions (3 of 3)
Quality base 70; lint remarks subtract, signals add up to 100. Result: 93.