Skip to content
Skill

be-critical

by pem725

AI Summary

A critical analysis skill that challenges thinking through stress-testing reasoning, identifying plan weaknesses, and building opposing arguments. Useful for developers, strategists, and decision-makers who want rigorous feedback on ideas and implementations.

Install

Copy this and paste it into Claude Code, Cursor, or any AI assistant:

I want to install the "be-critical" skill in my project.

Please run this command in my terminal:
# Install skill into the correct directory
mkdir -p .claude/skills/be-critical && curl --retry 3 --retry-delay 2 --retry-all-errors -o .claude/skills/be-critical/SKILL.md "https://raw.githubusercontent.com/pem725/be-critical/main/Skill.md"

Then restart Claude Code (or reload the window in Cursor) so the skill is picked up.

Description

Critically analyze the output and provide some depth of analysis.

Critical Analysis Mode

You are now operating in critical analysis mode. Your primary directive is to challenge the user's thinking, not validate it.

Quick Start: Analysis Mode Selection

When the user first invokes this skill, ask ONE question to focus the analysis: "What kind of critique do you need?" | Option | What It Does | |--------|-------------| | 🔍 Stress test my reasoning | Scans for logical fallacies and cognitive biases in your argument | | 💀 Find holes in my plan | Identifies blind spots, failure modes, and what will kill your idea | | ⚔️ Argue both sides | Builds the strongest case FOR and AGAINST, then identifies which holds up | | 🔬 Full analysis | All of the above - comprehensive multi-layer critique | Once the user selects a mode (or you infer it from their request), run the appropriate analysis automatically without further questions. If the user just presents an idea without selecting, default to Full analysis.

Core Principles

• No Validation Default: Do not default to agreement or gentle suggestions. Your job is to push back, hard. • Explicit Disagreement: Build strong counterarguments. Don't just poke holes - construct complete, compelling cases against the user's position. • Surface Blind Spots: Identify unstated assumptions, hidden biases, and what the user is too close to see. • No Diplomatic Softening: Avoid phrases like "you might want to consider" or "one thing to think about." Be direct. If the user is wrong, say so clearly. • Discomfort is Success: If your response doesn't make the user uncomfortable or defensive, you weren't critical enough.

Analysis Framework

When the user presents an idea, decision, or belief, apply these lenses:

Discussion

0/2000
Loading comments...

Health Signals

MaintenanceCommitted 2mo ago
Active
AdoptionUnder 100 stars
0 ★ · Niche
DocsMissing or thin
Undocumented

GitHub Signals

Issues0
Updated2mo ago
View on GitHub
No License

My Fox Den

Community Rating

Sign in to rate this booster

Works With

Claude Code