SKILLEMALL.ai

AB critical-code-reviewer

Conduct rigorous, adversarial code reviews with zero tolerance for mediocrity. Use when users ask to "critically review" my code or a PR, "critique my code", "find issues in my code", or "what's wrong with this code". Identifies security holes, lazy patterns, edge case failures, and bad practices across Python, R, JavaScript/TypeScript, SQL, and front-end code. Scrutinizes error handling, type safety, performance, accessibility, and code quality. Provides structured feedback with severity tiers (Blocking, Required, Suggestions) and specific, actionable recommendations.

ClawHub Agent Skills author: yun520-1 v1.0.0 MIT-0 3 files body ≈ 2 027 tokens Open the sourceclawhub.ai analyzed 3 d ago

As a process B 66/100 · Nearly there — weak spots: when it triggers, inputs and preconditions, running it twice

AnalyzerSoftware developmenttype and topics are labelled automatically from the skill text
JSON
Technical rating
A
95/100
safety, quality, tests
Safety 60%
100
Quality 40%
87
Run on models
none yet
Process rating
B
66/100
Nearly there
Inputs and preconditions w 11
0
Progress reporting w 2
0
When it triggers w 12
20
the three weakest of ten parameters · all ten
This is a copy of a skill from another catalog; the rating counts the canonical one: critical-code-reviewer (ClawHub)

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

    ✓ No critical or high findings

    Files scanned: 3. 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 66/100

    • 0Inputs and preconditions. Does not say what the process needs to start
    • 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
    • 60Result and completion. Output format stated, no completion criterion
    • 70Failures and branches. 5 branches
    • 100Tools and files. No external tools needed
    • 100Steps. 73 steps
    • 100Consistency. Name and required fields are in place
    • 100Execution cost. Instruction body is 2027 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)
    • -5TODO / placeholder text left in the skill
    • +1No license
    • +2Single-language instructions
    • +5Description quotes 4 example trigger phrases
    • +3Description length 575: enough signal without eating the budget
    • +4Structure: 14 headings
    • +3Step-by-step instructions: 73 items
    • +3Output format is stated explicitly
    • +4Has examples (1 code blocks)

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

    External checks

    ClawHub: clean
    The artifacts are powerful operational/admin skills, but the sensitive behavior is disclosed, purpose-aligned, and generally controlled by explicit user or admin actions.
    LLM: benign (medium) · VirusTotal: · 9 Jul 2026