Academic Venue Research
joshua-zyy/academic-paper-writer
Research target venue requirements and writing style for CS/AI/ML papers.
A skill your agent uses when revising a TACAS (ETAPS) paper for a clear construction-or-analysis contribution on the first page, a stated soundness/completeness claim, honest benchmark evidence…
Install Tacas Writing Style
$ npx skills add brycewang-stanford/Awesome-Journal-Skills --skill tacas-writing-style -a claude-codeProject install by default; add -g for ~/.claude/skills/.
$ gh skill install brycewang-stanford/Awesome-Journal-Skills tacas-writing-style --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-writing-style .claude/skills/tacas-writing-style && 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-writing-style" agent skill from https://github.com/brycewang-stanford/Awesome-Journal-Skills/tree/main/TACAS-Skills/skills/tacas-writing-style into .claude/skills/tacas-writing-style/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "tacas-writing-style", 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-writing-styleType 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-writing-style -a codexProject install goes to .agents/skills/; add -g for ~/.codex/skills/.
$ gh skill install brycewang-stanford/Awesome-Journal-Skills tacas-writing-style --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-writing-style .agents/skills/tacas-writing-style && 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-writing-style" agent skill from https://github.com/brycewang-stanford/Awesome-Journal-Skills/tree/main/TACAS-Skills/skills/tacas-writing-style into .agents/skills/tacas-writing-style/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "tacas-writing-style", 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-writing-style -a cursorProject install goes to .agents/skills/; add -g for ~/.cursor/skills/.
$ gh skill install brycewang-stanford/Awesome-Journal-Skills tacas-writing-style --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-writing-style .cursor/skills/tacas-writing-style && 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-writing-style" agent skill from https://github.com/brycewang-stanford/Awesome-Journal-Skills/tree/main/TACAS-Skills/skills/tacas-writing-style into .cursor/skills/tacas-writing-style/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "tacas-writing-style", 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-writing-style--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-writing-style -a gemini-cliProject install goes to .agents/skills/; add -g for ~/.gemini/skills/.
$ gh skill install brycewang-stanford/Awesome-Journal-Skills tacas-writing-style --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-writing-style .gemini/skills/tacas-writing-style && 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-writing-style" agent skill from https://github.com/brycewang-stanford/Awesome-Journal-Skills/tree/main/TACAS-Skills/skills/tacas-writing-style into .gemini/skills/tacas-writing-style/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "tacas-writing-style", 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-writing-styleInstalls 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-writing-style -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-writing-style .github/skills/tacas-writing-style && 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-writing-style" agent skill from https://github.com/brycewang-stanford/Awesome-Journal-Skills/tree/main/TACAS-Skills/skills/tacas-writing-style into .github/skills/tacas-writing-style/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "tacas-writing-style", 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-writing-style -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-writing-style --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-writing-style .opencode/skills/tacas-writing-style && 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-writing-style" agent skill from https://github.com/brycewang-stanford/Awesome-Journal-Skills/tree/main/TACAS-Skills/skills/tacas-writing-style into .opencode/skills/tacas-writing-style/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "tacas-writing-style", 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-writing-style- GitHub stars
- 1.2k
- Token cost
- ~1.4k tokens
- SKILL.md length
- 596 words
- Files
- 1
- Skills in repo
- 2,387
- Repo updated
- First seen
- Licence
- MIT
At a glance
A skill your agent uses when revising a TACAS (ETAPS) paper for a clear construction-or-analysis contribution on the first page, a stated soundness/completeness claim, honest benchmark evidence…
- Revising a TACAS (ETAPS) paper for a clear construction-or-analysis contribution on the first page
- SKILL.md covers Revision rules (all categories), Category skeletons, Sentence-level rewrites and Soundness-and-evidence…, plus 2 more sections
- Instructions only: no scripts, shell commands, URLs or credentials in SKILL.md
- A stated soundness/completeness claim
What it does
Tacas Writing Style is an agent skill from brycewang-stanford/Awesome-Journal-Skills. Use when revising a TACAS (ETAPS) paper for a clear construction-or-analysis contribution on the first page, a stated soundness/completeness claim, honest benchmark evidence, category-appropriate structure (research vs tool vs case-study vs tool-demo), disciplined use of the 16-page (or 6-page) LNCS budget, and correct handling of double-blind wording for research papers.
Its SKILL.md is about 1.4k 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 Brand voice and tone. 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
- Revising a TACAS (ETAPS) paper for a clear construction-or-analysis contribution on the first page
- A stated soundness/completeness claim
- Honest benchmark evidence
- Category-appropriate structure (research vs tool vs case-study vs tool-demo)
Example prompts
- “/tacas-writing-style”
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 Writing Style loads about 1.4k tokens when it runs. Until then it costs about 99 tokens; SKILL.md has 596 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). 596 words, ~1,393 tokens.
Download SKILL.mdSave it as
.claude/skills/tacas-writing-style/SKILL.md (or your agent's skills folder).- name
- tacas-writing-style
- description
- Use when revising a TACAS (ETAPS) paper for a clear construction-or-analysis contribution on the first page, a stated soundness/completeness claim, honest benchmark evidence, category-appropriate structure (research vs tool vs case-study vs tool-demo), disciplined use of the 16-page (or 6-page) LNCS budget, and correct handling of double-blind wording for research papers.
TACAS Writing Style
Use this when revising the main paper. TACAS papers are LNCS articles read by verification experts, so they need the contribution stated precisely on the first page and claims a reviewer can check — a soundness argument for a research paper, a working tool with reproducible numbers for a tool paper. The failure this skill prevents is a paper that gestures at "efficiency" and "novelty" without a crisp algorithmic claim or an honest evaluation.
Revision rules (all categories)
- Lead with the construction/analysis problem and the contribution. State what the paper builds or decides, on what inputs, and how — before any adjective. A verification reader wants the object of study (a property, a system model, a decision problem) named immediately.
- State the soundness claim explicitly. "Sound," "sound and complete," "complete up to bound k," or "unsound but effective, and here is why that is acceptable" — say which, and point to the argument. An unstated correctness posture is the first thing a TACAS reviewer probes.
- Pair every empirical claim with honest evidence — named benchmarks, a fair baseline, wall-clock time on stated hardware, and solved/unsolved counts — not "outperforms."
- Match structure to category. A research paper foregrounds the algorithm and its proof; a tool paper foregrounds the tool, its architecture, and its artifact; a case study foregrounds the system and the lessons; a tool-demo foregrounds a reproducible demonstration in six pages.
- Respect the page budget as a design constraint. 16 pages (or 6 for a tool-demo) in
llncs.cls, excluding references and appendix — a contribution that only fits by compressing the soundness argument is over-scoped for the category. - For a research (double-blind) paper, maintain anonymity in prose: third-person self-citation, no tool name that identifies you, no identifying acknowledgements. A tool/case-study paper is single-blind and names itself.
Category skeletons
| Category | First-page job | Backbone sections | Common failure |
|---|---|---|---|
| Research | Problem, algorithm, soundness claim, evidence preview | Preliminaries; algorithm; correctness; evaluation | Leads with a trend, hides the algorithm and its guarantee |
| Regular tool | What the tool does, how, availability | Architecture; technique realized; evaluation on benchmarks; artifact | Adjectives instead of an architecture and a fair comparison |
| Case study | The real system and the question | System; method applied; results; lessons and threats | Anecdote instead of transferable, honestly bounded lessons |
| Tool-demo | A concrete demonstration in 6 pages | What is shown; how a user drives it; what is reproducible | Compressed research paper instead of a genuine demonstration |
Show full SKILL.md (201 more words)Show less
Sentence-level rewrites
| Draft pattern | TACAS-safe rewrite |
|---|---|
| "Our tool is very efficient and novel." | "solves N/120 benchmarks vs M/120 for <baseline>, median 3.1x less wall-clock time (same hardware, equal timeout)" |
| "We prove the approach is correct." | "Theorem 1: the encoding is sound and complete up to bound k (proof in §3.2 / appendix)" |
| "We outperform existing approaches." | "against <named baseline> configured with an equal time budget, on <named benchmark set>" |
| "The tool scales well." | "runtime grows sub-linearly to inputs of 10^6 states; the largest solved instance is stated in Table 2" |
| "Extensive experiments show..." | "we evaluate on <benchmark set> (N tasks); results, hardware, and timeouts are in §4 and the artifact" |
Soundness-and-evidence discipline
[Guarantee] sound? complete? bounded? unsound-but-useful? -> state it and cite the argument
[Baseline] the strongest available tool, configured fairly, on the same benchmarks and hardware
[Reporting] solved/unsolved, wall-clock with timeouts, memory; no single hidden headline ratio
[Reproduce] every reported number traces to a script/log in the artifact (mandatory for tools)
-> place the guarantee near the algorithm and the evidence near the claim it supportsVignette: compressing a research paper to 16 pages
A draft with a full proof, three optimizations, and a sprawling background: keep the algorithm, the soundness theorem with a proof sketch (full proof to the appendix), the one optimization that carries the speedup, and the benchmark comparison; move the secondary optimizations and extended proofs to the appendix with forward references; cut background to what the argument needs. The test of a good cut: a reviewer can state your guarantee and reproduce your headline benchmark result from the body alone.
Output format
[Writing diagnosis] clear / under-specified / over-claimed / evidence-thin / wrong-category-shape
[First-page fix] <new framing: problem -> contribution -> guarantee -> evidence>
[Guarantee audit] <soundness/completeness/bound stated? where argued?>
[Evidence audit] <claim -> benchmark -> baseline -> fair? reproducible? yes/no>
[Anonymity edits] (research only) <tool names / self-citations / acks to rewrite>© 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-writing-style of brycewang-stanford/Awesome-Journal-Skills.
Open the folder on GitHubat commit 932eb23
Compare with similar skills
Tacas Writing Style 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 Writing Style this skillbrycewang-stanford/Awesome-Journal-Skills | 1.2k | — | ~1.4k | Automated safety check: Pass | MIT | |
| Academic Venue Researchjoshua-zyy/academic-paper-writer | 115 | — | ~626 | Automated safety check: Pass | MIT | |
| Agsy Writing Stylefranklee16/academic-research-skills | 223 | 1 repos | ~1k | Automated safety check: Pass | None | |
| Artbull Writing Style And Citationfranklee16/academic-research-skills | 223 | 1 repos | ~848 | Automated safety check: Pass | None | |
| Ectheory Writing Stylefranklee16/academic-research-skills | 223 | 1 repos | ~874 | Automated safety check: Pass | None | |
| Io Writing Stylefranklee16/academic-research-skills | 223 | 1 repos | ~1.1k | Automated safety check: Pass | None |
Similar skills
Agsy Writing Style
franklee16/academic-research-skills
A skill your agent uses when drafting or polishing an Agricultural Systems (AgSy) manuscript so it reads clearly for a systems-science audience, follows the journal's format, and meets front-matter…
Artbull Writing Style And Citation
franklee16/academic-research-skills
A skill your agent uses when polishing prose and formatting citations for an Art Bulletin article to The Chicago Manual of Style — endnotes (not author-date), full credit-line captions, and…
Ectheory Writing Style
franklee16/academic-research-skills
A skill your agent uses to polish the prose, notation, and proof exposition of an Econometric Theory (ET) manuscript — theorem-proof clarity, consistent notation, APA author-date references, and ET…
Io Writing Style
franklee16/academic-research-skills
A skill your agent uses when drafting or polishing an International Organization (IO) manuscript so it reads for international-relations scholars across paradigms, fits the word caps (Research…
Jape Writing Style
franklee16/academic-research-skills
A skill your agent uses when drafting or polishing prose for a Journal of Applied Econometrics (JAE) manuscript to its house conventions — a 100-word citation-free summary, up to six keywords…
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 Writing Style
What does Tacas Writing Style do?
A skill your agent uses when revising a TACAS (ETAPS) paper for a clear construction-or-analysis contribution on the first page, a stated soundness/completeness claim, honest benchmark evidence…. Tacas Writing Style is an agent skill from brycewang-stanford/Awesome-Journal-Skills. Use when revising a TACAS (ETAPS) paper for a clear construction-or-analysis contribution on the first page, a stated soundness/completeness claim, honest benchmark evidence, category-appropriate structure (research vs tool vs case-study vs tool-demo), disciplined use of the 16-page (or 6-page) LNCS budget, and correct handling of double-blind wording for research papers.
When should I use Tacas Writing Style?
Tacas Writing Style fits situations like: revising a TACAS (ETAPS) paper for a clear construction-or-analysis contribution on the first page; A stated soundness/completeness claim; honest benchmark evidence; category-appropriate structure (research vs tool vs case-study vs tool-demo).
How do I install Tacas Writing Style in Claude Code?
Run `npx skills add brycewang-stanford/Awesome-Journal-Skills --skill tacas-writing-style -a claude-code`. Or copy the skill folder (TACAS-Skills/skills/tacas-writing-style in brycewang-stanford/Awesome-Journal-Skills) into .claude/skills/tacas-writing-style in your project. Claude Code loads it when a task matches its description.
How do I install Tacas Writing Style in Codex?
Run `npx skills add brycewang-stanford/Awesome-Journal-Skills --skill tacas-writing-style -a codex`. Or copy the skill folder (TACAS-Skills/skills/tacas-writing-style in brycewang-stanford/Awesome-Journal-Skills) into .agents/skills/tacas-writing-style in your project. Codex loads it when a task matches its description.
Can I use Tacas Writing Style 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-writing-style -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-writing-style, .gemini/skills/tacas-writing-style, .github/skills/tacas-writing-style and .opencode/skills/tacas-writing-style in your project.
What does Tacas Writing Style need to run?
SKILL.md names no scripts, command-line tools or credentials: Tacas Writing Style is instructions for the agent only.
Does Tacas Writing Style 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 Writing Style 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 Writing Style use?
Tacas Writing Style 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 Writing Style use?
About 1.4k tokens (SKILL.md is roughly 5.6k 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 Writing Style?
Skills that share tags, products or a category with Tacas Writing Style: Academic Venue Research (joshua-zyy/academic-paper-writer, 115 stars), Agsy Writing Style (franklee16/academic-research-skills, 223 stars), Artbull Writing Style And Citation (franklee16/academic-research-skills, 223 stars) and Ectheory Writing Style (franklee16/academic-research-skills, 223 stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.
Who maintains Tacas Writing Style?
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.