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 TACAS (ETAPS) paper body versus its appendix, supplementary website, and artifact, covering the 16-page (or 6-page) llncs.cls budget that…
Install Tacas Supplementary
$ npx skills add brycewang-stanford/Awesome-Journal-Skills --skill tacas-supplementary -a claude-codeProject install by default; add -g for ~/.claude/skills/.
$ gh skill install brycewang-stanford/Awesome-Journal-Skills tacas-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/TACAS-Skills/skills/tacas-supplementary .claude/skills/tacas-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 "tacas-supplementary" agent skill from https://github.com/brycewang-stanford/Awesome-Journal-Skills/tree/main/TACAS-Skills/skills/tacas-supplementary into .claude/skills/tacas-supplementary/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "tacas-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/TACAS-Skills/skills/tacas-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 tacas-supplementary -a codexProject install goes to .agents/skills/; add -g for ~/.codex/skills/.
$ gh skill install brycewang-stanford/Awesome-Journal-Skills tacas-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/TACAS-Skills/skills/tacas-supplementary .agents/skills/tacas-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 "tacas-supplementary" agent skill from https://github.com/brycewang-stanford/Awesome-Journal-Skills/tree/main/TACAS-Skills/skills/tacas-supplementary into .agents/skills/tacas-supplementary/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "tacas-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 tacas-supplementary -a cursorProject install goes to .agents/skills/; add -g for ~/.cursor/skills/.
$ gh skill install brycewang-stanford/Awesome-Journal-Skills tacas-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/TACAS-Skills/skills/tacas-supplementary .cursor/skills/tacas-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 "tacas-supplementary" agent skill from https://github.com/brycewang-stanford/Awesome-Journal-Skills/tree/main/TACAS-Skills/skills/tacas-supplementary into .cursor/skills/tacas-supplementary/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "tacas-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 TACAS-Skills/skills/tacas-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 tacas-supplementary -a gemini-cliProject install goes to .agents/skills/; add -g for ~/.gemini/skills/.
$ gh skill install brycewang-stanford/Awesome-Journal-Skills tacas-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/TACAS-Skills/skills/tacas-supplementary .gemini/skills/tacas-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 "tacas-supplementary" agent skill from https://github.com/brycewang-stanford/Awesome-Journal-Skills/tree/main/TACAS-Skills/skills/tacas-supplementary into .gemini/skills/tacas-supplementary/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "tacas-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 tacas-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 tacas-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/TACAS-Skills/skills/tacas-supplementary .github/skills/tacas-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 "tacas-supplementary" agent skill from https://github.com/brycewang-stanford/Awesome-Journal-Skills/tree/main/TACAS-Skills/skills/tacas-supplementary into .github/skills/tacas-supplementary/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "tacas-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 tacas-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 tacas-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/TACAS-Skills/skills/tacas-supplementary .opencode/skills/tacas-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 "tacas-supplementary" agent skill from https://github.com/brycewang-stanford/Awesome-Journal-Skills/tree/main/TACAS-Skills/skills/tacas-supplementary into .opencode/skills/tacas-supplementary/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "tacas-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
tacas-supplementary- GitHub stars
- 1.2k
- Token cost
- ~1.2k tokens
- SKILL.md length
- 418 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 TACAS (ETAPS) paper body versus its appendix, supplementary website, and artifact, covering the 16-page (or 6-page) llncs.cls budget that…
- Deciding what belongs in a TACAS (ETAPS) paper body versus its appendix
- SKILL.md covers What goes where, The page-budget discipline, Category-appropriate anonymity… and The mandatory-artifact…, plus 2 more sections
- Instructions only: no scripts, shell commands, URLs or credentials in SKILL.md
- Supplementary website
What it does
Tacas Supplementary is an agent skill from brycewang-stanford/Awesome-Journal-Skills. Use when deciding what belongs in a TACAS (ETAPS) paper body versus its appendix, supplementary website, and artifact, covering the 16-page (or 6-page) llncs.cls budget that excludes references and appendix, the rule that decision-critical content stays in the reviewed pages, category-appropriate anonymity of supplementary material, and how to split a verification paper between body, appendix, and a mandatory-or-voluntary artifact.
Its SKILL.md is about 1.2k 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 TACAS (ETAPS) paper body versus its appendix
- Supplementary website
- Covering the 16-page (or 6-page) llncs.cls budget that excludes references and appendix
- The rule that decision-critical content stays in the reviewed pages
Example prompts
- “/tacas-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
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
Tacas Supplementary loads about 1.2k tokens when it runs. Until then it costs about 114 tokens; SKILL.md has 418 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). 418 words, ~1,176 tokens.
Download SKILL.mdSave it as
.claude/skills/tacas-supplementary/SKILL.md (or your agent's skills folder).- name
- tacas-supplementary
- description
- Use when deciding what belongs in a TACAS (ETAPS) paper body versus its appendix, supplementary website, and artifact, covering the 16-page (or 6-page) llncs.cls budget that excludes references and appendix, the rule that decision-critical content stays in the reviewed pages, category-appropriate anonymity of supplementary material, and how to split a verification paper between body, appendix, and a mandatory-or-voluntary artifact.
TACAS Supplementary
Use this when assembling TACAS supplementary material. The governing rule: the paper must be judgeable from the reviewed pages alone. The appendix, the supplementary website, and the artifact support the paper; they do not hold the argument. Reviewers read supplementary material at their discretion, so anything the decision depends on lives in the body.
What goes where
| Content | Body (within page limit) | Appendix / website / artifact |
|---|---|---|
| Problem, contribution, and the soundness claim | Yes | — |
| The core algorithm / tool architecture | Yes | Full pseudocode variants, extra config |
| The soundness argument | Theorem + proof sketch in body | Full proof in appendix |
| Headline benchmark results | Yes (key table) | Full per-benchmark tables, extra plots |
| Benchmark setup (machine, timeout, baseline) | Stated in body | Full logs, raw outputs |
| The tool itself + reproduction scripts | A pointer | The artifact (mandatory for tools) |
| Extra examples, secondary optimizations | Summary | Appendix / website |
If a reviewer would need to open the appendix or artifact to know whether the result is sound or the comparison is fair, the paper is mis-partitioned — move that into the body.
The page-budget discipline
TACAS's llncs.cls budget (16 pages for research / case-study / regular tool; 6 pages for
tool-demonstration) excludes references and a clearly marked end appendix. Consequences:
- Keep the soundness claim, the core algorithm, and the headline comparison in the body — they are decision-critical.
- Full proofs, per-benchmark tables, and secondary material go to the appendix (at the end, clearly marked) or a supplementary website, with explicit forward references.
- Do not use the appendix or artifact to smuggle in a result that would not otherwise fit — an argument that only closes with out-of-body material reads as unreviewable. Appendices are read at the reviewer's discretion.
Show full SKILL.md (145 more words)Show less
Category-appropriate anonymity of supplementary material
[Research (double-blind)] appendix, website, and any review artifact must be anonymous: no authors,
affiliations, acks, grants, cluster paths, tool identity, or repo owners;
route the website through an anonymizing host
[Tool / case-study (single-blind)] supplementary material is named; the tool identity is expected,
but still ship a clean archive (no credentials, no .git cruft)
[Clean archive] no .git history, .DS_Store, credentials, caches, or huge irrelevant files
[Opens clean] verify the appendix/website/artifact is navigable and the README orients a
reader in one minuteThe mandatory-artifact interaction (tool and tool-demo papers)
For a regular tool or tool-demonstration paper the artifact is not "supplementary" in the
optional sense — it is a mandatory, evaluated deliverable submitted after the paper. Split so
that the body makes the paper judgeable and the artifact makes every claim reproducible; the two
must agree. See tacas-artifact-evaluation and tacas-reproducibility.
Vignette: splitting a research paper with a long proof
A paper with a new algorithm, a substantial soundness proof, and a large benchmark table: the body keeps the algorithm, the theorem with a proof sketch, the key benchmark comparison with the setup stated, and the external-validity limits; the appendix holds the full proof and the per-benchmark tables; the (voluntary) artifact holds the tool and the scripts that regenerate the tables. Nothing decision-critical — soundness or comparison fairness — lives only outside the body.
Output format
[Supplement status] ready / needs fixes / not ready
[Partition check] anything decision-critical (soundness/fairness) outside the body? <none / move: what>
[Page budget] body within 16/6 limit? references + appendix excluded correctly? yes/no
[Anonymity] (research) appendix/website/artifact clean of identity + metadata? passed/issues
[Body dependency] <what a reviewer can decide without opening the appendix/artifact>© 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 TACAS-Skills/skills/tacas-supplementary of brycewang-stanford/Awesome-Journal-Skills.
Open the folder on GitHubat commit 932eb23
Compare with similar skills
Tacas 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 |
|---|---|---|---|---|---|---|
| Tacas Supplementary this skillbrycewang-stanford/Awesome-Journal-Skills | 1.2k | — | ~1.2k | 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 Tacas Supplementary
What does Tacas Supplementary do?
A skill your agent uses when deciding what belongs in a TACAS (ETAPS) paper body versus its appendix, supplementary website, and artifact, covering the 16-page (or 6-page) llncs.cls budget that…. Tacas Supplementary is an agent skill from brycewang-stanford/Awesome-Journal-Skills.cls budget that excludes references and appendix, the rule that decision-critical content stays in the reviewed pages, category-appropriate anonymity of supplementary material, and how to split a verification paper between body, appendix, and a mandatory-or-voluntary artifact.
When should I use Tacas Supplementary?
Tacas Supplementary fits situations like: deciding what belongs in a TACAS (ETAPS) paper body versus its appendix; supplementary website; covering the 16-page (or 6-page) llncs.cls budget that excludes references and appendix; the rule that decision-critical content stays in the reviewed pages.
How do I install Tacas Supplementary in Claude Code?
Run `npx skills add brycewang-stanford/Awesome-Journal-Skills --skill tacas-supplementary -a claude-code`. Or copy the skill folder (TACAS-Skills/skills/tacas-supplementary in brycewang-stanford/Awesome-Journal-Skills) into .claude/skills/tacas-supplementary in your project. Claude Code loads it when a task matches its description.
How do I install Tacas Supplementary in Codex?
Run `npx skills add brycewang-stanford/Awesome-Journal-Skills --skill tacas-supplementary -a codex`. Or copy the skill folder (TACAS-Skills/skills/tacas-supplementary in brycewang-stanford/Awesome-Journal-Skills) into .agents/skills/tacas-supplementary in your project. Codex loads it when a task matches its description.
Can I use Tacas 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 tacas-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/tacas-supplementary, .gemini/skills/tacas-supplementary, .github/skills/tacas-supplementary and .opencode/skills/tacas-supplementary in your project.
What does Tacas Supplementary need to run?
SKILL.md names no scripts, command-line tools or credentials: Tacas Supplementary is instructions for the agent only.
Does Tacas 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 Tacas 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 Tacas Supplementary use?
Tacas 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 Tacas Supplementary use?
About 1.2k tokens (SKILL.md is roughly 4.7k 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 Tacas Supplementary?
Skills that share tags, products or a category with Tacas 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 Tacas 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.