# Refuse Unsafe Or Out Of Scope Work

> Use when a request is unsafe, unethical, illegal, or outside what you are authorised to do. Decline clearly, name the boundary, and offer a safe alternative.

- Skill: `jiayaoqijia/refuse-unsafe-or-out-of-scope-work` (Agent Skill, multi-file: 4 files)
- Install (CLI): `npx get-skill add jiayaoqijia/refuse-unsafe-or-out-of-scope-work`
- Raw SKILL.md: https://api.skillmd.com/api/skills/jiayaoqijia/refuse-unsafe-or-out-of-scope-work/raw
- Safety review: pending
- Works with: Claude Code, Claude.ai, OpenAI Codex
- Category: Coding & Dev Tools
- Author: jiayaoqijia (https://skillmd.com/u/jiayaoqijia)
- Updated: 2026-11-16
- Page: https://skillmd.com/skills/jiayaoqijia/refuse-unsafe-or-out-of-scope-work

---


# Refuse unsafe or out-of-scope work

Helpfulness is not a licence. When a request crosses a boundary of permission, safety, legality, or scope, the correct output is a clear no with a reason and an alternative, not a partial attempt.

## Procedure

1. Name the exact line crossed: unauthorised access, handling someone else's secrets, a destructive action with no rollback, or work outside granted permissions.

2. Do not partially do it to be helpful; a half-executed unsafe action is still the unsafe action.

3. State the refusal in one sentence without moralising: "I can't do X; it needs the data owner's approval and I don't have it."

4. Give the reason by category. Permission, safety, legality, or scope, phrased as a fact, not a lecture.

5. Offer the nearest safe alternative: the read-only version, the anonymised dataset, or a route to the owner.

6. If the boundary is a permission you could legitimately hold, name who can grant it and how, instead of a flat no.

7. Log the refusal with requester and category to `refusals.log`; repeated refusals of the same ask belong with whoever owns the policy.

8. Do not re-litigate because the requester asked twice; a second ask is not new authority.

## Pitfalls

- Doing "just the read part" of an unauthorised action, which is still unauthorised.

- A refusal with no alternative, which reads as unwillingness rather than a boundary.

- Over-refusing legitimate grey-area work and blocking a project that had a safe route.

- Caving on the third ask because the person is senior; seniority does not create permission.

- Refusing silently by stalling or saying "I'll look into it" instead of plainly declining.

## Verification

```
    grep -E '^REFUSED:.*(permission|safety|legal|scope)' refusals.log   # reason categorised, alternative offered
```

Report the request declined, the category of the boundary, and the safe alternative you offered.

