Sync Upstream
nyaruka/phonenumbers
Sync this Go port with a new upstream google/libphonenumber release — regenerate the embedded metadata and reconcile the ported Java logic.
A skill your agent uses when designing or auditing the evaluation of an ATC (ACM SIGOPS Annual Technical Conference, formerly USENIX ATC) systems paper — matching evidence to the claim with real…
Install Atc Experiments
$ npx skills add brycewang-stanford/Awesome-Journal-Skills --skill atc-experiments -a claude-codeProject install by default; add -g for ~/.claude/skills/.
$ gh skill install brycewang-stanford/Awesome-Journal-Skills atc-experiments --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/ATC-Skills/skills/atc-experiments .claude/skills/atc-experiments && 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 "atc-experiments" agent skill from https://github.com/brycewang-stanford/Awesome-Journal-Skills/tree/main/ATC-Skills/skills/atc-experiments into .claude/skills/atc-experiments/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "atc-experiments", 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/ATC-Skills/skills/atc-experimentsType 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 atc-experiments -a codexProject install goes to .agents/skills/; add -g for ~/.codex/skills/.
$ gh skill install brycewang-stanford/Awesome-Journal-Skills atc-experiments --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/ATC-Skills/skills/atc-experiments .agents/skills/atc-experiments && rm -rf skills-srcUse ~/.agents/skills/ instead of .agents/skills for a personal install.
Codex skills documentation · loads skills from .agents/skills/
Install the "atc-experiments" agent skill from https://github.com/brycewang-stanford/Awesome-Journal-Skills/tree/main/ATC-Skills/skills/atc-experiments into .agents/skills/atc-experiments/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "atc-experiments", 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 atc-experiments -a cursorProject install goes to .agents/skills/; add -g for ~/.cursor/skills/.
$ gh skill install brycewang-stanford/Awesome-Journal-Skills atc-experiments --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/ATC-Skills/skills/atc-experiments .cursor/skills/atc-experiments && 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 "atc-experiments" agent skill from https://github.com/brycewang-stanford/Awesome-Journal-Skills/tree/main/ATC-Skills/skills/atc-experiments into .cursor/skills/atc-experiments/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "atc-experiments", 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 ATC-Skills/skills/atc-experiments--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 atc-experiments -a gemini-cliProject install goes to .agents/skills/; add -g for ~/.gemini/skills/.
$ gh skill install brycewang-stanford/Awesome-Journal-Skills atc-experiments --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/ATC-Skills/skills/atc-experiments .gemini/skills/atc-experiments && 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 "atc-experiments" agent skill from https://github.com/brycewang-stanford/Awesome-Journal-Skills/tree/main/ATC-Skills/skills/atc-experiments into .gemini/skills/atc-experiments/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "atc-experiments", 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 atc-experimentsInstalls 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 atc-experiments -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/ATC-Skills/skills/atc-experiments .github/skills/atc-experiments && 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 "atc-experiments" agent skill from https://github.com/brycewang-stanford/Awesome-Journal-Skills/tree/main/ATC-Skills/skills/atc-experiments into .github/skills/atc-experiments/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "atc-experiments", 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 atc-experiments -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 atc-experiments --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/ATC-Skills/skills/atc-experiments .opencode/skills/atc-experiments && 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 "atc-experiments" agent skill from https://github.com/brycewang-stanford/Awesome-Journal-Skills/tree/main/ATC-Skills/skills/atc-experiments into .opencode/skills/atc-experiments/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "atc-experiments", 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
atc-experiments- GitHub stars
- 1.2k
- Token cost
- ~1.3k tokens
- SKILL.md length
- 545 words
- Files
- 1
- Skills in repo
- 2,387
- Repo updated
- First seen
- Licence
- MIT
At a glance
A skill your agent uses when designing or auditing the evaluation of an ATC (ACM SIGOPS Annual Technical Conference, formerly USENIX ATC) systems paper — matching evidence to the claim with real…
- Auditing the evaluation of an ATC (ACM SIGOPS Annual Technical Conference
- SKILL.md covers Match evidence to claim shape, Real testbeds and workloads, Fair baselines and End-to-end plus microbenchmarks, plus 4 more sections
- Instructions only: no scripts, shell commands, URLs or credentials in SKILL.md
- Formerly USENIX ATC) systems paper — matching evidence to the claim with real testbeds
What it does
Atc Experiments is an agent skill from brycewang-stanford/Awesome-Journal-Skills. Use when designing or auditing the evaluation of an ATC (ACM SIGOPS Annual Technical Conference, formerly USENIX ATC) systems paper — matching evidence to the claim with real testbeds, fair baselines, end-to-end plus microbenchmark results, tail-latency and variance reporting, workload realism, and honest cost accounting.
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 Business, Finance & HR, covering Accounting and bookkeeping and End-to-end testing. 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
- Auditing the evaluation of an ATC (ACM SIGOPS Annual Technical Conference
- Formerly USENIX ATC) systems paper — matching evidence to the claim with real testbeds
- End-to-end plus microbenchmark results
- Tail-latency and variance reporting
Example prompts
- “/atc-experiments”
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 Experiments loads about 1.3k tokens when it runs. Until then it costs about 85 tokens; SKILL.md has 545 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). 545 words, ~1,311 tokens.
Download SKILL.mdSave it as
.claude/skills/atc-experiments/SKILL.md (or your agent's skills folder).- name
- atc-experiments
- description
- Use when designing or auditing the evaluation of an ATC (ACM SIGOPS Annual Technical Conference, formerly USENIX ATC) systems paper — matching evidence to the claim with real testbeds, fair baselines, end-to-end plus microbenchmark results, tail-latency and variance reporting, workload realism, and honest cost accounting.
ATC Experiments
Match the evidence to the claim. ATC is the systems community's implementation-and-measurement venue: reviewers read for measured behavior on a real system, not asymptotics or accuracy on a dataset. In round two, 3-4 reviewers close to your subarea will open the artifact and probe whether the numbers are end-to-end, fair, and honest about cost. Design the evaluation so their first three objections are already answered.
Match evidence to claim shape
| If your claim is... | The evidence ATC expects |
|---|---|
| "Faster / lower latency" | End-to-end latency including tails (p99/p999) and throughput at a matched operating point, on a described testbed |
| "Lower overhead / cheaper" | The resource cost (CPU, memory, writes, energy) measured, at matched function — not just the headline win |
| "Scales" | Measurements across a real range of load/nodes/cores with the scaling curve and where it bends |
| "More reliable / correct" | Fault-injection or crash/recovery experiments, not just steady-state runs |
| "Useful in practice" (experience) | Production-derived workloads and lessons; what broke and what generalizes |
Real testbeds and workloads
- Describe the testbed so results are reproducible: CPU/NIC/SSD models, core counts, memory, kernel/OS versions, network topology, and any co-location. A result without its testbed is not a systems result.
- Use realistic workloads. Production-derived traces, standard benchmarks, or documented generators beat hand-picked inputs. State how the workload was obtained and why it is representative; if it is synthetic, justify the parameters.
- Warm-up and steady state. Say how you handled cold start, warm-up windows, and measurement duration — systems reviewers know where transient effects hide.
Fair baselines
- Compare against the strongest reasonable alternative, configured well (a strawman baseline is caught immediately). If you tuned your system, tune the baseline.
- Compare at a matched cost or operating point: same memory budget, same flash-write budget, same load. An unmatched comparison is the classic systems-reviewer objection.
- If no baseline exists, say so and use the unmodified system or an ablation of your own design as the reference.
Show full SKILL.md (232 more words)Show less
End-to-end plus microbenchmarks
ATC reviewers want both:
- End-to-end results show the contribution matters for the whole system under a real workload.
- Microbenchmarks isolate the mechanism, attributing the win (or cost) to your design rather than to unrelated system effects. A paper with only end-to-end numbers cannot explain why; one with only microbenchmarks cannot show it matters.
Tails, variance, and honest reporting
- Report tail latency (p99, often p999), not just means — the tail is where systems pain lives.
- Report variance across repeated runs (multiple trials, min/max or CIs). A single run is a data point, not a result.
- Report the cost beside the gain, at the matched operating point (see
atc-writing-style). A win with an unstated cost reads as a hidden weakness. - State negative or neutral regions honestly — "where the working set fits, our policy neither helps nor hurts" builds more trust than a uniformly rosy curve.
Provenance you cannot reconstruct later
Pin these at collection time — they cannot be recovered at the deadline (see atc-reproducibility):
[Hardware] CPU/NIC/SSD models, core/memory counts, firmware where it matters
[Software] kernel/OS versions, library and compiler versions, config flags
[Workload] trace source and date, generator version and seeds, request mix
[Method] warm-up window, measurement duration, number of runs, aggregation
[Code] commit SHAs for the system and every baselineSpecial cases
- Concurrency/nondeterminism: report the distribution and the scheduling/affinity settings, not a lucky run.
- Energy/power claims: name the measurement instrument and boundary (wall vs. component).
- Security/isolation claims: state the threat model and what the measurement does and does not cover.
- Experience papers: the "evaluation" is the deployment itself — scale, duration, incidents, and transferable lessons; ATC's Deployed Systems lane values this even without a new mechanism.
Output format
[Claim -> evidence] each claim mapped to the experiment that supports it; gaps flagged
[Testbed] hardware/software/workload described enough to reproduce? yes/no
[Baselines] strongest alternative, well-configured, at a matched operating point? yes/no
[Depth] end-to-end AND microbenchmarks present? tails + variance reported?
[Honesty] costs reported beside gains? neutral/negative regions stated?
[Provenance] hardware/software/workload/method/code pinned at collection time? yes/no© 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-experiments of brycewang-stanford/Awesome-Journal-Skills.
Open the folder on GitHubat commit 932eb23
Compare with similar skills
Atc Experiments 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 |
|---|---|---|---|---|---|---|
| Atc Experiments this skillbrycewang-stanford/Awesome-Journal-Skills | 1.2k | — | ~1.3k | Automated safety check: Pass | MIT | |
| Sync Upstreamnyaruka/phonenumbers | 1.6k | — | ~2.8k | Automated safety check: Pass | MIT | |
| Polymarket TradingBlockRunAI/ClawRouter | 6.6k | — | ~1.4k | Automated safety check: Pass | MIT | |
| Longbridge Value Investinghelsome/folio | 269 | 2 repos | ~1.2k | Automated safety check: Pass | MIT | |
| Radiology Tablehuang-sir1/radiology-skills | 1.9k | — | ~1.3k | Automated safety check: Pass | Custom licence | |
| Odoo Agency Fleet Reviewerpipe-org/mcp-odoo | 420 | — | ~699 | Automated safety check: Pass | MIT |
Similar skills
Polymarket Trading
BlockRunAI/ClawRouter
A skill your agent uses when the user wants to actually PLACE, manage, or redeem bets on Polymarket (not just read odds — that's the blockrunpredexon data tools).
Longbridge Value Investing
helsome/folio
Value investing analysis using Graham (NCAV/net-net/defensive-investor) and Buffett (economic moat/ROE/FCF) methodologies.
Radiology Table
huang-sir1/radiology-skills
Create/audit editable publication tables with source reconciliation; not figures or statistical inference.
Odoo Agency Fleet Review
erpipe-org/mcp-odoo
Review many client Odoo databases at once through odoo-mcp's cross-instance tools — fleet-wide accounting health, per-client aging, partial-failure triage — for agencies and partners managing 5–50…
Beancount Close
bex-co/beancount-io
Close an accounting period in a Beancount ledger by reconciling each active account through beancount-reconcile, checking assertions and recurring gaps, reviewing flags, then proposing a commit with…
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 Atc Experiments
What does Atc Experiments do?
A skill your agent uses when designing or auditing the evaluation of an ATC (ACM SIGOPS Annual Technical Conference, formerly USENIX ATC) systems paper — matching evidence to the claim with real…. Atc Experiments is an agent skill from brycewang-stanford/Awesome-Journal-Skills. Use when designing or auditing the evaluation of an ATC (ACM SIGOPS Annual Technical Conference, formerly USENIX ATC) systems paper — matching evidence to the claim with real testbeds, fair baselines, end-to-end plus microbenchmark results, tail-latency and variance reporting, workload realism, and honest cost accounting.
When should I use Atc Experiments?
Atc Experiments fits situations like: auditing the evaluation of an ATC (ACM SIGOPS Annual Technical Conference; formerly USENIX ATC) systems paper — matching evidence to the claim with real testbeds; end-to-end plus microbenchmark results; tail-latency and variance reporting.
How do I install Atc Experiments in Claude Code?
Run `npx skills add brycewang-stanford/Awesome-Journal-Skills --skill atc-experiments -a claude-code`. Or copy the skill folder (ATC-Skills/skills/atc-experiments in brycewang-stanford/Awesome-Journal-Skills) into .claude/skills/atc-experiments in your project. Claude Code loads it when a task matches its description.
How do I install Atc Experiments in Codex?
Run `npx skills add brycewang-stanford/Awesome-Journal-Skills --skill atc-experiments -a codex`. Or copy the skill folder (ATC-Skills/skills/atc-experiments in brycewang-stanford/Awesome-Journal-Skills) into .agents/skills/atc-experiments in your project. Codex loads it when a task matches its description.
Can I use Atc Experiments 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-experiments -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-experiments, .gemini/skills/atc-experiments, .github/skills/atc-experiments and .opencode/skills/atc-experiments in your project.
What does Atc Experiments need to run?
SKILL.md names no scripts, command-line tools or credentials: Atc Experiments is instructions for the agent only.
Does Atc Experiments 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 Experiments 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 Experiments use?
Atc Experiments 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 Experiments use?
About 1.3k tokens (SKILL.md is roughly 5.2k 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 Experiments?
Skills that share tags, products or a category with Atc Experiments: Sync Upstream (nyaruka/phonenumbers, 1.6k stars), Polymarket Trading (BlockRunAI/ClawRouter, 6.6k stars), Longbridge Value Investing (helsome/folio, 269 stars) and Radiology Table (huang-sir1/radiology-skills, 1.9k stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.
Who maintains Atc Experiments?
brycewang-stanford (a GitHub user) maintains it in brycewang-stanford/Awesome-Journal-Skills, which has 1,219 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.