SKILLEMALL.ai
GitHub ↗ RU Sign in

BB code-review-web

Review web application code for bugs, security issues, performance problems, and stack-specific anti-patterns. Use this skill whenever the user wants to review code, debug a production issue, investigate a build failure, audit security, or check a PR before merging. Triggers on code review, review my code, debug, build error, broken, not working, why is X failing, check this code, security check, PR review, audit code, refactor. Also triggers when investigating 4xx or 5xx errors, deploy failures, environment variable issues, and CMS integration problems.

rampstackco/claude-skills Agent Skills author: rampstackco 4 files body ≈ 2 495 tokens Open the sourcegithub.com↗ analyzed 8 h ago

Review web application code for bugs, security issues, performance problems, and stack-specific anti-patterns.

As a process B 75/100 · Nearly there — weak spots: running it twice

AnalyzerWordPressSoftware 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%
98
Quality 40%
85
Run on models
none yet
Process rating
B
75/100
Nearly there
Running it twice w 4
30
Tools and files w 18
60
Result and completion w 14
60
the three weakest of ten parameters · all ten
This is a copy of a skill from another catalog; the rating counts the canonical one: code-review-web (rampstackco/claude-skills)

How to improve

    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 · 2

    ✓ No critical or high findings

    Medium and low: 2
    • low Exfiltration net-credential-use references/nextjs-patterns.md:245
      Credential used in a network call (verify the destination is the intended service) (documentation of a security skill)
      curl -X POST "https://yourdomain.com/api/revalidate?path=/&secret=…"
      security skill

    A further 1 matches are quotations in this security skill's documentation and are not counted as findings.

    Files scanned: 4. Evidence is masked. Grey chips explain why severity was lowered.

    Against the Agent Skills spec

    • note frontmatter-key unknown frontmatter key "catalog_summary"
    • note frontmatter-key unknown frontmatter key "display_order"

    Process rating: all ten parameters 75/100

    • 30Running it twice. 7 mutating operations with no state check
    • 60Tools and files. Uses tools (web) that frontmatter does not declare
    • 60Result and completion. Output format stated, no completion criterion
    • 70When it triggers. States when to use, but not when not to
    • 70Inputs and preconditions. Inputs and preconditions are listed
    • 85Steps. 97 steps, 2 vague phrases
    • 100Failures and branches. 1 branches, has a failure section
    • 100Consistency. Name and required fields are in place
    • 100Execution cost. Instruction body is 2495 tokens
    • 100Progress reporting. Reports progress
    • medium Safety rules and hard prohibitions inside a skill: they belong in the system prompt, here they protect nothing
    • 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)
    • +4No input/output examples
    • +1No license
    • +2Single-language instructions
    • +3Description length 560: enough signal without eating the budget
    • +4Structure: 23 headings
    • +3Step-by-step instructions: 97 items
    • +3Output format is stated explicitly
    • +4Reference files are cited in the instructions (3 of 3)

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