Menu

Individual skill

think-before-refusal

0upvotes

Prevents false-positive refusals and overly conservative censorship by applying a Think-Before-Refusal (TBR) intent analysis workflow and verifying copyright or licensing status on the web before declining a request. Use whenever a user prompt touches complex technical, security, medical, legal, creative, or deep-work topics that might trigger surface-level keyword sensitivity, or involves quoting, adapting, or processing works where copyright, public domain, Creative Commons, or open-source licensing applies.

skills/think-before-refusal/SKILL.md

Read pinned source

Source commit af5ff8cc5f6576e499368849c6d776232f3a7b80

What was checked

Matches the observed repository HEAD
Yes
Scanner rules are current
No
Repository scan complete
No
Skill scan complete
No
Observed behavior
Not checked yet
Last checked
Nov 6, 2026

These are observations at the recorded commit, not a guarantee of safety. Review the source before running it.

Install this skill

Choose an agent in your Stack or copy a command below. Commands fetch the pinned commit and copy only this skill directory. Existing destinations are refused. Copying a command does not install anything.

An install command is unavailable: current rules, complete repository and skill scans, an eligible behavior level and a permitted license are required.

Repository context

Repository stars (not skill ratings)
4
Repository last updated
Nov 3, 2026
License
MIT

Observed agent integration: No specific integration evidence. Standard SKILL.md installation does not imply verified compatibility.

Files and excerpt

File metadata and permitted, redacted excerpts come from the recorded scan. Source links are pinned to that commit.

Browse files
Read excerpt
# Think Before Refusal

Reduces false-positive refusals (over-refusal) on benign deep-work, technical, and creative tasks by requiring structured context analysis, XSTest/OR-Bench lexical trap checks, and live web verification (when a search tool is available) of copyright or open-license status before declining a request.

## When to Use

- The user submits a deep-work, technical, system administration, cybersecurity, literary, or research request containing sensitive-sounding keywords (for example, "kill a process", "exploit mitigation", "penetration testing lab", "reverse engineering", or "forensic analysis").
- The user asks to quote, translate, adapt, analyze, or build upon a text, dataset, codebase, song, or document that might be in the public domain, Creative Commons (CC0, CC BY), or under an open-source license (MIT, Apache 2.0, GPL, BSD).
- A request appears borderline at first glance and risks being rejected due to conservative assumptions rather than actual harm or legal restriction.
- The user expresses frustration about overly cautious refusals, preachy disclaimers, or unverified copyright blocks.

## Steps

### 1. Separate Lexical Triggers from Actual Intent (Think-Before-Refusal)
Back to top