メニュー
Create CCF paper project folders, select or copy LaTeX templates, initialize ccfa.yaml, and prepare artifact directories. Use for project scaffolding and reproducible workspace setup. Do not generate research content.
Codex または Claude でインストール この Prompt をコピーして Codex、Claude、または他のアシスタントに貼り付けると、Skill ページを確認してインストールできます。
SOC 職業分類に基づく
Compose, polish, generate, and QA publication-grade CCF paper figures, tables, captions, palettes, panel maps, Python plotting code, and manuscript visual layout integration from supplied data/results. Use for figure/table layout, visual QA, palette selection, LaTeX figure/table placement, multi-panel design, creative data visualization, data-analysis plots, pie/donut charts, bar charts, volcano plots, correlation heatmaps, composite dashboards, source-data traceability, and making visuals fit naturally in the paper. Do not design experiments, invent results, write manuscript prose as the main task, or perform final submission compliance.
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.
Design CCF paper evidence packages: datasets, baselines, metrics, ablations, robustness tests, result-table templates, and real-result figure/table presentation. Use for experiment design, benchmark planning, baseline selection, ablation design, result tables, publication figures from supplied numbers, 设计实验, 对比实验, 消融, 结果图表. Do not invent results.
Audit CCF paper integrity: claim-support alignment, result-to-claim consistency, numeric consistency, terminology consistency, figure/table-to-text consistency, existing citation existence, BibTeX metadata, and citation-context support. Use for evidence audit, citation audit, consistency check, 引用核验, claim审计, 数字一致性. Do not perform full scientific review or broad literature search.
Review CCF/target-venue manuscripts end to end: scientific novelty, soundness, evidence, simulated reviewers, AC/meta-review, score risk, writing logic, paragraph clarity, LaTeX/format presentation, and reviewer-facing revision actions. Use for paper review, scientific review, writing review, format review, 审稿, 模拟审稿, 论文评分, 写作评审, 逐段评审, LaTeX检查. Do not rewrite the manuscript as the main task and do not write rebuttals.
Convert user-provided conference paper PDFs into distilled writing exemplar cards for the ccf-paper-writer skill. Extracts full text, analyzes writing patterns by venue, and produces ready-to-use exemplar cards with story patterns, abstract/introduction/method/evidence moves, and citation-style analysis. Use when the user wants to add custom writing exemplars, convert favorite papers into reusable writing templates, or build a personal exemplar library for a target venue.
| name | ccf-project-scaffolder |
| description | Create CCF paper project folders, select or copy LaTeX templates, initialize ccfa.yaml, and prepare artifact directories. Use for project scaffolding and reproducible workspace setup. Do not generate research content. |
| 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/"}} |
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.
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.
Project name, target venue, output directory, template preference, and optional paper type.
../ccf-common/references/skill-trigger-registry.yaml for ownership boundaries before absorbing adjacent work.ccfa.yaml when it exists. If absent, continue with supplied artifacts and report that project-state tracking is unavailable.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 to ccf-pipeline-orchestrator for stage management, ccf-paper-writer for manuscript work, and ccf-submission-checker for build checks.
Do not invent title, abstract, claims, experiments, or citations unless the user explicitly supplies them.