mcpbeat Sign in

Hum Critical Thinking Agent Skill

Apply structured critical thinking — identifying claims, evidence, reasoning chains, hidden assumptions, and logical fallacies — to evaluate or construct specific written arguments rigorously. Use this skill when the user presents a concrete argument, claim, op-ed, research finding, or piece of reasoning to be analyzed for logical validity or flaws, even if they say 'is this argument valid', 'what logical fallacies are in this', or 'what assumptions am I making in this thesis'. Do NOT use for casual plan review, trip planning, project risk brainstorming, or pre-mortems — 'poke holes in my plan' requests are red-team / risk review, not argument analysis.

10k tokens
context cost
the whole folder, loaded on every use
4
files
instructions only
0
copies elsewhere
how many repositories repackaged it
223
stars on the repo
on the repository, not the skill itself

Install

one command, takes just this skill from the repository
npx skills add https://github.com/asgard-ai-platform/skills --skill hum-critical-thinking

What comes with it

32 714 bytes besides the instruction
examples/sample_scenario.md
references/fallacy-catalog.md
references/formal-logic.md

The instruction itself

12 sections, as written by the author

Critical Thinking Framework

Overview

Critical thinking systematically evaluates arguments by decomposing them into claims, evidence, reasoning, and assumptions. It identifies where arguments are strong, weak, or fallacious — not to "win" debates but to arrive at better-justified conclusions.

Framework

IRON LAW: Separate the Argument from the Person

Evaluate the ARGUMENT (claim + evidence + reasoning), not the person
making it. A bad person can make a good argument. A trusted expert
can make a bad argument. Ad hominem (attacking the person) and appeal
to authority (trusting the person) are both fallacies.

Argument Structure

Every argument has four components:

  • Claim: What is being asserted? (conclusion)
  • Evidence: What facts/data support the claim?
  • Reasoning: How does the evidence support the claim? (the logical bridge)
  • Assumptions: What unstated premises must be true for the reasoning to hold?

Evaluation Steps

Step 1: Identify the claim — What exactly is being argued? Restate in one sentence.

Step 2: Examine the evidence

  • Is it factual or anecdotal?
  • Is it sufficient (enough data points)?
  • Is it relevant (does it actually relate to the claim)?
  • Is it current (not outdated)?
  • Could the evidence support a different claim?

Step 3: Evaluate the reasoning

  • Does the evidence logically lead to the claim?
  • Are there logical fallacies? (see catalog below)
  • Is correlation being mistaken for causation?
  • Are there alternative explanations?

Step 4: Surface assumptions

  • What must be true for this argument to work?
  • Are these assumptions reasonable?
  • What happens if an assumption is wrong?

Common Logical Fallacies

| Fallacy | What It Does | Example |

|---------|-------------|---------|

| Ad hominem | Attacks the person, not the argument | "You can't talk about economics, you're not an economist" |

| Straw man | Distorts the opponent's argument to attack a weaker version | "You want to reduce military spending? So you want us defenseless?" |

| False dichotomy | Presents only two options when more exist | "You're either with us or against us" |

| Slippery slope | Claims one event will inevitably lead to extreme consequences | "If we allow remote work, soon no one will come to the office ever" |

| Appeal to authority | Uses authority status instead of evidence | "The CEO says AI will replace all jobs, so it must be true" |

| Hasty generalization | Draws broad conclusion from limited cases | "My two friends who studied art are unemployed, so art degrees are useless" |

| Red herring | Introduces irrelevant information to distract | "Yes, our product has bugs, but look at our amazing company culture" |

| Circular reasoning | Conclusion is assumed in the premise | "This is the best approach because there's no better one" |

Output Format

# Argument Analysis: {Topic}

## Claim
{One-sentence restatement of the core argument}

## Evidence Assessment
| Evidence | Type | Sufficient? | Relevant? | Current? |
|----------|------|------------|-----------|----------|
| {evidence 1} | {fact/anecdote/expert/stat} | Y/N | Y/N | Y/N |

## Reasoning Evaluation
- Logical validity: {valid / fallacious}
- Fallacies detected: {list with explanation}
- Alternative explanations: {what else could explain the evidence}

## Hidden Assumptions
1. {assumption} — reasonable? {Y/N, why}

