cognitive-routing

Routes user requests between fast pattern matching and deep deliberative reasoning using complexity scoring.

3|2|Updated Feb 13, 2026
One-click install
npx skills add https://github.com/Yoodaddy0311/artibot --skill cognitive-routing-yoodaddy0311
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: cognitive-routing
Source: https://github.com/Yoodaddy0311/artibot/tree/main/plugins/artibot/skills/cognitive-routing
Command: npx skills add https://github.com/Yoodaddy0311/artibot --skill cognitive-routing-yoodaddy0311

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Deciding whether a request needs a quick heuristic answer or deep multi-step analysis is inconsistent when done manually, leading to wasted tokens on trivial tasks or shallow answers on complex ones. This Skill automates that decision with a dual-process routing engine inspired by Kahneman's System 1/2 theory. ## Core Features & Use Cases - Complexity Scoring: Weighs token estimate, domain count, step count, ambiguity, and risk level into a normalized 0-1 score compared against a configurable threshold. - Escalation Rules: Automatically escalates from System 1 to System 2 on low confidence, pattern misses, high-risk keywords, multi-domain requests, or explicit flags like --think and --ultrathink. - Adaptive Learning Loop: Adjusts the routing threshold based on outcome feedback, tightening on success and loosening on failure or escalation. - Advisor Routing: Lets Sonnet-tier executors consult an Opus advisor for architecture decisions, security assessments, and complex debugging instead of full handoff. - Use Case: A developer asks Claude Code to fix a typo versus audit authentication security; the router sends the first to fast pattern matching and the second to deep deliberative analysis with sandbox verification. ## Quick Start Ask Claude Code any development question and the cognitive-router hook will automatically classify its complexity and route it to fast or deep processing.

Frequently Asked Questions about cognitive-routing

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

FAQPage Schema
How does dual-process routing decide between fast and deep analysis?▼

The router computes a complexity score from five weighted factors: token estimate, domain count, step count, ambiguity, and risk level. Scores below the 0.4 threshold go to System 1 fast processing; scores at or above it go to System 2 deep analysis.

How do I force deep reasoning instead of automatic routing?▼

Add an explicit flag such as --think, --think-hard, or --ultrathink to your request. These flags bypass System 1 and route directly to System 2 deliberative processing regardless of the computed complexity score.

When does System 1 escalate to System 2 automatically?▼

Escalation triggers when confidence drops below 0.6, latency exceeds 100ms, no cached pattern matches, security or production keywords appear, the request spans 3 or more domains, or an explicit think flag is present.

Can the routing threshold be configured or learned automatically?▼

Yes, the threshold defaults to 0.4 and is configurable in artibot.config.json under cognitive.router. An adaptive learning loop adjusts it by the adaptRate step of 0.05 based on outcome feedback from each routed request.

When should I not use cognitive routing?▼

Skip it for simple one-step requests where classification overhead adds no value, and outside the Artibot plugin environment where the cognitive-router hook is not active. Manual routing suffices for trivial single-domain tasks.