Agent skill

Atc Artifact Evaluation

by brycewang-stanford in brycewang-stanford/Awesome-Journal-Skills

A skill your agent uses when packaging an ATC (ACM SIGOPS Annual Technical Conference, formerly USENIX ATC) artifact for the USENIX-lineage evaluation scheme — earning the Artifacts Available…

MITAuto-check passed

Install Atc Artifact Evaluation

skills CLI
$ npx skills add brycewang-stanford/Awesome-Journal-Skills --skill atc-artifact-evaluation -a claude-code

Project install by default; add -g for ~/.claude/skills/.

GitHub CLI
$ gh skill install brycewang-stanford/Awesome-Journal-Skills atc-artifact-evaluation --agent claude-code

Project scope by default; add --scope user for a personal install. Needs GitHub CLI 2.90.0 or later (public preview).

Manual copy
$ git clone --depth 1 https://github.com/brycewang-stanford/Awesome-Journal-Skills.git skills-src && mkdir -p .claude/skills && cp -r skills-src/ATC-Skills/skills/atc-artifact-evaluation .claude/skills/atc-artifact-evaluation && rm -rf skills-src

Use ~/.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/

Facts

Skill name
atc-artifact-evaluation
GitHub stars
1.2k
Token cost
~1.4k tokens
SKILL.md length
532 words
Files
1
Skills in repo
2,387
Repo updated
First seen
Licence
MIT

At a glance

A skill your agent uses when packaging an ATC (ACM SIGOPS Annual Technical Conference, formerly USENIX ATC) artifact for the USENIX-lineage evaluation scheme — earning the Artifacts Available…

  • Packaging an ATC (ACM SIGOPS Annual Technical Conference
  • SKILL.md covers The three badges (verify the…, What AEC evaluators open first, Packaging plan and Anonymized review artifact vs.…, plus 3 more sections
  • Instructions only: no scripts, shell commands, URLs or credentials in SKILL.md
  • Formerly USENIX ATC) artifact for the USENIX-lineage evaluation scheme — earning the Artifacts Available

What it does

Atc Artifact Evaluation is an agent skill from brycewang-stanford/Awesome-Journal-Skills. Use when packaging an ATC (ACM SIGOPS Annual Technical Conference, formerly USENIX ATC) artifact for the USENIX-lineage evaluation scheme — earning the Artifacts Available, Artifacts Functional, and Results Reproduced badges from the Artifact Evaluation Committee on its separate post-acceptance deadline, with evaluator-proof documentation and a turnkey path to the paper's numbers.

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 an ATC (ACM SIGOPS Annual Technical Conference
  • Formerly USENIX ATC) artifact for the USENIX-lineage evaluation scheme — earning the Artifacts Available
  • Artifacts Functional
  • Results Reproduced badges from the Artifact Evaluation Committee on its separate post-acceptance deadline

Example prompts

  • “/atc-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

Atc Artifact Evaluation loads about 1.4k tokens when it runs. Until then it costs about 102 tokens; SKILL.md has 532 words of instructions outside code blocks.

Always · name and description, kept in context so the agent knows when to use it
~102
When it runs · the whole SKILL.md, loaded when a task matches
~1.4k

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). 532 words, ~1,389 tokens.

