Ccf Submission Checker
mikubaka88/CCFA-Skills
Check CCF venue rules and submission packages: template, pages, anonymity, PDF build, metadata, and reproducibility.
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…
Install Fse Submission
$ npx skills add brycewang-stanford/Awesome-Journal-Skills --skill fse-submission -a claude-codeProject install by default; add -g for ~/.claude/skills/.
$ gh skill install brycewang-stanford/Awesome-Journal-Skills fse-submission --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/brycewang-stanford/Awesome-Journal-Skills.git skills-src && mkdir -p .claude/skills && cp -r skills-src/FSE-Skills/skills/fse-submission .claude/skills/fse-submission && 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 "fse-submission" agent skill from https://github.com/brycewang-stanford/Awesome-Journal-Skills/tree/main/FSE-Skills/skills/fse-submission into .claude/skills/fse-submission/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "fse-submission", 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/brycewang-stanford/Awesome-Journal-Skills/tree/main/FSE-Skills/skills/fse-submissionType 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 brycewang-stanford/Awesome-Journal-Skills --skill fse-submission -a codexProject install goes to .agents/skills/; add -g for ~/.codex/skills/.
$ gh skill install brycewang-stanford/Awesome-Journal-Skills fse-submission --agent codexProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/brycewang-stanford/Awesome-Journal-Skills.git skills-src && mkdir -p .agents/skills && cp -r skills-src/FSE-Skills/skills/fse-submission .agents/skills/fse-submission && rm -rf skills-srcUse ~/.agents/skills/ instead of .agents/skills for a personal install.
Codex skills documentation · loads skills from .agents/skills/
Install the "fse-submission" agent skill from https://github.com/brycewang-stanford/Awesome-Journal-Skills/tree/main/FSE-Skills/skills/fse-submission into .agents/skills/fse-submission/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "fse-submission", 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 brycewang-stanford/Awesome-Journal-Skills --skill fse-submission -a cursorProject install goes to .agents/skills/; add -g for ~/.cursor/skills/.
$ gh skill install brycewang-stanford/Awesome-Journal-Skills fse-submission --agent cursorProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/brycewang-stanford/Awesome-Journal-Skills.git skills-src && mkdir -p .cursor/skills && cp -r skills-src/FSE-Skills/skills/fse-submission .cursor/skills/fse-submission && 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 "fse-submission" agent skill from https://github.com/brycewang-stanford/Awesome-Journal-Skills/tree/main/FSE-Skills/skills/fse-submission into .cursor/skills/fse-submission/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "fse-submission", 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/brycewang-stanford/Awesome-Journal-Skills.git --path FSE-Skills/skills/fse-submission--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 brycewang-stanford/Awesome-Journal-Skills --skill fse-submission -a gemini-cliProject install goes to .agents/skills/; add -g for ~/.gemini/skills/.
$ gh skill install brycewang-stanford/Awesome-Journal-Skills fse-submission --agent gemini-cliProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/brycewang-stanford/Awesome-Journal-Skills.git skills-src && mkdir -p .gemini/skills && cp -r skills-src/FSE-Skills/skills/fse-submission .gemini/skills/fse-submission && 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 "fse-submission" agent skill from https://github.com/brycewang-stanford/Awesome-Journal-Skills/tree/main/FSE-Skills/skills/fse-submission into .gemini/skills/fse-submission/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "fse-submission", 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 brycewang-stanford/Awesome-Journal-Skills fse-submissionInstalls 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 brycewang-stanford/Awesome-Journal-Skills --skill fse-submission -a github-copilotProject install goes to .agents/skills/; add -g for ~/.copilot/skills/.
$ git clone --depth 1 https://github.com/brycewang-stanford/Awesome-Journal-Skills.git skills-src && mkdir -p .github/skills && cp -r skills-src/FSE-Skills/skills/fse-submission .github/skills/fse-submission && 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 "fse-submission" agent skill from https://github.com/brycewang-stanford/Awesome-Journal-Skills/tree/main/FSE-Skills/skills/fse-submission into .github/skills/fse-submission/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "fse-submission", 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 brycewang-stanford/Awesome-Journal-Skills --skill fse-submission -a opencodeOpenCode documents no install command of its own. Project install goes to .agents/skills/; add -g for ~/.config/opencode/skills/.
$ gh skill install brycewang-stanford/Awesome-Journal-Skills fse-submission --agent opencodeProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/brycewang-stanford/Awesome-Journal-Skills.git skills-src && mkdir -p .opencode/skills && cp -r skills-src/FSE-Skills/skills/fse-submission .opencode/skills/fse-submission && 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 "fse-submission" agent skill from https://github.com/brycewang-stanford/Awesome-Journal-Skills/tree/main/FSE-Skills/skills/fse-submission into .opencode/skills/fse-submission/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "fse-submission", 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
fse-submission- GitHub stars
- 1.2k
- Token cost
- ~1.5k tokens
- SKILL.md length
- 681 words
- Files
- 1
- Skills in repo
- 2,387
- Repo updated
- First seen
- Licence
- MIT
At a glance
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…
- Works in 6 steps: Freeze the body early; references can… → Register… → Build the anonymized artifact and place… → …
- Auditing an ESEC/FSE research-track submission for HotCRP readiness
- SKILL.md covers The two-step deadline, Format and page budget, Double-anonymous "heavy" sweep and Open science at submission time, plus 4 more sections
- Calls pdftotext
What it does
Fse Submission is an agent skill from brycewang-stanford/Awesome-Journal-Skills. Use when auditing an ESEC/FSE research-track submission for HotCRP readiness, covering the mandatory paper-registration step, the ACM Primary Article Template page budget, double-anonymous "heavy" anonymity, the open-science Data Availability statement, PACMSE publication, and desk-reject triage before the AoE cutoff.
Its SKILL.md is about 1.5k tokens, which your agent loads only when the skill is triggered. It is a single SKILL.md file with no bundled scripts.
It sits in Research & Science, covering Reproducible research and Programmatic SEO. The repository describes itself as: Journal-specific Claude Code/Codex skill packs covering mainstream journals — AER, QJE, Nature, Cell, 管理世界, 经济研究 & 200+ more — your fast track to getting published. ｜ 覆盖主流期刊的… The licence is MIT.
When your agent uses it
- Auditing an ESEC/FSE research-track submission for HotCRP readiness
- Covering the mandatory paper-registration step
- The ACM Primary Article Template page budget
- Double-anonymous heavy anonymity
Example prompts
- “/fse-submission”
Workflow steps
6 steps, taken from the first numbered list in SKILL.md.
- Freeze the body early; references can churn, the argument cannot.
- Register title/abstract/authors/conflicts well before the registration cutoff.
- Build the anonymized artifact and place its link and Data Availability statement in the paper.
- Run the mechanical anonymity checks on the final PDF and the final archive, not drafts.
- Fill every HotCRP field — topics that match your evidence, conflicts for every coauthor's
- Re-download the uploaded PDF and read it cold to confirm it is the file you meant.
What it can do on your machine
Read from SKILL.md and the folder at commit 932eb23. 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
Shell commands in SKILL.md call:
pdftotext
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
Fse Submission loads about 1.5k tokens when it runs. Until then it costs about 84 tokens; SKILL.md has 681 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 brycewang-stanford/Awesome-Journal-Skills at commit 932eb23, republished under its MIT licence (© brycewang-stanford). 681 words, ~1,481 tokens.
Download SKILL.mdSave it as
.claude/skills/fse-submission/SKILL.md (or your agent's skills folder).- name
- fse-submission
- description
- Use when auditing an ESEC/FSE research-track submission for HotCRP readiness, covering the mandatory paper-registration step, the ACM Primary Article Template page budget, double-anonymous "heavy" anonymity, the open-science Data Availability statement, PACMSE publication, and desk-reject triage before the AoE cutoff.
FSE Submission
Run this audit before uploading to the FSE HotCRP site. FSE research papers are published as
journal articles in PACMSE (Proceedings of the ACM on Software Engineering), so the
submission is judged like a journal manuscript that also earns a conference slot. Every number
below was read from the FSE 2026/2027 research-papers calls on 2026-07-09 via search renderings
of the conf.researchr.org URLs (see resources/official-source-map.md); treat them as a
one-cycle snapshot and reopen the live call first.
The two-step deadline
FSE separates paper registration from paper submission, and both are AoE:
- Registration locks in title, abstract, authors, and conflicts a week early (FSE 2026: 4 September 2025). Miss it and the system will not accept the PDF later.
- Submission uploads the anonymized PDF (FSE 2026: 11 September 2025). FSE 2027's single research deadline is 2 October 2026.
Register with the real title and abstract, not a placeholder — the abstract drives reviewer bidding, and a registered abstract that diverges from the final paper quietly worsens your PC match.
Format and page budget
- ACM Primary Article Template, unmodified, in the single-column review format. This is the ACM path, not IEEE — do not carry an IEEEtran habit over from a sibling venue.
- Page budget (verify per cycle): FSE 2027 posts ≤18 pages for all text and figures plus 4 pages for references only. There is no separate unlimited appendix; anything reviewers must read to judge the paper lives inside the budget.
- Margins, font size, and spacing are fixed by the template; editorial compression, not template tampering, is how you recover space.
Double-anonymous "heavy" sweep
FSE runs heavy double-anonymous review: anonymity is preserved through all reviewing and discussion, and even a later Major Revision response letter must stay anonymous. Because SE papers lean on tools, repositories, and mined data, the leak surface is wide:
# Mechanical pass on the submission PDF and any anonymized artifact archive
pdfinfo paper.pdf | grep -Ei 'author|creator|producer'
pdftotext paper.pdf - | grep -nEi 'github\.com/[a-z0-9-]+|gitlab|zenodo\.org/record|acknowledg|grant' | head
unzip -l artifact.zip | grep -Ei '\.git/|\.DS_Store|/home/|/Users/' | head
grep -rni 'university\|@[a-z0-9.]*\.edu\|our (tool|group|lab)' artifact/ --include='*.md' | headThe SE-specific leaks: a tool named after your lab, a screenshot showing a username, a data- availability link pointing at a personal GitHub, commit metadata inside a zipped repository, and issue-tracker URLs in the evaluation. Re-host artifacts behind an anonymizing service before upload.
Open science at submission time
FSE expects sharing by default under an open-science policy. Concretely for the submission:
- Provide an anonymized artifact link or upload anonymized material, and add a Data Availability statement describing what exists and where it will live after acceptance.
- If you genuinely cannot share (industrial confidentiality, human-subjects limits), say so and why — a missing availability story reads as a scored weakness, not a neutral choice.
- Cache LLM outputs and pin mining provenance now; these cannot be reconstructed at review time.
Show full SKILL.md (253 more words)Show less
Desk-risk triage
| Finding at audit time | Severity | Real fix |
|---|---|---|
| Main text over the page budget | Desk-reject-grade | Cut or move to the artifact; reference pages do not absorb body text |
| Template altered (margins, shrunk font) | Named desk-reject ground | Recompile clean, recover space editorially |
| Identity leak in PDF, artifact, or tool name | Anonymity violation | Re-anonymize and re-host; scrub PDF metadata |
| Abstract/paper not registered by the earlier date | No submission slot exists | Nothing fixes this post-AoE — calendar it now |
| No availability statement, no artifact | Scored against the paper | Add the statement + an anonymized package |
| Same study under review elsewhere | Dual-submission exposure | Withdraw one venue; verify the current concurrent-submission wording |
Final-week order of operations
- Freeze the body early; references can churn, the argument cannot.
- Register title/abstract/authors/conflicts well before the registration cutoff.
- Build the anonymized artifact and place its link and Data Availability statement in the paper.
- Run the mechanical anonymity checks on the final PDF and the final archive, not drafts.
- Fill every HotCRP field — topics that match your evidence, conflicts for every coauthor's institution and recent collaborators — a day early; late conflicts are the classic midnight failure.
- Re-download the uploaded PDF and read it cold to confirm it is the file you meant.
Reverify each cycle
- Whether the year runs one deadline or two (FSE 2024 used two; 2025-2027 post one).
- The page budget and which ACM template revision is required.
- Supplementary handling, artifact-track timing, dual-submission wording, and any AI-disclosure rule — all cycle-volatile; none should be assumed stable.
Output format
[FSE submission status] ready / blocked / needs work
[Registration] title/abstract/authors/conflicts locked by the earlier deadline? yes/no
[Format] pages used (body/refs), ACM template compliance
[Anonymity] clean / leaks: <where>
[Open science] artifact link present? Data Availability statement present?
[Fix queue] <ordered, with owners and dates before the AoE cutoff>© brycewang-stanford, MIT. Rendered from Markdown: HTML in the file is shown as text, images as links, and headings moved down two levels. Raw file
Files
Just SKILL.md in FSE-Skills/skills/fse-submission of brycewang-stanford/Awesome-Journal-Skills.
Open the folder on GitHubat commit 932eb23
Compare with similar skills
Fse Submission 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 |
|---|---|---|---|---|---|---|
| Fse Submission this skillbrycewang-stanford/Awesome-Journal-Skills | 1.2k | — | ~1.5k | Automated safety check: Pass | MIT | |
| Ccf Submission Checkermikubaka88/CCFA-Skills | 3k | — | ~1.3k | Automated safety check: Pass | MIT | |
| Peer ReviewK-Dense-AI/claude-scientific-writer | 2.4k | 2 repos | ~3.1k | Automated safety check: Notes | MIT | |
| CHARLS Paper Reproduction Guidexjtulyc/MedgeClaw | 617 | 1 repos | ~1.8k | Automated safety check: Pass | None | |
| Compute Environment Setupaipoch/open-science | 5.5k | — | ~2.6k | Automated safety check: Pass | Apache-2.0 | |
| Figure Styleaipoch/open-science | 5.5k | — | ~5.1k | Automated safety check: Pass | Apache-2.0 |
Similar skills
Peer Review
K-Dense-AI/claude-scientific-writer
Prepare evidence-bounded, constructive peer-review drafts and structured manuscript assessments.
CHARLS Paper Reproduction Guide
xjtulyc/MedgeClaw
Guides an agent through reproducing papers built on the CHARLS health and retirement survey, from variable mapping to cognition, depression and isolation scores.
Compute Environment Setup
aipoch/open-science
Prepares setup instructions and a named activation file for a user-managed software environment on an Open-Science SSH or Slurm compute host.
Figure Style
aipoch/open-science
Publication-grade correctness and legibility rules for final-deliverable scientific figures, not exploratory plots.
Add Bactopia Tool
bactopia/bactopia
Scaffold a complete Bactopia Tool across all three tiers -- module, subworkflow, and workflow entry point under workflows/bactopia-tools/.
More from brycewang-stanford/Awesome-Journal-Skills
All 2,387 skills in this repoAaag Data Analysis
brycewang-stanford/Awesome-Journal-Skills
A skill your agent uses when running and reporting the analysis for an Annals of the American Association of Geographers manuscript — spatial statistics and modeling, remote-sensing accuracy, or…
Aaag Literature Positioning
brycewang-stanford/Awesome-Journal-Skills
A skill your agent uses when positioning an Annals of the American Association of Geographers manuscript in the literature — engaging geographic scholarship across the relevant area and the…
Aaag Rebuttal
brycewang-stanford/Awesome-Journal-Skills
A skill your agent uses when responding to an Annals of the American Association of Geographers decision letter (major/minor revision) — building a point-by-point response to the subject editor and…
Aaag Research Design
brycewang-stanford/Awesome-Journal-Skills
A skill your agent uses when defending the research design of an Annals of the American Association of Geographers manuscript — spatial/quantitative analysis and GIScience, remote-sensing and…
Aaag Review Process
brycewang-stanford/Awesome-Journal-Skills
A skill your agent uses when you need to understand how the Annals of the American Association of Geographers evaluates a manuscript — double-anonymous review routed through a subject editor by…
Aaag Submission
brycewang-stanford/Awesome-Journal-Skills
A skill your agent uses when running the final pre-submission preflight for the Annals of the American Association of Geographers via ScholarOne Manuscripts — area/article-type selection…
Related
Categories
Questions about Fse Submission
What does Fse Submission do?
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…. Fse Submission is an agent skill from brycewang-stanford/Awesome-Journal-Skills. Use when auditing an ESEC/FSE research-track submission for HotCRP readiness, covering the mandatory paper-registration step, the ACM Primary Article Template page budget, double-anonymous "heavy" anonymity, the open-science Data Availability statement, PACMSE publication, and desk-reject triage before the AoE cutoff.
When should I use Fse Submission?
Fse Submission fits situations like: auditing an ESEC/FSE research-track submission for HotCRP readiness; covering the mandatory paper-registration step; the ACM Primary Article Template page budget; double-anonymous heavy anonymity.
How do I install Fse Submission in Claude Code?
Run `npx skills add brycewang-stanford/Awesome-Journal-Skills --skill fse-submission -a claude-code`. Or copy the skill folder (FSE-Skills/skills/fse-submission in brycewang-stanford/Awesome-Journal-Skills) into .claude/skills/fse-submission in your project. Claude Code loads it when a task matches its description.
How do I install Fse Submission in Codex?
Run `npx skills add brycewang-stanford/Awesome-Journal-Skills --skill fse-submission -a codex`. Or copy the skill folder (FSE-Skills/skills/fse-submission in brycewang-stanford/Awesome-Journal-Skills) into .agents/skills/fse-submission in your project. Codex loads it when a task matches its description.
Can I use Fse Submission 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 brycewang-stanford/Awesome-Journal-Skills --skill fse-submission -a cursor` (or -a gemini-cli, github-copilot or opencode for the others). To copy it by hand, put the folder in .cursor/skills/fse-submission, .gemini/skills/fse-submission, .github/skills/fse-submission and .opencode/skills/fse-submission in your project.
What does Fse Submission need to run?
Going by SKILL.md and its folder, Fse Submission needs the command-line tools its instructions call (pdftotext).
Does Fse Submission 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 Fse Submission 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 Fse Submission use?
Fse Submission 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 Fse Submission use?
About 1.5k tokens (SKILL.md is roughly 5.9k 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 Fse Submission?
Skills that share tags, products or a category with Fse Submission: Ccf Submission Checker (mikubaka88/CCFA-Skills, 3k stars), Peer Review (K-Dense-AI/claude-scientific-writer, 2.4k stars), CHARLS Paper Reproduction Guide (xjtulyc/MedgeClaw, 617 stars) and Compute Environment Setup (aipoch/open-science, 5.5k stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.
Who maintains Fse Submission?
brycewang-stanford (a GitHub user) maintains it in brycewang-stanford/Awesome-Journal-Skills, which has 1,231 GitHub stars. The repository holds 2,387 skills in this directory. The repository was last updated on September 27, 2026.
Source: brycewang-stanford/Awesome-Journal-Skills on GitHub. Facts on this page come from the repository at the commit we read; the author's words are quoted as theirs.