Arize Evaluator
github/awesome-copilot
Handles LLM-as-judge evaluation workflows on Arize including creating/updating evaluators, running evaluations on spans or experiments, managing tasks, trigger-run operations, column mapping, and…
Agent skill
Tacas Artifact Evaluation
by brycewang-stanford in brycewang-stanford/Awesome-Journal-Skills
A skill your agent uses when packaging a TACAS (ETAPS) artifact for the ETAPS Artifact Badges (Available, Functional, Reusable), covering the two-round model (mandatory, PC-parallel evaluation for…
MITAuto-check passed
Install Tacas Artifact Evaluation
$ npx skills add brycewang-stanford/Awesome-Journal-Skills --skill tacas-artifact-evaluation -a claude-codeProject install by default; add -g for ~/.claude/skills/.
$ gh skill install brycewang-stanford/Awesome-Journal-Skills tacas-artifact-evaluation --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-artifact-evaluation .claude/skills/tacas-artifact-evaluation && 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-artifact-evaluation" agent skill from https://github.com/brycewang-stanford/Awesome-Journal-Skills/tree/main/TACAS-Skills/skills/tacas-artifact-evaluation into .claude/skills/tacas-artifact-evaluation/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "tacas-artifact-evaluation", 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-artifact-evaluationType 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-artifact-evaluation -a codexProject install goes to .agents/skills/; add -g for ~/.codex/skills/.
$ gh skill install brycewang-stanford/Awesome-Journal-Skills tacas-artifact-evaluation --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-artifact-evaluation .agents/skills/tacas-artifact-evaluation && 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-artifact-evaluation" agent skill from https://github.com/brycewang-stanford/Awesome-Journal-Skills/tree/main/TACAS-Skills/skills/tacas-artifact-evaluation into .agents/skills/tacas-artifact-evaluation/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "tacas-artifact-evaluation", 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-artifact-evaluation -a cursorProject install goes to .agents/skills/; add -g for ~/.cursor/skills/.
$ gh skill install brycewang-stanford/Awesome-Journal-Skills tacas-artifact-evaluation --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-artifact-evaluation .cursor/skills/tacas-artifact-evaluation && 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-artifact-evaluation" agent skill from https://github.com/brycewang-stanford/Awesome-Journal-Skills/tree/main/TACAS-Skills/skills/tacas-artifact-evaluation into .cursor/skills/tacas-artifact-evaluation/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "tacas-artifact-evaluation", 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-artifact-evaluation--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-artifact-evaluation -a gemini-cliProject install goes to .agents/skills/; add -g for ~/.gemini/skills/.
$ gh skill install brycewang-stanford/Awesome-Journal-Skills tacas-artifact-evaluation --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-artifact-evaluation .gemini/skills/tacas-artifact-evaluation && 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-artifact-evaluation" agent skill from https://github.com/brycewang-stanford/Awesome-Journal-Skills/tree/main/TACAS-Skills/skills/tacas-artifact-evaluation into .gemini/skills/tacas-artifact-evaluation/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "tacas-artifact-evaluation", 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-artifact-evaluationInstalls 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-artifact-evaluation -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-artifact-evaluation .github/skills/tacas-artifact-evaluation && 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-artifact-evaluation" agent skill from https://github.com/brycewang-stanford/Awesome-Journal-Skills/tree/main/TACAS-Skills/skills/tacas-artifact-evaluation into .github/skills/tacas-artifact-evaluation/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "tacas-artifact-evaluation", 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-artifact-evaluation -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-artifact-evaluation --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-artifact-evaluation .opencode/skills/tacas-artifact-evaluation && 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-artifact-evaluation" agent skill from https://github.com/brycewang-stanford/Awesome-Journal-Skills/tree/main/TACAS-Skills/skills/tacas-artifact-evaluation into .opencode/skills/tacas-artifact-evaluation/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "tacas-artifact-evaluation", 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-artifact-evaluation- GitHub stars
- 1.2k
- Token cost
- ~1.4k tokens
- SKILL.md length
- 593 words
- Files
- 1
- Skills in repo
- 2,387
- Repo updated
- First seen
- Licence
- MIT
At a glance
A skill your agent uses when packaging a TACAS (ETAPS) artifact for the ETAPS Artifact Badges (Available, Functional, Reusable), covering the two-round model (mandatory, PC-parallel evaluation for…
- Packaging a TACAS (ETAPS) artifact for the ETAPS Artifact Badges (Available
- SKILL.md covers The two rounds (know which one…, The ETAPS Artifact Badges, What the AEC opens first and Packaging plan, plus 4 more sections
- Instructions only: no scripts, shell commands, URLs or credentials in SKILL.md
- Covering the two-round model (mandatory
What it does
Tacas Artifact Evaluation is an agent skill from brycewang-stanford/Awesome-Journal-Skills. Use when packaging a TACAS (ETAPS) artifact for the ETAPS Artifact Badges (Available, Functional, Reusable), covering the two-round model (mandatory, PC-parallel evaluation for tool and tool-demo papers vs voluntary post-acceptance evaluation for research and case-study papers), what the AEC checks on the clean evaluation VM, DOI-issuing archives, and evaluator-proof documentation.
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.
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
- Packaging a TACAS (ETAPS) artifact for the ETAPS Artifact Badges (Available
- Covering the two-round model (mandatory
- PC-parallel evaluation for tool and tool-demo papers vs voluntary post-acceptance evaluation for research and case-study papers)
- What the AEC checks on the clean evaluation VM
Example prompts
- “/tacas-artifact-evaluation”
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 Artifact Evaluation loads about 1.4k tokens when it runs. Until then it costs about 103 tokens; SKILL.md has 593 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). 593 words, ~1,409 tokens.
Download SKILL.mdSave it as
.claude/skills/tacas-artifact-evaluation/SKILL.md (or your agent's skills folder).- name
- tacas-artifact-evaluation
- description
- Use when packaging a TACAS (ETAPS) artifact for the ETAPS Artifact Badges (Available, Functional, Reusable), covering the two-round model (mandatory, PC-parallel evaluation for tool and tool-demo papers vs voluntary post-acceptance evaluation for research and case-study papers), what the AEC checks on the clean evaluation VM, DOI-issuing archives, and evaluator-proof documentation.
TACAS Artifact Evaluation
Use this for the artifact track. TACAS treats the artifact as a first-class citizen, and the process differs from most venues in two ways: for tool papers it is mandatory and runs in parallel with paper review, and badging follows the ETAPS Artifact Badge guidelines, decided by the Artifact Evaluation Committee (AEC) and printed on the paper's title page.
The two rounds (know which one you are in)
| Round | Applies to | Timing | Consequence |
|---|---|---|---|
| Round 1 — mandatory | Regular tool + tool-demonstration papers | Submitted right after the paper, evaluated with the PC | Outcome feeds the acceptance decision |
| Round 2 — voluntary | Regular research + case-study papers | After acceptance notification | Earns title-page badges; does not gate acceptance |
The consequence for a tool paper is blunt: a package that does not build or run on the clean evaluation VM can cost the paper, not merely a badge. Treat the artifact as a co-equal deliverable due about two weeks after the paper.
The ETAPS Artifact Badges
| Badge | What it certifies | What earns it |
|---|---|---|
| Available | The artifact is permanently, publicly retrievable | Deposit in a DOI-issuing archive (Zenodo, figshare, Software Heritage) |
| Functional | The artifact runs and does what the paper says | A clean-VM install, a smoke run, and documented expected outputs |
| Reusable | Others can build on and adapt it | The Functional bar plus careful docs, structure, licensing, and generality |
The AEC decides which subset a given artifact receives. Available is low-cost, high-value (archive the package); Functional and Reusable require the evaluator's own run to succeed on the provided VM, so the failure mode is always "did not run in their environment," never "the idea was weak."
What the AEC opens first
| Claim type | First thing inspected | Common failure caught |
|---|---|---|
| A verification tool | The README and one smoke command on the VM | Undocumented deps; needs network; only-builds-on-authors'-machine |
| A benchmark comparison | The script that regenerates the headline table | Numbers in the PDF no script reproduces |
| A soundness claim | The validation / witness-checking path | "Fast" results that were never checked for correctness |
| A tool-demonstration | The documented demo walkthrough | The demo the paper describes cannot be driven on the VM |
Assume a bounded evaluator time budget on the clean ETAPS VM. Design for the first ten minutes to succeed: a smoke run that finishes fast and prints an expected output.
Show full SKILL.md (215 more words)Show less
Packaging plan
[VM-ready] a package that builds/runs inside the provided VM image, offline, deps vendored
[README] one screen: what it is, smoke run, per-claim reproduction, expected outputs + runtimes
[Mapping] an explicit table: paper claim -> script -> expected result
[Benchmarks] the actual task set vendored (or documented access), not just a pointer
[Validation] a witness-checking or cross-tool script for any soundness/correctness claim
[License] an OSI-approved license so the artifact can be badged Reusable
[Archive] deposit in a DOI-issuing repository for the Available badge (esp. at camera-ready)Anonymity by category (do not get this backwards)
- Round-1 tool / tool-demo artifacts are single-blind — they may carry the tool identity and authorship, matching the single-blind paper.
- Round-2 research artifacts are submitted after acceptance, so anonymity is no longer the concern; but a research review artifact attached to the double-blind paper (if you choose to supply one at submission) must be anonymized — no owner strings, lab names, or identity-revealing repository URLs.
Worked vignette: badging a model-checking tool
A regular tool paper contributes a new checker. To target Available + Functional + Reusable: ship a
VM-ready image with the tool prebuilt; a smoke.sh that verifies one small bundled task in under a
minute; a reproduce/ directory whose scripts regenerate the benchmark table from logged runs; a
claim-to-script mapping in the README; the vendored benchmark set; a witness-validation script for
the soundness claim; and an Apache/MIT license. State honestly which results are turnkey and which
need the full (slow) benchmark run. Deposit the final version on Zenodo for the DOI.
Calibration
- The badge set, the round structure, and the VM image are set per edition on the
tacas.infoartifact page — confirm the current guidelines and image before packaging. - Do not conflate the mandatory Round-1 deadline with the voluntary Round-2 or the camera-ready; they are distinct dates.
Output format
[Round] mandatory (tool/tool-demo, PC-parallel) / voluntary (research/case-study, post-acceptance)
[Target badges] Available / Functional / Reusable
[Clean-VM test] does build + smoke run succeed offline on the provided VM? yes/no
[Claim mapping] <claim -> script -> expected result present? yes/no>
[Archive] DOI-issuing deposit ready for Available? yes/no
[Fixes before upload] <ordered list>© 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-artifact-evaluation of brycewang-stanford/Awesome-Journal-Skills.
Open the folder on GitHubat commit 932eb23
Compare with similar skills
Tacas Artifact Evaluation 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 Artifact Evaluation this skillbrycewang-stanford/Awesome-Journal-Skills | 1.2k | — | ~1.4k | Automated safety check: Pass | MIT | |
| Arize Evaluatorgithub/awesome-copilot | 40k | 1 repos | ~8.1k | Automated safety check: Notes | MIT | |
| Ccs Artifact Evaluationbrycewang-stanford/Awesome-Journal-Skills | 1.2k | — | ~969 | Automated safety check: Pass | MIT | |
| Mobisys Artifact Evaluationbrycewang-stanford/Awesome-Journal-Skills | 1.2k | — | ~1k | Automated safety check: Pass | MIT | |
| Issta Artifact Evaluationbrycewang-stanford/Awesome-Journal-Skills | 1.2k | — | ~1.2k | Automated safety check: Pass | MIT | |
| Sigcomm Artifact Evaluationbrycewang-stanford/Awesome-Journal-Skills | 1.2k | — | ~1.1k | Automated safety check: Pass | MIT |
Similar skills
- Official
Ccs Artifact Evaluation
brycewang-stanford/Awesome-Journal-Skills
A skill your agent uses when packaging ACM CCS artifacts for the artifact-evaluation committee and the ACM badges — Artifacts Available, Artifacts Evaluated Functional, Artifacts Evaluated Reusable…
Mobisys Artifact Evaluation
brycewang-stanford/Awesome-Journal-Skills
A skill your agent uses when packaging a MobiSys artifact for the Artifact Evaluation Committee — choosing among the three independent ACM badges (Available, Evaluated–Functional, Results…
Issta Artifact Evaluation
brycewang-stanford/Awesome-Journal-Skills
A skill your agent uses when packaging an ISSTA tool, benchmark, and results for the artifact-evaluation track, covering the ACM badges (Artifacts Available via Zenodo, Evaluated Functional and…
Sigcomm Artifact Evaluation
brycewang-stanford/Awesome-Journal-Skills
A skill your agent uses when packaging an ACM SIGCOMM paper's code, traces, topologies, and configuration for the artifact-evaluation committee — choosing ACM badges (Artifacts Available, Evaluated…
Sigmetrics Artifact Evaluation
brycewang-stanford/Awesome-Journal-Skills
A skill your agent uses when packaging an ACM SIGMETRICS artifact for the ACM Artifact Review and Badging scheme (Artifacts Available, Evaluated Functional and Reusable, Results Reproduced)…
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 Artifact Evaluation
What does Tacas Artifact Evaluation do?
A skill your agent uses when packaging a TACAS (ETAPS) artifact for the ETAPS Artifact Badges (Available, Functional, Reusable), covering the two-round model (mandatory, PC-parallel evaluation for…. Tacas Artifact Evaluation is an agent skill from brycewang-stanford/Awesome-Journal-Skills. Use when packaging a TACAS (ETAPS) artifact for the ETAPS Artifact Badges (Available, Functional, Reusable), covering the two-round model (mandatory, PC-parallel evaluation for tool and tool-demo papers vs voluntary post-acceptance evaluation for research and case-study papers), what the AEC checks on the clean evaluation VM, DOI-issuing archives, and evaluator-proof documentation.
When should I use Tacas Artifact Evaluation?
Tacas Artifact Evaluation fits situations like: packaging a TACAS (ETAPS) artifact for the ETAPS Artifact Badges (Available; covering the two-round model (mandatory; PC-parallel evaluation for tool and tool-demo papers vs voluntary post-acceptance evaluation for research and case-study papers); what the AEC checks on the clean evaluation VM.
How do I install Tacas Artifact Evaluation in Claude Code?
Run `npx skills add brycewang-stanford/Awesome-Journal-Skills --skill tacas-artifact-evaluation -a claude-code`. Or copy the skill folder (TACAS-Skills/skills/tacas-artifact-evaluation in brycewang-stanford/Awesome-Journal-Skills) into .claude/skills/tacas-artifact-evaluation in your project. Claude Code loads it when a task matches its description.
How do I install Tacas Artifact Evaluation in Codex?
Run `npx skills add brycewang-stanford/Awesome-Journal-Skills --skill tacas-artifact-evaluation -a codex`. Or copy the skill folder (TACAS-Skills/skills/tacas-artifact-evaluation in brycewang-stanford/Awesome-Journal-Skills) into .agents/skills/tacas-artifact-evaluation in your project. Codex loads it when a task matches its description.
Can I use Tacas Artifact Evaluation 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-artifact-evaluation -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-artifact-evaluation, .gemini/skills/tacas-artifact-evaluation, .github/skills/tacas-artifact-evaluation and .opencode/skills/tacas-artifact-evaluation in your project.
What does Tacas Artifact Evaluation need to run?
SKILL.md names no scripts, command-line tools or credentials: Tacas Artifact Evaluation is instructions for the agent only.
Does Tacas Artifact Evaluation 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 Artifact Evaluation 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 Artifact Evaluation use?
Tacas Artifact Evaluation 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 Artifact Evaluation 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 Artifact Evaluation?
Skills that share tags, products or a category with Tacas Artifact Evaluation: Arize Evaluator (github/awesome-copilot, 40k stars), Ccs Artifact Evaluation (brycewang-stanford/Awesome-Journal-Skills, 1.2k stars), Mobisys Artifact Evaluation (brycewang-stanford/Awesome-Journal-Skills, 1.2k stars) and Issta Artifact Evaluation (brycewang-stanford/Awesome-Journal-Skills, 1.2k stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.
Who maintains Tacas Artifact Evaluation?
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.