SKILLEMALL.ai
GitHub ↗ RU Sign in

AB security-review

Review a design, PR, or feature for security issues before it ships. Use when asked to do a security review, security-review a change/PR, or check a feature for vulnerabilities. Produces a structured review across the common risk areas (authn/authz, input handling, secrets, data exposure, dependencies), findings ranked by severity with concrete fixes, and a ship / fix-first verdict. For code and systems you own or are authorized to review.

mohitagw15856/pm-claude-skills Agent Skills author: mohitagw15856 MIT 1 file body ≈ 788 tokens Open the sourcegithub.com↗ analyzed 2 d ago

Review a design, PR, or feature for security issues before it ships.

As a process B 70/100 · Nearly there — weak spots: when it triggers, failures and branches, progress reporting

AnalyzerSoftware developmentSecuritytype 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
A
91/100
safety, quality, tests
Safety 60%
96
Quality 40%
83
Run on models
none yet
Process rating
B
70/100
Nearly there
Failures and branches w 10
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: security-review (mohitagw15856/pm-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 · 4

    ✓ No critical or high findings

    Medium and low: 4
    • low Risky intent intent-offensive-security SKILL.md:11
      Offensive-security / dual-use content (legitimate for authorised testing; review intended use) (detector / deny-list definition)
      complements (not replaces) automated scanners and a formal pentest.
      detector
    • low Risky intent intent-offensive-security SKILL.md:28
      Offensive-security / dual-use content (legitimate for authorised testing; review intended use)
      1. **AuthN / AuthZ** — is identity verified, and is every action authorized (incl. object-level / IDOR, privilege escalation)?
    • low Risky intent intent-offensive-security SKILL.md:45
      Offensive-security / dual-use content (legitimate for authorised testing; review intended use) (detector / deny-list definition)
      **Follow-ups** — anything needing a scanner, a pentest, or a deeper look.
      detector
    • low Risky intent intent-offensive-security SKILL.md:53
      Offensive-security / dual-use content (legitimate for authorised testing; review intended use) (detector / deny-list definition)
      - [ ] Existing good controls are acknowledged; deeper follow-ups (scanner/pentest) are flagged
      detector

    Files scanned: 1. 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 70/100

    • 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
    • 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. 19 steps
    • 100Consistency. Name and required fields are in place
    • 100Execution cost. Instruction body is 788 tokens
    • 100Running it twice. No mutating operations
    • medium Safety rules and hard prohibitions inside a skill: they belong in the system prompt, here they protect nothing

    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 443: enough signal without eating the budget
    • +4Structure: 7 headings
    • +3Step-by-step instructions: 19 items
    • +3Output format is stated explicitly

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