## Verdict
- Argument strength: Strong / Moderate / Weak
- Key weakness: {the biggest flaw}
- What would strengthen it: {what evidence or reasoning is missing}

Examples

Correct Application

Scenario: Evaluating the claim "Remote work reduces productivity"

  • Claim: Remote work reduces productivity
  • Evidence cited: "Our Q3 output dropped 15% after going remote"
  • Assumption surfaced: That the output drop was CAUSED by remote work (not by Q3 seasonality, new hires ramping up, product pivot, or pandemic stress)
  • Fallacy: Post hoc ergo propter hoc (after it, therefore because of it) — correlation assumed to be causation
  • Verdict: Weak — single data point, confounded by multiple factors, no controlled comparison ✓

Incorrect Application

  • "The CEO said remote work is bad, so the argument must be wrong" → Ad hominem in reverse (dismissing based on who said it). Violates Iron Law: evaluate the argument, not the person.

Gotchas

  • Strong arguments can have wrong conclusions: An argument can be logically valid (reasoning follows from premises) but unsound (premises are false). Check both.
  • "I feel" is not evidence: Emotions are valid as human experiences but not as evidence for factual claims. "I feel unsafe" is a legitimate concern; "I feel this policy doesn't work" is not evidence of policy failure.
  • Burden of proof: The person making the claim bears the burden of proof. "You can't prove it's wrong" is not evidence that it's right (argument from ignorance).
  • Steelmanning > strawmanning: Instead of attacking the weakest version of an argument (strawman), construct the STRONGEST version (steelman) and then evaluate it. This produces better analysis.
  • Critical thinking is not cynicism: The goal is better-justified beliefs, not skepticism of everything. Some arguments are strong. Acknowledging strong arguments is part of critical thinking.

References

  • For formal logic notation and syllogisms, see references/formal-logic.md
  • For fallacy catalog with extended examples, see references/fallacy-catalog.md

Other skills for the same job

different authors, same section of the catalogue
Doc Coauthoring
by anthropics
vendor ×10

Guide users through a structured workflow for co-authoring documentation. Use when user wants to write documentation, proposals, technical specs, decision docs, or similar structured content. This workflow helps users efficiently transfer context, refine content through iteration, and verify the doc works for readers. Trigger when user mentions writing docs, creating proposals, drafting specs, or similar documentation tasks.

4k tokens
File Organizer
by frostant
×10

Intelligently organizes your files and folders across your computer by understanding context, finding duplicates, suggesting better structures, and automating cleanup tasks. Reduces cognitive load and keeps your digital workspace tidy without manual effort.

3k tokens
Domain Name Brainstormer
by frostant
×8

Generates creative domain name ideas for your project and checks availability across multiple TLDs (.com, .io, .dev, .ai, etc.). Saves hours of brainstorming and manual checking.

1k tokens
Brainstorming
by ZhanlinCui
×4

You MUST use this before any creative work - creating features, building components, adding functionality, or modifying behavior. Explores user intent, requirements and design before implementation.

626 tokens
Planning With Files
by ZhanlinCui
×3

Implements Manus-style file-based planning for complex tasks. Creates task_plan.md, findings.md, and progress.md. Use when starting complex multi-step tasks, research projects, or any task requiring >5 tool calls.

9k tokens scripts
Scientific Brainstorming
by christophacham
×3

Creative research ideation and exploration. Use for open-ended brainstorming sessions, exploring interdisciplinary connections, challenging assumptions, or identifying research gaps. Best for early-stage research planning when you do not have specific observations yet. For formulating testable hypotheses from data use hypothesis-generation.

5k tokens
GitHub Project Management
by ComeOnOliver
×3

Comprehensive GitHub project management with swarm-coordinated issue tracking, project board automation, and sprint planning

14k tokens
Grill Me
by ComeOnOliver
×3

Interview the user relentlessly about a plan or design until reaching shared understanding, resolving each branch of the decision tree. Use when user wants to stress-test a plan, get grilled on their design, or mentions "grill me".

3k tokens

How to use it

Copy the folder

Take asgard-ai-platform/hum-critical-thinking from the repository into ~/.claude/skills for personal use, or into .claude/skills inside a project.

Check the name does not clash

The agent identifies a skill by the name field in its header. Two skills with the same name cannot sit side by side — one of them will be ignored.