SKILLEMALL.ai
GitHub ↗ RU Sign in

BC why

Use for 'why does X work this way', 'why we picked Y', design rationale, regressions, postmortems, or data-backed thresholds. Discovers available MCPs and queries each evidence category (source control, issue tracker, long-form docs, real-time chat, infrastructure observability, error tracking, product analytics warehouse) in parallel, then returns a cited read on decisions and tradeoffs. Use how for runtime behavior.

cursor/plugins Claude Code author: cursor 13 files body ≈ 2 152 tokens Open the sourcegithub.com↗ analyzed 3 d ago

Use for 'why does X work this way', 'why we picked Y', design rationale, regressions, postmortems, or data-backed thresholds.

As a process C 54/100 · Has gaps — References files that are not bundled: ../../docs/harness/claude-code.md, references/sources/<source>.md

ProcedureData and analyticsInfrastructuretype and topics are labelled automatically from the skill text
Runs in: Claude / Claude Code ChatGPT / Codex Gemini CLI Cursor GitHub Copilot / VS Code Qwen Code Kimi Code CLI Z.ai (GLM) DeepSeek (Deep Code) Mistral Vibe LangChain (deepagents) OpenClaw Goose OpenCode
JSON
Technical rating
B
91/100
safety, quality, tests
Safety 60%
100
Quality 40%
78
Run on models
none yet
Process rating
C
54/100
Has gaps
References files that are not bundled: ../../docs/harness/claude-code.md, references/sources/<source>.md
Tools and files w 18
0
Inputs and preconditions w 11
0
Running it twice w 4
30
the three weakest of ten parameters · all ten
This is a copy of a skill from another catalog; the rating counts the canonical one: why (cursor/plugins)

How to improve

  1. The text references files that are not there: add them or drop the references.
For the model run — optional
  • 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: 13. Evidence is masked. Grey chips explain why severity was lowered.

Against the Agent Skills spec

  • warning missing-ref reference to a missing file: ../../docs/harness/claude-code.md
  • warning missing-ref reference to a missing file: references/sources/<source>.md

Process rating: all ten parameters 54/100

Will not run. References files that are not bundled: ../../docs/harness/claude-code.md, references/sources/<source>.md
  • 0Tools and files. 2 referenced file(s) missing: ../../docs/harness/claude-code.md, references/sources/<source>.md
  • 0Inputs and preconditions. Does not say what the process needs to start
  • 30Running it twice. 9 mutating operations with no state check
  • 50When it triggers. No condition that starts the skill
  • 60Result and completion. Output format stated, no completion criterion
  • 85Steps. 25 steps, 1 vague phrases
  • 100Failures and branches. 2 branches, has a failure section
  • 100Consistency. Name and required fields are in place
  • 100Execution cost. Instruction body is 2152 tokens
  • 100Progress reporting. Reports progress
  • low The response is described with custom markup (8 tags): a typed call is more reliable

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

  • +5Description has no quoted example phrases that should trigger the skill
  • +4Description does not say when NOT to use the skill (false activations)
  • +4No input/output examples
  • +1No license
  • +2Single-language instructions
  • +3Description length 421: enough signal without eating the budget
  • +4Structure: 12 headings
  • +3Step-by-step instructions: 25 items
  • +3Output format is stated explicitly
  • +4Reference files are cited in the instructions (4 of 4)

Quality base 70; lint remarks subtract, signals add up to 100. Result: 78.