Ieee Paper Reader
CloudWave818/ieee-skills
Read, decompose, and analyze IEEE-style papers using routed technical-reading workflows.
A skill your agent uses when positioning a TACAS (ETAPS) submission against the verification literature across TACAS, CAV, VMCAI, FMCAD, SPIN, and journals (STTT, FMSD), writing delta-first contrast…
Install Tacas Related Work
$ npx skills add brycewang-stanford/Awesome-Journal-Skills --skill tacas-related-work -a claude-codeProject install by default; add -g for ~/.claude/skills/.
$ gh skill install brycewang-stanford/Awesome-Journal-Skills tacas-related-work --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-related-work .claude/skills/tacas-related-work && 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-related-work" agent skill from https://github.com/brycewang-stanford/Awesome-Journal-Skills/tree/main/TACAS-Skills/skills/tacas-related-work into .claude/skills/tacas-related-work/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "tacas-related-work", 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-related-workType 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-related-work -a codexProject install goes to .agents/skills/; add -g for ~/.codex/skills/.
$ gh skill install brycewang-stanford/Awesome-Journal-Skills tacas-related-work --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-related-work .agents/skills/tacas-related-work && 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-related-work" agent skill from https://github.com/brycewang-stanford/Awesome-Journal-Skills/tree/main/TACAS-Skills/skills/tacas-related-work into .agents/skills/tacas-related-work/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "tacas-related-work", 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-related-work -a cursorProject install goes to .agents/skills/; add -g for ~/.cursor/skills/.
$ gh skill install brycewang-stanford/Awesome-Journal-Skills tacas-related-work --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-related-work .cursor/skills/tacas-related-work && 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-related-work" agent skill from https://github.com/brycewang-stanford/Awesome-Journal-Skills/tree/main/TACAS-Skills/skills/tacas-related-work into .cursor/skills/tacas-related-work/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "tacas-related-work", 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-related-work--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-related-work -a gemini-cliProject install goes to .agents/skills/; add -g for ~/.gemini/skills/.
$ gh skill install brycewang-stanford/Awesome-Journal-Skills tacas-related-work --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-related-work .gemini/skills/tacas-related-work && 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-related-work" agent skill from https://github.com/brycewang-stanford/Awesome-Journal-Skills/tree/main/TACAS-Skills/skills/tacas-related-work into .gemini/skills/tacas-related-work/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "tacas-related-work", 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-related-workInstalls 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-related-work -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-related-work .github/skills/tacas-related-work && 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-related-work" agent skill from https://github.com/brycewang-stanford/Awesome-Journal-Skills/tree/main/TACAS-Skills/skills/tacas-related-work into .github/skills/tacas-related-work/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "tacas-related-work", 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-related-work -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-related-work --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-related-work .opencode/skills/tacas-related-work && 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-related-work" agent skill from https://github.com/brycewang-stanford/Awesome-Journal-Skills/tree/main/TACAS-Skills/skills/tacas-related-work into .opencode/skills/tacas-related-work/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "tacas-related-work", 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-related-work- GitHub stars
- 1.2k
- Token cost
- ~1.3k tokens
- SKILL.md length
- 519 words
- Files
- 1
- Skills in repo
- 2,387
- Repo updated
- First seen
- Licence
- MIT
At a glance
A skill your agent uses when positioning a TACAS (ETAPS) submission against the verification literature across TACAS, CAV, VMCAI, FMCAD, SPIN, and journals (STTT, FMSD), writing delta-first contrast…
- Positioning a TACAS (ETAPS) submission against the verification literature across TACAS
- SKILL.md covers Positioning checks, Verification literature lanes, Delta-first positioning vignette and Concurrent and prior-version…, plus 2 more sections
- Instructions only: no scripts, shell commands, URLs or credentials in SKILL.md
- Writing delta-first contrast against the nearest tools and algorithms
What it does
Tacas Related Work is an agent skill from brycewang-stanford/Awesome-Journal-Skills. Use when positioning a TACAS (ETAPS) submission against the verification literature across TACAS, CAV, VMCAI, FMCAD, SPIN, and journals (STTT, FMSD), writing delta-first contrast against the nearest tools and algorithms, crediting the benchmarks and solvers you build on, keeping self-citations anonymous for double-blind research papers, and handling competition-tool and prior-version overlap.
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, covering Literature review, Positioning and messaging and Citation management. 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
- Positioning a TACAS (ETAPS) submission against the verification literature across TACAS
- Writing delta-first contrast against the nearest tools and algorithms
- Crediting the benchmarks and solvers you build on
- Keeping self-citations anonymous for double-blind research papers
Example prompts
- “/tacas-related-work”
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 Related Work loads about 1.3k tokens when it runs. Until then it costs about 104 tokens; SKILL.md has 519 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). 519 words, ~1,344 tokens.
Download SKILL.mdSave it as
.claude/skills/tacas-related-work/SKILL.md (or your agent's skills folder).- name
- tacas-related-work
- description
- Use when positioning a TACAS (ETAPS) submission against the verification literature across TACAS, CAV, VMCAI, FMCAD, SPIN, and journals (STTT, FMSD), writing delta-first contrast against the nearest tools and algorithms, crediting the benchmarks and solvers you build on, keeping self-citations anonymous for double-blind research papers, and handling competition-tool and prior-version overlap.
TACAS Related Work
Use this to audit novelty and eligibility. TACAS reviewers are close to the verification literature and to the tools it produces, so they expect to see where your algorithm or tool sits relative to the nearest prior work — as a delta, not a catalog. Reopen the current call for dual-submission, anonymity, and prior-publication rules before advising authors.
Positioning checks
- Separate the algorithmic novelty from the engineering. What is new: a new decision procedure, a new encoding, a new abstraction, a tool that first makes a technique usable, or a case study that first applies it at scale? Name it precisely.
- Cover the verification venues. TACAS reviewers expect the flagships and the journals, not just the papers nearest your method (see the table). Missing the obvious CAV/VMCAI/FMCAD predecessor reads as unaware.
- Credit what you build on. If you use an SMT solver, a benchmark suite, or a model-checking backend, cite it — TACAS is a tool-and-algorithm community and reviewers notice uncredited infrastructure or benchmarks.
- Write delta-first. Each closely related tool/algorithm gets one sentence on what it did and one on what you do differently (a stronger guarantee, a new class handled, an order-of-magnitude scaling, a first working tool) — not a summary.
- Anonymity by category. For a double-blind research paper, cite your own prior work in the third person and never link reviewers to an identity-revealing preprint or repository. A tool / case-study paper is single-blind and cites itself normally.
- Declare overlap with any prior workshop version, SV-COMP competition paper, or concurrent submission; do not re-submit archival work as new.
Show full SKILL.md (260 more words)Show less
Verification literature lanes
| Lane | Typical venues | What TACAS reviewers check |
|---|---|---|
| Tools & algorithms (home) | TACAS | Whether the nearest tool/algorithm predecessor is compared or distinguished |
| Broad formal methods | CAV | Whether the closest FM-flagship technique is credited and contrasted |
| Verification / abstract interpretation foundations | VMCAI | Whether the foundational predecessor is engaged |
| Hardware / SAT-centric FM | FMCAD | Whether the relevant hardware/SAT lineage is acknowledged |
| Explicit-state / software model checking | SPIN | Whether the model-checking predecessor is cited |
| Journals | STTT, FMSD | Whether deeper journal treatments on the topic are engaged |
| Competitions | SV-COMP, VerifyThis | Whether shared benchmarks / competing verifiers are credited |
A bibliography that cites only your own subarea suggests the delta is smaller than claimed; one that reaches the flagships, journals, and competitions signals command of the field.
Delta-first positioning vignette
Suppose the paper presents a new tool for bounded refinement checking. Its nearest neighbors: a CAV algorithm that requires linearization-point annotations (yours is annotation-free), a TACAS tool that enumerates histories without reduction (yours uses an SMT reduction and scales further), and a journal study characterizing the problem (no tool). The novelty sentence should name all three contrasts — annotation-free where prior work needed annotations, an SMT reduction where prior work enumerated, and a working, benchmarked tool where the journal offered only characterization.
Concurrent and prior-version judgment calls
[SV-COMP competition paper] your tool's competition entry is often citable but archival-limited;
state what the TACAS paper adds beyond the competition contribution
[Concurrent arXiv work] cite neutrally, state the technical difference, avoid priority claims;
keep the citation anonymous for a double-blind research paper
[Prior workshop version] usually citable; declare the overlap and state what the full paper adds
[Prior tool release] crediting your own earlier tool version is fine (single-blind tool paper);
for a research paper, keep it third-personEligibility red flags
- Substantial text overlap with a published paper by the same authors (self-plagiarism risk).
- A "new" tool paper that re-reports a prior release's benchmarks without a new capability.
- Citations only to non-verification venues, signaling the paper may be a visitor better suited to another community and not reframed.
Output format
[Eligibility] clear / needs declaration / risky
[Lanes covered] <TACAS / CAV / VMCAI / FMCAD / SPIN / journals / competitions>
[Nearest 3 works] <work -> one-line delta>
[Infrastructure credited] <solvers / benchmarks / backends cited? yes/no>
[Archival-overlap risk] <none / declare: what (incl. SV-COMP entry)>
[Novelty sentence] <TACAS-ready contribution contrast against the nearest tools/algorithms>© 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-related-work of brycewang-stanford/Awesome-Journal-Skills.
Open the folder on GitHubat commit 932eb23
Compare with similar skills
Tacas Related Work 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 Related Work this skillbrycewang-stanford/Awesome-Journal-Skills | 1.2k | — | ~1.3k | Automated safety check: Pass | MIT | |
| Ieee Paper ReaderCloudWave818/ieee-skills | 359 | — | ~591 | Automated safety check: Pass | MIT | |
| Gec Literature Positioningfranklee16/academic-research-skills | 223 | 1 repos | ~855 | Automated safety check: Pass | None | |
| Jpe Literature Positioningfranklee16/academic-research-skills | 223 | 1 repos | ~1.1k | Automated safety check: Pass | None | |
| Systematic Review ScreenerImbad0202/academic-research-skills | 51k | — | ~8.4k | Automated safety check: Pass | Custom licence | |
| Literature Reviewneflibata-feng/MyArxiv-Agent | 126 | 20 repos | ~5.9k | Automated safety check: Notes | MIT |
Similar skills
Gec Literature Positioning
franklee16/academic-research-skills
A skill your agent uses when positioning a Global Environmental Change (GEC) manuscript against the relevant literatures.
Jpe Literature Positioning
franklee16/academic-research-skills
A skill your agent uses when writing or repairing the introduction and related-work framing for a Journal of Political Economy (JPE) manuscript — situating the contribution in the economics…
Systematic Review Screener
Imbad0202/academic-research-skills
Screens records for systematic, scoping and rapid reviews against fixed eligibility rules, using two blinded AI reviewers and a third adjudicator, with traceable PRISMA counts.
Literature Review
neflibata-feng/MyArxiv-Agent
Conduct comprehensive, systematic literature reviews using multiple academic databases (PubMed, arXiv, bioRxiv, Semantic Scholar, etc.).
Preprint Search on bioRxiv
LigphiDonk/Oh-my--paper
Searches bioRxiv life sciences preprints by keyword, author, date range or category with a Python script, returning JSON metadata and optional PDF downloads.
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 Related Work
What does Tacas Related Work do?
A skill your agent uses when positioning a TACAS (ETAPS) submission against the verification literature across TACAS, CAV, VMCAI, FMCAD, SPIN, and journals (STTT, FMSD), writing delta-first contrast…. Tacas Related Work is an agent skill from brycewang-stanford/Awesome-Journal-Skills. Use when positioning a TACAS (ETAPS) submission against the verification literature across TACAS, CAV, VMCAI, FMCAD, SPIN, and journals (STTT, FMSD), writing delta-first contrast against the nearest tools and algorithms, crediting the benchmarks and solvers you build on, keeping self-citations anonymous for double-blind research papers, and handling competition-tool and prior-version overlap.
When should I use Tacas Related Work?
Tacas Related Work fits situations like: positioning a TACAS (ETAPS) submission against the verification literature across TACAS; writing delta-first contrast against the nearest tools and algorithms; crediting the benchmarks and solvers you build on; keeping self-citations anonymous for double-blind research papers.
How do I install Tacas Related Work in Claude Code?
Run `npx skills add brycewang-stanford/Awesome-Journal-Skills --skill tacas-related-work -a claude-code`. Or copy the skill folder (TACAS-Skills/skills/tacas-related-work in brycewang-stanford/Awesome-Journal-Skills) into .claude/skills/tacas-related-work in your project. Claude Code loads it when a task matches its description.
How do I install Tacas Related Work in Codex?
Run `npx skills add brycewang-stanford/Awesome-Journal-Skills --skill tacas-related-work -a codex`. Or copy the skill folder (TACAS-Skills/skills/tacas-related-work in brycewang-stanford/Awesome-Journal-Skills) into .agents/skills/tacas-related-work in your project. Codex loads it when a task matches its description.
Can I use Tacas Related Work 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-related-work -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-related-work, .gemini/skills/tacas-related-work, .github/skills/tacas-related-work and .opencode/skills/tacas-related-work in your project.
What does Tacas Related Work need to run?
SKILL.md names no scripts, command-line tools or credentials: Tacas Related Work is instructions for the agent only.
Does Tacas Related Work 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 Related Work 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 Related Work use?
Tacas Related Work 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 Related Work use?
About 1.3k tokens (SKILL.md is roughly 5.4k 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 Related Work?
Skills that share tags, products or a category with Tacas Related Work: Ieee Paper Reader (CloudWave818/ieee-skills, 359 stars), Gec Literature Positioning (franklee16/academic-research-skills, 223 stars), Jpe Literature Positioning (franklee16/academic-research-skills, 223 stars) and Systematic Review Screener (Imbad0202/academic-research-skills, 51k stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.
Who maintains Tacas Related Work?
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.