Paper Lens
YSQ-boop/paper-lens
Read and critically analyze one academic paper from an arXiv URL/ID or a local PDF, producing a source-grounded Markdown report that can grow from a quick read into a reviewer-level deep review.
Check CCF venue rules and submission packages: template, pages, anonymity, PDF build, metadata, and reproducibility.
Install Ccf Submission Checker
$ npx skills add mikubaka88/CCFA-Skills --skill ccf-submission-checker -a claude-codeProject install by default; add -g for ~/.claude/skills/.
$ gh skill install mikubaka88/CCFA-Skills ccf-submission-checker --agent claude-codeProject scope by default; add --scope user for a personal install. Needs GitHub CLI 2.90.0 or later (public preview).
$ git clone --depth 1 https://github.com/mikubaka88/CCFA-Skills.git skills-src && mkdir -p .claude/skills && cp -r skills-src/ccf-submission-checker .claude/skills/ccf-submission-checker && rm -rf skills-srcUse ~/.claude/skills/ instead of .claude/skills for a personal install. The folder must contain SKILL.md.
Claude Code skills documentation · loads skills from .claude/skills/
Install the "ccf-submission-checker" agent skill from https://github.com/mikubaka88/CCFA-Skills/tree/main/ccf-submission-checker into .claude/skills/ccf-submission-checker/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "ccf-submission-checker", then confirm the skill loads.Claude Code copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$skill-installer install https://github.com/mikubaka88/CCFA-Skills/tree/main/ccf-submission-checkerType this inside Codex. $skill-installer <name> installs a curated skill from openai/skills. The installer writes to $CODEX_HOME/skills (default ~/.codex/skills). Restart Codex if the skill does not show up.
$ npx skills add mikubaka88/CCFA-Skills --skill ccf-submission-checker -a codexProject install goes to .agents/skills/; add -g for ~/.codex/skills/.
$ gh skill install mikubaka88/CCFA-Skills ccf-submission-checker --agent codexProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/mikubaka88/CCFA-Skills.git skills-src && mkdir -p .agents/skills && cp -r skills-src/ccf-submission-checker .agents/skills/ccf-submission-checker && rm -rf skills-srcUse ~/.agents/skills/ instead of .agents/skills for a personal install.
Codex skills documentation · loads skills from .agents/skills/
Install the "ccf-submission-checker" agent skill from https://github.com/mikubaka88/CCFA-Skills/tree/main/ccf-submission-checker into .agents/skills/ccf-submission-checker/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "ccf-submission-checker", then confirm the skill loads.Codex copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ npx skills add mikubaka88/CCFA-Skills --skill ccf-submission-checker -a cursorProject install goes to .agents/skills/; add -g for ~/.cursor/skills/.
$ gh skill install mikubaka88/CCFA-Skills ccf-submission-checker --agent cursorProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/mikubaka88/CCFA-Skills.git skills-src && mkdir -p .cursor/skills && cp -r skills-src/ccf-submission-checker .cursor/skills/ccf-submission-checker && rm -rf skills-srcUse ~/.cursor/skills/ instead of .cursor/skills for a personal install.
Cursor skills documentation · loads skills from .cursor/skills/, .agents/skills/, .claude/skills/, .codex/skills/
Install the "ccf-submission-checker" agent skill from https://github.com/mikubaka88/CCFA-Skills/tree/main/ccf-submission-checker into .cursor/skills/ccf-submission-checker/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "ccf-submission-checker", then confirm the skill loads.Cursor copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ gemini skills install https://github.com/mikubaka88/CCFA-Skills.git --path ccf-submission-checker--scope user (default) or --scope workspace; --path is the subfolder of the repo that holds the skill; --consent skips the security confirmation prompt.
$ npx skills add mikubaka88/CCFA-Skills --skill ccf-submission-checker -a gemini-cliProject install goes to .agents/skills/; add -g for ~/.gemini/skills/.
$ gh skill install mikubaka88/CCFA-Skills ccf-submission-checker --agent gemini-cliProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/mikubaka88/CCFA-Skills.git skills-src && mkdir -p .gemini/skills && cp -r skills-src/ccf-submission-checker .gemini/skills/ccf-submission-checker && rm -rf skills-srcUse ~/.gemini/skills/ instead of .gemini/skills for a personal install, then run /skills reload.
Gemini CLI skills documentation · loads skills from .gemini/skills/, .agents/skills/
Install the "ccf-submission-checker" agent skill from https://github.com/mikubaka88/CCFA-Skills/tree/main/ccf-submission-checker into .gemini/skills/ccf-submission-checker/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "ccf-submission-checker", then confirm the skill loads.Gemini CLI copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ gh skill install mikubaka88/CCFA-Skills ccf-submission-checkerInstalls for Copilot at project scope by default; add --scope user for a personal install. Preview a skill first with gh skill preview. Needs GitHub CLI 2.90.0 or later (public preview).
$ npx skills add mikubaka88/CCFA-Skills --skill ccf-submission-checker -a github-copilotProject install goes to .agents/skills/; add -g for ~/.copilot/skills/.
$ git clone --depth 1 https://github.com/mikubaka88/CCFA-Skills.git skills-src && mkdir -p .github/skills && cp -r skills-src/ccf-submission-checker .github/skills/ccf-submission-checker && rm -rf skills-srcUse ~/.copilot/skills/ instead of .github/skills for a personal install. Commit .github/skills so cloud agent and code review can use it.
GitHub Copilot skills documentation · loads skills from .github/skills/, .claude/skills/, .agents/skills/
Install the "ccf-submission-checker" agent skill from https://github.com/mikubaka88/CCFA-Skills/tree/main/ccf-submission-checker into .github/skills/ccf-submission-checker/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "ccf-submission-checker", then confirm the skill loads.GitHub Copilot copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ npx skills add mikubaka88/CCFA-Skills --skill ccf-submission-checker -a opencodeOpenCode documents no install command of its own. Project install goes to .agents/skills/; add -g for ~/.config/opencode/skills/.
$ gh skill install mikubaka88/CCFA-Skills ccf-submission-checker --agent opencodeProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/mikubaka88/CCFA-Skills.git skills-src && mkdir -p .opencode/skills && cp -r skills-src/ccf-submission-checker .opencode/skills/ccf-submission-checker && rm -rf skills-srcUse ~/.config/opencode/skills/ instead of .opencode/skills for a personal install.
OpenCode skills documentation · loads skills from .opencode/skills/, .claude/skills/, .agents/skills/
Install the "ccf-submission-checker" agent skill from https://github.com/mikubaka88/CCFA-Skills/tree/main/ccf-submission-checker into .opencode/skills/ccf-submission-checker/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "ccf-submission-checker", then confirm the skill loads.OpenCode copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
Facts
- Skill name
ccf-submission-checker- GitHub stars
- 3k
- Token cost
- ~1.3k tokens
- SKILL.md length
- 535 words
- Files
- 2
- Skills in repo
- 17
- Repo updated
- First seen
- Licence
- MIT
At a glance
Check CCF venue rules and submission packages: template, pages, anonymity, PDF build, metadata, and reproducibility.
- Works in 6 steps: Identify venue/year/track, submission… → Read ccfa.yaml when available. If… → For venue questions, read… → …
- Artifact readiness
- SKILL.md covers Family File Contract, Collaboration Contract, Core Rule and Modes, plus 3 more sections
- Instructions only: no scripts, shell commands, URLs or credentials in SKILL.md
What it does
Ccf Submission Checker is an agent skill from mikubaka88/CCFA-Skills. 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.
Its SKILL.md is about 1.3k tokens, which your agent loads only when the skill is triggered. The skill folder holds 2 other files (for example `agents/openai.yaml`).
It sits in Documents & Office, covering Programmatic SEO and Reproducible research. The repository describes itself as: A skill family for shaping the research storyline of CCF-A papers. The licence is MIT.
When your agent uses it
- Artifact readiness
- Tasks that involve Programmatic SEO
- Tasks that involve Reproducible research
Example prompts
- “/ccf-submission-checker”
Workflow steps
6 steps, taken from the first numbered list in SKILL.md.
- Identify venue/year/track, submission mode, project directory, TeX/PDF files, supplementary/artifact files, and deadline pressure.
- Read ccfa.yaml when available. If absent, proceed with supplied files and state that project-state tracking is unavailable.
- For venue questions, read ../ccf-paper-writer/references/venue-guides/index.md and the specific venue guide before checking official…
- For package checks, inspect the actual TeX/PDF/build output, page accounting for the exact venue/year/track, anonymity, fonts, metadata…
- For artifact checks, build a reproducibility checklist: code, data, models, environment, seeds, hardware, license, access restrictions…
- Hand off to ccf-paper-writer for text/page rewrites: compression when over limit, substantive expansion when actual explanation is…
What it can do on your machine
Read from SKILL.md and the folder at commit 5969e6b. It shows what the files ask for, not the result of running them.
Tool permissions
Pre-approves nothing: there is no allowed-tools line, so your agent's usual permission prompts apply.
From allowed-tools in the SKILL.md frontmatter.
Runs code
No scripts in the folder and no shell commands in SKILL.md.
From the folder's file list and the shell code blocks in SKILL.md.
Network
No URLs in SKILL.md.
From URLs in SKILL.md, links to its own repository left out.
Credentials
Names no API keys, tokens, secrets or passwords.
From names ending in _API_KEY, _TOKEN, _SECRET, _KEY or _PASSWORD in SKILL.md.
Context cost
Ccf Submission Checker loads about 1.3k tokens when it runs. Until then it costs about 77 tokens; SKILL.md has 535 words of instructions outside code blocks.
Estimates: characters ÷ 4, the usual rule of thumb; real counts depend on the model's tokenizer. Scripts and assets cost tokens only if the agent reads them.
Safety
Auto-check passed
The automated check found no risky patterns in SKILL.md.
Automated static check — not a guarantee. Review scripts before installing. It scans the text of SKILL.md for risky patterns (piping downloads into a shell, reading credential files, hidden Unicode, destructive commands); files beside SKILL.md are not scanned.
SKILL.md
The full file from mikubaka88/CCFA-Skills at commit 5969e6b, republished under its MIT licence (© mikubaka88). 535 words, ~1,289 tokens.
Download SKILL.mdSave it as
.claude/skills/ccf-submission-checker/SKILL.md (or your agent's skills folder). This skill also uses 1 other file; get the full folder from GitHub.- 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.
CCF Submission Checker
Family File Contract
Before writing, resolve the canonical output and one stable working directory per task/artifact. Reuse explicit or established task paths; otherwise use project-root ccfa-workfiles/<purpose>/<artifact-id>/, with source/, assets/, cache/, and build/ only as needed. Update current files in place; do not scatter intermediates or create iteration copies. Preserve inputs and required evidence; clean only verified disposable files created by this task. Use UTF-8 text I/O and check Chinese text after saving or rendering. For file work, apply artifact-contracts.md and reuse the same paths across skill transitions.
Collaboration Contract
Before specialist execution, read and apply ccf-humanization first, then ccf-common. 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.
Keep one integrating owner and actively use other skills to resolve missing prerequisites or check material findings. Reuse applicable evidence; do not skip necessary groundwork to save tokens. Before finalizing, integrate contributions and verify affected results. Follow the conditional cooperation routes; avoid unrelated stages and 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.
Show full SKILL.md (285 more words)Show less
Workflow
- Identify venue/year/track, submission mode, project directory, TeX/PDF files, supplementary/artifact files, and deadline pressure.
- Read
ccfa.yamlwhen available. If absent, proceed with supplied files and state that project-state tracking is unavailable. - For venue questions, read
../ccf-paper-writer/references/venue-guides/index.mdand the specific venue guide before checking official freshness. - 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 ICLR 2027, apply the matched guide's year-specific template, stage-specific page budget, and AI-use statement/form checks; unconfirmed usage facts remain not verified. Read logs and affected pages; do not infer a successful build from file presence.
- For artifact checks, build a reproducibility checklist: code, data, models, environment, seeds, hardware, license, access restrictions, and README.
- Hand off to
ccf-paper-writerfor text/page rewrites: compression when over limit, substantive expansion when actual explanation is missing, and normal polishing when within budget. Hand off toccf-experiment-designerfor missing reproducibility experiments,ccf-visual-composerfor figure/table float order, caption placement, font, clipping, palette, or visual readability fixes, andccf-rebuttal-writerfor 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: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. Rendered from Markdown: HTML in the file is shown as text, images as links, and headings moved down two levels. Raw file
Files
SKILL.md and 1 other file in ccf-submission-checker of mikubaka88/CCFA-Skills.
- SKILL.md
- agents/openai.yaml
Open the folder on GitHubat commit 5969e6b
Compare with similar skills
Ccf Submission Checker next to the 5 skills that share the most tags, products or categories with it. Stars are the repository's; “used in” counts other GitHub owners with a copy.
| Skill | Stars | Used in | Tokens | Auto-check | Licence | Repo updated |
|---|---|---|---|---|---|---|
| Ccf Submission Checker this skillmikubaka88/CCFA-Skills | 3k | — | ~1.3k | Automated safety check: Pass | MIT | |
| Paper LensYSQ-boop/paper-lens | 101 | — | ~1.3k | Automated safety check: Pass | Apache-2.0 | |
| Evidence Ledgerwanshuiyin/Anti-Autoresearch | 160 | — | ~11k | Automated safety check: Notes | MIT | |
| Response Letteraipoch/medical-research-skills | 1.9k | — | ~2.1k | Automated safety check: Pass | MIT | |
| Fse Submissionbrycewang-stanford/Awesome-Journal-Skills | 1.2k | — | ~1.5k | Automated safety check: Pass | MIT | |
| Review RevisionM1n-n9/paper-lifecycle | 693 | — | ~2.3k | Automated safety check: Pass | None |
Similar skills
Evidence Ledger
wanshuiyin/Anti-Autoresearch
Build the deterministic evidence ledger (artifactmanifest.json + claims.json) that every other Anti-Autoresearch auditor reads.
Response Letter
aipoch/medical-research-skills
Helps organize reviewer comments and generate a standardized Word (.docx) response letter that maps each change to its exact location (page/paragraph/line).
Fse Submission
brycewang-stanford/Awesome-Journal-Skills
A skill your agent uses when auditing an ESEC/FSE research-track submission for HotCRP readiness, covering the mandatory paper-registration step, the ACM Primary Article Template page budget…
Review Revision
M1n-n9/paper-lifecycle
Review and revise academic papers with a senior-reviewer workflow.
Bio Expression Matrix Gene Id Mapping
GPTomics/bioSkills
Maps between gene identifier systems (Ensembl, Entrez, HGNC symbol, UniProt, RefSeq, MANE) using AnnotationDbi, biomaRt, mygene, pyensembl, and Ensembl REST.
More from mikubaka88/CCFA-Skills
All 17 skills in this repoCcf Paper Reviewer
mikubaka88/CCFA-Skills
Review manuscript claims, evidence, and writing without rewriting.
Ccf Rebuttal Writer
mikubaka88/CCFA-Skills
Write CCF rebuttals, author responses, revision ledgers, response letters, and conservative resubmission plans.
Ccf Common
mikubaka88/CCFA-Skills
Required shared preflight for every CCFA skill after ccf-humanization: apply routing, scope, prerequisites, evidence rules, handoffs, and artifact contracts.
Ccf Experiment Designer
mikubaka88/CCFA-Skills
Design CCF experiment protocols and evidence schemas: datasets, baselines, metrics, ablations, and result-table contents.
Ccf Humanization
mikubaka88/CCFA-Skills
Required first preflight before every CCFA skill, including research, review, retrieval, experiments, visuals, and maintenance.
Ccf Literature Monitor
mikubaka88/CCFA-Skills
Scan recent arXiv/OpenReview papers, venue feeds, labs, and competitors for overlap.
Related
Questions about Ccf Submission Checker
What does Ccf Submission Checker do?
Check CCF venue rules and submission packages: template, pages, anonymity, PDF build, metadata, and reproducibility. Ccf Submission Checker is an agent skill from mikubaka88/CCFA-Skills. Check CCF venue rules and submission packages: template, pages, anonymity, PDF build, metadata, and reproducibility.
When should I use Ccf Submission Checker?
Ccf Submission Checker fits situations like: artifact readiness; tasks that involve Programmatic SEO; tasks that involve Reproducible research.
How do I install Ccf Submission Checker in Claude Code?
Run `npx skills add mikubaka88/CCFA-Skills --skill ccf-submission-checker -a claude-code`. Or copy the skill folder (ccf-submission-checker in mikubaka88/CCFA-Skills) into .claude/skills/ccf-submission-checker in your project. Claude Code loads it when a task matches its description.
How do I install Ccf Submission Checker in Codex?
Run `npx skills add mikubaka88/CCFA-Skills --skill ccf-submission-checker -a codex`. Or copy the skill folder (ccf-submission-checker in mikubaka88/CCFA-Skills) into .agents/skills/ccf-submission-checker in your project. Codex loads it when a task matches its description.
Can I use Ccf Submission Checker in Cursor, Gemini CLI or GitHub Copilot?
Cursor, Gemini CLI, GitHub Copilot and OpenCode also load SKILL.md folders. With the skills CLI, run `npx skills add mikubaka88/CCFA-Skills --skill ccf-submission-checker -a cursor` (or -a gemini-cli, github-copilot or opencode for the others). To copy it by hand, put the folder in .cursor/skills/ccf-submission-checker, .gemini/skills/ccf-submission-checker, .github/skills/ccf-submission-checker and .opencode/skills/ccf-submission-checker in your project.
What does Ccf Submission Checker need to run?
SKILL.md names no scripts, command-line tools or credentials: Ccf Submission Checker is instructions for the agent only.
Does Ccf Submission Checker access the network?
SKILL.md contains no URLs. Any network use would come from the scripts or tools the agent runs. This is read from the text; nothing was executed.
Is Ccf Submission Checker safe to install?
Our automated static check of SKILL.md found no risky patterns, such as piping downloads into a shell, reading credential files or hidden Unicode. It is not a guarantee. Review the folder before installing.
What licence does Ccf Submission Checker use?
Ccf Submission Checker is published under the MIT licence (the repository's licence). It allows redistribution, so the full SKILL.md is shown on this page.
How many tokens does Ccf Submission Checker use?
About 1.3k tokens (SKILL.md is roughly 5.2k characters). Agents keep only the skill's name and description in context until a task matches; then they load SKILL.md in full.
What are the alternatives to Ccf Submission Checker?
Skills that share tags, products or a category with Ccf Submission Checker: Paper Lens (YSQ-boop/paper-lens, 101 stars), Evidence Ledger (wanshuiyin/Anti-Autoresearch, 160 stars), Response Letter (aipoch/medical-research-skills, 1.9k stars) and Fse Submission (brycewang-stanford/Awesome-Journal-Skills, 1.2k stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.
Who maintains Ccf Submission Checker?
mikubaka88 (a GitHub user) maintains it in mikubaka88/CCFA-Skills, which has 3,015 GitHub stars. The repository holds 17 skills in this directory. The repository was last updated on September 16, 2026.
Source: mikubaka88/CCFA-Skills on GitHub. Facts on this page come from the repository at the commit we read; the author's words are quoted as theirs.