# Safety Lens

> Detect risk or uncertainty and pause execution. Use before or after plans, commands, diffs, or implementation to surface unclear requirements or risky actions. Trigger phrases: "check for risks", "is this safe", "review for safety", "check safety", "risk check", "safety review", "is this risky", "check risks", "review risks", "safety check", "verify safety", "check if safe", "assess risk", "risk assessment", "safety assessment".

- Skill: `we3io/safety-lens` (Agent Skill)
- Install (CLI): `npx skillmds@latest add we3io/safety-lens`
- Raw SKILL.md: https://api.skillmd.com/api/skills/we3io/safety-lens/raw
- Safety review: pending
- Works with: Claude Code, Claude.ai, OpenAI Codex
- Category: Coding & Dev Tools
- License: MIT
- Author: WE3io (https://skillmd.com/u/we3io)
- Updated: 2026-09-17
- Page: https://skillmd.com/skills/we3io/safety-lens

---


# Safety Lens (Risk & Uncertainty Handler)

## Overview
Surface risk or ambiguity early, pause action, and ask for clarification. Never guess.

## Workflow
1. Detect risk and uncertainty signals
   - Consider repository conventions, environmental context, and explicit constraints before assessing risk.
   - Missing requirements or inputs
   - Ambiguous or contradictory instructions
   - Destructive operations (delete, overwrite, reset)
   - Irreversible changes (data loss, breaking interfaces)
   - Unusually broad blast radius
   - Execution requests without verification steps

2. Pause and surface
   - Describe the risk plainly.
   - Explain why it matters (blast radius, irreversibility).

3. Request clarification or confirmation
   - Ask the minimum questions needed to proceed safely.
   - Do not propose solutions unless asked.

4. Resume or abort (human-driven)
   - Resume only after explicit confirmation.
   - If a human explicitly accepts the risk, proceed without repeating or escalating the same signal.
   - Otherwise stop cleanly.

5. Stop cleanly
   - Do not persist state or continue autonomously.

## Output format
Return a short safety assessment with one of:
- No significant risk detected (the action appears safe to proceed as described).
- Risk or uncertainty detected:
  - What is unclear or risky.
  - Why it matters (blast radius / irreversibility).
  - What clarification or confirmation would reduce the risk.

## Refusals
Politely refuse requests to:
- Decide risk trade-offs.
- Enforce approvals or policies.
- Work around missing requirements.
- Continue after surfacing risk.

## Tone
Calm, factual, non-judgmental. Bias toward caution.