Jeden Skill in Manus ausführen
mit einem Klick

Jeden Skill in Manus mit einem Klick ausführen

logical-gearbox

Sterne0

Forks0

Aktualisiert11. Juni 2026 um 20:58

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

Installation

Mit Codex oder Claude installieren Kopieren Sie diesen Prompt, fügen Sie ihn in Codex, Claude oder einen anderen Assistant ein und lassen Sie die Skill-Seite prüfen und installieren.

In Manus ausführen

Quelle

whichguy

whichguy/c-thru

GitHub-Repository öffnen Creator-Repositorys ansehen

Download

In Manus ausführen

Verwandte BerufeSOC

Basierend auf der SOC-Berufsklassifikation

SoftwareentwicklerInformatik- und Mathematikberufe·SOC 15-1252

SKILL.md

readonly

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

logical-gearbox

Use this format to visualize the 'Internal Gearbox' of a complex discovery/resolution loop.

Visual Schema

[PHASE 🔵: EPISTEMIC AUDIT] 🛡️

Represents the Phase 0 gate.
Colors: 🔵 Blue = Booting/Auditing.

[PHASE 🟡: THE RATIONALIZER] ⚙️

Represents the Inquiry Graph and Backlog calculation.
Colors: 🟡 Yellow = Processing/Thinking.

[PHASE 🟣: INSTRUMENTAL ACTION] 🛠️

Represents the actual tool execution.
Colors: 🟣 Purple = Acting.

[PHASE 🟢: SSoT SYNC] 💾

Represents the state file update and wiki contribution.
Colors: 🟢 Green = Persisting Memory.

[PHASE 🔴: THE PARITY SHIELD] 🛡️

Represents the final logical consistency check.
Colors: 🔴 Red = Terminating/Verifying.

Rendering Protocol

Map State: Identify which logical block the agent is in.
Trace Inquiry: Show the "Expected Information Gain" for the turn.
Audit Grounding: Link the current turn to an Evidence ID.

Mehr aus diesem Repository

gleiches Repository

Agentic infrastructure control for c-thru. Interrogate the proxy for hardware status, active models, and connectivity health. Dynamically switch routing modes (connected, offline, etc.) using natural language prompts.

2026-06-130

review-fix

whichguy/c-thru

Iterative review-fix loop: routes each file to the appropriate reviewer (code-reviewer, gas-code-review, gas-ui-review, gas-gmail-cards), applies Fix blocks, rechecks until clean (max 5 rounds), then commits/PRs. commit_mode="pr" (default): commit + push + PR + squash merge + delete branch. commit_mode="commit": commit only (POST_IMPLEMENT pipeline). Git fallback: WIP → last commit when target_files empty. **AUTOMATICALLY INVOKE** after implementing features, fixing bugs, before committing, or after plan implementation completes (user approves + all changes made). **STRONGLY RECOMMENDED** before merging to main, after refactoring, and when code-reviewer returns NEEDS_REVISION. Trigger phrases: "review and fix", "polish this", "clean this up", "make sure this is good", "before committing", "before merging", "loop until clean".

2026-06-110

review-plan

whichguy/c-thru

Universal plan review: 3 layers (general quality, code change quality, ecosystem specialization). Invokes gas-plan for GAS plans or node-plan for Node.js/TypeScript plans, conditionally based on detected patterns. AUTOMATICALLY INVOKE when: - MANDATORY_PRE_EXIT_PLAN directive applies (before ExitPlanMode) - User says "review plan", "check plan", "plan ready?" - Any plan file needs review (GAS or non-GAS) NOT for: Code review of existing files (use /gas-review or /review-fix)

2026-06-110

update-model-research

whichguy/c-thru

Research and update docs/local-model-prompt-techniques.md with latest community findings, Ollama version-specific fixes, and authoritative corrections for all local models in config/model-map.json. Scope: client-observable behavior through the Ollama API — prompting patterns, request parameters, response format, tool-calling behavior, dangers, and best practices. Internal server mechanics and deployment configuration are out of scope unless they directly explain a client-visible API behavior. Spawns parallel research agents per model family, applies a strict citation and confidence standard, and writes a diff-summary of changes. Invoked as /update-model-research [--model <family>] [--section <topic>]

2026-06-110

c-thru-plan

whichguy/c-thru

Agentic plan/wave orchestrator. Breaks any task into a wave-based execution plan, drives waves to completion, and tracks state in ${TMPDIR:-/tmp}/c-thru/<repo>/<slug>/. Invoked as /c-thru-plan <user intent>.

2026-05-080

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

logical-gearbox

Use this format to visualize the 'Internal Gearbox' of a complex discovery/resolution loop.

Visual Schema

[PHASE 🔵: EPISTEMIC AUDIT] 🛡️

Represents the Phase 0 gate.
Colors: 🔵 Blue = Booting/Auditing.

[PHASE 🟡: THE RATIONALIZER] ⚙️

Represents the Inquiry Graph and Backlog calculation.
Colors: 🟡 Yellow = Processing/Thinking.

[PHASE 🟣: INSTRUMENTAL ACTION] 🛠️

Represents the actual tool execution.
Colors: 🟣 Purple = Acting.

[PHASE 🟢: SSoT SYNC] 💾

Represents the state file update and wiki contribution.
Colors: 🟢 Green = Persisting Memory.

[PHASE 🔴: THE PARITY SHIELD] 🛡️

Represents the final logical consistency check.
Colors: 🔴 Red = Terminating/Verifying.

Rendering Protocol

Map State: Identify which logical block the agent is in.
Trace Inquiry: Show the "Expected Information Gain" for the turn.
Audit Grounding: Link the current turn to an Evidence ID.