agentleFS
iamcaominhtieniamcaominhtien/kanban-board-mcp/.github/skills/critical-thinking/SKILL.md

critical-thinking

Skill1 starsChanged 38 days agoMITView on GitHub

Critical thinking skill for engineers. Use when: evaluating an idea from someone else, cross-checking information you are not sure about, planning a feature or project, reviewing code for bugs or impact, making changes without breaking things, voicing disagreement, challenging assumptions. Triggers: 'think critically', 'challenge this', 'verify this', 'review this carefully', 'help me plan', 'is this a good idea', 'cross-check', 'spot risks', 'am I missing something', 'devil's advocate', 'pre-mortem', 'what could go wrong'.

21 other projects use a version of this.

Adopted by

Most recently taken up by

The file

We split this skill into the rules it gives an agent

2 rules. 0 are common, 2 are distinctive, and 0 are very specific to this project.

  • 0

    Common

    Most of the 19 edited versions we read keep these.

  • 2

    Distinctive

    This author's own choices. Worth a look.

  • 0

    Very specific

    Tied to their project's names, files or tools. Probably skip.

  • Common
  • Distinctive
  • Very specific
  1. Distinctive:

    If uncertain at any step, load the relevant reference file above.

    line 57
  2. Distinctive:

    Do I actually understand why this is true — or am I assuming it?

    line 63

“Common” is measured: kept by at least 6 in 10 of the 19 edited versions of this file we could read. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.

Keep what fits and drop the rest. Your version, ready for your agents.
Files
SKILL.md

Critical Thinking Skill

What Is It

Critical thinking is the habit of questioning assumptions and verifying beliefs before acting on them.

It is not being negative or skeptical for its own sake. It is asking:

  • "How do I know this is true?"
  • "What am I assuming?"
  • "What would prove me wrong?"

Core Mindset Shifts

Old habitNew habit
Accept because someone senior said itEvaluate the argument, not the authority
"Sounds right" → move on"What would make this wrong?"
Stay silent to avoid conflictSilence costs more than speaking up
Trust first, verify neverVerify before trusting when stakes are high
First explanation = final answerPause and ask "What else could explain this?"
Your idea = your identityIdeas are hypotheses — update them freely

When to Use This Skill

SituationWhat to do
Someone proposes an idea→ Evaluate the idea
You need to cross-check information→ Cross-checking workflow
Planning a feature or project→ Planning checklist
Reviewing code→ Code review checklist
Making a code change→ Change safety checklist
You want to disagree but feel unsure→ How to voice disagreement
You want to use a mental model→ Frameworks & mental models
You notice a cognitive bias→ Bias list & counters

Quick Procedure

For any situation, follow this 4-step loop:

  1. Clarify — What exactly are we claiming or deciding?
  2. Challenge — What assumptions does this rest on? Are they verified?
  3. Explore — What are the alternatives? What could go wrong?
  4. Decide — Given the above, what's the most reasonable action?

If uncertain at any step, load the relevant reference file above.


Fast Self-Check (3 questions before acting)

  1. Do I actually understand why this is true — or am I assuming it?
  2. What breaks if I'm wrong about this?
  3. Have I heard the strongest argument against my current view?

References

  • Frameworks & Mental Models — First Principles, Pre-mortem, Inversion, 5 Whys, Red Teaming, etc.
  • Checklists — Situation-specific self-questioning prompts
  • Cognitive Biases — Common biases + how to counter them
  • How to Voice Disagreement — Language patterns, habits, what to avoid

Download now (ZIP)

Does it work?

Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.

No reviews yet

People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.

  • It worked
  • Partly
  • It didn't
What did you use it for? e.g. Reviewing pull requests in a Rails app

Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.

Your trail

Files you open will collect here, so you can find them again.

Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.

Now do this for your own.

Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.