mikubaka88/ccfa-skills

ccf-project-scaffolder

Create CCF paper project folders, select or copy LaTeX templates, initialize ccfa.yaml, and prepare artifact directories.

View source
Original skill document

Rendered from the source repository. Headings, examples, code, tables, links, and referenced images are preserved.

CCF Project Scaffolder

Invocation Controls

CCFA Handoff Mode: PARTIAL (Recommended). Follow metadata.ccf_skill_controls.handoff_question_mode, ../ccf-common/references/handoff-modes.md, ../ccf-common/references/task-modes.md, and ../ccf-common/references/skill-trigger-registry.yaml.

Treat private manuscripts, reviews, drafts, results, code, and project state as private user material. Do not browse with private text unless the user authorizes it or the shared privacy/evidence policy allows a safe transformed query.

Core Rule

Create structure and metadata only. Prefer the target venue guide index for template discovery, then initialize ccfa.yaml from assets/ccfa.yaml with explicit placeholders.

Inputs

Project name, target venue, output directory, template preference, and optional paper type.

Workflow

  1. Identify quick or standard mode from the request, available artifacts, and deadline pressure.
  2. Check ../ccf-common/references/skill-trigger-registry.yaml for ownership boundaries before absorbing adjacent work.
  3. Read ccfa.yaml when it exists. If absent, continue with supplied artifacts and report that project-state tracking is unavailable.
  4. Execute only this skill's owned task. Mark missing evidence, stale venue rules, missing files, or authorization gaps explicitly.
  5. Produce the requested scaffold result and name the next owning skill when handoff is needed.

Quick And Standard Modes

  • Quick mode: answer the narrow request with the minimum relevant checklist and a compact risk note.
  • Standard mode: produce the full table/checklist, artifact-state notes, boundary checks, and handoff recommendations.

Adaptive Output Contract

If files were created or copied, report the directory tree, template paths, initialized ccfa.yaml, and next-step handoff. If the user only asks for a dry-run plan or install subset, return that requested shape instead. Do not force a full checklist for a small scaffold command.

Handoff

Handoff to ccf-pipeline-orchestrator for stage management, ccf-paper-writer for manuscript work, and ccf-submission-checker for build checks.

Forbidden

Do not invent title, abstract, claims, experiments, or citations unless the user explicitly supplies them.

from this repository

More skills

All skills
mikubaka88
Community

ccf-common

Shared governance for the CCFA family: routing, trigger registry, task modes, handoff modes, source registry, privacy/evidence policy, ccfa.yaml, and artifact contracts. Use only when maintaining or auditing CCFA skills; not for ordinary research tasks.

installs
5
GitHub stars
1993
Updated
8月13日
mikubaka88
Community

ccf-experiment-designer

Own experiment evidence semantics: decide datasets, baselines, metrics, ablations, robustness tests, chart evidence, and exactly what rows or columns a result table should contain. Use for experiment design, benchmark planning, supplied-result evidence structure, result-table schema, chart-spec semantics, 设计实验, 对比实验, 消融, 结果表证据结构. Do not search literature as the main deliverable, visually beautify or render an already specified table/figure, improve layout/colors/readability, or invent results.

installs
5
GitHub stars
1993
Updated
8月13日
mikubaka88
Community

ccf-humanization

Humanize and de-defend publication-facing CCF/AI prose and artifacts as a sidecar preflight, never as the primary task owner. Use before manuscript drafting/revision and before final manuscript experiment text, tables, captions, or method descriptions when Codex must remove defensive writing, boilerplate disclaimers, repetitive improbable edge cases, unnecessary safeguards, generic SHA-256/checksum requirements, duplicated smoke tests, simplified/toy methods, or AI-like risk narration. Do not auto-load as the sole owner for raw experiment planning, retrieval, review, auditing, routing, visual rendering, or assessment-only tasks without publication prose. Keep necessary concerns in a separate user-review warning instead of silently injecting them into files. Do not conceal material evidence, fabricate results, or override venue-mandated disclosures.

installs
5
GitHub stars
1993
Updated
8月13日
mikubaka88
Community

ccf-idea-optimizer

Turn rough CCF research directions into concrete problem, gap, insight, method, novelty, and evidence plans. Use for idea optimization, fuzzy idea concretization, develop a fuzzy idea with no score, research direction shaping, early direction exploration, salvage routes, 优化idea, 具象化idea, 研究思路优化, 找方向, 方向探索. Do not rank or score multiple ideas as the main output.

installs
5
GitHub stars
1993
Updated
8月13日