Download SKILL.mdSave it as .claude/skills/atc-artifact-evaluation/SKILL.md (or your agent's skills folder).
name
atc-artifact-evaluation
description
Use when packaging an ATC (ACM SIGOPS Annual Technical Conference, formerly USENIX ATC) artifact for the USENIX-lineage evaluation scheme — earning the Artifacts Available, Artifacts Functional, and Results Reproduced badges from the Artifact Evaluation Committee on its separate post-acceptance deadline, with evaluator-proof documentation and a turnkey path to the paper's numbers.

ATC Artifact Evaluation

Use this for the artifact track. ATC follows the shared USENIX/SIGOPS artifact-evaluation scheme: an Artifact Evaluation Committee (AEC) runs a separate, post-acceptance process through HotCRP and awards up to three badges — Artifacts Available, Artifacts Functional, and Results Reproduced. Two things to internalize: badges are earned by evaluators actually using your package, and the review artifact (anonymized, for the paper's reviewers) is not the same deliverable as the badge artifact (de-anonymized, permanently archived). ATC's artifact culture is strong and high-participation — for USENIX ATC '25, most evaluated artifacts earned Functional and a large majority earned Reproduced.

The three badges (verify the current set and names)

BadgeWhat it certifiesWhat earns it
Artifacts AvailableThe artifact is permanently, publicly retrievableDeposit in a DOI-issuing archive (Zenodo, figshare, Software Heritage)
Artifacts FunctionalIt is documented, complete, and exercisable — it runs and does what the paper saysClean-machine install, a demo, scripts + data to run the experiments
Results ReproducedAn evaluator reproduced the paper's main resultsA turnkey path from the artifact to the headline figures/tables

Available is low-cost, high-value (archive the package). Functional and Reproduced require the evaluator's own run to succeed, so the failure mode is always "did not run on their machine," never "the idea was weak."

What AEC evaluators open first

Claim typeFirst thing inspectedCommon failure caught
A built system / mechanismThe README and one install/run commandUndocumented deps; only-works-on-authors'-hardware
A performance resultThe scripts that turn a run into the paper's figuresNumbers in the PDF no script reproduces
A result needing specific hardware (RDMA/NVMe/NIC)The documented host requirements + a small-scale modeRequires unavailable hardware; no fallback
A trace-driven studyThe traces + the processing scriptsQuery shipped, data missing; provenance unpinned

Assume the evaluator has a bounded time budget on a clean machine and may lack your exact hardware. Design the first ten minutes to succeed and provide a reduced-scale path.

Packaging plan

text
[Container]   a Dockerfile or pinned environment; document any host/hardware the container cannot abstract
[README]      one-screen orientation: what it is, install, run the demo, reproduce each claim, expected runtime/outputs
[Mapping]     an explicit table: paper claim -> script -> expected figure/table -> tolerance
[Scale]       a full-scale path AND a small-scale mode for evaluators without the hardware
[Data]        the traces/datasets themselves (or durable documented access), not just the query
[Provenance]  kernel/OS versions, hardware models, commit SHAs, workload seeds, run counts
[License]     an OSI-approved license so the artifact can be shared and reused
[Archive]     deposit in a DOI-issuing repository for the Available badge
Show full SKILL.md (213 more words)Show less

Anonymized review artifact vs. badge artifact

  • At submission (review): anonymized for the paper's double-blind reviewers — no owner strings, cluster hostnames, lab/product names, or identity-revealing links, and no live repo that discloses authors (see atc-reproducibility).
  • After acceptance (badge): replace anonymized placeholders with the public, licensed, DOI-issuing archive; this is the version the AEC badges and the camera-ready cites.

Worked vignette: a storage-cache policy + measurement

A paper contributes a flash-cache admission policy and a testbed evaluation. To target Functional and Reproduced: ship a container with the modified server pre-built; a run_demo.sh that exercises the policy on a bundled trace sample in a minute; a reproduce/ directory whose scripts regenerate each figure from logged runs; a claim-to-script mapping with tolerances in the README; the production-derived trace sample (with pinned provenance) plus documentation of the full trace's access; a documented note that the full-scale p99 result needs the 12-node testbed, with a single-node small-scale mode; and an MIT/Apache license. State honestly which results are full-scale-only.

Calibration

  • The AEC deadline is after acceptance and independent of the camera-ready — do not conflate them (plan both in atc-workflow).
  • Badge names, the exact set offered, and whether evaluation is single- or double-anonymous can vary by cycle and moved in the SIGOPS transition — confirm on the current call for artifacts.

Output format

text
[Target badges] Available / Functional / Reproduced
[Artifact role] anonymized review artifact / public badge artifact
[Contents] <system/data/scripts/provenance/license/archive>
[Ten-minute test] install + demo succeed on a clean machine? yes/no
[Reproduce] claim -> script -> expected figure present? small-scale mode for missing hardware? 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 ATC-Skills/skills/atc-artifact-evaluation of brycewang-stanford/Awesome-Journal-Skills.

Open the folder on GitHubat commit 932eb23

Compare with similar skills

Atc 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.

Atc Artifact Evaluation compared with similar skills
SkillStarsUsed inTokensAuto-checkLicenceRepo updated
Atc Artifact Evaluation this skillbrycewang-stanford/Awesome-Journal-Skills1.2k—~1.4kAutomated safety check: PassMIT
Arize Evaluatorgithub/awesome-copilot40k1 repos~8.1kAutomated safety check: NotesMIT
Ccs Artifact Evaluationbrycewang-stanford/Awesome-Journal-Skills1.2k—~969Automated safety check: PassMIT
Sigcomm Artifact Evaluationbrycewang-stanford/Awesome-Journal-Skills1.2k—~1.1kAutomated safety check: PassMIT
Sigmetrics Artifact Evaluationbrycewang-stanford/Awesome-Journal-Skills1.2k—~1.4kAutomated safety check: PassMIT
Socc Artifact Evaluationbrycewang-stanford/Awesome-Journal-Skills1.2k—~1.5kAutomated safety check: PassMIT

Similar skills

  • Arize Evaluator

    github/awesome-copilot

    Official

    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…

    40k GitHub starsUsed in 1 repo~8.1k tokens
    AI & LLM EngineeringAuto-check: notes
  • 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…

    1.2k GitHub stars~969 tokensUpdated 13 days ago
    Auto-check passed
  • 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…

    1.2k GitHub stars~1.1k tokensUpdated 13 days ago
    Business, Finance & HRAuto-check passed
  • 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)…

    1.2k GitHub stars~1.4k tokensUpdated 13 days ago
    Auto-check passed
  • Socc Artifact Evaluation

    brycewang-stanford/Awesome-Journal-Skills

    A skill your agent uses when packaging an ACM SoCC artifact for the ACM Artifact Review and Badging scheme (Artifacts Available, Evaluated Functional and Reusable, Results Reproduced), covering what…

    1.2k GitHub stars~1.5k tokensUpdated 13 days ago
    Auto-check passed
  • 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…

    1.2k GitHub stars~1k tokensUpdated 13 days ago
    Auto-check passed

More from brycewang-stanford/Awesome-Journal-Skills

All 2,387 skills in this repo
  • Aaag 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…

    1.2k GitHub stars~1.3k tokensUpdated 13 days ago
    Auto-check passed
  • 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…

    1.2k GitHub stars~1.3k tokensUpdated 13 days ago
    Auto-check passed
  • 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…

    1.2k GitHub stars~1.4k tokensUpdated 13 days ago
    Auto-check passed
  • 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…

    1.2k GitHub stars~1.4k tokensUpdated 13 days ago
    Auto-check passed
  • 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…

    1.2k GitHub stars~1.3k tokensUpdated 13 days ago
    Auto-check passed
  • 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…

    1.2k GitHub stars~1.6k tokensUpdated 13 days ago
    Auto-check passed

Questions about Atc Artifact Evaluation

What does Atc Artifact Evaluation do?

A skill your agent uses when packaging an ATC (ACM SIGOPS Annual Technical Conference, formerly USENIX ATC) artifact for the USENIX-lineage evaluation scheme — earning the Artifacts Available…. Atc Artifact Evaluation is an agent skill from brycewang-stanford/Awesome-Journal-Skills. Use when packaging an ATC (ACM SIGOPS Annual Technical Conference, formerly USENIX ATC) artifact for the USENIX-lineage evaluation scheme — earning the Artifacts Available, Artifacts Functional, and Results Reproduced badges from the Artifact Evaluation Committee on its separate post-acceptance deadline, with evaluator-proof documentation and a turnkey path to the paper's numbers.

When should I use Atc Artifact Evaluation?

Atc Artifact Evaluation fits situations like: packaging an ATC (ACM SIGOPS Annual Technical Conference; formerly USENIX ATC) artifact for the USENIX-lineage evaluation scheme — earning the Artifacts Available; artifacts Functional; results Reproduced badges from the Artifact Evaluation Committee on its separate post-acceptance deadline.

How do I install Atc Artifact Evaluation in Claude Code?

Run `npx skills add brycewang-stanford/Awesome-Journal-Skills --skill atc-artifact-evaluation -a claude-code`. Or copy the skill folder (ATC-Skills/skills/atc-artifact-evaluation in brycewang-stanford/Awesome-Journal-Skills) into .claude/skills/atc-artifact-evaluation in your project. Claude Code loads it when a task matches its description.

How do I install Atc Artifact Evaluation in Codex?

Run `npx skills add brycewang-stanford/Awesome-Journal-Skills --skill atc-artifact-evaluation -a codex`. Or copy the skill folder (ATC-Skills/skills/atc-artifact-evaluation in brycewang-stanford/Awesome-Journal-Skills) into .agents/skills/atc-artifact-evaluation in your project. Codex loads it when a task matches its description.

Can I use Atc 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 atc-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/atc-artifact-evaluation, .gemini/skills/atc-artifact-evaluation, .github/skills/atc-artifact-evaluation and .opencode/skills/atc-artifact-evaluation in your project.

What does Atc Artifact Evaluation need to run?

SKILL.md names no scripts, command-line tools or credentials: Atc Artifact Evaluation is instructions for the agent only.

Does Atc 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 Atc 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 Atc Artifact Evaluation use?

Atc 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 Atc 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 Atc Artifact Evaluation?

Skills that share tags, products or a category with Atc Artifact Evaluation: Arize Evaluator (github/awesome-copilot, 40k stars), Ccs Artifact Evaluation (brycewang-stanford/Awesome-Journal-Skills, 1.2k stars), Sigcomm Artifact Evaluation (brycewang-stanford/Awesome-Journal-Skills, 1.2k stars) and Sigmetrics 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 Atc 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.