mcpbeat Sign in

Grad Dual Process Agent Skill

Apply dual-process theory to diagnose whether judgments arise from fast intuitive (System 1) or slow analytical (System 2) processing and identify resulting cognitive biases. Use this skill when the user needs to explain why quick decisions go wrong, design choice architectures that account for cognitive defaults, audit decision processes for heuristic errors, or when they ask 'why do people misjudge probability', 'how to reduce snap-judgment errors', or 'when does intuition fail'.

3k tokens
context cost
the whole folder, loaded on every use
2
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 grad-dual-process

What comes with it

5 987 bytes besides the instruction
examples/sample_scenario.md

The instruction itself

13 sections, as written by the author

Dual-Process Theory

Overview

Dual-process theory (Kahneman, 2011; Stanovich & West, 2000) distinguishes two modes of cognitive processing: System 1 (fast, automatic, heuristic-driven) and System 2 (slow, deliberate, rule-based). Most judgments default to System 1, which is efficient but prone to systematic biases when heuristics misfire.

When to Use

  • Explaining why stakeholders make predictable judgment errors under time pressure or complexity
  • Designing decision environments (nudges, checklists) that compensate for System 1 defaults
  • Auditing existing processes to identify where heuristic shortcuts introduce risk
  • Evaluating when intuitive expertise is reliable vs. when it is misleading

When NOT to Use

  • When decisions are already well-structured with algorithmic procedures (bias is engineered out)
  • As an excuse to dismiss all intuitive judgment — expert intuition can be accurate in high-validity environments
  • When the problem is motivational rather than cognitive (people know the right answer but choose otherwise)

Assumptions

IRON LAW: System 1 operates by DEFAULT — System 2 engagement
requires cognitive effort and is easily depleted. Under time
pressure, cognitive load, or ego depletion, System 1 dominates
and heuristic biases amplify.

Key assumptions:

  • System 1 and System 2 are metaphors for processing modes, not discrete brain systems
  • Heuristics are generally adaptive — biases emerge at the boundary conditions
  • System 2 can override System 1, but only when cued and when cognitive resources are available

Methodology

Step 1 — Identify the Judgment or Decision Context

Characterize the decision: time pressure, complexity, familiarity, stakes, emotional involvement.

Step 2 — Classify Processing Mode

| Feature | System 1 | System 2 |

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

| Speed | Fast, automatic | Slow, effortful |

| Awareness | Unconscious | Conscious |

| Capacity | High (parallel) | Low (serial) |

| Basis | Heuristics, associations | Rules, logic |

| Error type | Systematic biases | Computational mistakes |

| Triggered by | Default, familiarity | Novelty, conflict detection |

Step 3 — Map Relevant Heuristics and Biases

Common System 1 heuristics and their failure modes:

  • Availability: judge frequency by ease of recall — biased by salience and recency
  • Representativeness: judge probability by similarity — ignores base rates
  • Anchoring: estimate by adjusting from initial value — insufficient adjustment
  • Affect: judge risk/benefit by emotional reaction — neglects statistical evidence

Step 4 — Design Intervention

  • De-bias: slow down decisions, require explicit justification, use pre-mortems
  • Nudge: restructure choice architecture to align System 1 defaults with desired outcomes
  • Leverage: use System 1 strengths (pattern recognition) in high-validity, rapid-feedback domains

Output Format

## Dual-Process Analysis: [Context]

### Decision Environment
- Time pressure: [High/Medium/Low]
- Complexity: [High/Medium/Low]
- Emotional involvement: [High/Medium/Low]
- Dominant processing: [System 1 / System 2 / Mixed]

### Heuristic-Bias Map
| Heuristic | Bias Triggered | Evidence | Risk Level |
|-----------|---------------|----------|------------|
| [heuristic] | [bias] | [observation] | [High/Med/Low] |

### Intervention Design
1. [De-biasing or nudge strategy]
2. [Process change]
3. [Environmental redesign]

Gotchas

  • System 1/System 2 is a useful metaphor, not a literal brain architecture — avoid reifying the distinction
  • Expert intuition (System 1) is highly accurate in domains with clear feedback and regular patterns (e.g., chess, firefighting)
  • De-biasing training has poor transfer — changing the environment is more effective than training individuals
  • Cognitive depletion effects are debated; do not assume a simple "willpower battery" model
  • System 2 is not inherently "better" — it is slower, more costly, and still subject to motivated reasoning
  • People often confuse confidence with accuracy; high System 1 confidence does not indicate correctness

References

  • Kahneman, D. (2011). *Thinking, fast and slow*. Farrar, Straus and Giroux.
  • Stanovich, K. E. & West, R. F. (2000). Individual differences in reasoning: implications for the rationality debate. *Behavioral and Brain Sciences*, 23(5), 645-665.
  • Tversky, A. & Kahneman, D. (1974). Judgment under uncertainty: heuristics and biases. *Science*, 185(4157), 1124-1131.

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/grad-dual-process 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.