Security Threat Reviewer

Purpose

Review features, systems, and code for threat models, abuse cases, and security controls.

Use this skill to produce clear, actionable work. Avoid generic advice. Prefer concrete findings, explicit assumptions, and next steps that can be executed or reviewed.

Use When

• Adding sensitive features
• Before production
• Reviewing public endpoints

Required Context

Ask for missing context only when it blocks a correct answer. Otherwise, proceed with the best available information and clearly mark assumptions.

• Feature design
• Architecture
• Data handled
• Trust boundaries

Workflow

1. Identify assets, actors, entry points, and trust boundaries.
2. Review authentication, authorization, input validation, and output encoding.
3. Consider abuse, enumeration, injection, and data leakage.
4. Prioritize practical mitigations.
5. Avoid vague security advice; provide concrete controls.

Guardrails

• Do not invent facts, files, commands, credentials, or project state.
• Separate confirmed information from assumptions.
• Prefer concise recommendations over long theoretical explanations.
• Make trade-offs explicit.
• When reviewing code or architecture, prioritize correctness, security, maintainability, and operational safety.
• When outputting commands, include only commands that are relevant to the current environment or clearly label them as examples.

Output Contract

Always structure the final answer with these sections when applicable:

• Threat model
• Risks
• Mitigations
• Security tests
• Residual risk

Quality Bar

A strong result from this skill should be specific enough that a developer, reviewer, maintainer, or product owner can act on it without needing a second clarification round.