Sanity Check

Before building on assumptions, validates them first. Activates when making claims about how code works, what exists, or why something happens. Prevents assumption cascades where one wrong guess leads to a completely wrong solution.

Install

skills CLI (Claude Code, Cursor, Codex and more)
npx skills add ElliotJLT/Claude-Skill-Potions --skill sanity-check
Manual install
git clone --depth 1 https://github.com/ElliotJLT/Claude-Skill-Potions.git /tmp/Claude-Skill-Potions
mkdir -p ~/.claude/skills
cp -r /tmp/Claude-Skill-Potions/skills/sanity-check ~/.claude/skills/sanity-check

Personal skills live in ~/.claude/skills. Use .claude/skills in a project folder to share a skill with your team.

From the SKILL.md

# Sanity Check

<purpose>
Claude confidently builds on assumptions that turn out to be wrong. "The auth
middleware probably checks X" becomes a 50-line solution for a problem that
doesn't exist. This skill forces verification of key assumptions before
building on them.
</purpose>

## When To Activate

<triggers>
- Using words like "probably", "likely", "I assume", "should be"
- Explaining how code works without reading it
- Diagnosing a bug without reproducing it
- Making claims about what exists or doesn't exist
- Building a solution based on inferred behavior
- User asks "why is X happening?" and you're about to guess
</triggers>

## Instructions

### Identify Your Assumptions

Before proposing a solution, list what you're assuming:

```markdown
## Assumptions

1. [The function X exists and does Y]
2. [The error is caused by Z]
3. [This file is imported by W]
4. [The config value is set to V]
```

### Verify Before Building

<verify>
For each assumption, verify it:

| Assumption | Verification | Status |
|------------|--------------|--------|
| Function X does Y | Read the function | Verified / Wrong |
| Error caused by Z | Check error logs | Verified / Wrong |
| File imported by W | Grep for imports | Verified / Wrong |

**Stop if any key assumption is wrong.** Don't patch - reassess.
</verify>

### Types of Assumptions

**Existence assumptions:**
- "There's probably a config file for this"
- "The API endpoint likely exists"
- Verify: `find`, `grep`, `ls`
Read the full skill on GitHub

Details

Skill name
sanity-check
Path
skills/sanity-check/SKILL.md
License
MIT
Repo updated
12 February 2026

FAQ

What does the Sanity Check skill do?

Before building on assumptions, validates them first. Activates when making claims about how code works, what exists, or why something happens. Prevents assumption cascades where one wrong guess leads to a completely wrong solution.

How do I install the Sanity Check skill?

skills CLI (Claude Code, Cursor, Codex and more): npx skills add ElliotJLT/Claude-Skill-Potions --skill sanity-check. Skills go in ~/.claude/skills (personal) or .claude/skills (project), and Claude loads them automatically when a task matches the description.

Is Sanity Check popular?

It lives in ElliotJLT/Claude-Skill-Potions, which has 62 GitHub stars and 2 forks.

Related skills

Agent Audit

62

ElliotJLT/Claude-Skill-Potions

When reviewing, optimizing, or inheriting an LLM agent, systematically identify what's actually load-bearing vs. cruft. Instruments usage, ablates components, and strips the agent to minimum viable form. Answers: "What can we remove without degrading quality?" The goal is the leanest agent that still works.

AI, LLMs & Agents

Battle Plan

62

ElliotJLT/Claude-Skill-Potions

Before ANY significant development task (new feature, refactor, integration, migration), run a complete planning ritual by orchestrating other skills in sequence: rubber-duck (clarify scope) -> pre-mortem (assess risks) -> eta (estimate time) -> final confirmation. Do not start coding until the battle plan is approved.

Software Development

Breadcrumbs

62

ElliotJLT/Claude-Skill-Potions

Leaves notes for future Claude sessions in .claude/breadcrumbs.md. At session end or after significant work, records what was tried, what worked, what failed, and context for next time. On session start, reads breadcrumbs to understand history. Session-to-session memory without manual updates.

Productivity & Notes

Analyze Account Health

48

amplitude/mcp-marketplace

Summarizes B2B account health by analyzing usage patterns, engagement trends, risk signals, and expansion opportunities. Use for customer success reviews, renewal preparation, QBRs, or account prioritization.

Marketing, Sales & Business12

Word Contract Formatting

43

bstevescherer/heycounsel-community

Apply Darwin Legal formatting conventions when drafting or generating any contract, agreement, amendment, or legal document as a Word (.docx) file. Use this skill whenever Ryan asks to draft, generate, or format any agreement — including RSPAs, consulting agreements, amendments, board consents, side letters, or any other legal document — even if the request doesn't explicitly mention formatting. Also use when asked to reformat or clean up an existing contract. Always read this skill before producing any .docx legal document.

Marketing, Sales & Business

Analyze Feedback

48

amplitude/mcp-marketplace

Synthesizes customer feedback into actionable themes including feature requests, bugs, pain points, and praise. Use when planning product roadmap, understanding user sentiment, investigating specific issues, or preparing voice-of-customer reports.

Marketing, Sales & Business12

Browse the most popular Claude skills, all marketing, sales & business skills, or write your own with the skills generator.