agentsclimarketplace
Sign in

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

Install
npx -y skills add WE3io/lightweight-ai-development-agent-skills --skill safety-lens

Assembled 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

  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.

What ships with it

Read from the repository

Just SKILL.md. No reference files, no scripts.

Gives 0 of the 12 instructions most quality gates skills give in 348 tokens

Counted across 1,195 of the 2,094 authors here whose files we hold, read 2026-08-07

  • Read the output and check the exit codein 54 of 1195, across 14 files
  • Verify requirements using a line-by-line checklistin 53 of 1195, across 12 files
  • Identify the verification command proving the claimin 51 of 1195, across 12 files
  • Run the full verification commandin 50 of 1195, across 11 files
  • Verify output confirms the claimin 49 of 1195, across 12 files
  • Check version control diff after agent delegationin 46 of 1195, across 6 files
  • State claim with evidencein 44 of 1195, across 4 files
  • Run the test suitein 33 of 1195, across 26 files
  • Keep state in memory by defaultin 27 of 1195, across 6 files
  • Make prototype runnable with one commandin 26 of 1195, across 5 files
  • Produce a verification reportin 25 of 1195, across 14 files
  • Detect the package manager from lockfilesin 24 of 1195, across 5 files

Said here and by no other author read

  • consider conventions and context before assessing risk
  • detect missing or ambiguous requirements
  • identify destructive or irreversible operations
  • pause execution and describe the risk plainly
  • explain why the risk matters
  • ask minimum questions needed to proceed safely

Grouped from the skills themselves: near-identical wordings counted once, and counted by distinct author, so one author publishing three of these counts once. Length counted with cl100k_base; the agent that loads this file may tokenize it differently.

Keep looking

Skills are one crate of 326,861. Ordering is by how many stacks a row turns up in, so the top of any crate is what has actually been picked rather than what has the most stars.