Santa Method
affaan-m/ECC
Multi-agent adversarial verification: two independent reviewers with the same rubric must both pass before output ships, with a fix-and-re-review convergence loop and human escalation cap.
A skill your agent uses when deciding whether a formal-methods / verification project belongs at TACAS (ETAPS) or a sibling like CAV, VMCAI, FMCAD, SPIN, or a journal, AND — distinctively — which of…
MITAuto-check passed
Install Tacas Topic Selection
$ npx skills add brycewang-stanford/Awesome-Journal-Skills --skill tacas-topic-selection -a claude-codeProject install by default; add -g for ~/.claude/skills/.
$ gh skill install brycewang-stanford/Awesome-Journal-Skills tacas-topic-selection --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-topic-selection .claude/skills/tacas-topic-selection && 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-topic-selection" agent skill from https://github.com/brycewang-stanford/Awesome-Journal-Skills/tree/main/TACAS-Skills/skills/tacas-topic-selection into .claude/skills/tacas-topic-selection/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "tacas-topic-selection", 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-topic-selectionType 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-topic-selection -a codexProject install goes to .agents/skills/; add -g for ~/.codex/skills/.
$ gh skill install brycewang-stanford/Awesome-Journal-Skills tacas-topic-selection --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-topic-selection .agents/skills/tacas-topic-selection && 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-topic-selection" agent skill from https://github.com/brycewang-stanford/Awesome-Journal-Skills/tree/main/TACAS-Skills/skills/tacas-topic-selection into .agents/skills/tacas-topic-selection/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "tacas-topic-selection", 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-topic-selection -a cursorProject install goes to .agents/skills/; add -g for ~/.cursor/skills/.
$ gh skill install brycewang-stanford/Awesome-Journal-Skills tacas-topic-selection --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-topic-selection .cursor/skills/tacas-topic-selection && 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-topic-selection" agent skill from https://github.com/brycewang-stanford/Awesome-Journal-Skills/tree/main/TACAS-Skills/skills/tacas-topic-selection into .cursor/skills/tacas-topic-selection/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "tacas-topic-selection", 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-topic-selection--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-topic-selection -a gemini-cliProject install goes to .agents/skills/; add -g for ~/.gemini/skills/.
$ gh skill install brycewang-stanford/Awesome-Journal-Skills tacas-topic-selection --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-topic-selection .gemini/skills/tacas-topic-selection && 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-topic-selection" agent skill from https://github.com/brycewang-stanford/Awesome-Journal-Skills/tree/main/TACAS-Skills/skills/tacas-topic-selection into .gemini/skills/tacas-topic-selection/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "tacas-topic-selection", 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-topic-selectionInstalls 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-topic-selection -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-topic-selection .github/skills/tacas-topic-selection && 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-topic-selection" agent skill from https://github.com/brycewang-stanford/Awesome-Journal-Skills/tree/main/TACAS-Skills/skills/tacas-topic-selection into .github/skills/tacas-topic-selection/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "tacas-topic-selection", 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-topic-selection -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-topic-selection --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-topic-selection .opencode/skills/tacas-topic-selection && 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-topic-selection" agent skill from https://github.com/brycewang-stanford/Awesome-Journal-Skills/tree/main/TACAS-Skills/skills/tacas-topic-selection into .opencode/skills/tacas-topic-selection/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "tacas-topic-selection", 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-topic-selection- GitHub stars
- 1.2k
- Token cost
- ~1.6k tokens
- SKILL.md length
- 643 words
- Files
- 1
- Skills in repo
- 2,387
- Repo updated
- First seen
- Licence
- MIT
At a glance
A skill your agent uses when deciding whether a formal-methods / verification project belongs at TACAS (ETAPS) or a sibling like CAV, VMCAI, FMCAD, SPIN, or a journal, AND — distinctively — which of…
- Deciding whether a formal-methods / verification project belongs at TACAS (ETAPS)
- SKILL.md covers First cut: is this TACAS, or a…, Second cut: which of the four…, Contribution shapes TACAS… and The tool-vs-research and…, plus 2 more sections
- Instructions only: no scripts, shell commands, URLs or credentials in SKILL.md
- A sibling like CAV
What it does
Tacas Topic Selection is an agent skill from brycewang-stanford/Awesome-Journal-Skills. Use when deciding whether a formal-methods / verification project belongs at TACAS (ETAPS) or a sibling like CAV, VMCAI, FMCAD, SPIN, or a journal, AND — distinctively — which of TACAS's four categories (research, case-study, regular tool, tool-demonstration) it fits, plus whether the work is a SV-COMP competition contribution rather than a paper.
Its SKILL.md is about 1.6k tokens, which your agent loads only when the skill is triggered. It is a single SKILL.md file with no bundled scripts.
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 whether a formal-methods / verification project belongs at TACAS (ETAPS)
- A sibling like CAV
- — distinctively — which of TACASs four categories (research
- Tool-demonstration) it fits
Example prompts
- “/tacas-topic-selection”
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 Topic Selection loads about 1.6k tokens when it runs. Until then it costs about 93 tokens; SKILL.md has 643 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). 643 words, ~1,575 tokens.
Download SKILL.mdSave it as
.claude/skills/tacas-topic-selection/SKILL.md (or your agent's skills folder).- name
- tacas-topic-selection
- description
- Use when deciding whether a formal-methods / verification project belongs at TACAS (ETAPS) or a sibling like CAV, VMCAI, FMCAD, SPIN, or a journal, AND — distinctively — which of TACAS's four categories (research, case-study, regular tool, tool-demonstration) it fits, plus whether the work is a SV-COMP competition contribution rather than a paper.
TACAS Topic Selection
Decide two things before drafting: is this TACAS, and which TACAS category. TACAS — Tools and Algorithms for the Construction and Analysis of Systems — is the ETAPS conference at the tool-and-algorithm end of verification: model checking, program analysis, SMT and decision procedures, testing and synthesis, and the systems that implement them. Its defining feature versus its siblings is that a usable, evaluated tool is a first-class contribution, backed by a mandatory artifact. A brilliant idea with no tool and no experiment can still be a research paper, but a paper that is really a benchmark ranking is a SV-COMP contribution, not a TACAS paper.
First cut: is this TACAS, or a sibling?
TACAS overlaps heavily with the other verification venues, so decide by emphasis and calendar, not by topic alone.
| Signal in your project | Better home | Why |
|---|---|---|
| A tool or algorithm for constructing/analysing systems, with real experiments, ETAPS timing fits | TACAS | Tools-and-algorithms core; mandatory-artifact culture; LNCS open access |
| Deep new verification theory/algorithm, breadth of formal methods, larger page room | CAV | Closest sibling; broader FM flagship, different calendar and process |
| Principled study of verification/abstract-interpretation foundations | VMCAI | Verification, model checking, and abstract interpretation focus |
| Hardware / SAT-centric formal methods, industrial hardware verification | FMCAD | Its named center |
| Explicit-state / software model checking around the SPIN lineage | SPIN | Community and tooling match |
| A full journal-length treatment with proofs and extended evaluation | STTT / FMSD / a journal | No conference page ceiling; STTT is the TACAS-adjacent journal |
| A verifier to be run on the common task set and ranked | SV-COMP (at TACAS) | It is a competition entry, not a stand-alone tool paper |
CAV is the trap. Many canonical tools (NuSMV, CPAchecker, Storm) debuted at CAV, not TACAS. Differentiate by TACAS's ETAPS context, its tool/tool-demo/case-study categories, its per-category page limits, and its artifact-as-first-class model — and check dblp before assuming a lineage.
Second cut: which of the four categories?
| Your contribution | Category | Page limit | Note |
|---|---|---|---|
| A new algorithm, encoding, decision procedure, or theory with a correctness argument | Regular research | ≤16 | Double-blind; artifact voluntary |
| Applying existing methods/tools to a substantial real system, with lessons | Case-study | ≤16 | Single-blind; artifact voluntary |
| A usable tool realizing a technique, with an evaluation | Regular tool | ≤16 | Single-blind; mandatory artifact |
| A mature tool shown in operation, focused on usage/UI/workflow | Tool-demonstration | ≤6 | Single-blind; mandatory artifact |
The category is a commitment: a research paper is judged on the idea and its soundness; a tool paper is judged on the tool and its runnable artifact; a case-study paper is judged on the realism of the system and the honesty of the lessons; a tool-demo is judged on a working demonstration in six pages. Pick the one whose bar your evidence actually clears.
Show full SKILL.md (200 more words)Show less
Contribution shapes TACAS rewards
- Algorithm / reduction — a new way to construct or analyse systems with a soundness (and often completeness/complexity) argument (the BMC lineage).
- Tool — a downloadable, evaluated implementation others can point at their own inputs (the CBMC / Z3 lineage), now inseparable from a working artifact.
- Case study — a substantial application of verification to a real system that teaches the community what works and what breaks at scale.
- Competition-driven — participation in SV-COMP / VerifyThis that advances shared benchmarks and reproducible comparison.
The tool-vs-research and re-label tests
- Tool-vs-research test: if the paper's core would survive with the tool removed (an algorithm and a proof), it is a research paper; if the core is the working tool and its evaluation, it is a tool paper — and then the artifact is mandatory.
- Re-label test: could this be submitted to CAV/VMCAI/FMCAD unchanged and read as native there? If its heart is FM breadth or new theory depth, weigh those venues; TACAS rewards the tool-and-algorithm framing with reproducible experiments.
Cheap reconnaissance before committing
[Scope] scan the last two TACAS proceedings (dblp, Springer LNCS) for your subarea
-> several recent papers = a reviewer pool exists; none = mismatch or a CAV/FMCAD topic
[Category] find 2-3 recent papers in the category you plan to use; match their evidence depth
[Artifact] if tool/tool-demo, can you package a clean-VM artifact by the post-paper deadline? if
not, the category is wrong for this cycle
[Calendar] compare the next ETAPS/TACAS deadline with CAV/VMCAI/FMCAD dates -> route to the
nearest honest fit rather than idling a yearDecision procedure
[Is it TACAS?] tool/algorithm to construct/analyse systems + experiments? -> yes; else CAV/VMCAI/FMCAD/journal
[Competition?] a verifier to be ranked on common tasks -> SV-COMP, not a tool paper
[Category] algorithm+proof -> research; usable tool+eval -> regular tool; mature tool in use -> tool-demo;
real-system application -> case-study
[Blind + artifact] research -> double-blind, voluntary artifact; tool/tool-demo -> single-blind, mandatory artifact
[Verdict] TACAS <category> / sibling venue / SV-COMP / journal, with a one-line reasonRun this before the writing skills; a wrong venue-or-category decision wastes every later step. When
the verdict is TACAS, continue with tacas-workflow for the calendar and tacas-writing-style for
the paper shape.
© 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-topic-selection of brycewang-stanford/Awesome-Journal-Skills.
Open the folder on GitHubat commit 932eb23
Compare with similar skills
Tacas Topic Selection 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 Topic Selection this skillbrycewang-stanford/Awesome-Journal-Skills | 1.2k | — | ~1.6k | Automated safety check: Pass | MIT | |
| Santa Methodaffaan-m/ECC | 276k | 3 repos | ~3.1k | Automated safety check: Pass | MIT | |
| Santa Methodaffaan-m/ECC | 276k | — | ~2.1k | Automated safety check: Pass | MIT | |
| Santa Methodaffaan-m/ECC | 276k | — | ~1.9k | Automated safety check: Pass | MIT | |
| Formal Methods Reconcilermizchi/skills | 360 | — | ~1.9k | Automated safety check: Pass | None | |
| Modern Array Methodsthedaviddias/Front-End-Checklist | 74k | — | ~494 | Automated safety check: Pass | MIT |
Similar skills
Santa Method
affaan-m/ECC
収束ループを持つマルチエージェント敵対的検証。2つの独立したレビューエージェントが両方合格して初めて出力を出荷できます。
Santa Method
affaan-m/ECC
具有收敛循环的多智能体对抗验证。两个独立的审查代理必须都通过，输出才能发送。
Formal Methods Reconciler
mizchi/skills
A skill your agent uses when reconciling software specs, docs, tests, configs, code, logs, or incidents with formal methods.
Modern Array Methods
thedaviddias/Front-End-Checklist
A skill your agent uses when reviewing scripts, client components, bundles, or runtime behavior related to Use modern array and object methods.
Statistical Method Design
aiming-lab/AutoResearchClaw
Design statistical methods, baselines, diagnostics, variants, and ablations that directly address a formal problem formulation.
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…
Questions about Tacas Topic Selection
What does Tacas Topic Selection do?
A skill your agent uses when deciding whether a formal-methods / verification project belongs at TACAS (ETAPS) or a sibling like CAV, VMCAI, FMCAD, SPIN, or a journal, AND — distinctively — which of…. Tacas Topic Selection is an agent skill from brycewang-stanford/Awesome-Journal-Skills. Use when deciding whether a formal-methods / verification project belongs at TACAS (ETAPS) or a sibling like CAV, VMCAI, FMCAD, SPIN, or a journal, AND — distinctively — which of TACAS's four categories (research, case-study, regular tool, tool-demonstration) it fits, plus whether the work is a SV-COMP competition contribution rather than a paper.
When should I use Tacas Topic Selection?
Tacas Topic Selection fits situations like: deciding whether a formal-methods / verification project belongs at TACAS (ETAPS); A sibling like CAV; — distinctively — which of TACASs four categories (research; tool-demonstration) it fits.
How do I install Tacas Topic Selection in Claude Code?
Run `npx skills add brycewang-stanford/Awesome-Journal-Skills --skill tacas-topic-selection -a claude-code`. Or copy the skill folder (TACAS-Skills/skills/tacas-topic-selection in brycewang-stanford/Awesome-Journal-Skills) into .claude/skills/tacas-topic-selection in your project. Claude Code loads it when a task matches its description.
How do I install Tacas Topic Selection in Codex?
Run `npx skills add brycewang-stanford/Awesome-Journal-Skills --skill tacas-topic-selection -a codex`. Or copy the skill folder (TACAS-Skills/skills/tacas-topic-selection in brycewang-stanford/Awesome-Journal-Skills) into .agents/skills/tacas-topic-selection in your project. Codex loads it when a task matches its description.
Can I use Tacas Topic Selection 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-topic-selection -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-topic-selection, .gemini/skills/tacas-topic-selection, .github/skills/tacas-topic-selection and .opencode/skills/tacas-topic-selection in your project.
What does Tacas Topic Selection need to run?
SKILL.md names no scripts, command-line tools or credentials: Tacas Topic Selection is instructions for the agent only.
Does Tacas Topic Selection 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 Topic Selection 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 Topic Selection use?
Tacas Topic Selection 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 Topic Selection use?
About 1.6k tokens (SKILL.md is roughly 6.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 Topic Selection?
Skills that share tags, products or a category with Tacas Topic Selection: Santa Method (affaan-m/ECC, 276k stars), Santa Method (affaan-m/ECC, 276k stars), Santa Method (affaan-m/ECC, 276k stars) and Formal Methods Reconciler (mizchi/skills, 360 stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.
Who maintains Tacas Topic Selection?
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.