mikubaka88/ccfa-skills

ccf-submission-checker

Check CCF conference submission readiness: venue LaTeX/template/page/anonymity/camera-ready rules, LaTeX/PDF build, metadata, fonts, supplementary files, artifact/reproducibility package, code/data/model release plan, licenses, seeds, and policy freshness.

View source
Original skill document

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

CCF Submission Checker

Core Rule

Treat submission as a build, venue-policy, page-budget, and artifact-readiness gate. Use local venue guides for expected rules, then require official-policy freshness for final decisions. Do not rewrite paper content.

Modes

  • venue-format: template, page limit, anonymity, author block, supplementary and camera-ready rules.
  • package-check: LaTeX/PDF build, metadata, fonts, page count, file structure, and submission checklist.
  • artifact: code/data/model release plan, environment, seeds, hardware, licenses, artifact README, and reproducibility appendix.
  • full: venue + package + artifact.

Workflow

  1. Identify venue/year/track, submission mode, project directory, TeX/PDF files, supplementary/artifact files, and deadline pressure.
  2. Read ccfa.yaml when available. If absent, proceed with supplied files and state that project-state tracking is unavailable.
  3. For venue questions, read ../ccf-paper-writer/references/venue-guides/index.md and the specific venue guide before checking official freshness.
  4. For package checks, inspect compile status, page count, target page budget, anonymity, fonts, PDF metadata, template path, references, supplementary files, and required forms.
  5. For artifact checks, build a reproducibility checklist: code, data, models, environment, seeds, hardware, license, access restrictions, and README.
  6. Hand off to ccf-paper-writer for text/page rewrites: compression when over limit, expansion when a full manuscript is materially underfilled, and normal polishing when within budget. Hand off to ccf-experiment-designer for missing reproducibility experiments, ccf-visual-composer for figure/table float order, caption placement, font, clipping, palette, or visual readability fixes, and ccf-rebuttal-writer for post-review response packaging.

Output Contract

text
Mode:
Venue and rule freshness:
Files checked:
Pass/fail checklist:
Build/package issues:
Anonymity/page/font/metadata issues:
Length budget status:
Artifact/reproducibility issues:
Required fixes:
Next CCFA owner:
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
2천
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
2천
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
2천
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
2천
Updated
8월 13일