logical-gearbox

Render ASCII Gearbox diagrams to visualize and debug agent logic.

Updated Apr 17, 2026
One-click install
npx skills add https://github.com/whichguy/c-thru --skill logical-gearbox
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: logical-gearbox
Source: https://github.com/whichguy/c-thru/tree/main/skills/logical-gearbox
Command: npx skills add https://github.com/whichguy/c-thru --skill logical-gearbox

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Codifies the visual 'ASCII Gearbox' format for debugging agent logic. Used to trace state transitions, logic loops, and evidence grounding.

Core Features & Use Cases

  • Visualizes internal decision states across phases (Epistemic Audit, The Rationalizer, Instrumental Action, SoT Sync, Parity Shield).
  • Provides a structured rendering protocol to map state, trace inquiry, and audit grounding.
  • Aids debugging and documentation by turning abstract reasoning steps into a repeatable visual format.

Quick Start

Explain how to render an ASCII Gearbox diagram for a given agent run.

Frequently Asked Questions about logical-gearbox

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

FAQPage Schema
How do I visualize agent logic for debugging multi-phase reasoning workflows?

You can visualize agent logic by rendering an ASCII Gearbox diagram that maps internal decision states across phases like Epistemic Audit and Instrumental Action. This provides a structured protocol to trace state transitions and audit evidence grounding during debugging.

What is an ASCII Gearbox diagram used for in state tracing?

An ASCII Gearbox diagram is used to codify visual formats for debugging agent logic. It turns abstract reasoning steps into a repeatable visual format to trace inquiry, map states, and document evidence in testing sessions.

How do I document evidence grounding during agent development and testing?

Document evidence grounding by applying the ASCII Gearbox rendering protocol to your agent run. It visually audits grounding and traces inquiry across phases like The Rationalizer and SoT Sync, creating structured documentation for development.

Do I need YAML frontmatter to trace state transitions with an ASCII Gearbox?

Yes, you need a YAML frontmatter containing a name and description to trace state transitions. You can optionally include scripts, references, or assets to support the visualization and debugging of your agent logic workflow.

Can I use ASCII visualization for parity shield and SoT sync logic loops?

Yes, ASCII visualization supports mapping logic loops and state transitions across specific phases including Parity Shield and SoT Sync. It provides a structured rendering protocol to debug these internal decision states effectively.

What are the limitations of using ASCII diagrams for agent logic debugging?

ASCII diagrams for agent logic debugging codify visual formats into text-based renderings, which may lack the interactive scalability of graphical UI tools but provide a lightweight, repeatable protocol for documenting state transitions and evidence grounding.