Hypothesis Generation
spacering-net/codeg
Structured hypothesis formulation from observations. An agent skill from spacering-net/codeg.
A skill your agent uses when deciding what belongs in a SOSP supplementary document versus the 12-page paper, packaging proofs, extended analyses, and methodological detail as a separate anonymized…
Install Sosp Supplementary
$ npx skills add brycewang-stanford/Awesome-Journal-Skills --skill sosp-supplementary -a claude-codeProject install by default; add -g for ~/.claude/skills/.
$ gh skill install brycewang-stanford/Awesome-Journal-Skills sosp-supplementary --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/SOSP-Skills/skills/sosp-supplementary .claude/skills/sosp-supplementary && 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 "sosp-supplementary" agent skill from https://github.com/brycewang-stanford/Awesome-Journal-Skills/tree/main/SOSP-Skills/skills/sosp-supplementary into .claude/skills/sosp-supplementary/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "sosp-supplementary", 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/SOSP-Skills/skills/sosp-supplementaryType 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 sosp-supplementary -a codexProject install goes to .agents/skills/; add -g for ~/.codex/skills/.
$ gh skill install brycewang-stanford/Awesome-Journal-Skills sosp-supplementary --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/SOSP-Skills/skills/sosp-supplementary .agents/skills/sosp-supplementary && rm -rf skills-srcUse ~/.agents/skills/ instead of .agents/skills for a personal install.
Codex skills documentation · loads skills from .agents/skills/
Install the "sosp-supplementary" agent skill from https://github.com/brycewang-stanford/Awesome-Journal-Skills/tree/main/SOSP-Skills/skills/sosp-supplementary into .agents/skills/sosp-supplementary/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "sosp-supplementary", 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 sosp-supplementary -a cursorProject install goes to .agents/skills/; add -g for ~/.cursor/skills/.
$ gh skill install brycewang-stanford/Awesome-Journal-Skills sosp-supplementary --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/SOSP-Skills/skills/sosp-supplementary .cursor/skills/sosp-supplementary && 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 "sosp-supplementary" agent skill from https://github.com/brycewang-stanford/Awesome-Journal-Skills/tree/main/SOSP-Skills/skills/sosp-supplementary into .cursor/skills/sosp-supplementary/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "sosp-supplementary", 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 SOSP-Skills/skills/sosp-supplementary--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 sosp-supplementary -a gemini-cliProject install goes to .agents/skills/; add -g for ~/.gemini/skills/.
$ gh skill install brycewang-stanford/Awesome-Journal-Skills sosp-supplementary --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/SOSP-Skills/skills/sosp-supplementary .gemini/skills/sosp-supplementary && 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 "sosp-supplementary" agent skill from https://github.com/brycewang-stanford/Awesome-Journal-Skills/tree/main/SOSP-Skills/skills/sosp-supplementary into .gemini/skills/sosp-supplementary/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "sosp-supplementary", 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 sosp-supplementaryInstalls 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 sosp-supplementary -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/SOSP-Skills/skills/sosp-supplementary .github/skills/sosp-supplementary && 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 "sosp-supplementary" agent skill from https://github.com/brycewang-stanford/Awesome-Journal-Skills/tree/main/SOSP-Skills/skills/sosp-supplementary into .github/skills/sosp-supplementary/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "sosp-supplementary", 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 sosp-supplementary -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 sosp-supplementary --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/SOSP-Skills/skills/sosp-supplementary .opencode/skills/sosp-supplementary && 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 "sosp-supplementary" agent skill from https://github.com/brycewang-stanford/Awesome-Journal-Skills/tree/main/SOSP-Skills/skills/sosp-supplementary into .opencode/skills/sosp-supplementary/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "sosp-supplementary", 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
sosp-supplementary- GitHub stars
- 1.2k
- Token cost
- ~1.3k tokens
- SKILL.md length
- 587 words
- Files
- 1
- Skills in repo
- 2,387
- Repo updated
- First seen
- Licence
- MIT
At a glance
A skill your agent uses when deciding what belongs in a SOSP supplementary document versus the 12-page paper, packaging proofs, extended analyses, and methodological detail as a separate anonymized…
- Works in 3 steps: Supplementary document — submitted with… → Artifact package — prepared after… → Camera-ready appendix — final papers get…
- Deciding what belongs in a SOSP supplementary document versus the 12-page paper
- SKILL.md covers The governing asymmetry, Anonymity extends to the…, Supplement, artifact, and… and Structuring for a skimming…, plus 1 more section
- Calls pdftotext
What it does
Sosp Supplementary is an agent skill from brycewang-stanford/Awesome-Journal-Skills. Use when deciding what belongs in a SOSP supplementary document versus the 12-page paper, packaging proofs, extended analyses, and methodological detail as a separate anonymized upload, and keeping review-critical evidence out of material reviewers are not obligated to read.
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
- Deciding what belongs in a SOSP supplementary document versus the 12-page paper
- Packaging proofs
- Extended analyses
- Methodological detail as a separate anonymized upload
Example prompts
- “/sosp-supplementary”
Workflow steps
3 steps, taken from the first numbered list in SKILL.md.
- Supplementary document — submitted with the paper in April, anonymized,
- Artifact package — prepared after acceptance for the sysartifacts evaluation,
- Camera-ready appendix — final papers get 13 pages (14 with shepherd approval),
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
Sosp Supplementary loads about 1.3k tokens when it runs. Until then it costs about 74 tokens; SKILL.md has 587 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). 587 words, ~1,320 tokens.
Download SKILL.mdSave it as
.claude/skills/sosp-supplementary/SKILL.md (or your agent's skills folder).- name
- sosp-supplementary
- description
- Use when deciding what belongs in a SOSP supplementary document versus the 12-page paper, packaging proofs, extended analyses, and methodological detail as a separate anonymized upload, and keeping review-critical evidence out of material reviewers are not obligated to read.
SOSP Supplementary Material
Use this while splitting content between the SOSP paper and its optional supplement.
The CFP (2026 cycle, checked 2026-07-08 via sigops.org/s/conferences/sosp/2026/cfp.html
and the sosp26.hotcrp.com submission form) allows supplementary material as a
separate document uploaded alongside the anonymized PDF. Its charter is narrow:
content that supports the paper but is not critical to evaluating it — formal
proofs, extra data analyses, methodological detail. Reviewers may open it; nothing
obligates them to.
The governing asymmetry
The paper must stand alone inside its 12 pages of technical content. The supplement can only deepen an argument the paper already completes — it cannot carry one. This produces a simple sorting rule for every candidate paragraph, proof, and figure:
| Content | Where it lives | Why |
|---|---|---|
| The invariant your correctness claim rests on, stated and argued | Paper | Review-critical; a reviewer who skips the supplement must still be convinced |
| The full mechanized or manual proof of that invariant | Supplement | Depth behind a claim the paper already supports with a proof sketch |
| Headline performance results and their experimental setup | Paper | Claims and their primary evidence are inseparable |
| Per-workload breakdowns, extra hardware configurations, sensitivity sweeps | Supplement | Corroboration, not the load-bearing evidence |
| Anything a reviewer needs to check soundness of the method | Paper | "Not critical to evaluating the paper" excludes it from the supplement by definition |
| Pseudocode too long for the paper, trace-format specifications | Supplement | Methodological detail |
The classic failure: page pressure at T-minus-two-weeks pushes the failure-recovery evaluation into the supplement, a reviewer never opens it, and the review reads "no failure experiments." During SOSP's response phase you may point back to the supplement — it was part of the submission — but a pointer in a sub-500-word response is a weak substitute for evidence on the reviewed pages.
Anonymity extends to the supplement
The supplement is reviewed under the same double-blind rules as the paper. It is the more dangerous document because it is assembled last and checked least:
- Appendix LaTeX often still carries
\authorblocks, acknowledgment stubs, or grant numbers from an earlier tech-report build. - Extended data tables can leak cluster hostnames, internal project codenames, or usernames embedded in file paths.
- PDF metadata is regenerated at every compile; scrub the supplement's, not only the paper's.
# Run the same leak sweep on the supplement as on the paper
pdfinfo supplement.pdf | grep -iE '^(author|creator)'
pdftotext supplement.pdf - | grep -inE 'acknowledg|grant|@[a-z-]+\.(edu|com)|/home/[a-z]|corp\.' | head
# Cross-check: every paper reference to the supplement resolves
pdftotext main.pdf - | grep -oE 'supplement[a-z]* (§|Section |Appendix )?[A-Z0-9.]*' | sort -uShow full SKILL.md (222 more words)Show less
Supplement, artifact, and appendix are three different objects
Teams routinely conflate three artifacts with different clocks and audiences:
- Supplementary document — submitted with the paper in April, anonymized, read (maybe) by paper reviewers. Governed by this skill.
- Artifact package — prepared after acceptance for the sysartifacts evaluation,
non-anonymous, exercised by a separate committee (see
sosp-artifact-evaluation). Do not burn April effort polishing container images no paper reviewer will run. - Camera-ready appendix — final papers get 13 pages (14 with shepherd approval),
so some supplement content may graduate into the paper itself after acceptance
(see
sosp-camera-ready).
Plan the April supplement knowing routes 2 and 3 exist: its only job is to survive review, not to be the archival record of everything you know.
Structuring for a skimming reviewer
A SOSP reviewer opening the supplement is looking for one specific thing mid-review. Optimize for that entry pattern:
- Open with a half-page map: each supplement section, one line on what it adds, and which paper section or claim it backs.
- Number supplement sections to continue or clearly reference the paper's numbering, and cite them from the paper precisely ("full proof in supplement §B.2"), never as a bare "see supplement."
- Keep each section self-contained enough to read without the neighboring ones; a reviewer chasing the proof of Invariant I2 should not need supplement §A first.
Output format
[Split audit] review-critical content found in supplement? <list or none>
[Paper -> supplement pointers] all resolve? <broken refs>
[Anonymity] supplement metadata + text sweep result
[Confusion check] AE-only material mistakenly built now? camera-ready graduation list?
[Map] supplement sections -> paper claims they back
[Fix order] <moves before the upload>© 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 SOSP-Skills/skills/sosp-supplementary of brycewang-stanford/Awesome-Journal-Skills.
Open the folder on GitHubat commit 932eb23
Compare with similar skills
Sosp Supplementary 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 |
|---|---|---|---|---|---|---|
| Sosp Supplementary 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 Sosp Supplementary
What does Sosp Supplementary do?
A skill your agent uses when deciding what belongs in a SOSP supplementary document versus the 12-page paper, packaging proofs, extended analyses, and methodological detail as a separate anonymized…. Sosp Supplementary is an agent skill from brycewang-stanford/Awesome-Journal-Skills. Use when deciding what belongs in a SOSP supplementary document versus the 12-page paper, packaging proofs, extended analyses, and methodological detail as a separate anonymized upload, and keeping review-critical evidence out of material reviewers are not obligated to read.
When should I use Sosp Supplementary?
Sosp Supplementary fits situations like: deciding what belongs in a SOSP supplementary document versus the 12-page paper; packaging proofs; extended analyses; methodological detail as a separate anonymized upload.
How do I install Sosp Supplementary in Claude Code?
Run `npx skills add brycewang-stanford/Awesome-Journal-Skills --skill sosp-supplementary -a claude-code`. Or copy the skill folder (SOSP-Skills/skills/sosp-supplementary in brycewang-stanford/Awesome-Journal-Skills) into .claude/skills/sosp-supplementary in your project. Claude Code loads it when a task matches its description.
How do I install Sosp Supplementary in Codex?
Run `npx skills add brycewang-stanford/Awesome-Journal-Skills --skill sosp-supplementary -a codex`. Or copy the skill folder (SOSP-Skills/skills/sosp-supplementary in brycewang-stanford/Awesome-Journal-Skills) into .agents/skills/sosp-supplementary in your project. Codex loads it when a task matches its description.
Can I use Sosp Supplementary 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 sosp-supplementary -a cursor` (or -a gemini-cli, github-copilot or opencode for the others). To copy it by hand, put the folder in .cursor/skills/sosp-supplementary, .gemini/skills/sosp-supplementary, .github/skills/sosp-supplementary and .opencode/skills/sosp-supplementary in your project.
What does Sosp Supplementary need to run?
Going by SKILL.md and its folder, Sosp Supplementary needs the command-line tools its instructions call (pdftotext).
Does Sosp Supplementary 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 Sosp Supplementary 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 Sosp Supplementary use?
Sosp Supplementary 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 Sosp Supplementary use?
About 1.3k tokens (SKILL.md is roughly 5.3k 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 Sosp Supplementary?
Skills that share tags, products or a category with Sosp Supplementary: 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 Sosp Supplementary?
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.