OpenParable
Skip to content
← Back to skills

Ccf Submission Checker

Documents
ccf-submission-checker

Ccf Submission Checker is an Agent Skill for documents published in the mikubaka88/CCFA-Skills repository on GitHub: a SKILL.md instruction file an AI agent can load to do this task.

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. Use for submission check, venue format, NeurIPS/CVPR/ICML template/page limit, artifact package, 投稿检查, 会议格式. Do not polish manuscript content.

View on GitHub ↗
QUICK START

How to use this skill

Bring this guide into your coding agent with a prompt tailored to the tool you use.

  1. Open your project in Codex.
  2. Copy and paste the prompt below.
  3. Review files and risks before approving any action.
Prompt to paste
Inspect the Agent Skill at https://github.com/mikubaka88/CCFA-Skills/blob/HEAD/ccf-submission-checker/SKILL.md and all supporting files. Report provenance, permissions, scripts, dependencies, and security risks. Propose an exact installation into .agents/skills/ccf-submission-checker, but wait for my approval before writing files or running scripts.

Copying this prompt does not install or run the skill. Review third-party files before use.

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

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: