Bridge Orchestration Gaps with the EC Compatibility Alias

Where this fits

You're pair-debugging a service in Claude Code and type /ec to start Cobbler's orchestration loop, but Claude doesn't resolve the command because the alias isn't installed. The ec skill short-circuits that problem: it's a lightweight compatibility surface that routes /ec requests directly to the installed Elves Cobbler instructions. It turns a missing command into a predictable entry point, so you can keep working without re-learning invocation details.

Why agents benefit

• Agents know exactly which path to take: ec tells Claude to use Cobbler's ## Cobbler section, avoiding ambiguous mode-mixing.
• It preserves read-only behavior for one-off questions, so agents don't accidentally mutate files during quick "what should I do?" prompts.
• For active runs, agents route through Cobbler-first coordination and use Claude Code subagents as independent lenses, producing multiple views of the same problem.
• The alias enforces the harness loop: capability scan, route and medium selection, context packet, evidence collection, and reclassification when new evidence changes the task.
• Since it's a compatibility alias, the underlying Elves skill remains the single source of truth, so maintenance stays centralized.

Practical scenarios

Quick Cobbler answer, stay stateless

A developer types /ec with a question like "What's the safest way to refactor this function?" The alias keeps the session read-only, avoids spawning agents, and returns a focused recommendation.

Multi-file implementation task

When a feature spans several files, /ec triggers the full harness loop. Cobbler selects the right medium and route, worker agents edit scoped files under normal Elves rules, and evidence is collected before the final answer is presented.

Using subagents for independent review

For a debugging session, /ec routes work through Cobbler-first coordination, then dispatches multiple Claude Code subagents to inspect logs, code, and tests in parallel. The agents' independent lenses are merged into a single evidence-backed conclusion.

Add it to your agent workflow

Install the alias with:

npx skills add aigorahub/elves --skill ec

Once installed, invoke it from Claude Code by simply typing:

/ec

For non-trivial tasks, the installed elves skill's harness loop takes over automatically—no extra flags or setup required.

Compare before adopting

Before committing, compare the ec alias against the full Elves skill itself and other orchestration skills. Check whether the alias is actively maintained (the 217-star repo is a good start), whether the underlying Cobbler model matches your workflow, and whether you need the full harness loop or just a thin routing layer. Also compare how often the prompt instructions change, because a stale alias will route to outdated logic.

Why it is worth tracking

The ec skill is worth tracking because it solves a real friction point: command invocations that don't map to installed orchestration logic. Its low complexity makes it a good canary for how the Elves ecosystem evolves—if the alias changes, the core Cobbler model likely changed too. Review it again when you update your agent skills or when Elves releases a new orchestration pattern. For a full breakdown of the skill's metadata and history, see the listing at https://www.openagentskill.com/skills/aigorahub-ec.