SkillsAdd

mikubaka88/ccfa-skills

ccf-pipeline-orchestrator

Plan or coordinate CCF research stages, goals, gates, artifacts, and ccfa.yaml state.

Trending #2517 Hot #6320 First seen Jun 10, 2026

Installation

$ npx skills add mikubaka88/ccfa-skills --skill ccf-pipeline-orchestrator
View on skills.sh ↗ GitHub repository ↗

Summary

  • 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.

Similar popular skills

Related neighbors and high-traction skills in the same topics — useful to compare before installing.

find-skills Same topic
vercel-labs/skills

Helps users discover and install agent skills when they ask questions like "how do I do X", "fi…

3.3M installs
agent-browser Same topic
vercel-labs/agent-browser

Browser automation CLI for AI agents. Use when the user needs to interact with websites, includ…

810.4K installs
vercel-react-best-practices Same topic
vercel-labs/agent-skills 697.8K installs
web-design-guidelines Same topic
vercel-labs/agent-skills

Review UI code for Web Interface Guidelines compliance. Use when asked to "review my UI", "chec…

617.3K installs
microsoft-foundry Same topic
microsoft/azure-skills

Build, deploy, evaluate, optimize, fine-tune, and manage Microsoft Foundry agents, models, and …

576.5K installs
azure-prepare Same topic
microsoft/azure-skills

Prepare azd-based Azure projects for deployment: generates azure.yaml, infrastructure (Bicep/Te…

568.3K installs

Also in this package

Other skills from mikubaka88/ccfa-skills · top by installs.

npx skills add mikubaka88/ccfa-skills
ccf-paper-writer 45 ccf-common 2 ccf-integrity-auditor 45 ccf-paper-reviewer 44 ccf-experiment-designer 2 ccf-literature-searcher 45 ccf-idea-optimizer 2 ccf-idea-reviewer 2 ccf-visual-composer 43 ccf-literature-monitor 2

Browse all from mikubaka88/ccfa-skills

More details

Agent compatibility

Declared targets from SKILL.md / docs. Unmarked agents are not listed — the skill may still install via the CLI.

Claude Code Not declared
Cursor Not declared
Codex Not declared
GitHub Copilot Not declared
Windsurf Not declared
Gemini CLI Not declared
Cline Not declared
OpenCode Not declared

Repository health

Stars 2.3K
License LICENSE
Default branch main
Open issues 4
Status Active

Skill metadata

Parsed from SKILL.md frontmatter.

More metadata
ccf_skill_controls
{"handoff_question_mode":"partial","respect_session_denylists":true,"protect_idea_scope_in_writing":true,"private_material_safety":"moderate","shared_controls":"..\/ccf-common\/references\/"}

Package contents

Files included with this skill beyond the listing page.

  • skill md SKILL.md 3,769 B
  • docs SUMMARY.md 314 B

History

  1. First seen on skills.sh
  2. First recorded snapshot · 712 installs

SKILL.md

CCF Pipeline Orchestrator

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.

Place ccf-humanization before any handoff that will write manuscript text or create publication-facing experiment artifacts. This priority preflight does not replace the downstream owner and requires no extra handoff question.

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.

Workflow

  1. Identify target venue, current stage, available artifacts, constraints, deadline pressure, and the user's immediate goal.
  2. Read ccfa.yaml when available; if absent, continue with supplied artifacts and report that project-state tracking is unavailable.
  3. For unclear projects, use references/workflow-planning/intake-protocol.md, approach-options.md, and design-brief-template.md.
  4. Classify the next owner: ccf-project-scaffolder, ccf-idea-optimizer, ccf-idea-reviewer, ccf-literature-monitor, ccf-literature-searcher, ccf-experiment-designer, ccf-visual-composer, ccf-paper-to-exemplar, ccf-paper-writer, ccf-paper-reviewer, ccf-integrity-auditor, ccf-submission-checker, or ccf-rebuttal-writer. Prefix ccf-humanization when the output will enter a manuscript or publication-facing experiment artifact.
  5. Define the gate: required input, output artifact, pass condition, blocker, and handoff.
  6. Resolve canonical input/output and working paths before each file-producing handoff. Reuse the current artifact and hand off changed requirements plus source locations, not duplicated full reports. Keep independent owners from writing the same file concurrently. Update existing ccfa.yaml stage/gate fields when project-state maintenance is authorized; preserve unrelated fields and the existing contract. For a planning-only request, propose the update without writing. Reuse existing artifact/state fields for the current goal, evidence locations, completed work, and next step when continuation needs it.

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: