corvus-control

Route cstar commands and workflows across Node.js and Python dispatchers.

Updated Jan 31, 2026
One-click install
npx skills add https://github.com/Clinscott/CStar --skill corvus-control
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: corvus-control
Source: https://github.com/Clinscott/CStar/tree/main/.agent/skills/corvus-control
Command: npx skills add https://github.com/Clinscott/CStar --skill corvus-control

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) components.

What problem does it solve?

Orchestrates cross-engine command routing and workflow orchestration for the Corvus Star framework, enabling consistent dispatch across Node.js and Python and persisting learning state.

Core Features & Use Cases

  • Resolve commands to the correct engine (Node.js for start, dominion, odin, ravens; Python for lets-go, run-task, investigate, etc.)
  • Execute workflows by loading context from .agent/workflows and updating memory or task state as required by the workflow handshake
  • Monitor health and learning: check Ravens status, trigger investigation workflows when tasks fail, and ensure changes go through Gungnir Matrix checks.

Quick Start

Instruct the agent to resolve a cstar command or start a lets-go workflow.

Frequently Asked Questions about corvus-control

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

FAQPage Schema
How do I route workflow commands across Node.js and Python dispatchers?

Cross-engine command routing resolves cstar commands to the correct engine, directing Node.js tasks like start and dominion, and Python tasks like lets-go or run-task, through a resolver-based mechanism for consistent execution.

How does workflow orchestration read context and persist progress during a handshake?

Workflow orchestration loads context from .agent/workflows and persists progress by updating tasks.qmd or memory.qmd, ensuring state is maintained during the execution handshake across Node.js and Python dispatchers.

Can I use this to trigger investigation workflows when tasks fail?

Yes, you can trigger investigation workflows when tasks fail. The system monitors health by checking Ravens status and ensures changes pass through Gungnir Matrix checks to maintain workflow integrity.

What is the best way to execute a lets-go workflow across different engines?

To execute a lets-go workflow, instruct the agent to start the process. The resolver-based command resolution automatically routes it to the Python dispatcher and loads the required context from .agent/workflows.

Do I need the Corvus Star framework to use resolver-based command resolution?

Yes, resolver-based command resolution is designed specifically for the Corvus Star framework to orchestrate cross-engine dispatch, apply cstar commands, and manage workflow state during the handshake.

Why does my ravens status check not update the task state?

Ravens status checks update task state by persisting progress in tasks.qmd or memory.qmd. If the workflow context from .agent/workflows is not loaded correctly, the handshake fails to persist learning state.