cognitive-bias-checklist-skill

Identifies and corrects cognitive biases in slow-mode AI reasoning outputs.

1|Updated Apr 19, 2026
One-click install
npx skills add https://github.com/StepowskiEric/Jerrys-agent-skills --skill cognitive-bias-checklist-skill
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: cognitive-bias-checklist-skill
Source: https://github.com/StepowskiEric/Jerrys-agent-skills/tree/main/.agents/skills/judgment-and-routing/cognitive-bias-checklist-skill
Command: npx skills add https://github.com/StepowskiEric/Jerrys-agent-skills --skill cognitive-bias-checklist-skill

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

The bias checklist helps ensure slow-mode outputs are free of high-consequence cognitive biases by requiring explicit checks before finalization.

Core Features & Use Cases

  • Applies after slow-mode analysis, recommendation, or estimate to surface and mitigate biases.
  • Covers Anchoring Bias, Availability Heuristic, Confirmation Bias, Planning Fallacy, Scope Insensitivity, Overconfidence Bias, Substitution Bias, and Narrative Fallacy with structured checks.
  • Provides a Bias Checklist Template, pairing guidance, and workflow definitions to integrate risk-aware decision making.

Quick Start

Run the bias checklist after slow-mode reasoning to identify bias risks and guide corrective actions.

Frequently Asked Questions about cognitive-bias-checklist-skill

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I check for cognitive bias in AI reasoning outputs?

To check for cognitive bias in AI reasoning outputs, apply a structured bias checklist after slow-mode analysis to surface risks like anchoring and confirmation bias, then guide corrective actions across engineering and product decisions.

What is slow-mode reasoning in AI safety and risk management?

Slow-mode reasoning in AI safety is a deliberate analysis phase where outputs are generated before undergoing explicit cognitive bias checks to ensure risk-aware decision making and mitigate high-consequence errors.

How do I mitigate the planning fallacy and overconfidence bias in software engineering estimates?

To mitigate the planning fallacy and overconfidence bias in software engineering estimates, enforce explicit checks using a bias checklist template after slow-mode analysis to record final confidence levels and remaining uncertainties.

Can I integrate a bias checklist into operations and product analysis workflows?

Yes, you can integrate a bias checklist into operations and product analysis workflows by applying it after slow-mode reasoning, using the provided workflow definitions and pairing guidance to enforce risk-aware decision making.

Does this bias check approach cover availability heuristic and narrative fallacy?

Yes, this bias check approach covers the availability heuristic and narrative fallacy, alongside anchoring, confirmation, scope insensitivity, and substitution bias, by enforcing structured checks before finalizing slow-mode outputs.

What are the limitations of using a cognitive bias checklist for AI safety?

A limitation of using a cognitive bias checklist for AI safety is that it must be applied after slow-mode reasoning completes, meaning it surfaces biases post-analysis and records remaining uncertainties rather than preventing them during initial generation.