Team Agent Orchestration
affaan-m/ECC
Run team-based orchestration for agent squads: work items with owners and scope, agent Kanban state, branch isolation, control pane visibility, and merge gates.
Plan or coordinate CCF research stages, goals, gates, artifacts, and ccfa.yaml state.
MITAuto-check passed
Install Ccf Pipeline Orchestrator
$ npx skills add mikubaka88/CCFA-Skills --skill ccf-pipeline-orchestrator -a claude-codeProject install by default; add -g for ~/.claude/skills/.
$ gh skill install mikubaka88/CCFA-Skills ccf-pipeline-orchestrator --agent claude-codeProject scope by default; add --scope user for a personal install. Needs GitHub CLI 2.90.0 or later (public preview).
$ git clone --depth 1 https://github.com/mikubaka88/CCFA-Skills.git skills-src && mkdir -p .claude/skills && cp -r skills-src/ccf-pipeline-orchestrator .claude/skills/ccf-pipeline-orchestrator && rm -rf skills-srcUse ~/.claude/skills/ instead of .claude/skills for a personal install. The folder must contain SKILL.md.
Claude Code skills documentation · loads skills from .claude/skills/
Install the "ccf-pipeline-orchestrator" agent skill from https://github.com/mikubaka88/CCFA-Skills/tree/main/ccf-pipeline-orchestrator into .claude/skills/ccf-pipeline-orchestrator/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "ccf-pipeline-orchestrator", then confirm the skill loads.Claude Code copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$skill-installer install https://github.com/mikubaka88/CCFA-Skills/tree/main/ccf-pipeline-orchestratorType this inside Codex. $skill-installer <name> installs a curated skill from openai/skills. The installer writes to $CODEX_HOME/skills (default ~/.codex/skills). Restart Codex if the skill does not show up.
$ npx skills add mikubaka88/CCFA-Skills --skill ccf-pipeline-orchestrator -a codexProject install goes to .agents/skills/; add -g for ~/.codex/skills/.
$ gh skill install mikubaka88/CCFA-Skills ccf-pipeline-orchestrator --agent codexProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/mikubaka88/CCFA-Skills.git skills-src && mkdir -p .agents/skills && cp -r skills-src/ccf-pipeline-orchestrator .agents/skills/ccf-pipeline-orchestrator && rm -rf skills-srcUse ~/.agents/skills/ instead of .agents/skills for a personal install.
Codex skills documentation · loads skills from .agents/skills/
Install the "ccf-pipeline-orchestrator" agent skill from https://github.com/mikubaka88/CCFA-Skills/tree/main/ccf-pipeline-orchestrator into .agents/skills/ccf-pipeline-orchestrator/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "ccf-pipeline-orchestrator", then confirm the skill loads.Codex copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ npx skills add mikubaka88/CCFA-Skills --skill ccf-pipeline-orchestrator -a cursorProject install goes to .agents/skills/; add -g for ~/.cursor/skills/.
$ gh skill install mikubaka88/CCFA-Skills ccf-pipeline-orchestrator --agent cursorProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/mikubaka88/CCFA-Skills.git skills-src && mkdir -p .cursor/skills && cp -r skills-src/ccf-pipeline-orchestrator .cursor/skills/ccf-pipeline-orchestrator && rm -rf skills-srcUse ~/.cursor/skills/ instead of .cursor/skills for a personal install.
Cursor skills documentation · loads skills from .cursor/skills/, .agents/skills/, .claude/skills/, .codex/skills/
Install the "ccf-pipeline-orchestrator" agent skill from https://github.com/mikubaka88/CCFA-Skills/tree/main/ccf-pipeline-orchestrator into .cursor/skills/ccf-pipeline-orchestrator/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "ccf-pipeline-orchestrator", then confirm the skill loads.Cursor copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ gemini skills install https://github.com/mikubaka88/CCFA-Skills.git --path ccf-pipeline-orchestrator--scope user (default) or --scope workspace; --path is the subfolder of the repo that holds the skill; --consent skips the security confirmation prompt.
$ npx skills add mikubaka88/CCFA-Skills --skill ccf-pipeline-orchestrator -a gemini-cliProject install goes to .agents/skills/; add -g for ~/.gemini/skills/.
$ gh skill install mikubaka88/CCFA-Skills ccf-pipeline-orchestrator --agent gemini-cliProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/mikubaka88/CCFA-Skills.git skills-src && mkdir -p .gemini/skills && cp -r skills-src/ccf-pipeline-orchestrator .gemini/skills/ccf-pipeline-orchestrator && rm -rf skills-srcUse ~/.gemini/skills/ instead of .gemini/skills for a personal install, then run /skills reload.
Gemini CLI skills documentation · loads skills from .gemini/skills/, .agents/skills/
Install the "ccf-pipeline-orchestrator" agent skill from https://github.com/mikubaka88/CCFA-Skills/tree/main/ccf-pipeline-orchestrator into .gemini/skills/ccf-pipeline-orchestrator/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "ccf-pipeline-orchestrator", then confirm the skill loads.Gemini CLI copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ gh skill install mikubaka88/CCFA-Skills ccf-pipeline-orchestratorInstalls for Copilot at project scope by default; add --scope user for a personal install. Preview a skill first with gh skill preview. Needs GitHub CLI 2.90.0 or later (public preview).
$ npx skills add mikubaka88/CCFA-Skills --skill ccf-pipeline-orchestrator -a github-copilotProject install goes to .agents/skills/; add -g for ~/.copilot/skills/.
$ git clone --depth 1 https://github.com/mikubaka88/CCFA-Skills.git skills-src && mkdir -p .github/skills && cp -r skills-src/ccf-pipeline-orchestrator .github/skills/ccf-pipeline-orchestrator && rm -rf skills-srcUse ~/.copilot/skills/ instead of .github/skills for a personal install. Commit .github/skills so cloud agent and code review can use it.
GitHub Copilot skills documentation · loads skills from .github/skills/, .claude/skills/, .agents/skills/
Install the "ccf-pipeline-orchestrator" agent skill from https://github.com/mikubaka88/CCFA-Skills/tree/main/ccf-pipeline-orchestrator into .github/skills/ccf-pipeline-orchestrator/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "ccf-pipeline-orchestrator", then confirm the skill loads.GitHub Copilot copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ npx skills add mikubaka88/CCFA-Skills --skill ccf-pipeline-orchestrator -a opencodeOpenCode documents no install command of its own. Project install goes to .agents/skills/; add -g for ~/.config/opencode/skills/.
$ gh skill install mikubaka88/CCFA-Skills ccf-pipeline-orchestrator --agent opencodeProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/mikubaka88/CCFA-Skills.git skills-src && mkdir -p .opencode/skills && cp -r skills-src/ccf-pipeline-orchestrator .opencode/skills/ccf-pipeline-orchestrator && rm -rf skills-srcUse ~/.config/opencode/skills/ instead of .opencode/skills for a personal install.
OpenCode skills documentation · loads skills from .opencode/skills/, .claude/skills/, .agents/skills/
Install the "ccf-pipeline-orchestrator" agent skill from https://github.com/mikubaka88/CCFA-Skills/tree/main/ccf-pipeline-orchestrator into .opencode/skills/ccf-pipeline-orchestrator/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "ccf-pipeline-orchestrator", then confirm the skill loads.OpenCode copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
Facts
- Skill name
ccf-pipeline-orchestrator- GitHub stars
- 3k
- Token cost
- ~1.4k tokens
- SKILL.md length
- 622 words
- Files
- 5 (incl. references)
- Skills in repo
- 17
- Repo updated
- First seen
- Licence
- MIT
At a glance
Plan or coordinate CCF research stages, goals, gates, artifacts, and ccfa.yaml state.
- Works in 7 steps: Identify target venue, current stage,… → Read ccfa.yaml when available; if… → For unclear projects, use… → …
- Explicitly requested end-to-end coordination
- SKILL.md covers Family File Contract, Collaboration Contract, Core Rule and Workflow, plus 1 more section
- Instructions only: no scripts, shell commands, URLs or credentials in SKILL.md
What it does
Ccf Pipeline Orchestrator is an agent skill from mikubaka88/CCFA-Skills. Plan or coordinate CCF research stages, goals, gates, artifacts, and ccfa.yaml state. Use for 任务拆解, 流程规划, project status, and explicitly requested end-to-end coordination. Specialist skills own research outputs; ccf-project-scaffolder owns folder/template creation.
Its SKILL.md is about 1.4k tokens, which your agent loads only when the skill is triggered. The skill folder holds 7 other files, including reference files (for example `agents/openai.yaml`, `references/workflow-planning/approach-options.md` and `references/workflow-planning/design-brief-template.md`).
The repository describes itself as: A skill family for shaping the research storyline of CCF-A papers. The licence is MIT.
When your agent uses it
- Explicitly requested end-to-end coordination
Example prompts
- “/ccf-pipeline-orchestrator”
Workflow steps
7 steps, taken from the first numbered list in SKILL.md.
- Identify target venue, current stage, available artifacts, constraints, deadline pressure, and the user's immediate goal.
- Read ccfa.yaml when available; if absent, continue with supplied artifacts. Do not require setup or create project state merely to route…
- For unclear projects, use references/workflow-planning/intake-protocol.md, approach-options.md, and design-brief-template.md.
- Assign integrating owners using ../ccf-common/references/routing.md. Work backward from the requested outcome to missing prerequisites and…
- Define each applicable gate through its required evidence, output, pass condition, blocker, and responsible skill. Mark prerequisites…
- Use the continuity/return contract in ../ccf-common/references/handoff-modes.md: carry current scope, evidence/version, canonical paths…
- Integrate specialist results, resolve conflicts against source evidence, and check affected downstream conclusions. Advance gates from…
What it can do on your machine
Read from SKILL.md and the folder at commit 5969e6b. It shows what the files ask for, not the result of running them.
Tool permissions
Pre-approves nothing: there is no allowed-tools line, so your agent's usual permission prompts apply.
From allowed-tools in the SKILL.md frontmatter.
Runs code
No scripts in the folder and no shell commands in SKILL.md.
From the folder's file list and the shell code blocks in SKILL.md.
Network
No URLs in SKILL.md.
From URLs in SKILL.md, links to its own repository left out.
Credentials
Names no API keys, tokens, secrets or passwords.
From names ending in _API_KEY, _TOKEN, _SECRET, _KEY or _PASSWORD in SKILL.md.
Context cost
Ccf Pipeline Orchestrator loads about 1.4k tokens when it runs, and up to ~3.1k if it reads all its reference files. Until then it costs about 73 tokens; SKILL.md has 622 words of instructions outside code blocks.
Estimates: characters ÷ 4, the usual rule of thumb; real counts depend on the model's tokenizer. Scripts and assets cost tokens only if the agent reads them.
Safety
Auto-check passed
The automated check found no risky patterns in SKILL.md.
Automated static check — not a guarantee. Review scripts before installing. It scans the text of SKILL.md for risky patterns (piping downloads into a shell, reading credential files, hidden Unicode, destructive commands); files beside SKILL.md are not scanned.
SKILL.md
The full file from mikubaka88/CCFA-Skills at commit 5969e6b, republished under its MIT licence (© mikubaka88). 622 words, ~1,437 tokens.
Download SKILL.mdSave it as
.claude/skills/ccf-pipeline-orchestrator/SKILL.md (or your agent's skills folder). This skill also uses 4 other files; get the full folder from GitHub.- name
- ccf-pipeline-orchestrator
- description
- Plan or coordinate CCF research stages, goals, gates, artifacts, and ccfa.yaml state. Use for 任务拆解, 流程规划, project status, and explicitly requested end-to-end coordination. Specialist skills own research outputs; ccf-project-scaffolder owns folder/template creation.
CCF Pipeline Orchestrator
Family File Contract
Before writing, resolve the canonical output and one stable working directory per task/artifact. Reuse explicit or established task paths; otherwise use project-root ccfa-workfiles/<purpose>/<artifact-id>/, with source/, assets/, cache/, and build/ only as needed. Update current files in place; do not scatter intermediates or create iteration copies. Preserve inputs and required evidence; clean only verified disposable files created by this task. Use UTF-8 text I/O and check Chinese text after saving or rendering. For file work, apply artifact-contracts.md and reuse the same paths across skill transitions.
Collaboration Contract
Before specialist execution, read and apply ccf-humanization first, then ccf-common. At every handoff, reuse their applicable active rules or refresh missing/changed ones. Both preflights are required even without prose; detailed editing, experiment, and maintenance modes run only when relevant.
Keep one integrating owner and actively use other skills to resolve missing prerequisites or check material findings. Reuse applicable evidence; do not skip necessary groundwork to save tokens. Before finalizing, integrate contributions and verify affected results. Follow the conditional cooperation routes; avoid unrelated stages and duplicate reports.
Core Rule
Operate as the project coordinator and workflow planner. Clarify the goal, map the current stage, update or read ccfa.yaml, define gates, and name the next owner skill. Specialist skills own downstream outputs. For a plan-only request, return the plan. For explicitly requested end-to-end execution, coordinate the authorized owners through completion rather than stopping after naming the next skill. Follow ../ccf-common/references/task-modes.md: if the user asks for a short plan, checklist, YAML update, table, or narrative roadmap, use that visible shape instead of forcing a fixed report.
Ensure Humanization and Common are active before planning and every contributing skill. Reuse their applicable rules at handoffs. Apply Humanization's detailed prose modes within authorized writing stages; raw planning and rendering still receive its baseline without a manuscript-edit workflow.
Follow ../ccf-common/references/handoff-modes.md and ../ccf-common/references/artifact-contracts.md. Later user corrections normally steer the active project: preserve valid completed work, update affected requirements, and continue. Do not invent completed stages or automatic background jobs.
Show full SKILL.md (288 more words)Show less
Workflow
- Identify target venue, current stage, available artifacts, constraints, deadline pressure, and the user's immediate goal.
- Read
ccfa.yamlwhen available; if absent, continue with supplied artifacts. Do not require setup or create project state merely to route work; disclose its absence only when it limits requested tracking. - For unclear projects, use
references/workflow-planning/intake-protocol.md,approach-options.md, anddesign-brief-template.md. - Assign integrating owners using
../ccf-common/references/routing.md. Work backward from the requested outcome to missing prerequisites and material checks, including upstream work not named by the user. Distinguish bounded contributions from next-artifact ownership; carry both active preflights throughout and apply detailed Humanization modes when relevant. Preserve explicit scope limits. - Define each applicable gate through its required evidence, output, pass condition, blocker, and responsible skill. Mark prerequisites satisfied, missing, conflicting, or outside scope; reuse valid ones and resolve missing/conflicting ones before advancing dependent conclusions. Tool completion alone does not pass a gate.
- Use the continuity/return contract in
../ccf-common/references/handoff-modes.md: carry current scope, evidence/version, canonical paths, edit ownership, and the exact next action. Update existingccfa.yamlstage/gate fields only when state maintenance is authorized; preserve unrelated fields and schema. A planning-only request proposes changes without writing. - Integrate specialist results, resolve conflicts against source evidence, and check affected downstream conclusions. Advance gates from actual evidence; preserve valid completed work and continue independent stages around a blocker. Reopen only changed dependencies or unresolved findings. Finish when requested outputs and applicable prerequisites/checks are complete, or identify the precise dependent result that remains incomplete.
Adaptive Output Contract
Put the requested artifact first: roadmap, next-step decision, task list, handoff packet, or ccfa.yaml patch instructions. Use the full structure below only for standard planning, ambiguous multi-stage projects, or when the user asks for a complete coordination report.
Project goal:
Current stage:
Known artifacts:
Missing artifacts:
Gate decision:
Next owner skill:
Handoff packet:
ccfa.yaml update:
Risks / blockers:© mikubaka88, MIT. Rendered from Markdown: HTML in the file is shown as text, images as links, and headings moved down two levels. Raw file
Files
SKILL.md and 4 other files (references) in ccf-pipeline-orchestrator of mikubaka88/CCFA-Skills.
- SKILL.md
- agents/openai.yaml
- references/workflow-planning/approach-options.md
- references/workflow-planning/design-brief-template.md
- references/workflow-planning/intake-protocol.md
Open the folder on GitHubat commit 5969e6b
Compare with similar skills
Ccf Pipeline Orchestrator next to the 5 skills that share the most tags, products or categories with it. Stars are the repository's; “used in” counts other GitHub owners with a copy.
| Skill | Stars | Used in | Tokens | Auto-check | Licence | Repo updated |
|---|---|---|---|---|---|---|
| Ccf Pipeline Orchestrator this skillmikubaka88/CCFA-Skills | 3k | — | ~1.4k | Automated safety check: Pass | MIT | |
| Team Agent Orchestrationaffaan-m/ECC | 277k | 1 repos | ~1.2k | Automated safety check: Pass | MIT | |
| Orchestratesickn33/agentic-awesome-skills | 47k | 1 repos | ~692 | Automated safety check: Pass | MIT | |
| Goalscodewhale-hq/Codewhale | 41k | — | ~273 | Automated safety check: Pass | MIT | |
| Cursor Orchestratecursor/plugins | 11k | — | ~1.1k | Automated safety check: Pass | None | |
| Orca Orchestrationstablyai/orca | 89k | — | ~916 | Automated safety check: Pass | MIT |
Similar skills
Orchestrate
sickn33/agentic-awesome-skills
Coordinate focused subagents on substantial work, keep their ownership non-overlapping, and integrate verified results.
Goals
codewhale-hq/Codewhale
Set, review, and update the user's goals. An agent skill from codewhale-hq/Codewhale.
- Official
Cursor Orchestrate
cursor/plugins
Splits a large goal into a tree of parallel Cursor cloud agents, with planners, workers and verifiers coordinated by a script and reporting through structured handoffs.
Orca Orchestration
stablyai/orca
Coordinate supervised Orca workers: threaded messages, blocking ask/reply, task dispatch, worker_done/escalation waits, task DAGs, decision gates, coordinator…
Agent Orchestrator Task
ruvnet/ruflo
Agent skill for orchestrator-task - invoke with $agent-orchestrator-task
More from mikubaka88/CCFA-Skills
All 17 skills in this repoCcf Paper Reviewer
mikubaka88/CCFA-Skills
Review manuscript claims, evidence, and writing without rewriting.
Ccf Rebuttal Writer
mikubaka88/CCFA-Skills
Write CCF rebuttals, author responses, revision ledgers, response letters, and conservative resubmission plans.
Ccf Common
mikubaka88/CCFA-Skills
Required shared preflight for every CCFA skill after ccf-humanization: apply routing, scope, prerequisites, evidence rules, handoffs, and artifact contracts.
Ccf Experiment Designer
mikubaka88/CCFA-Skills
Design CCF experiment protocols and evidence schemas: datasets, baselines, metrics, ablations, and result-table contents.
Ccf Humanization
mikubaka88/CCFA-Skills
Required first preflight before every CCFA skill, including research, review, retrieval, experiments, visuals, and maintenance.
Ccf Literature Monitor
mikubaka88/CCFA-Skills
Scan recent arXiv/OpenReview papers, venue feeds, labs, and competitors for overlap.
Questions about Ccf Pipeline Orchestrator
What does Ccf Pipeline Orchestrator do?
Plan or coordinate CCF research stages, goals, gates, artifacts, and ccfa.yaml state. Ccf Pipeline Orchestrator is an agent skill from mikubaka88/CCFA-Skills.yaml state.
When should I use Ccf Pipeline Orchestrator?
Ccf Pipeline Orchestrator fits situations like: explicitly requested end-to-end coordination.
How do I install Ccf Pipeline Orchestrator in Claude Code?
Run `npx skills add mikubaka88/CCFA-Skills --skill ccf-pipeline-orchestrator -a claude-code`. Or copy the skill folder (ccf-pipeline-orchestrator in mikubaka88/CCFA-Skills) into .claude/skills/ccf-pipeline-orchestrator in your project. Claude Code loads it when a task matches its description.
How do I install Ccf Pipeline Orchestrator in Codex?
Run `npx skills add mikubaka88/CCFA-Skills --skill ccf-pipeline-orchestrator -a codex`. Or copy the skill folder (ccf-pipeline-orchestrator in mikubaka88/CCFA-Skills) into .agents/skills/ccf-pipeline-orchestrator in your project. Codex loads it when a task matches its description.
Can I use Ccf Pipeline Orchestrator in Cursor, Gemini CLI or GitHub Copilot?
Cursor, Gemini CLI, GitHub Copilot and OpenCode also load SKILL.md folders. With the skills CLI, run `npx skills add mikubaka88/CCFA-Skills --skill ccf-pipeline-orchestrator -a cursor` (or -a gemini-cli, github-copilot or opencode for the others). To copy it by hand, put the folder in .cursor/skills/ccf-pipeline-orchestrator, .gemini/skills/ccf-pipeline-orchestrator, .github/skills/ccf-pipeline-orchestrator and .opencode/skills/ccf-pipeline-orchestrator in your project.
What does Ccf Pipeline Orchestrator need to run?
SKILL.md names no scripts, command-line tools or credentials: Ccf Pipeline Orchestrator is instructions for the agent only.
Does Ccf Pipeline Orchestrator access the network?
SKILL.md contains no URLs. Any network use would come from the scripts or tools the agent runs. This is read from the text; nothing was executed.
Is Ccf Pipeline Orchestrator safe to install?
Our automated static check of SKILL.md found no risky patterns, such as piping downloads into a shell, reading credential files or hidden Unicode. It is not a guarantee. Review the folder before installing.
What licence does Ccf Pipeline Orchestrator use?
Ccf Pipeline Orchestrator is published under the MIT licence (the repository's licence). It allows redistribution, so the full SKILL.md is shown on this page.
How many tokens does Ccf Pipeline Orchestrator use?
About 1.4k tokens (SKILL.md is roughly 5.7k characters). Agents keep only the skill's name and description in context until a task matches; then they load SKILL.md in full. Its references folder adds about 1.7k tokens, read only when the agent opens those files.
What are the alternatives to Ccf Pipeline Orchestrator?
Skills that share tags, products or a category with Ccf Pipeline Orchestrator: Team Agent Orchestration (affaan-m/ECC, 277k stars), Orchestrate (sickn33/agentic-awesome-skills, 47k stars), Goals (codewhale-hq/Codewhale, 41k stars) and Cursor Orchestrate (cursor/plugins, 11k stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.
Who maintains Ccf Pipeline Orchestrator?
mikubaka88 (a GitHub user) maintains it in mikubaka88/CCFA-Skills, which has 3,015 GitHub stars. The repository holds 17 skills in this directory. The repository was last updated on September 16, 2026.
Source: mikubaka88/CCFA-Skills on GitHub. Facts on this page come from the repository at the commit we read; the author's words are quoted as theirs.