Stata
dylantmoore/stata-skill
Comprehensive Stata reference for writing correct .do files, data management, econometrics, causal inference, graphics, Mata programming, and 20 community packages (reghdfe, estout, did, rdrobust…
A skill your agent uses when deciding what goes into the 10-page body versus the replication package of an ICSE research-track submission, covering the no-unlimited-appendix page model, anonymized…
Install Icse Supplementary
$ npx skills add brycewang-stanford/Awesome-Journal-Skills --skill icse-supplementary -a claude-codeProject install by default; add -g for ~/.claude/skills/.
$ gh skill install brycewang-stanford/Awesome-Journal-Skills icse-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/ICSE-Skills/skills/icse-supplementary .claude/skills/icse-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 "icse-supplementary" agent skill from https://github.com/brycewang-stanford/Awesome-Journal-Skills/tree/main/ICSE-Skills/skills/icse-supplementary into .claude/skills/icse-supplementary/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "icse-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/ICSE-Skills/skills/icse-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 icse-supplementary -a codexProject install goes to .agents/skills/; add -g for ~/.codex/skills/.
$ gh skill install brycewang-stanford/Awesome-Journal-Skills icse-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/ICSE-Skills/skills/icse-supplementary .agents/skills/icse-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 "icse-supplementary" agent skill from https://github.com/brycewang-stanford/Awesome-Journal-Skills/tree/main/ICSE-Skills/skills/icse-supplementary into .agents/skills/icse-supplementary/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "icse-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 icse-supplementary -a cursorProject install goes to .agents/skills/; add -g for ~/.cursor/skills/.
$ gh skill install brycewang-stanford/Awesome-Journal-Skills icse-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/ICSE-Skills/skills/icse-supplementary .cursor/skills/icse-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 "icse-supplementary" agent skill from https://github.com/brycewang-stanford/Awesome-Journal-Skills/tree/main/ICSE-Skills/skills/icse-supplementary into .cursor/skills/icse-supplementary/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "icse-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 ICSE-Skills/skills/icse-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 icse-supplementary -a gemini-cliProject install goes to .agents/skills/; add -g for ~/.gemini/skills/.
$ gh skill install brycewang-stanford/Awesome-Journal-Skills icse-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/ICSE-Skills/skills/icse-supplementary .gemini/skills/icse-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 "icse-supplementary" agent skill from https://github.com/brycewang-stanford/Awesome-Journal-Skills/tree/main/ICSE-Skills/skills/icse-supplementary into .gemini/skills/icse-supplementary/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "icse-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 icse-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 icse-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/ICSE-Skills/skills/icse-supplementary .github/skills/icse-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 "icse-supplementary" agent skill from https://github.com/brycewang-stanford/Awesome-Journal-Skills/tree/main/ICSE-Skills/skills/icse-supplementary into .github/skills/icse-supplementary/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "icse-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 icse-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 icse-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/ICSE-Skills/skills/icse-supplementary .opencode/skills/icse-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 "icse-supplementary" agent skill from https://github.com/brycewang-stanford/Awesome-Journal-Skills/tree/main/ICSE-Skills/skills/icse-supplementary into .opencode/skills/icse-supplementary/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "icse-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
icse-supplementary- GitHub stars
- 1.2k
- Token cost
- ~1.5k tokens
- SKILL.md length
- 655 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 goes into the 10-page body versus the replication package of an ICSE research-track submission, covering the no-unlimited-appendix page model, anonymized…
- Deciding what goes into the 10-page body versus the replication package of an ICSE research-track submission
- SKILL.md covers The placement rule, Summarize-and-point discipline, Package layout reviewers can… and Anonymity of the archive, plus 4 more sections
- Calls git
- Covering the no-unlimited-appendix page model
What it does
Icse Supplementary is an agent skill from brycewang-stanford/Awesome-Journal-Skills. Use when deciding what goes into the 10-page body versus the replication package of an ICSE research-track submission, covering the no-unlimited-appendix page model, anonymized supplementary links and HotCRP uploads, package organization for reviewer navigation, and content-placement rules that protect the review.
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 Econometrics and empirical research. 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 goes into the 10-page body versus the replication package of an ICSE research-track submission
- Covering the no-unlimited-appendix page model
- Anonymized supplementary links and HotCRP uploads
- Package organization for reviewer navigation
Example prompts
- “/icse-supplementary”
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:
git
From the folder's file list and the shell code blocks in SKILL.md.
Network
No URLs in SKILL.md. Its commands use git, which can reach the network depending on how they are called.
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
Icse Supplementary loads about 1.5k tokens when it runs. Until then it costs about 84 tokens; SKILL.md has 655 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). 655 words, ~1,510 tokens.
Download SKILL.mdSave it as
.claude/skills/icse-supplementary/SKILL.md (or your agent's skills folder).- name
- icse-supplementary
- description
- Use when deciding what goes into the 10-page body versus the replication package of an ICSE research-track submission, covering the no-unlimited-appendix page model, anonymized supplementary links and HotCRP uploads, package organization for reviewer navigation, and content-placement rules that protect the review.
ICSE Supplementary Material
ICSE's page model is stricter than most authors coming from ML venues expect, and it inverts their packing instincts. The 2027 research-track format (read 2026-07-08): main text ≤ 10 pages inclusive of all figures, tables, and appendices, plus up to 2 pages of references only. There is no unlimited in-PDF appendix. Everything else travels as supplementary material — an anonymized link in the paper or an upload via HotCRP — and must be assumed optional reading.
The placement rule
One question decides placement: must a reviewer see it to score the paper?
| Content | Placement | Why |
|---|---|---|
| Anything a criterion score depends on: RQ answers, key tables, protocol essentials, the threat analysis | The 10 pages | Optional material cannot carry mandatory weight |
| Full prompt templates, extended proofs, extra result tables, per-subject breakdowns | Package, summarized in-body | Body states the finding + pointer; package holds the mass |
| Tool source, benchmark, scripts, raw outputs | Replication package | This is the verifiability substrate (icse-reproducibility) |
| Interview guides, codebooks, instruments | Package, named in the availability statement | Reviewers audit method through them when they choose to |
| Demo video, screenshots gallery | Package, only if genuinely clarifying | Never as a substitute for a precise in-body description |
The failure mode is load-bearing supplement: "due to space, the evaluation methodology is described in the supplementary material" invites the reviewer to score what the body shows — an unevidenced claim. Compress into the body instead: a protocol table instead of two prose pages, a summary row instead of the full matrix.
Summarize-and-point discipline
Every relocation leaves a residue in the body — the conclusion plus a precise pointer:
Patches for all 214 bugs, with per-bug generation logs, are in the package (
results/patches/); Table 5 reports the aggregate. The full 41-item codebook is incodebook.pdf; Table 2 shows the 6 categories with ≥10% prevalence.
Precise pointers (directory, file, section of the package README) also pay forward: they become the artifact-evaluation roadmap after acceptance.
Package layout reviewers can navigate in five minutes
replication-package/
├── README.md # map: claim/table/figure -> command -> output
├── REQUIREMENTS.md # env: versions, container digest, hardware, runtime
├── LICENSE # open license even at review time (anonymized holder)
├── code/ # tool source, pinned dependencies
├── benchmark/ # subjects or fetch-scripts with SHAs + mining date
├── scripts/ # one entry point per paper table/figure:
│ ├── run_rq1.sh # names match the RQs, not internal jargon
│ └── make_table3.py
├── results/ # raw outputs the paper's numbers derive from
└── appendix.pdf # extended tables/proofs that did not fit the bodyThe README's first section is a claims map: each headline claim, the command that regenerates its evidence, expected runtime, and expected output. A reviewer who checks one row and succeeds extends trust to the rest; one who hits a broken path on the first try generalizes that, too.
Show full SKILL.md (286 more words)Show less
Anonymity of the archive
The supplement must hold the same double-anonymous line as the paper:
git archive exports (no history), scrubbed notebook metadata, no
/home/username/ paths in configs or logs, no institutional hostnames, no
author names in LICENSE/setup.py/CITATION files, hosting through an
anonymizing service rather than a personal account. Scrub, then re-run the
entry-point scripts — anonymization that breaks paths converts your evidence
into a liability.
What must stay out of the package
Screening for exclusions is as important as packing inclusions: third-party code or datasets whose licenses forbid redistribution (link with pinned fetch-scripts instead); human-subjects raw data beyond what consent covers — transcripts, recordings, un-aggregated survey rows; credentials, API keys, and internal hostnames hiding in config files and CI logs; and proprietary industrial code shown to you under NDA, even in fragments quoted in comments. A replication package is a publication: it gets the same legal and ethical review as the paper, and a leak in the supplement is harder to retract than a sentence.
Size and dependency realism
No supplement size cap was verifiable for 2027 (待核实 on the live HotCRP form), so engineer for reviewer patience instead: keep the download small (fetch-scripts for large corpora, with checksums), keep the smoke test under minutes on a laptop, and never require credentials, cluster schedulers, or paid API keys for at least a reduced-scale verification path. Provide cached outputs beside every expensive step so the analysis chain can be verified without the compute.
Reverify each cycle
The 10+2 model, the HotCRP supplementary option, and the availability- statement placement are 2027-cycle facts; page models have changed across ICSE editions before. Confirm the current call before deciding any placement that would be expensive to reverse in deadline week.
Output format
[Body/package split] each relocated item -> residue sentence + pointer present?
[Load-bearing check] any criterion-relevant content living only in the package? (must be none)
[Package audit] layout roles present; claims map covers every headline number
[Anonymity + runnability] scrub done; entry points re-run post-scrub
[Reviewer path] smoke test minutes, laptop-feasible, credential-free© 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 ICSE-Skills/skills/icse-supplementary of brycewang-stanford/Awesome-Journal-Skills.
Open the folder on GitHubat commit 932eb23
Compare with similar skills
Icse 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 |
|---|---|---|---|---|---|---|
| Icse Supplementary this skillbrycewang-stanford/Awesome-Journal-Skills | 1.2k | — | ~1.5k | Automated safety check: Pass | MIT | |
| Statadylantmoore/stata-skill | 291 | 1 repos | ~4.2k | Automated safety check: Pass | Custom licence | |
| Stata C Pluginsdylantmoore/stata-skill | 291 | 1 repos | ~5.8k | Automated safety check: Pass | Custom licence | |
| Example Datasetspymc-labs/CausalPy | 1.2k | — | ~587 | Automated safety check: Pass | Apache-2.0 | |
| Stata AuditSepineTam/mcp-for-stata | 264 | — | ~1.2k | Automated safety check: Pass | AGPL-3.0 | |
| Stata Skill Contributordylantmoore/stata-skill | 291 | 1 repos | ~2.4k | Automated safety check: Pass | Custom licence |
Similar skills
Stata C Plugins
dylantmoore/stata-skill
Develop high-performance C/C++ plugins for Stata using the stplugin.h SDK.
Example Datasets
pymc-labs/CausalPy
Load built-in CausalPy example datasets for demos, tutorials, tests, and quick causal-analysis prototypes.
Stata Audit
SepineTam/mcp-for-stata
Inspect, validate, summarize, and render local Stata-MCP audit evidence under .statamcp.
Stata Skill Contributor
dylantmoore/stata-skill
Guide for contributing to the stata-skill project. An agent skill from dylantmoore/stata-skill.
Diagnostic Dofile
SepineTam/mcp-for-stata
A skill your agent uses when the user needs to inspect, audit, or diagnose the safety of a Stata do-file.
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 Icse Supplementary
What does Icse Supplementary do?
A skill your agent uses when deciding what goes into the 10-page body versus the replication package of an ICSE research-track submission, covering the no-unlimited-appendix page model, anonymized…. Icse Supplementary is an agent skill from brycewang-stanford/Awesome-Journal-Skills. Use when deciding what goes into the 10-page body versus the replication package of an ICSE research-track submission, covering the no-unlimited-appendix page model, anonymized supplementary links and HotCRP uploads, package organization for reviewer navigation, and content-placement rules that protect the review.
When should I use Icse Supplementary?
Icse Supplementary fits situations like: deciding what goes into the 10-page body versus the replication package of an ICSE research-track submission; covering the no-unlimited-appendix page model; anonymized supplementary links and HotCRP uploads; package organization for reviewer navigation.
How do I install Icse Supplementary in Claude Code?
Run `npx skills add brycewang-stanford/Awesome-Journal-Skills --skill icse-supplementary -a claude-code`. Or copy the skill folder (ICSE-Skills/skills/icse-supplementary in brycewang-stanford/Awesome-Journal-Skills) into .claude/skills/icse-supplementary in your project. Claude Code loads it when a task matches its description.
How do I install Icse Supplementary in Codex?
Run `npx skills add brycewang-stanford/Awesome-Journal-Skills --skill icse-supplementary -a codex`. Or copy the skill folder (ICSE-Skills/skills/icse-supplementary in brycewang-stanford/Awesome-Journal-Skills) into .agents/skills/icse-supplementary in your project. Codex loads it when a task matches its description.
Can I use Icse 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 icse-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/icse-supplementary, .gemini/skills/icse-supplementary, .github/skills/icse-supplementary and .opencode/skills/icse-supplementary in your project.
What does Icse Supplementary need to run?
Going by SKILL.md and its folder, Icse Supplementary needs the command-line tools its instructions call (git).
Does Icse Supplementary access the network?
SKILL.md contains no URLs. Its commands use git, which can reach the network depending on how they are called. This is read from the text; nothing was executed.
Is Icse 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 Icse Supplementary use?
Icse 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 Icse Supplementary use?
About 1.5k tokens (SKILL.md is roughly 6k 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 Icse Supplementary?
Skills that share tags, products or a category with Icse Supplementary: Stata (dylantmoore/stata-skill, 291 stars), Stata C Plugins (dylantmoore/stata-skill, 291 stars), Example Datasets (pymc-labs/CausalPy, 1.2k stars) and Stata Audit (SepineTam/mcp-for-stata, 264 stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.
Who maintains Icse 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.