do

Name: do
Availability: InStock
Author: special-place-administrator

Route user intent to the cheapest capable orchestrator or skill.

Updated Mar 26, 2026

Search Tags:#automation #workflow #routing #cli #orchestration #skills-discovery #intent-classification

Ready to run

npx skills add https://github.com/special-place-administrator/citadel_codex --skill do-special-place-administrator

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: do
Source: https://github.com/special-place-administrator/citadel_codex/tree/main/skills/do
Command: npx skills add https://github.com/special-place-administrator/citadel_codex --skill do-special-place-administrator

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Classifies user input to determine the appropriate orchestrator or skill and routes execution to the most cost-effective path, eliminating manual tool selection.

Core Features & Use Cases

Automatic skill discovery: reads frontmatter from each installed SKILL.md to build a live routing registry.
Tiered routing: prefers direct actions, then single-skill routes, then complex orchestrators (marshal, archon, fleet) as needed.
Self-service management: supports status, list, and direct invocation for power users.

Quick Start

Tell do to handle it by saying 'do review my authentication module'.

Frequently Asked Questions about do

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

FAQPage Schema

How do I automate routing user intent to the right CLI tool or skill?▼

Automating intent routing involves classifying user input and directing execution to the cheapest capable orchestrator or skill. This unified router uses SKILL.md frontmatter to build live routing tables, eliminating manual tool selection across single-session or multi-skill campaigns.

What is intent classification for workflow orchestration and how does it work?▼

Intent classification for workflow orchestration determines the appropriate orchestrator or skill for a given task. It reads installed SKILL.md frontmatter to build a routing registry, applying tiered routing that prefers direct actions, then single-skill routes, then complex orchestrators.

Do I need a SKILL.md frontmatter for automatic skill discovery to work?▼

Yes, automatic skill discovery requires every installed skill to expose a SKILL.md frontmatter with name and description fields. The router reads this frontmatter to build live routing tables and provide fallback paths for cost-effective execution.

What is the best way to manage multi-skill campaigns without manual tool selection?▼

The best way to manage multi-skill campaigns is using a unified router that automatically discovers installed skills and routes execution to the most cost-effective path. It supports status checks, list views, and direct invocation for power users.

Can I use a unified router for single-session tasks and complex orchestration?▼

Yes, a unified router applies across single-session tasks to multi-skill campaigns. It uses tiered routing to escalate from direct actions to single-skill routes, and finally to complex orchestrators like marshal, archon, or fleet as needed.

Why does my automatic skill discovery fail to find installed orchestrators?▼

Automatic skill discovery fails when installed skills do not expose a SKILL.md frontmatter with valid name and description fields. The router requires this metadata to classify user intent, build routing tables, and execute fallback paths correctly.