Hypothesis Generation
spacering-net/codeg
Structured hypothesis formulation from observations. An agent skill from spacering-net/codeg.
A skill your agent uses when planning a TACAS (ETAPS) project timeline from category choice and venue fit through the EasyChair paper deadline, the mandatory tool-paper artifact deadline, the…
Install Tacas Workflow
$ npx skills add brycewang-stanford/Awesome-Journal-Skills --skill tacas-workflow -a claude-codeProject install by default; add -g for ~/.claude/skills/.
$ gh skill install brycewang-stanford/Awesome-Journal-Skills tacas-workflow --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-workflow .claude/skills/tacas-workflow && 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-workflow" agent skill from https://github.com/brycewang-stanford/Awesome-Journal-Skills/tree/main/TACAS-Skills/skills/tacas-workflow into .claude/skills/tacas-workflow/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "tacas-workflow", 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-workflowType 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-workflow -a codexProject install goes to .agents/skills/; add -g for ~/.codex/skills/.
$ gh skill install brycewang-stanford/Awesome-Journal-Skills tacas-workflow --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-workflow .agents/skills/tacas-workflow && 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-workflow" agent skill from https://github.com/brycewang-stanford/Awesome-Journal-Skills/tree/main/TACAS-Skills/skills/tacas-workflow into .agents/skills/tacas-workflow/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "tacas-workflow", 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-workflow -a cursorProject install goes to .agents/skills/; add -g for ~/.cursor/skills/.
$ gh skill install brycewang-stanford/Awesome-Journal-Skills tacas-workflow --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-workflow .cursor/skills/tacas-workflow && 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-workflow" agent skill from https://github.com/brycewang-stanford/Awesome-Journal-Skills/tree/main/TACAS-Skills/skills/tacas-workflow into .cursor/skills/tacas-workflow/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "tacas-workflow", 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-workflow--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-workflow -a gemini-cliProject install goes to .agents/skills/; add -g for ~/.gemini/skills/.
$ gh skill install brycewang-stanford/Awesome-Journal-Skills tacas-workflow --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-workflow .gemini/skills/tacas-workflow && 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-workflow" agent skill from https://github.com/brycewang-stanford/Awesome-Journal-Skills/tree/main/TACAS-Skills/skills/tacas-workflow into .gemini/skills/tacas-workflow/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "tacas-workflow", 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-workflowInstalls 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-workflow -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-workflow .github/skills/tacas-workflow && 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-workflow" agent skill from https://github.com/brycewang-stanford/Awesome-Journal-Skills/tree/main/TACAS-Skills/skills/tacas-workflow into .github/skills/tacas-workflow/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "tacas-workflow", 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-workflow -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-workflow --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-workflow .opencode/skills/tacas-workflow && 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-workflow" agent skill from https://github.com/brycewang-stanford/Awesome-Journal-Skills/tree/main/TACAS-Skills/skills/tacas-workflow into .opencode/skills/tacas-workflow/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "tacas-workflow", 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-workflow- GitHub stars
- 1.2k
- Token cost
- ~1.3k tokens
- SKILL.md length
- 598 words
- Files
- 1
- Skills in repo
- 2,387
- Repo updated
- First seen
- Licence
- MIT
At a glance
A skill your agent uses when planning a TACAS (ETAPS) project timeline from category choice and venue fit through the EasyChair paper deadline, the mandatory tool-paper artifact deadline, the…
- Planning a TACAS (ETAPS) project timeline from category choice and venue fit through the EasyChair paper deadline
- SKILL.md covers The reported TACAS 2026…, Milestones, Backward plan from the paper… and Failure modes by stage, plus 2 more sections
- Instructions only: no scripts, shell commands, URLs or credentials in SKILL.md
- The mandatory tool-paper artifact deadline
What it does
Tacas Workflow is an agent skill from brycewang-stanford/Awesome-Journal-Skills. Use when planning a TACAS (ETAPS) project timeline from category choice and venue fit through the EasyChair paper deadline, the mandatory tool-paper artifact deadline, the rebuttal window, notification, the voluntary post-acceptance artifact round, LNCS camera-ready, and presentation, with backward-planning offsets that account for TACAS's single annual round and its parallel paper+artifact review.
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
- Planning a TACAS (ETAPS) project timeline from category choice and venue fit through the EasyChair paper deadline
- The mandatory tool-paper artifact deadline
- The rebuttal window
- The voluntary post-acceptance artifact round
Example prompts
- “/tacas-workflow”
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 Workflow loads about 1.3k tokens when it runs. Until then it costs about 104 tokens; SKILL.md has 598 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). 598 words, ~1,326 tokens.
Download SKILL.mdSave it as
.claude/skills/tacas-workflow/SKILL.md (or your agent's skills folder).- name
- tacas-workflow
- description
- Use when planning a TACAS (ETAPS) project timeline from category choice and venue fit through the EasyChair paper deadline, the mandatory tool-paper artifact deadline, the rebuttal window, notification, the voluntary post-acceptance artifact round, LNCS camera-ready, and presentation, with backward-planning offsets that account for TACAS's single annual round and its parallel paper+artifact review.
TACAS Workflow
Use this as the project-management skill for a TACAS submission. Replace every date with the current ETAPS joint schedule and work backwards from the EasyChair paper deadline — remembering that for a tool or tool-demonstration paper a second, firm artifact deadline lands about two weeks later and its evaluation runs in parallel with the PC. TACAS runs a single annual review round on the shared ETAPS calendar (it does not use ESOP's two rounds), so missing the deadline costs roughly a year.
TACAS is a conference whose proceedings are an open-access LNCS volume: it has no standing editor-in-chief and no author-facing APC. Rotating leadership is the per-edition PC chairs and the ETAPS steering committee; the cost model is registration, and ETAPS funds the gold open access centrally. Chairs rotate yearly — re-check the current TACAS page rather than carrying a name forward.
The reported TACAS 2026 timeline (verify on the live page)
- Paper submission: 16 Oct 2025 (AoE).
- Mandatory artifact (regular tool + tool-demonstration): 30 Oct 2025.
- Rebuttal / author response: 8-10 Dec 2025.
- Notification: 22 Dec 2025.
- Voluntary artifact (accepted research + case-study): 8 Jan 2026.
- Conference: ETAPS 2026, Turin, 11-16 Apr 2026 (main conferences 13-16 Apr).
As of 2026-07-09 the TACAS 2026 edition has already taken place, so the live next target is TACAS 2027 (ETAPS 2027, Copenhagen, 10-15 Apr 2027).
Milestones
- Venue + category fit: confirm TACAS over CAV/VMCAI/FMCAD and pick the category
(
tacas-topic-selection) — this fixes the page limit, blind mode, and artifact obligation. - Evidence + tool lock: freeze the algorithm/tool, the benchmark set, the baselines, and the artifact contents.
- Submission: upload the LNCS PDF via EasyChair; anonymize if it is a research paper.
- Mandatory artifact (tool/tool-demo): submit the clean-VM artifact on its firm deadline; it gates acceptance.
- Rebuttal: answer the reviews in the ETAPS response window.
- Notification: archive reviews and every submitted version.
- Voluntary artifact (research/case-study): if pursuing badges, submit after acceptance.
- Camera-ready + presentation: prepare the LNCS camera-ready, complete Springer rights, register, and present.
Show full SKILL.md (275 more words)Show less
Backward plan from the paper deadline
| Weeks out (heuristic) | Verification-tool milestone |
|---|---|
| 10+ | Category chosen; algorithm/tool feature-frozen; benchmark set and baselines chosen |
| 8 | Experiments run; wall-clock/scalability logged on stated hardware; soundness argument drafted |
| 6 | Comparison against the strongest baseline complete with equal budgets; results tables built |
| 4 | Full draft in llncs.cls within the page limit; artifact assembled in the clean VM |
| 3 | Internal mock review by a verification-literate reader; artifact dry-run on a fresh VM |
| 2 | Tool/tool-demo: freeze the artifact for its post-paper deadline; research: anonymity sweep |
| 1 | Final PDF check; EasyChair fields, category, conflicts complete |
| 0 | Submit paper; then (tool/tool-demo) submit the mandatory artifact on its firm date |
These offsets are planning heuristics only — anchor every one to the current ETAPS joint CfP, never to a previous cycle.
Failure modes by stage
- Leaving the artifact to after the paper for a tool/tool-demo paper — the mandatory artifact deadline is only ~two weeks out and a package that does not build on the ETAPS VM costs the paper.
- Experiments still moving at week 4 forces last-minute benchmark runs nobody has audited — the classic unfair-comparison or unreproducible-result reject.
- Anonymizing the wrong category — stripping the tool name from a single-blind tool paper, or forgetting to anonymize a double-blind research paper.
- Treating the rebuttal as decisive — it corrects misreadings and supplies a missing number; it does not rewrite the paper.
Coordination notes
- Assign one owner for the artifact / clean-VM build and another for the paper; for a tool paper these are two deadlines a fortnight apart and shared ownership is how the artifact slips.
- Archive the exact submitted PDF and artifact — the rebuttal and camera-ready must quote them.
Output format
[Current stage] idea / evidence / writing / submitted / rebuttal / notified / camera-ready / accepted
[Category] research / case-study / regular tool / tool-demonstration
[Next official deadline] <paper or mandatory-artifact date and source, or unknown>
[Critical path] <three tasks that determine readiness, incl. artifact for tool papers>
[Risk register] <category fit / page limit / anonymity / benchmark fairness / artifact-on-VM / presentation>
[Owner map] <task -> person or role>© 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-workflow of brycewang-stanford/Awesome-Journal-Skills.
Open the folder on GitHubat commit 932eb23
Compare with similar skills
Tacas Workflow 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 Workflow 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 Tacas Workflow
What does Tacas Workflow do?
A skill your agent uses when planning a TACAS (ETAPS) project timeline from category choice and venue fit through the EasyChair paper deadline, the mandatory tool-paper artifact deadline, the…. Tacas Workflow is an agent skill from brycewang-stanford/Awesome-Journal-Skills. Use when planning a TACAS (ETAPS) project timeline from category choice and venue fit through the EasyChair paper deadline, the mandatory tool-paper artifact deadline, the rebuttal window, notification, the voluntary post-acceptance artifact round, LNCS camera-ready, and presentation, with backward-planning offsets that account for TACAS's single annual round and its parallel paper+artifact review.
When should I use Tacas Workflow?
Tacas Workflow fits situations like: planning a TACAS (ETAPS) project timeline from category choice and venue fit through the EasyChair paper deadline; the mandatory tool-paper artifact deadline; the rebuttal window; the voluntary post-acceptance artifact round.
How do I install Tacas Workflow in Claude Code?
Run `npx skills add brycewang-stanford/Awesome-Journal-Skills --skill tacas-workflow -a claude-code`. Or copy the skill folder (TACAS-Skills/skills/tacas-workflow in brycewang-stanford/Awesome-Journal-Skills) into .claude/skills/tacas-workflow in your project. Claude Code loads it when a task matches its description.
How do I install Tacas Workflow in Codex?
Run `npx skills add brycewang-stanford/Awesome-Journal-Skills --skill tacas-workflow -a codex`. Or copy the skill folder (TACAS-Skills/skills/tacas-workflow in brycewang-stanford/Awesome-Journal-Skills) into .agents/skills/tacas-workflow in your project. Codex loads it when a task matches its description.
Can I use Tacas Workflow 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-workflow -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-workflow, .gemini/skills/tacas-workflow, .github/skills/tacas-workflow and .opencode/skills/tacas-workflow in your project.
What does Tacas Workflow need to run?
SKILL.md names no scripts, command-line tools or credentials: Tacas Workflow is instructions for the agent only.
Does Tacas Workflow 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 Workflow 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 Workflow use?
Tacas Workflow 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 Workflow 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 Tacas Workflow?
Skills that share tags, products or a category with Tacas Workflow: 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 Workflow?
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.