Loading...
Loading...
Found 45 Skills
Direct research projects by gathering team feedback and delegating implementation tasks. Writes publication-quality scientific text and coordinates bioinformaticians, software developers, and biologist commentators via technical-pm.
Session mode: act as orchestrator brain only. Research and implementation go to cheaper-model subagents; the orchestrator scopes, briefs, verifies, and judges. User-invoked with the task as the argument.
Delegate implementation work to the coder agent. Provide requirements or feature file path.
Use when the user explicitly asks to invoke another coding agent CLI as a subagent. Triggers include phrases like 'get a second opinion from Codex', 'have Gemini review this', 'run this through Claude Code', 'ask another agent', or 'use a different model for this'. Supports Claude Code, Codex CLI, and Gemini CLI. Never invoke autonomously.
Delegate tasks to parallel worktree agents using worktrunk (wt). Use when asked to "spawn agents", "run in parallel", "delegate to worktrees", or split work across multiple Claude/OpenCode sessions.
Run fable-mode execution discipline on Claude Opus — the strongest staged run available. Routes the task to the @fable-orchestrator agent (Opus, Write-less), which stages the work, delegates artifact production to @fable-worker-sonnet / @fable-worker-haiku, and cold-checks deliverables with @fable-verifier. Trigger when the user explicitly asks for thorough/systematic/"deep work" handling on the strongest model ("fable on opus", "stage this on opus", "deep work mode, opus"). Do NOT use for ordinary single-pass tasks — and prefer fable-sonnet or fable-haiku when the task doesn't need peak reasoning.
Create and configure Claude Code subagents for specialized task delegation. Use when defining expert AI assistants with focused responsibilities, custom prompts, and specific tool permissions.
Coordinates project documentation creation. Gathers context once, detects project type, delegates to 5 L3 workers (ln-111-115). L2 Coordinator invoked by ln-100.
Use when executing multi-task plans where each task can be implemented independently by a subagent. Triggers when a plan has 3+ independent tasks, when speed of execution is important, when tasks have clear acceptance criteria suitable for delegation, or when two-stage review gates (spec compliance and code quality) are needed for iterative fix cycles.
Delegate a coding task to the Command Code CLI (`cmd`) as a background implementer, then review its diff and land it yourself. Use this whenever the user wants to hand implementation work to Command Code — phrasings like "have Command Code do X", "delegate this to commandcode", "run it through cmd", or "use Command Code to implement/fix/refactor" — or to run a queue of coding tasks through Command Code while staying the reviewer. DO NOT USE for tasks small enough to do inline, or when the user wants the code written directly without delegating.
Coordinate Codex sub-agents for substantial multi-step work. Requires Codex collaboration tools and the listed Luna, Terra, and Sol model families. Use proactively when a request involves two or more separable workstreams; repository exploration plus implementation or verification; production diagnosis across logs, code, and live systems; PR or release review; multi-source analytics or research; or long-running tests, transfers, workflows, and monitors that should not block user communication. Assign bounded leaf work to Luna and collaborative or high-stakes work to Terra or Sol. Skip only trivial single-step or tightly sequential tasks.
Community engagement coordinator: analyzes repo health, consults strategy, delegates to announcer/debater/triager