Hypothesis Generation
spacering-net/codeg
Structured hypothesis formulation from observations. An agent skill from spacering-net/codeg.
A skill your agent uses when preparing an accepted ACM SoCC paper for its camera-ready, covering de-anonymization, the acmart/sigconf final format and ACM metadata (DOI, ORCID, CCS concepts)…
Install Socc Camera Ready
$ npx skills add brycewang-stanford/Awesome-Journal-Skills --skill socc-camera-ready -a claude-codeProject install by default; add -g for ~/.claude/skills/.
$ gh skill install brycewang-stanford/Awesome-Journal-Skills socc-camera-ready --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/SoCC-Skills/skills/socc-camera-ready .claude/skills/socc-camera-ready && 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 "socc-camera-ready" agent skill from https://github.com/brycewang-stanford/Awesome-Journal-Skills/tree/main/SoCC-Skills/skills/socc-camera-ready into .claude/skills/socc-camera-ready/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "socc-camera-ready", 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/SoCC-Skills/skills/socc-camera-readyType 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 socc-camera-ready -a codexProject install goes to .agents/skills/; add -g for ~/.codex/skills/.
$ gh skill install brycewang-stanford/Awesome-Journal-Skills socc-camera-ready --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/SoCC-Skills/skills/socc-camera-ready .agents/skills/socc-camera-ready && rm -rf skills-srcUse ~/.agents/skills/ instead of .agents/skills for a personal install.
Codex skills documentation · loads skills from .agents/skills/
Install the "socc-camera-ready" agent skill from https://github.com/brycewang-stanford/Awesome-Journal-Skills/tree/main/SoCC-Skills/skills/socc-camera-ready into .agents/skills/socc-camera-ready/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "socc-camera-ready", 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 socc-camera-ready -a cursorProject install goes to .agents/skills/; add -g for ~/.cursor/skills/.
$ gh skill install brycewang-stanford/Awesome-Journal-Skills socc-camera-ready --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/SoCC-Skills/skills/socc-camera-ready .cursor/skills/socc-camera-ready && 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 "socc-camera-ready" agent skill from https://github.com/brycewang-stanford/Awesome-Journal-Skills/tree/main/SoCC-Skills/skills/socc-camera-ready into .cursor/skills/socc-camera-ready/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "socc-camera-ready", 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 SoCC-Skills/skills/socc-camera-ready--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 socc-camera-ready -a gemini-cliProject install goes to .agents/skills/; add -g for ~/.gemini/skills/.
$ gh skill install brycewang-stanford/Awesome-Journal-Skills socc-camera-ready --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/SoCC-Skills/skills/socc-camera-ready .gemini/skills/socc-camera-ready && 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 "socc-camera-ready" agent skill from https://github.com/brycewang-stanford/Awesome-Journal-Skills/tree/main/SoCC-Skills/skills/socc-camera-ready into .gemini/skills/socc-camera-ready/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "socc-camera-ready", 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 socc-camera-readyInstalls 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 socc-camera-ready -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/SoCC-Skills/skills/socc-camera-ready .github/skills/socc-camera-ready && 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 "socc-camera-ready" agent skill from https://github.com/brycewang-stanford/Awesome-Journal-Skills/tree/main/SoCC-Skills/skills/socc-camera-ready into .github/skills/socc-camera-ready/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "socc-camera-ready", 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 socc-camera-ready -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 socc-camera-ready --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/SoCC-Skills/skills/socc-camera-ready .opencode/skills/socc-camera-ready && 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 "socc-camera-ready" agent skill from https://github.com/brycewang-stanford/Awesome-Journal-Skills/tree/main/SoCC-Skills/skills/socc-camera-ready into .opencode/skills/socc-camera-ready/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "socc-camera-ready", 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
socc-camera-ready- GitHub stars
- 1.2k
- Token cost
- ~1.3k tokens
- SKILL.md length
- 519 words
- Files
- 1
- Skills in repo
- 2,387
- Repo updated
- First seen
- Licence
- MIT
At a glance
A skill your agent uses when preparing an accepted ACM SoCC paper for its camera-ready, covering de-anonymization, the acmart/sigconf final format and ACM metadata (DOI, ORCID, CCS concepts)…
- Preparing an accepted ACM SoCC paper for its camera-ready
- SKILL.md covers Camera-ready audit, De-anonymization sweep, ACM production checks and Worked example: integrating a…, plus 3 more sections
- Instructions only: no scripts, shell commands, URLs or credentials in SKILL.md
- Covering de-anonymization
What it does
Socc Camera Ready is an agent skill from brycewang-stanford/Awesome-Journal-Skills. Use when preparing an accepted ACM SoCC paper for its camera-ready, covering de-anonymization, the acmart/sigconf final format and ACM metadata (DOI, ORCID, CCS concepts), integrating reviewer-required changes without scope creep, permanentizing released code and traces, the ACM rights/e-copyright form, and the presentation obligation in Singapore.
Its SKILL.md is about 1.3k 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
- Preparing an accepted ACM SoCC paper for its camera-ready
- Covering de-anonymization
- The acmart/sigconf final format and ACM metadata (DOI
- Integrating reviewer-required changes without scope creep
Example prompts
- “/socc-camera-ready”
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
Socc Camera Ready loads about 1.3k tokens when it runs. Until then it costs about 92 tokens; SKILL.md has 519 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). 519 words, ~1,310 tokens.
Download SKILL.mdSave it as
.claude/skills/socc-camera-ready/SKILL.md (or your agent's skills folder).- name
- socc-camera-ready
- description
- Use when preparing an accepted ACM SoCC paper for its camera-ready, covering de-anonymization, the acmart/sigconf final format and ACM metadata (DOI, ORCID, CCS concepts), integrating reviewer-required changes without scope creep, permanentizing released code and traces, the ACM rights/e-copyright form, and the presentation obligation in Singapore.
SoCC Camera Ready
Use this after acceptance in a SoCC round. The camera-ready turns the anonymized acmart
submission into the final ACM Digital Library version of your ACM Symposium on Cloud Computing
paper. Reopen the current SoCC author instructions, the acceptance email, and the ACM rights page
before advising — SoCC is jointly SIGMOD+SIGOPS, and its camera-ready is an ACM production step,
not just a formatting pass.
Camera-ready audit
- De-anonymize completely: restore the author block, affiliations, acknowledgements, funding, and the real system, cluster, provider, and trace names that dual anonymity forced you to hide.
- Apply the final format: the ACM Primary Article Template,
sigconf, within the 12-page (full) or 6-page (short) budget, with any camera-ready page allowance the acceptance letter grants; references remain unlimited. - Complete ACM metadata: title/abstract, author order, ORCIDs, ACM CCS concepts and keywords, and the DOI-bearing citation once assigned. Metadata errors are harder to fix after publication than formatting ones.
- Integrate reviewer-required changes from the reviews and rebuttal faithfully — add the tail or cost breakdown you promised, fix the misread workload — without strengthening claims beyond what was evaluated.
- Permanentize reproducibility: replace anonymized artifact links with a public, licensed, DOI-issuing archive, and make released code, workload generators, and traces available (or document why a trace cannot be released).
- Confirm registration and presentation: SoCC 2026 is in person in Singapore (Nov 18-20, 2026); at least one author presents.
De-anonymization sweep
| Anonymized at submission | Restore at camera-ready | Watch for |
|---|---|---|
| Author block, affiliations, ORCID | Full, correctly ordered | Wrong author order breaks the DOI citation |
| System / cluster / trace name | Real name throughout text, figures, artifact | A leftover anonymized placeholder in a caption |
| Cloud provider / deployment identity | Restored where disclosable | Confidentiality limits on naming a provider |
| Acknowledgements, funding | Restored | Grant numbers required by funders |
| Self-citations (third person) | Natural first-person where it aids clarity | Over-correcting and double-citing |
| Artifact / trace link | Public archive DOI | The old anonymized URL surviving in a footnote |
Show full SKILL.md (203 more words)Show less
ACM production checks
[Template] acmart sigconf, current revision; no manual margin/font edits; correct page budget
[Metadata] title, abstract, authors+ORCID, CCS concepts, keywords entered and matching the PDF
[References] complete, consistent, DOIs where available; unlimited allowance, but keep it clean
[Figures] vector where possible; tail/cost plots readable in print; captions self-contained
[Rights] ACM e-rights/copyright form completed; correct rights block on the first page
[Links] every released-code and trace link resolves from a logged-out browserWorked example: integrating a rebuttal promise
The reviewers accepted the paper on the condition that the p99.9 breakdown and the pricing model behind the cost claim appear in the final version. Camera-ready move: add the p99.9 figure from the existing logs beside the p99 result, add one paragraph stating the pricing model and the resulting saving, restore the real system and testbed names in those figures, and point the availability statement at the now-public trace-replay archive — without expanding the cost claim beyond the regimes measured.
Artifact and badge handoff
If the edition runs artifact evaluation, the camera-ready and the artifact process may be separate
deadlines. Do not wait for the artifact result to finalize the paper, but make the paper's
availability statement consistent with the ACM badges you are pursuing (Available at minimum;
Functional / Reusable / Reproduced if the track grants them). Add any badge acknowledgement only per
the current instructions. Whether SoCC offers evaluation for a given edition is 待核实 — confirm
on the current call (socc-artifact-evaluation).
Hedged logistics
- Page allowances, metadata fields, rights-form mechanics, and exact camera-ready dates change each cycle and per round; confirm against the acceptance email and current SoCC instructions rather than a prior year.
Output format
[Camera-ready status] ready / needs fixes / blocked
[De-anonymization] author block / system+trace names / acks / links restored? yes/no
[ACM metadata] ORCID / CCS / keywords / rights form complete? yes/no
[Reviewer-change map] <required change -> final edit, no scope creep>
[Reproducibility] anonymized links replaced by DOI archive? trace released or exception documented?
[Remaining owner] <person -> task>© 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 SoCC-Skills/skills/socc-camera-ready of brycewang-stanford/Awesome-Journal-Skills.
Open the folder on GitHubat commit 932eb23
Compare with similar skills
Socc Camera Ready 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 |
|---|---|---|---|---|---|---|
| Socc Camera Ready this skillbrycewang-stanford/Awesome-Journal-Skills | 1.2k | — | ~1.3k | 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 Socc Camera Ready
What does Socc Camera Ready do?
A skill your agent uses when preparing an accepted ACM SoCC paper for its camera-ready, covering de-anonymization, the acmart/sigconf final format and ACM metadata (DOI, ORCID, CCS concepts)…. Socc Camera Ready is an agent skill from brycewang-stanford/Awesome-Journal-Skills. Use when preparing an accepted ACM SoCC paper for its camera-ready, covering de-anonymization, the acmart/sigconf final format and ACM metadata (DOI, ORCID, CCS concepts), integrating reviewer-required changes without scope creep, permanentizing released code and traces, the ACM rights/e-copyright form, and the presentation obligation in Singapore.
When should I use Socc Camera Ready?
Socc Camera Ready fits situations like: preparing an accepted ACM SoCC paper for its camera-ready; covering de-anonymization; the acmart/sigconf final format and ACM metadata (DOI; integrating reviewer-required changes without scope creep.
How do I install Socc Camera Ready in Claude Code?
Run `npx skills add brycewang-stanford/Awesome-Journal-Skills --skill socc-camera-ready -a claude-code`. Or copy the skill folder (SoCC-Skills/skills/socc-camera-ready in brycewang-stanford/Awesome-Journal-Skills) into .claude/skills/socc-camera-ready in your project. Claude Code loads it when a task matches its description.
How do I install Socc Camera Ready in Codex?
Run `npx skills add brycewang-stanford/Awesome-Journal-Skills --skill socc-camera-ready -a codex`. Or copy the skill folder (SoCC-Skills/skills/socc-camera-ready in brycewang-stanford/Awesome-Journal-Skills) into .agents/skills/socc-camera-ready in your project. Codex loads it when a task matches its description.
Can I use Socc Camera Ready 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 socc-camera-ready -a cursor` (or -a gemini-cli, github-copilot or opencode for the others). To copy it by hand, put the folder in .cursor/skills/socc-camera-ready, .gemini/skills/socc-camera-ready, .github/skills/socc-camera-ready and .opencode/skills/socc-camera-ready in your project.
What does Socc Camera Ready need to run?
SKILL.md names no scripts, command-line tools or credentials: Socc Camera Ready is instructions for the agent only.
Does Socc Camera Ready 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 Socc Camera Ready 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 Socc Camera Ready use?
Socc Camera Ready 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 Socc Camera Ready 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 Socc Camera Ready?
Skills that share tags, products or a category with Socc Camera Ready: 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 Socc Camera Ready?
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.