Safety lens
Skill WE3io/lightweight-ai-development-agent-skills/skills/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".From its SKILL.md
npx -y skills add WE3io/lightweight-ai-development-agent-skills --skill safety-lensAssembled from the repository path, not quoted from the project. Check it against their README if it does not work.
2 things to look at
- no licenseNo license file was found in the repository. Code published without one is not open source by default, so using it at work is a question for whoever answers licensing questions where you are.
- 1 stars1 stars. Stars are a popularity signal and not a quality one, but at this level it is likely that nobody has read this closely except its author, and you would be relying on your own review.
What its file declares
Copied from the file, not written here
The file declares its own license as MIT. That is the author’s claim about this one file, and it is not the same thing as the license GitHub reports for the repository, which is listed with the other numbers below.
SKILL.md
2.2 KB, 348 tokens by cl100k_base, as published. Nobody here has run it
Safety Lens (Risk & Uncertainty Handler)
Overview
Surface risk or ambiguity early, pause action, and ask for clarification. Never guess.
Workflow
-
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
-
Pause and surface
- Describe the risk plainly.
- Explain why it matters (blast radius, irreversibility).
-
Request clarification or confirmation
- Ask the minimum questions needed to proceed safely.
- Do not propose solutions unless asked.
-
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.
-
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.
What ships with it
Read from the repository
Just SKILL.md. No reference files, no scripts.