skill-orchestrator

Name: skill-orchestrator
Author: benbrastmckie

Engineering Community

Repo stars 435
Author updated Live
Author repo nvim

Fluxly profile Facts only: domain, agents, trust score, runtime, permissions and network

Domain: Engineering
Compatible agents: Claude Code
Cursor
Cline
Codex
Windsurf
Gemini CLI

+20
Trust score: 88 / 100 · community maintained
Author / version / license: @benbrastmckie · no license declared
Token usage: Lean
Setup complexity: Guided setup
External API key: Not required
Operating systems: Unspecified (assume cross-platform)
Runtime requirements: No special requirements
Permissions: Read-only
Write / modify
Shell exec
Network behavior: Local-only
Install commands: 26 variants

Profile is derived at build time from SKILL.md and install vectors. Subject to drift from author intent.

Heads up: 未限定 allowed-tools，默认拥有全部工具权限。

Output preview skill-orchestrator.preview

---
name: skill-orchestrator
description: Route commands to appropriate workflows based on task type and status. Invoke when executing /ta…
category: engineering
runtime: no special runtime
---

# skill-orchestrator output preview

## PART A: Task fit
- Use case: Route commands to appropriate workflows based on task type and status. Invoke when executing /task, /research, /plan, /implement commands. Central routing intelligence for the task management system. runs entirely locally. Works with Claude Code, Cursor, Cline and 23 more..
- Inputs: target material, constraints, expected output, and acceptance criteria.
- Evidence boundary: follow “Context Loading / Trigger Conditions / Core Responsibilities” and do not present inference as author intent.

## PART B: Execution result
- **01** The card summarizes the use case; runtime output centers on “Route commands to appropriate workflows based on task type and status. Invoke when executing /task, /research, /plan, /implement commands. Central routing intelligence for the task management system. runs entirely locally. Works with Claude Code, Cursor, Cline and 23 more.”.
- **02** When the source has headings, the agent prioritizes “Context Loading / Trigger Conditions / Core Responsibilities” so the result follows the author’s structure.
- **03** Typical output includes task judgment, concrete steps, required commands or file edits, validation, and follow-up options.
- **04** Risk context follows the fingerprint: read files, write/modify files, run shell commands; mostly runs locally; usually needs no extra API key.

## Running Rules
- read files, write/modify files, run shell commands; mostly runs locally; usually needs no extra API key.
- Validate with a small sample before expanding scope.
- Return the result, validation criteria, and next iteration options.

SKILL.md SKILL.md

---
name: skill-orchestrator
description: Route commands to appropriate workflows based on task type and status. Invoke when executing /ta…
category: engineering
source: benbrastmckie/nvim
---

# skill-orchestrator

## When to use
- Route commands to appropriate workflows based on task type and status. Invoke when executing /task, /research, /plan…
- Use it when the task has clear inputs, repeatable steps, and validation criteria.

## What to provide
- Target material, scope, expected result, and forbidden changes.
- Whether network, commands, file writes, or external services are allowed.

## Execution rules
- Organize steps around “Context Loading / Trigger Conditions / Core Responsibilities” and keep inference separate from source facts.
- read files, write/modify files, run shell commands; mostly runs locally; usually needs no extra API key.
- Validate with a small sample before expanding the task.

## Output requirements
- Return the deliverable, key evidence, validation method, and next action.
- Mark missing information as unknown; do not invent commands, platforms, or dependencies.

Evidence boundary and execution chain

The author source anchors workflow facts; repository files anchor sources and commands; Fluxly only adds fit, limitations, and quality judgment.

skill "skill-orchestrator" {
  input      -> user goal + target files + boundaries + acceptance criteria
  context    -> Context Loading / Trigger Conditions / Core Responsibilities
  rules      -> SKILL.md triggers / order / output contract
  runtime    -> no special runtime | read files, write/modify files, run shell commands | mostly runs locally
  guardrails -> usually needs no extra API key + small-sample validation + diff/log review
  output     -> copyable result + checklist + next iteration
}

Interpretation is structured for decision-making; original keeps the upstream SKILL.md unchanged.

Decide Fit First

Core job: Route commands to appropriate workflows based on task type and status. Invoke when executing /task, /research, /plan, /implement…
Best fit: Use it when the task has reusable inputs, steps, and validation criteria rather than a one-off answer.
Avoid forcing it: If the source lacks commands, platform support, or external-service evidence, keep those fields unknown instead of guessing.

Design Intent

