Hypothesis Generation
spacering-net/codeg
Structured hypothesis formulation from observations. An agent skill from spacering-net/codeg.
A skill your agent uses when auditing an ACM CCS submission for HotCRP readiness, dual-cycle abstract registration and full-paper deadlines, the 12-page ACM sigconf body, anonymization, the ethics…
Install Ccs Submission
$ npx skills add brycewang-stanford/Awesome-Journal-Skills --skill ccs-submission -a claude-codeProject install by default; add -g for ~/.claude/skills/.
$ gh skill install brycewang-stanford/Awesome-Journal-Skills ccs-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/ACM-CCS-Skills/skills/ccs-submission .claude/skills/ccs-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 "ccs-submission" agent skill from https://github.com/brycewang-stanford/Awesome-Journal-Skills/tree/main/ACM-CCS-Skills/skills/ccs-submission into .claude/skills/ccs-submission/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "ccs-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/ACM-CCS-Skills/skills/ccs-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 ccs-submission -a codexProject install goes to .agents/skills/; add -g for ~/.codex/skills/.
$ gh skill install brycewang-stanford/Awesome-Journal-Skills ccs-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/ACM-CCS-Skills/skills/ccs-submission .agents/skills/ccs-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 "ccs-submission" agent skill from https://github.com/brycewang-stanford/Awesome-Journal-Skills/tree/main/ACM-CCS-Skills/skills/ccs-submission into .agents/skills/ccs-submission/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "ccs-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 ccs-submission -a cursorProject install goes to .agents/skills/; add -g for ~/.cursor/skills/.
$ gh skill install brycewang-stanford/Awesome-Journal-Skills ccs-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/ACM-CCS-Skills/skills/ccs-submission .cursor/skills/ccs-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 "ccs-submission" agent skill from https://github.com/brycewang-stanford/Awesome-Journal-Skills/tree/main/ACM-CCS-Skills/skills/ccs-submission into .cursor/skills/ccs-submission/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "ccs-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 ACM-CCS-Skills/skills/ccs-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 ccs-submission -a gemini-cliProject install goes to .agents/skills/; add -g for ~/.gemini/skills/.
$ gh skill install brycewang-stanford/Awesome-Journal-Skills ccs-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/ACM-CCS-Skills/skills/ccs-submission .gemini/skills/ccs-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 "ccs-submission" agent skill from https://github.com/brycewang-stanford/Awesome-Journal-Skills/tree/main/ACM-CCS-Skills/skills/ccs-submission into .gemini/skills/ccs-submission/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "ccs-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 ccs-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 ccs-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/ACM-CCS-Skills/skills/ccs-submission .github/skills/ccs-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 "ccs-submission" agent skill from https://github.com/brycewang-stanford/Awesome-Journal-Skills/tree/main/ACM-CCS-Skills/skills/ccs-submission into .github/skills/ccs-submission/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "ccs-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 ccs-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 ccs-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/ACM-CCS-Skills/skills/ccs-submission .opencode/skills/ccs-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 "ccs-submission" agent skill from https://github.com/brycewang-stanford/Awesome-Journal-Skills/tree/main/ACM-CCS-Skills/skills/ccs-submission into .opencode/skills/ccs-submission/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "ccs-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
ccs-submission- GitHub stars
- 1.2k
- Token cost
- ~1k tokens
- SKILL.md length
- 486 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 ACM CCS submission for HotCRP readiness, dual-cycle abstract registration and full-paper deadlines, the 12-page ACM sigconf body, anonymization, the ethics…
- Works in 5 steps: Freeze the threat model and… → Re-run the adaptive-attack evaluation… → Draft the ethics and… → …
- Auditing an ACM CCS submission for HotCRP readiness
- SKILL.md covers Submission audit, Blocking risks, Desk-reject and triage table and Final-week sequence for an…, plus 2 more sections
- Instructions only: no scripts, shell commands, URLs or credentials in SKILL.md
What it does
Ccs Submission is an agent skill from brycewang-stanford/Awesome-Journal-Skills. Use when auditing an ACM CCS submission for HotCRP readiness, dual-cycle abstract registration and full-paper deadlines, the 12-page ACM sigconf body, anonymization, the ethics considerations appendix, artifact-availability posture, dual-submission policy, per-cycle submission caps, desk-reject triggers, and final-week sequencing.
Its SKILL.md is about 1k 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. 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 ACM CCS submission for HotCRP readiness
- Dual-cycle abstract registration and full-paper deadlines
- The 12-page ACM sigconf body
- The ethics considerations appendix
Example prompts
- “/ccs-submission”
Workflow steps
5 steps, taken from the first numbered list in SKILL.md.
- Freeze the threat model and attacker-capability statement; reviewers score against it.
- Re-run the adaptive-attack evaluation from logged configs so the PDF and artifact agree.
- Draft the ethics and responsible-disclosure section against what you actually did.
- Strip PDF metadata, tool authorship strings, and repository owner names from every link.
- Register the abstract early, then confirm the HotCRP PDF matches the registered abstract.
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
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
Ccs Submission loads about 1k tokens when it runs. Until then it costs about 87 tokens; SKILL.md has 486 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). 486 words, ~1,004 tokens.
Download SKILL.mdSave it as
.claude/skills/ccs-submission/SKILL.md (or your agent's skills folder).- name
- ccs-submission
- description
- Use when auditing an ACM CCS submission for HotCRP readiness, dual-cycle abstract registration and full-paper deadlines, the 12-page ACM sigconf body, anonymization, the ethics considerations appendix, artifact-availability posture, dual-submission policy, per-cycle submission caps, desk-reject triggers, and final-week sequencing.
CCS Submission
Use this for a CCS paper submission audit. Reopen the current Call for Papers, the cycle's HotCRP site, the ACM sigconf template, and the ethics policy before giving deadline-ready advice, because CCS rules and dates are set per cycle.
Submission audit
- Confirm the target is the main CCS research track, not a workshop, poster, or the SIGSAC co-located events.
- Register the abstract in HotCRP before the registration deadline. CCS requires a mandatory title, author list, abstract, and topics one week before the full-paper deadline; no abstract, no paper. In 2026 registration led the paper deadline by seven days each cycle.
- Apply the unaltered ACM
sigconftwo-column template. CCS 2026 set a 12-page main-text limit excluding the bibliography, well-marked appendices, and supplementary material. Whitespace and margin tampering is forbidden and is a desk-reject trigger. - Enforce anonymization: cite your own prior work in the third person, blind references only where third-person phrasing is infeasible, and strip identity from text, PDF metadata, system names, and repository links.
- Place the ethics considerations content in a dedicated section (in 2026, an appendix after the 12-page body and bibliography) whenever the work touches human subjects, user data, or real-world vulnerabilities.
- Respect the per-cycle submission cap (2026: at most 7 papers per author per cycle) and the one-cycle rule — a first-cycle reject cannot return the same year.
- Confirm the work is not concurrently under review at another archival venue.
Blocking risks
- Missing abstract registration, or a late abstract or paper upload.
- Overlength main text or an altered
sigconftemplate. - Identity leak in the PDF, metadata, artifact link, or a non-blinded system name.
- Missing ethics considerations section for work that plainly needs one.
- Dual submission to another archival security venue.
- A threat model too vague for reviewers to score the attacker.
Show full SKILL.md (191 more words)Show less
Desk-reject and triage table
| Trigger | Severity at CCS | Repair window |
|---|---|---|
| No registered abstract by the deadline | Cannot submit | None |
| Overlength 12-page body or template tampering | Desk reject | None after the deadline |
| Identity leak in PDF or artifact link | Desk reject | None |
| Ethics section missing for human-subjects/vuln work | Desk reject or major flag | Only before the deadline |
| Vague threat model | Review-stage damage | Fixable in the writing pass |
Final-week sequence for an attack-plus-defense paper
- Freeze the threat model and attacker-capability statement; reviewers score against it.
- Re-run the adaptive-attack evaluation from logged configs so the PDF and artifact agree.
- Draft the ethics and responsible-disclosure section against what you actually did.
- Strip PDF metadata, tool authorship strings, and repository owner names from every link.
- Register the abstract early, then confirm the HotCRP PDF matches the registered abstract.
Format anchors
- CCS uses a dense two-column
sigconflayout; wide system diagrams, protocol figures, and multi-column result tables that fit a one-column draft overflow, so compress early. - The page and cap numbers above describe the 2026 cycle; treat every number as provisional and recheck the current CFP before relying on it.
Output format
[CCS readiness] Ready / Needs fixes / Not ready
[Blocking checks] <abstract-reg / page / anonymity / ethics / dual-submission / cap>
[Threat-model risk] <one issue>
[Desk-reject risk] <one issue>
[Fix order] <ordered fixes before submission>© 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 ACM-CCS-Skills/skills/ccs-submission of brycewang-stanford/Awesome-Journal-Skills.
Open the folder on GitHubat commit 932eb23
Compare with similar skills
Ccs 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 |
|---|---|---|---|---|---|---|
| Ccs Submission this skillbrycewang-stanford/Awesome-Journal-Skills | 1.2k | — | ~1k | Automated safety check: Pass | MIT | |
| Hypothesis Generationspacering-net/codeg | 3.9k | 14 repos | ~3.6k | Automated safety check: Notes | MIT | |
| GitHub Deep Researchbytedance/deer-flow | 84k | 4 repos | ~1.3k | Automated safety check: Pass | MIT | |
| Nature Paper CardYuan1z0825/nature-skills | 47k | 2 repos | ~2.1k | Automated safety check: Pass | Apache-2.0 | |
| Content Research Writerweapp-tailwindcss/weapp-tailwindcss | 1.9k | 25 repos | ~3.5k | Automated safety check: Pass | MIT | |
| Last30daysmvanhorn/last30days-skill | 64k | — | ~7.9k | Automated safety check: Notes | MIT |
Similar skills
GitHub Deep Research
bytedance/deer-flow
Researches a GitHub repository over four rounds using the GitHub API and web search, then writes a structured markdown report with timeline, metrics and Mermaid diagrams.
Nature Paper Card
Yuan1z0825/nature-skills
Builds a structured deep-reading card for one scientific paper, covering methods, how experiments support claims, limitations and research ideas, with a script to prepare the source.
Content Research Writer
weapp-tailwindcss/weapp-tailwindcss
Assists in writing high-quality content by conducting research, adding citations, improving hooks, iterating on outlines, and providing real-time feedback on each section.
Last30days
mvanhorn/last30days-skill
Research what people actually say about any topic in the last 30 days.
Peer Review
spacering-net/codeg
Structured manuscript/grant review with checklist-based evaluation.
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 Ccs Submission
What does Ccs Submission do?
A skill your agent uses when auditing an ACM CCS submission for HotCRP readiness, dual-cycle abstract registration and full-paper deadlines, the 12-page ACM sigconf body, anonymization, the ethics…. Ccs Submission is an agent skill from brycewang-stanford/Awesome-Journal-Skills. Use when auditing an ACM CCS submission for HotCRP readiness, dual-cycle abstract registration and full-paper deadlines, the 12-page ACM sigconf body, anonymization, the ethics considerations appendix, artifact-availability posture, dual-submission policy, per-cycle submission caps, desk-reject triggers, and final-week sequencing.
When should I use Ccs Submission?
Ccs Submission fits situations like: auditing an ACM CCS submission for HotCRP readiness; dual-cycle abstract registration and full-paper deadlines; the 12-page ACM sigconf body; the ethics considerations appendix.
How do I install Ccs Submission in Claude Code?
Run `npx skills add brycewang-stanford/Awesome-Journal-Skills --skill ccs-submission -a claude-code`. Or copy the skill folder (ACM-CCS-Skills/skills/ccs-submission in brycewang-stanford/Awesome-Journal-Skills) into .claude/skills/ccs-submission in your project. Claude Code loads it when a task matches its description.
How do I install Ccs Submission in Codex?
Run `npx skills add brycewang-stanford/Awesome-Journal-Skills --skill ccs-submission -a codex`. Or copy the skill folder (ACM-CCS-Skills/skills/ccs-submission in brycewang-stanford/Awesome-Journal-Skills) into .agents/skills/ccs-submission in your project. Codex loads it when a task matches its description.
Can I use Ccs 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 ccs-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/ccs-submission, .gemini/skills/ccs-submission, .github/skills/ccs-submission and .opencode/skills/ccs-submission in your project.
What does Ccs Submission need to run?
SKILL.md names no scripts, command-line tools or credentials: Ccs Submission is instructions for the agent only.
Does Ccs 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 Ccs 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 Ccs Submission use?
Ccs 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 Ccs Submission use?
About 1k tokens (SKILL.md is roughly 4k 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 Ccs Submission?
Skills that share tags, products or a category with Ccs Submission: Hypothesis Generation (spacering-net/codeg, 3.9k stars), GitHub Deep Research (bytedance/deer-flow, 84k stars), Nature Paper Card (Yuan1z0825/nature-skills, 47k stars) and Content Research Writer (weapp-tailwindcss/weapp-tailwindcss, 1.9k stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.
Who maintains Ccs 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.