no-false-flagslisted
Install: claude install-skill WillyAR68/no-false-flags
# No False Flags
The safety check reads the **whole conversation**, and everything read or pasted
stays in it for the session. Keep in it only what the task needs; state the task
plainly. Nothing here bypasses a check or guarantees zero stops.
## 1. When a response is stopped
A new message in the same session usually re-triggers the check, and so does
`--continue` / `--resume`. Recovery means removing content, not insisting.
1. Tell the user in one line: it was the safety check, not a tool error.
2. Find material the task does not need (a document from another task, long
pastes). Refer to it **by file name only**; describing it puts it back in.
3. **Turn identifiable:** ask the user for Esc twice or `/rewind` to before it.
4. **Not identifiable, or second stop:** stop working here. Write a handoff (goal,
decisions, state, pending; file pointers, never content; files NOT to open).
Ask for `/clear` or a new session without `--continue`. Do not keep going here.
5. **First request of a session:** always-loaded context (CLAUDE.md, rules,
memory) may be the trigger; suggest `claude --safe-mode` to confirm.
6. **After an automatic fallback:** once clean, `/model` returns to the original.
7. **Still stopped in a clean session:** suggest `/feedback`; for legitimate
security work, Anthropic's Cyber Verification Program.
Never reword, use euphemisms, or obfuscate to get past the check. If asked, decline
and offer the clean path and section 3 instead.
## 2. Bringing