Structure: The skill is organized around “Context Loading”, “Trigger Conditions”, “Core Responsibilities”, “1. Task Lookup”, showing how the author expects the agent to judge fit, collect context, and produce verifiable output.
Trigger evidence: Prioritize the author’s wording around when to use it, what context to collect, and what output shape to produce.
Evidence boundary: Author text states facts, repository files prove commands and paths, and Fluxly only adds fit, limits, and usage judgment.

How To Use It

Inputs: Provide target material, scope, expected result, forbidden changes, and validation method.
Invocation: Name skill-orchestrator directly; if the source includes slash commands, start with the command and then add task context.
Validation: Start small and check whether the result follows “Context Loading / Trigger Conditions / Core Responsibilities” before expanding.

Boundaries And Review

Dependencies: It usually needs no extra API key, so start with a small validation task.
Permissions: Declared permissions include read / write / shell-exec; ask the agent to state file, command, and rollback boundaries before acting.
Quality bar: A useful result names the deliverable, evidence, and next action. Generic prose means the task needs tighter context.

Orchestrator Skill

Central routing intelligence for the task management system.

Context Loading

Load context on-demand when needed:

@.opencode/context/orchestration/orchestration-core.md - Routing, delegation, session tracking
@.opencode/context/orchestration/state-management.md - Task lookup and status validation
@.opencode/context/index.json - Full context discovery index

Trigger Conditions

This skill activates when:

A slash command needs task-type-based routing
Task context needs to be gathered before delegation
Multi-step workflows require coordination

Core Responsibilities

1. Task Lookup

Given a task number, retrieve full context:

1. Read specs/state.json
2. Find task by project_number
3. Extract: task_type, status, project_name, description, priority
4. Read TODO.md for additional context if needed

2. Task-Type-Based Routing

Route to appropriate skill based on task type:

Task Type	Research Skill	Implementation Skill
general	skill-researcher	skill-implementer
meta	skill-researcher	skill-implementer
markdown	skill-researcher	skill-implementer

Note: Additional languages (latex, typst) are available via extensions in .opencode/extensions/.

3. Status Validation

Before routing, validate task status is not terminal:

if status in [completed, abandoned, expanded]:
  ABORT "Task is in terminal state [$status]"

All operations (research, plan, implement, revise) are allowed from any non-terminal status.

4. Context Preparation

Prepare context package for delegated skill:

{
  "task_number": 259,
  "task_name": "task_slug",
  "task_type": "general",
  "status": "planned",
  "description": "Full task description",
  "artifacts": {
    "research": ["path/to/research.md"],
    "plan": "path/to/plan.md"
  },
  "focus_prompt": "Optional user-provided focus"
}

Execution Flow

1. Receive command context (task number, operation type)
2. Lookup task in state.json
3. Validate status for operation
4. Determine target skill by task_type
5. Prepare context package
6. Invoke target skill via Task tool
7. Receive and validate result
8. Return result to caller

Return Format

{
  "status": "completed|partial|failed",
  "routed_to": "skill-name",
  "task_number": 259,
  "result": {
    "artifacts": [],
    "summary": "..."
  }
}

Error Handling

Task not found: Return clear error with suggestions
Invalid status: Return error with current status and allowed operations
Skill invocation failure: Return partial result with error details

MUST NOT (Postflight Boundary)

After routing to a skill, this skill MUST NOT:

Edit source files - All work is done by routed skills/agents
Run build/test commands - Verification is done by routed skills/agents
Update task status - Status updates are done by routed skills
Create artifacts - Artifact creation is done by routed skills/agents

The orchestrator is a routing-only skill. It:

Looks up task context
Routes to appropriate skill based on task_type
Passes through the routed skill's return

Reference: @.opencode/context/standards/postflight-tool-restrictions.md

Install command

One-click installPick a runner, click Copy, paste into your terminal, press enter

npx skills add benbrastmckie/nvim/.opencode/skills/skill-orchestrator -y

Open general install guide

View skill source

Works with

Claude Code
Cursor
Cline
Codex
Windsurf
Gemini
OpenCode
Roo Code
AAide
+Augment
GitHub Copilot
OpenClaw
KKiro
Junie
WWarp
Goose
Trae
Kilo Code
OpenHands
Amp
Zencoder
CContinue
AIAider
CodeBuddy
CodeGeeX
Replit Agent

Security audit

88 / 100

Community

未声明 license/许可。
未声明 version。
未限定 allowed-tools，默认拥有全部工具权限。

Metadata

Source: github
benbrastmckie/nvim
中文

More by @benbrastmckie

Category & tags

Category Engineering