smith-clarity

Detect cognitive traps and logical fallacies in decision-making tasks.

1|Updated Nov 25, 2025
One-click install
npx skills add https://github.com/tianjianjiang/smith --skill smith-clarity
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: smith-clarity
Source: https://github.com/tianjianjiang/smith/tree/main/smith-clarity
Command: npx skills add https://github.com/tianjianjiang/smith --skill smith-clarity

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Cognitive trap detection and logic fallacy identification. Use when making decisions, evaluating approaches, risk assessment, or detecting faulty reasoning in arguments.

Core Features & Use Cases

  • Defensive thinking guardrails to avoid common reasoning errors
  • Flag cognitive traps and logical fallacies during evaluation and decision-making
  • Support verification through cross-referencing related skills for pre-mortem analysis and validation

Quick Start

Provide a decision scenario and I will identify cognitive traps and propose safer alternatives.

Frequently Asked Questions about smith-clarity

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

FAQPage Schema
How do I detect logical fallacies in my decision-making process?

To detect logical fallacies, you provide a decision scenario and the system flags cognitive traps and reasoning errors, proposing safer alternatives based on a defensive thinking framework.

When do I need to identify cognitive traps during risk assessment?

You need to identify cognitive traps during risk assessment when evaluating approaches in domains like strategy, product design, or code review to avoid common reasoning errors and faulty argumentative logic.

What is defensive thinking and how does it guard against faulty reasoning?

Defensive thinking is a framework that acts as guardrails to avoid common reasoning errors, flagging cognitive traps and logical fallacies during evaluation to ensure safer decision outcomes.

Can I use this for code review and product design evaluation?

Yes, you can use it for code review and product design evaluation, as it specifically detects faulty reasoning and cognitive traps across these domains when assessing approaches and risks.

What is the best way to evaluate arguments for hidden cognitive traps?

The best way to evaluate arguments for hidden cognitive traps is to apply a defensive thinking framework that cross-references related skills for pre-mortem analysis and validation to propose safer alternatives.