ccf-submission-checker — Claude Code skill: submission checks
ccf-submission-checker — a Claude Code skill checks CCF venue requirements and submission-package readiness. Run it to review formatting, a TeX/PDF build, or artifact reproducibility.
MIT 2,200 installs ★ 3,769 updated 2026-10-20
npx skills add mikubaka88/CCFA-Skills --skill ccf-submission-checker -a claude-codeWhat ccf-submission-checker does
The skill checks venue rules and the files prepared for a paper submission. It reviews templates, page limits, anonymity, metadata, fonts, file structure, and TeX/PDF build output. For artifacts, it creates a checklist covering code, data, models, environment, licensing, and reproducibility.
Its modes cover venue rules, package checks, artifacts, or a full review. Final decisions rely on current official rules for the specific venue, year, track, and submission stage. Local guides help locate requirements but do not replace the official source. The skill does not rewrite the paper or submit files.
Checks use the actual TeX/PDF files and build logs; a PDF on disk does not prove that the current build succeeded. scripts/check_cvpr2027.py runs local checks for CVPR 2027, but cannot confirm author enrollment or the truth of disclosures. The skill reads ccfa.yaml when present and can proceed with supplied files when it is absent.
What it helps with
- match a paper's format to a specific venue's rules
- check page limits and manuscript anonymity
- find TeX/PDF build and metadata issues
- list reproducibility gaps in research artifacts
Example prompts for the agent
- Check my paper's format, anonymity, and page limit for the named conference.
- Review the PDF build, metadata, and submission files.
- Create a reproducibility checklist for this project's code and data.
How to install ccf-submission-checker
1Skills CLI (Vercel)
npx skills add mikubaka88/CCFA-Skills --skill ccf-submission-checker -a claude-code2Manually: put the files in place
~/.claude/skills/ccf-submission-checker/SKILL.mdCopy the whole skill folder; for one project use .claude/skills/ccf-submission-checker/
1Skills CLI (Vercel)
npx skills add mikubaka88/CCFA-Skills --skill ccf-submission-checker -a codex2Manually: put the files in place
.agents/skills/ccf-submission-checker/SKILL.mdFor all projects use ~/.agents/skills/
1Skills CLI (Vercel)
npx skills add mikubaka88/CCFA-Skills --skill ccf-submission-checker -a cursor2Manually: put the files in place
.cursor/skills/ccf-submission-checker/SKILL.mdCursor also reads .agents/skills/ and .claude/skills/
1GitHub CLI
gh skill install mikubaka88/CCFA-Skills ccf-submission-checker2Manually: put the files in place
.github/skills/ccf-submission-checker/SKILL.md1Skills CLI (Vercel)
npx skills add mikubaka88/CCFA-Skills --skill ccf-submission-checker -a gemini-cli2Platform CLI
gemini skills install https://github.com/mikubaka88/CCFA-Skills --path ccf-submission-checkerManually: put the files in place
.devin/skills/ccf-submission-checker/SKILL.mdThe legacy .windsurf/skills/ path still works
Skills CLI (Vercel)
npx skills add mikubaka88/CCFA-Skills --skill ccf-submission-checker -a opencodeClaude.ai
Zip the folder and upload it in Settings → Capabilities → Skills
Step by step, with commands for each platform: How to install skills in Claude Code: five ways
Questions about ccf-submission-checker
How do I install ccf-submission-checker in Claude Code?
Run npx skills add mikubaka88/CCFA-Skills --skill ccf-submission-checker -a claude-code. The skill file is at ~/.claude/skills/ccf-submission-checker/SKILL.md.
What does ccf-submission-checker do?
It reviews conference requirements, the submission package and build, plus artifact reproducibility. It does not edit the paper or submit files.
Which conference rules does the skill apply?
Final checks use current official rules for the venue, year, track, and submission stage. Local guides serve as navigation, not as a substitute for the official source.
Source text
SKILL.md · MIT
---
name: ccf-submission-checker
description: "Check CCF venue rules and submission packages: template, pages, anonymity, PDF build, metadata, and reproducibility. Use for 投稿检查, 会议格式, page limits, and artifact readiness. Verify current official rules for the exact venue/year/track. Manuscript polishing belongs to ccf-paper-writer."
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/
---
# CCF Submission Checker
## Family File Contract
Before file work, reuse canonical paths and one task/artifact working directory; default to project-root `ccfa-workfiles/<purpose>/<artifact-id>/`. Update in place, preserve inputs, and use UTF-8 with Chinese-text checks. Apply [artifact-contracts.md](../ccf-common/references/artifact-contracts.md) for naming, ownership, and task-created cleanup; handoffs inherit these paths.
## Collaboration Contract
Before specialist execution, read and apply [ccf-humanization](../ccf-humanization/SKILL.md) first, then [ccf-common](../ccf-common/SKILL.md). At every handoff, reuse their applicable active rules or refresh missing/changed ones. Both preflights are required even without prose; detailed editing, experiment, and maintenance modes run only when relevant.
Integrate necessary specialist contributions under one owner; reuse valid prerequisites and verify affected results. Follow the [cooperation routes](../ccf-common/references/routing.md) without duplicate reports.
## 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; report only missing information that affects a requested check.
3. For venue questions, read `../ccf-paper-writer/references/venue-guides/index.md` and the specific guide as navigation. Apply format, page and anonymity rules only from a verified official source matching the venue/year/track/stage; reuse a current verified result. Legacy guide examples cannot override a supplied verified template. Resolve a real mismatch against the target official requirements before changing the manuscript.
4. For package checks, inspect the actual TeX/PDF/build output, page accounting for the exact venue/year/track, anonymity, fonts, metadata, references, and applicable required forms. For CVPR 2027, use the complete `CVPR/2027` bundle and the matched guide's eight-page main-text budget, required LLM Usage Statement placement, anonymity and enrollment/quota checks. Use `scripts/check_cvpr2027.py` for local TeX/PDF checks; it cannot establish author enrollment, disclosure truth or official-review AI authorization. For ICLR 2027, retain its distinct template, stage budget and AI-use statement/form rules. Unconfirmed facts remain not verified. Read logs and affected pages; do not infer a successful build from file presence.
5. For artifact checks, build a reproducibility checklist: code, data, models, environment, seeds, hardware, license, access restrictions, and README.
6. Route actual findings or authorized fixes through their owners: paper writer for needed text/page revisions, visual composer for figure/table layout defects, and rebuttal writer for post-review response packaging. A paper within the page budget does not automatically need polishing. For a reproducibility gap, distinguish missing documentation, configuration, code, and scientific evidence: research engineer handles implementation or reproduction work, and experiment designer resolves a comparison or protocol question. A missing checklist item alone does not require a new experiment.
## 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:
```
## Check Scope
Follow `../ccf-common/references/handoff-modes.md` and `../ccf-common/references/task-modes.md`. Run checks relevant to the requested mode and actual artifacts. Distinguish pass, fail, not applicable, and not verified; missing tools do not imply passing or failure. Record the official rule URL and the date checked. Reuse the project build configuration and place generated logs/previews in the established or shared task build directory. Update the canonical readiness report in place and distinguish old PDFs from successful current builds. Recheck only affected build surfaces after a fix. Underfilling a page budget alone is not a venue violation. Do not upload or submit files merely because a readiness check was requested.
© mikubaka88 · MIT · mikubaka88/CCFA-Skills