SKILLEMALL.ai
GitHub ↗ RU Sign in

CB coding-standards

Universal coding standards, best practices, and patterns for TypeScript, JavaScript, React, and Node.js development.

affaan-m/everything-claude-code Agent Skills author: affaan-m MIT 1 file body ≈ 2 898 tokens Open the sourcegithub.com↗ analyzed 25 h ago

Universal coding standards, best practices, and patterns for TypeScript, JavaScript, React, and Node.js development.

As a process B 74/100 · Nearly there — weak spots: when it triggers, running it twice

ReferenceSoftware 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
C
89/100
safety, quality, tests
Safety 60%
100
Quality 40%
72
Run on models
none yet
Process rating
B
74/100
Nearly there
When it triggers w 12
20
Running it twice w 4
30
Failures and branches w 10
50
the three weakest of ten parameters · all ten

The same skill appears in 2 more places: everything-claude-code, ECC

How to improve

  1. Say in the description WHEN to use the skill ("use when…", example requests): that is the agent's main cue.
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: 1. Evidence is masked. Grey chips explain why severity was lowered.

Against the Agent Skills spec

  • warning description-no-when description does not say WHEN to use the skill (no "use when")

Process rating: all ten parameters 74/100

  • 20When it triggers. No condition that starts the skill
  • 30Running it twice. 1 mutating operations with no state check
  • 50Failures and branches. 0 branches, has a failure section
  • 60Result and completion. Output format stated, no completion criterion
  • 70Inputs and preconditions. Inputs and preconditions are listed
  • 100Tools and files. No external tools needed
  • 100Steps. 25 steps
  • 100Consistency. Name and required fields are in place
  • 100Execution cost. Instruction body is 2898 tokens
  • 100Progress reporting. Reports progress
  • low 10 top-level sections: this looks like several domains in one skill

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)
  • +3Description length 116: 120–800 characters recommended
  • +1No license
  • +2Single-language instructions
  • +4Structure: 40 headings
  • +3Step-by-step instructions: 25 items
  • +3Output format is stated explicitly
  • +4Has examples (26 code blocks)

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