SKILLEMALL.ai
GitHub ↗ RU Sign in

BF how

Use for "how does X work", code walkthroughs before changing something, and placement / ownership / layering questions ("where should this live", "which package owns this", "is this the right layer"). Explains subsystem architecture, runtime flow, onboarding mental models. Use why for motivation.

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

Use for "how does X work", code walkthroughs before changing something, and placement / ownership / layering questions ("where should this live", "which…

As a process F 34/100 · No process to follow — References files that are not bundled: ../../docs/harness/claude-code.md

AnalyzerSoftware developmenttype 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
93/100
safety, quality, tests
Safety 60%
100
Quality 40%
83
Run on models
none yet
Process rating
F
34/100
No process to follow
References files that are not bundled: ../../docs/harness/claude-code.md
Tools and files w 18
0
Inputs and preconditions w 11
0
Failures and branches w 10
0
the three weakest of ten parameters · all ten
This is a copy of a skill from another catalog; the rating counts the canonical one: how (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: 3. 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

Process rating: all ten parameters 34/100

Will not run. References files that are not bundled: ../../docs/harness/claude-code.md
  • 0Tools and files. 1 referenced file(s) missing: ../../docs/harness/claude-code.md
  • 0Inputs and preconditions. Does not say what the process needs to start
  • 0Failures and branches. Linear process with no failure handling
  • 0Progress reporting. Says nothing while it works
  • 20When it triggers. No condition that starts the skill
  • 30Running it twice. 1 mutating operations with no state check
  • 50Steps. 2 steps
  • 60Result and completion. Output format stated, no completion criterion
  • 100Consistency. Name and required fields are in place
  • 100Execution cost. Instruction body is 618 tokens

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)
  • +3No numbered steps or checklist
  • +4No input/output examples
  • +1No license
  • +2Single-language instructions
  • +5Description quotes 4 example trigger phrases
  • +3Description length 297: enough signal without eating the budget
  • +4Structure: 6 headings
  • +3Output format is stated explicitly
  • +4Reference files are cited in the instructions (2 of 2)

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