Hypothesis Generation
spacering-net/codeg
Structured hypothesis formulation from observations. An agent skill from spacering-net/codeg.
A skill your agent uses when reasoning about how a TACAS (ETAPS) submission is evaluated, covering the per-category blind model (double-blind research vs single-blind tool/case-study), the single…
Install Tacas Review Process
$ npx skills add brycewang-stanford/Awesome-Journal-Skills --skill tacas-review-process -a claude-codeProject install by default; add -g for ~/.claude/skills/.
$ gh skill install brycewang-stanford/Awesome-Journal-Skills tacas-review-process --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-review-process .claude/skills/tacas-review-process && 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-review-process" agent skill from https://github.com/brycewang-stanford/Awesome-Journal-Skills/tree/main/TACAS-Skills/skills/tacas-review-process into .claude/skills/tacas-review-process/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "tacas-review-process", 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-review-processType 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-review-process -a codexProject install goes to .agents/skills/; add -g for ~/.codex/skills/.
$ gh skill install brycewang-stanford/Awesome-Journal-Skills tacas-review-process --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-review-process .agents/skills/tacas-review-process && 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-review-process" agent skill from https://github.com/brycewang-stanford/Awesome-Journal-Skills/tree/main/TACAS-Skills/skills/tacas-review-process into .agents/skills/tacas-review-process/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "tacas-review-process", 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-review-process -a cursorProject install goes to .agents/skills/; add -g for ~/.cursor/skills/.
$ gh skill install brycewang-stanford/Awesome-Journal-Skills tacas-review-process --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-review-process .cursor/skills/tacas-review-process && 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-review-process" agent skill from https://github.com/brycewang-stanford/Awesome-Journal-Skills/tree/main/TACAS-Skills/skills/tacas-review-process into .cursor/skills/tacas-review-process/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "tacas-review-process", 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-review-process--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-review-process -a gemini-cliProject install goes to .agents/skills/; add -g for ~/.gemini/skills/.
$ gh skill install brycewang-stanford/Awesome-Journal-Skills tacas-review-process --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-review-process .gemini/skills/tacas-review-process && 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-review-process" agent skill from https://github.com/brycewang-stanford/Awesome-Journal-Skills/tree/main/TACAS-Skills/skills/tacas-review-process into .gemini/skills/tacas-review-process/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "tacas-review-process", 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-review-processInstalls 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-review-process -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-review-process .github/skills/tacas-review-process && 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-review-process" agent skill from https://github.com/brycewang-stanford/Awesome-Journal-Skills/tree/main/TACAS-Skills/skills/tacas-review-process into .github/skills/tacas-review-process/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "tacas-review-process", 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-review-process -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-review-process --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-review-process .opencode/skills/tacas-review-process && 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-review-process" agent skill from https://github.com/brycewang-stanford/Awesome-Journal-Skills/tree/main/TACAS-Skills/skills/tacas-review-process into .opencode/skills/tacas-review-process/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "tacas-review-process", 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-review-process- GitHub stars
- 1.2k
- Token cost
- ~1.5k tokens
- SKILL.md length
- 659 words
- Files
- 1
- Skills in repo
- 2,387
- Repo updated
- First seen
- Licence
- MIT
At a glance
A skill your agent uses when reasoning about how a TACAS (ETAPS) submission is evaluated, covering the per-category blind model (double-blind research vs single-blind tool/case-study), the single…
- Reasoning about how a TACAS (ETAPS) submission is evaluated
- SKILL.md covers Process model, Reading a decision against the…, How TACAS differs from its… and Who reads you, plus 3 more sections
- Instructions only: no scripts, shell commands, URLs or credentials in SKILL.md
- Covering the per-category blind model (double-blind research vs single-blind tool/case-study)
What it does
Tacas Review Process is an agent skill from brycewang-stanford/Awesome-Journal-Skills. Use when reasoning about how a TACAS (ETAPS) submission is evaluated, covering the per-category blind model (double-blind research vs single-blind tool/case-study), the single annual PC round with a rebuttal, the parallel mandatory artifact evaluation that feeds tool-paper acceptance, accept/reject decisions, and how TACAS's process differs from CAV's and from a journal's.
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. 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
- Reasoning about how a TACAS (ETAPS) submission is evaluated
- Covering the per-category blind model (double-blind research vs single-blind tool/case-study)
- The single annual PC round with a rebuttal
- The parallel mandatory artifact evaluation that feeds tool-paper acceptance
Example prompts
- “s process differs from CAV”
- “/tacas-review-process”
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 Review Process loads about 1.5k tokens when it runs. Until then it costs about 99 tokens; SKILL.md has 659 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). 659 words, ~1,476 tokens.
Download SKILL.mdSave it as
.claude/skills/tacas-review-process/SKILL.md (or your agent's skills folder).- name
- tacas-review-process
- description
- Use when reasoning about how a TACAS (ETAPS) submission is evaluated, covering the per-category blind model (double-blind research vs single-blind tool/case-study), the single annual PC round with a rebuttal, the parallel mandatory artifact evaluation that feeds tool-paper acceptance, accept/reject decisions, and how TACAS's process differs from CAV's and from a journal's.
TACAS Review Process
Model the pipeline before interpreting any single review. TACAS's process has three features that surprise authors arriving from other venues: reviewing is blind by category, the decision for a tool paper depends on a parallel artifact evaluation, and the whole thing runs in a single annual round on the ETAPS schedule with a short rebuttal — not a rolling or multi-round journal cycle.
Process model
- Submission and review run on EasyChair under the ETAPS joint schedule. Reviewing is per-category: regular research papers are double-blind; case-study, regular tool, and tool-demonstration papers are single-blind.
- Each paper is read by multiple PC members who weigh, for a research paper, the soundness and significance of the algorithm; for a tool paper, the tool's contribution and its working artifact; for a case study, the realism of the system and the honesty of the lessons.
- For regular tool and tool-demonstration papers, a mandatory artifact is evaluated by the Artifact Evaluation Committee in parallel with the PC, and the artifact outcome feeds the acceptance decision — a paper whose artifact does not work is in real jeopardy.
- There is a short rebuttal / author-response window before the PC finalizes decisions.
- Accepted papers publish in Springer LNCS, gold open access; badges earned by the AEC (Available / Functional / Reusable) are printed on the title page.
Reading a decision against the category
| Category | What reviewers weigh most | Author move on a weak review |
|---|---|---|
| Research | Soundness of the algorithm/encoding; is the correctness argument right? | Correct a misread proof/step in the rebuttal; supply the missing lemma or example |
| Regular tool | Does the tool work and advance practice? Does the artifact reproduce the claims? | Fix/clarify the artifact story; show the benchmark comparison is fair |
| Case study | Is the system real and the evaluation honest? Are the lessons transferable? | Sharpen what generalizes; bound the threats to the lessons |
| Tool-demonstration | Is there a genuine, reproducible demonstration in six pages? | Clarify the demo path; ensure the artifact demonstrates what the text claims |
The strategic reading: for a tool paper, the artifact is part of the review — a great write-up with a broken package still fails. Budget the artifact like a co-equal deliverable, not an afterthought.
Show full SKILL.md (300 more words)Show less
How TACAS differs from its siblings
- vs. CAV: CAV is the broader formal-methods flagship with more theory room and a different calendar; TACAS's identity is the tools-and-algorithms emphasis, the four categories, and the mandatory tool-paper artifact integrated into acceptance. Never assume a shared deadline, page limit, or template — TACAS is LNCS via ETAPS.
- vs. a journal (STTT/FMSD): a journal offers revise-and-resubmit and no page ceiling; TACAS is a single-round conference with a rebuttal, not an R&R. Route a long, proof-heavy treatment to the journal.
- vs. SV-COMP: the competition ranks verifiers on a common task set and its results are reported separately; a tool paper is peer-reviewed prose about a tool, judged on contribution and artifact, not on a leaderboard position.
Who reads you
Expect verification experts matched to your subarea. For a research paper they will check the soundness argument line by line; for a tool paper they (or the AEC) will try to run your artifact and reproduce a headline result; for a case study they will probe whether the system is representative. Vague algorithm descriptions and unreproducible tool claims are caught, not skimmed.
Where author leverage actually exists
[Before submission] category choice + topic keywords -> reviewer match (largest lever)
[Artifact (tool)] a clean-VM package that reproduces the claims (co-decides tool papers)
[Rebuttal] correct factual misreadings, supply a requested number, clarify a proof step
[After reject] no appeal; reroute to CAV/VMCAI/FMCAD or a journal, or return next TACAS cycleA rebuttal moves borderline papers when it fixes a misreading or answers a concrete question; it does not move papers by arguing taste, and it cannot repair a fundamentally broken artifact after the fact.
Misreadings to avoid
- Thinking the artifact is post-acceptance for a tool paper — it is mandatory, parallel, and decision-feeding.
- Anonymity confusion — only research papers are double-blind; do not anonymize a single-blind tool paper, and do not deanonymize a research paper.
- Treating the rebuttal as a second submission — it is short and targeted; the paper as submitted carries the argument.
- Projecting CAV's or last year's process — categories, dates, and artifact rules are set per ETAPS edition.
Output format
[Process stage] pre-submission / under review / rebuttal / notified / accepted
[Category + blind mode] research (double-blind) / case-study|tool|tool-demo (single-blind)
[Decision drivers] soundness | tool+artifact | case realism | demo reproducibility
[Artifact status] (tool/tool-demo) reproduces claims on clean VM? yes/no
[Leverage plan] the next-stage action that can actually change the outcome
[Forbidden moves] wrong-category anonymity error / unrunnable artifact / unsupported new claims in rebuttal© 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-review-process of brycewang-stanford/Awesome-Journal-Skills.
Open the folder on GitHubat commit 932eb23
Compare with similar skills
Tacas Review Process 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 Review Process this skillbrycewang-stanford/Awesome-Journal-Skills | 1.2k | — | ~1.5k | 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 Review Process
What does Tacas Review Process do?
A skill your agent uses when reasoning about how a TACAS (ETAPS) submission is evaluated, covering the per-category blind model (double-blind research vs single-blind tool/case-study), the single…. Tacas Review Process is an agent skill from brycewang-stanford/Awesome-Journal-Skills. Use when reasoning about how a TACAS (ETAPS) submission is evaluated, covering the per-category blind model (double-blind research vs single-blind tool/case-study), the single annual PC round with a rebuttal, the parallel mandatory artifact evaluation that feeds tool-paper acceptance, accept/reject decisions, and how TACAS's process differs from CAV's and from a journal's.
When should I use Tacas Review Process?
Tacas Review Process fits situations like: reasoning about how a TACAS (ETAPS) submission is evaluated; covering the per-category blind model (double-blind research vs single-blind tool/case-study); the single annual PC round with a rebuttal; the parallel mandatory artifact evaluation that feeds tool-paper acceptance.
How do I install Tacas Review Process in Claude Code?
Run `npx skills add brycewang-stanford/Awesome-Journal-Skills --skill tacas-review-process -a claude-code`. Or copy the skill folder (TACAS-Skills/skills/tacas-review-process in brycewang-stanford/Awesome-Journal-Skills) into .claude/skills/tacas-review-process in your project. Claude Code loads it when a task matches its description.
How do I install Tacas Review Process in Codex?
Run `npx skills add brycewang-stanford/Awesome-Journal-Skills --skill tacas-review-process -a codex`. Or copy the skill folder (TACAS-Skills/skills/tacas-review-process in brycewang-stanford/Awesome-Journal-Skills) into .agents/skills/tacas-review-process in your project. Codex loads it when a task matches its description.
Can I use Tacas Review Process 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-review-process -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-review-process, .gemini/skills/tacas-review-process, .github/skills/tacas-review-process and .opencode/skills/tacas-review-process in your project.
What does Tacas Review Process need to run?
SKILL.md names no scripts, command-line tools or credentials: Tacas Review Process is instructions for the agent only.
Does Tacas Review Process 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 Review Process 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 Review Process use?
Tacas Review Process 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 Review Process use?
About 1.5k tokens (SKILL.md is roughly 5.9k 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 Review Process?
Skills that share tags, products or a category with Tacas Review Process: 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 Review Process?
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.