lean-security
Installation
SKILL.md
lean-security
Ground rules
- Standalone. Standalone skill: use the current request, project instructions and available tools.
- No installation. No companion, runtime or scanner installation is required.
- When to apply. Apply for a requested security review/hardening task or a consequential changed security boundary, not a blanket audit of unrelated work.
- Depth. Use standard procedure depth unless requested otherwise; deeper investigation does not change model settings or permission.
Input and result
- Input. Establish the target repository/revision or service, protected assets, relevant change, intended security properties and requested endpoint: assessment, repair, or verification. Reuse the existing agreement.
- Authorization. A clear repair request authorizes matching local work; an assessment alone does not authorize application edits. Resolve missing material ownership/permission rules before dependent work.
- Assessment result. For an assessment, return PASS when the required bounded assessment is complete with no mandatory findings, REWORK for demonstrated mandatory violations, or BLOCKED/unverified for missing required coverage. Findings already established remain actionable even if another area is blocked.
- PASS. PASS is a statement about the assessed scope and evidence, not a guarantee that the whole application is secure.
- Repair result. For a requested repair, DONE requires the agreed security and valid-use behavior, current checks, required review and delivery destination. Missing prerequisites are BLOCKED; demonstrated unresolved mandatory failures are FAILED.
- Report. Give assessed state, findings/dispositions, probes and results, coverage limits and the exact next action. When used inside a larger workflow, return this result to its owner without starting a second scope or repair loop. Do not publish findings or deploy repairs without matching authorization.