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
Aamas Artifact Evaluation
by brycewang-stanford in brycewang-stanford/Awesome-Journal-Skills
A skill your agent uses when packaging AAMAS multiagent code, environments, opponent and population sets, random seeds, game definitions, and logs as anonymous supplementary evidence or a public…
MITAuto-check passed
Install Aamas Artifact Evaluation
$ npx skills add brycewang-stanford/Awesome-Journal-Skills --skill aamas-artifact-evaluation -a claude-codeProject install by default; add -g for ~/.claude/skills/.
$ gh skill install brycewang-stanford/Awesome-Journal-Skills aamas-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/AAMAS-Skills/skills/aamas-artifact-evaluation .claude/skills/aamas-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 "aamas-artifact-evaluation" agent skill from https://github.com/brycewang-stanford/Awesome-Journal-Skills/tree/main/AAMAS-Skills/skills/aamas-artifact-evaluation into .claude/skills/aamas-artifact-evaluation/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "aamas-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/AAMAS-Skills/skills/aamas-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 aamas-artifact-evaluation -a codexProject install goes to .agents/skills/; add -g for ~/.codex/skills/.
$ gh skill install brycewang-stanford/Awesome-Journal-Skills aamas-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/AAMAS-Skills/skills/aamas-artifact-evaluation .agents/skills/aamas-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 "aamas-artifact-evaluation" agent skill from https://github.com/brycewang-stanford/Awesome-Journal-Skills/tree/main/AAMAS-Skills/skills/aamas-artifact-evaluation into .agents/skills/aamas-artifact-evaluation/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "aamas-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 aamas-artifact-evaluation -a cursorProject install goes to .agents/skills/; add -g for ~/.cursor/skills/.
$ gh skill install brycewang-stanford/Awesome-Journal-Skills aamas-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/AAMAS-Skills/skills/aamas-artifact-evaluation .cursor/skills/aamas-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 "aamas-artifact-evaluation" agent skill from https://github.com/brycewang-stanford/Awesome-Journal-Skills/tree/main/AAMAS-Skills/skills/aamas-artifact-evaluation into .cursor/skills/aamas-artifact-evaluation/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "aamas-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 AAMAS-Skills/skills/aamas-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 aamas-artifact-evaluation -a gemini-cliProject install goes to .agents/skills/; add -g for ~/.gemini/skills/.
$ gh skill install brycewang-stanford/Awesome-Journal-Skills aamas-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/AAMAS-Skills/skills/aamas-artifact-evaluation .gemini/skills/aamas-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 "aamas-artifact-evaluation" agent skill from https://github.com/brycewang-stanford/Awesome-Journal-Skills/tree/main/AAMAS-Skills/skills/aamas-artifact-evaluation into .gemini/skills/aamas-artifact-evaluation/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "aamas-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 aamas-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 aamas-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/AAMAS-Skills/skills/aamas-artifact-evaluation .github/skills/aamas-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 "aamas-artifact-evaluation" agent skill from https://github.com/brycewang-stanford/Awesome-Journal-Skills/tree/main/AAMAS-Skills/skills/aamas-artifact-evaluation into .github/skills/aamas-artifact-evaluation/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "aamas-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 aamas-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 aamas-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/AAMAS-Skills/skills/aamas-artifact-evaluation .opencode/skills/aamas-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 "aamas-artifact-evaluation" agent skill from https://github.com/brycewang-stanford/Awesome-Journal-Skills/tree/main/AAMAS-Skills/skills/aamas-artifact-evaluation into .opencode/skills/aamas-artifact-evaluation/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "aamas-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
aamas-artifact-evaluation- GitHub stars
- 1.2k
- Token cost
- ~958 tokens
- SKILL.md length
- 436 words
- Files
- 1
- Skills in repo
- 2,387
- Repo updated
- First seen
- Licence
- MIT
At a glance
A skill your agent uses when packaging AAMAS multiagent code, environments, opponent and population sets, random seeds, game definitions, and logs as anonymous supplementary evidence or a public…
- Packaging AAMAS multiagent code
- SKILL.md covers Artifact plan, What AAMAS evidence reviewers…, Worked vignette: packaging a… and Calibration anchors, plus 1 more section
- Instructions only: no scripts, shell commands, URLs or credentials in SKILL.md
- Opponent and population sets
What it does
Aamas Artifact Evaluation is an agent skill from brycewang-stanford/Awesome-Journal-Skills. Use when packaging AAMAS multiagent code, environments, opponent and population sets, random seeds, game definitions, and logs as anonymous supplementary evidence or a public post-acceptance release, even without a separate artifact badge, so that game-theory and MARL reviewers can inspect and re-run the interaction claims.
Its SKILL.md is about 960 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 AAMAS multiagent code
- Opponent and population sets
- Game definitions
- Logs as anonymous supplementary evidence
Example prompts
- “/aamas-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
Aamas Artifact Evaluation loads about 958 tokens when it runs. Until then it costs about 88 tokens; SKILL.md has 436 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). 436 words, ~958 tokens.
Download SKILL.mdSave it as
.claude/skills/aamas-artifact-evaluation/SKILL.md (or your agent's skills folder).- name
- aamas-artifact-evaluation
- description
- Use when packaging AAMAS multiagent code, environments, opponent and population sets, random seeds, game definitions, and logs as anonymous supplementary evidence or a public post-acceptance release, even without a separate artifact badge, so that game-theory and MARL reviewers can inspect and re-run the interaction claims.
AAMAS Artifact Evaluation
Use this for evidence packaging around AAMAS. Because the venue is about interaction, an artifact must make a multiagent claim inspectable: the game, the other agents, and the protocol, not just a single trained model.
Artifact plan
- Decide what a reviewer needs to believe the interaction claim: game or environment code, opponent/population definitions, the training regime, seeds, payoff logs, proofs, or qualitative episode traces.
- Keep decision-critical evidence in the main paper or appendix; optional bulk runs can live in the supplementary zip.
- Anonymize repository history, paths, environment names, license headers, cluster paths, and commit authors for the review version.
- Include a minimal reproduction map: environment build, dependencies, hardware, commands, expected outputs, per-run wall-clock, seeds, and known nondeterminism (especially in self-play).
- For a deployed or human-subject setting, give enough provenance for credible reproduction without violating data-use terms.
- After acceptance, replace anonymous archives with a public, licensed, citable artifact.
What AAMAS evidence reviewers open first
The single fact that shapes packaging: a reviewer will re-run a small game far sooner than they will retrain a large policy, so make the strategic core turnkey before polishing anything.
| Claim type | First artifact inspected | Common failure caught |
|---|---|---|
| Convergence to an equilibrium | The game definition and the learning-rule code | Solution concept named in the paper but not encoded in the evaluation |
| Emergent cooperation/defection | The environment and reward specification | Result depends on an undocumented reward-shaping constant |
| Beats other agents | The opponent/population set and match protocol | Only self-play reported; no held-out opponents |
| Mechanism is truthful | The payment rule plus a strategic-deviation test | No script that lets an agent try to game the mechanism |
Show full SKILL.md (168 more words)Show less
Worked vignette: packaging a self-play study
A hypothetical submission claims a learning rule that converges to a correlated equilibrium in a repeated congestion game, shown by self-play.
- Ship the game as one parameterized generator (number of agents, capacity, payoff scale) rather than constants buried in a notebook, so reviewers can vary the interaction.
- Record the exact seed sequence and replication count behind every convergence plot; an equilibrium-convergence claim without seeds is unfalsifiable.
- Emit payoff and regret tables directly from logged results so PDF and artifact numbers cannot drift.
- Include a strategic-deviation harness: a script that drops in a non-conforming agent and measures whether it profits, because that is exactly what a game-theory reviewer will try.
Calibration anchors
- Supplement inspection at AAMAS is at reviewer discretion; assume only the README and one entry script get opened, and design the top level accordingly.
- Supplement size and format caps vary by cycle (25 MB single zip in 2026); verify against the current OpenReview form rather than a past year.
Output format
[Artifact role] anonymous supplement / camera-ready release / public archive
[Contents] <game/env/opponents/seeds/proofs/logs>
[Anonymity risks] <paths/metadata/licenses/URLs>
[Reproduction level] turnkey / scripted / descriptive / weak
[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 AAMAS-Skills/skills/aamas-artifact-evaluation of brycewang-stanford/Awesome-Journal-Skills.
Open the folder on GitHubat commit 932eb23
Compare with similar skills
Aamas 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 |
|---|---|---|---|---|---|---|
| Aamas Artifact Evaluation this skillbrycewang-stanford/Awesome-Journal-Skills | 1.2k | — | ~958 | Automated safety check: Pass | MIT | |
| Arize Evaluatorgithub/awesome-copilot | 40k | 1 repos | ~8.1k | Automated safety check: Notes | MIT | |
| Artifacts Buildernexu-io/open-design | 100k | — | ~347 | Automated safety check: Pass | Apache-2.0 | |
| Flox Environmentsaffaan-m/ECC | 276k | 1 repos | ~3.5k | 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 |
Similar skills
- Official
Artifacts Builder
nexu-io/open-design
Suite of tools for creating elaborate, multi-component claude.ai HTML artifacts using modern frontend web technologies (React, Tailwind CSS, shadcn/ui).
Flox Environments
affaan-m/ECC
Create reproducible, cross-platform (macOS/Linux) development environments with Flox, a declarative Nix-based environment manager.
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…
Fast Artifact Evaluation
brycewang-stanford/Awesome-Journal-Skills
A skill your agent uses when packaging a USENIX FAST artifact for the USENIX Artifact Evaluation scheme (Artifacts Available, Artifacts Functional, Results Reproduced), covering what a storage AEC…
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 Aamas Artifact Evaluation
What does Aamas Artifact Evaluation do?
A skill your agent uses when packaging AAMAS multiagent code, environments, opponent and population sets, random seeds, game definitions, and logs as anonymous supplementary evidence or a public…. Aamas Artifact Evaluation is an agent skill from brycewang-stanford/Awesome-Journal-Skills. Use when packaging AAMAS multiagent code, environments, opponent and population sets, random seeds, game definitions, and logs as anonymous supplementary evidence or a public post-acceptance release, even without a separate artifact badge, so that game-theory and MARL reviewers can inspect and re-run the interaction claims.
When should I use Aamas Artifact Evaluation?
Aamas Artifact Evaluation fits situations like: packaging AAMAS multiagent code; opponent and population sets; game definitions; logs as anonymous supplementary evidence.
How do I install Aamas Artifact Evaluation in Claude Code?
Run `npx skills add brycewang-stanford/Awesome-Journal-Skills --skill aamas-artifact-evaluation -a claude-code`. Or copy the skill folder (AAMAS-Skills/skills/aamas-artifact-evaluation in brycewang-stanford/Awesome-Journal-Skills) into .claude/skills/aamas-artifact-evaluation in your project. Claude Code loads it when a task matches its description.
How do I install Aamas Artifact Evaluation in Codex?
Run `npx skills add brycewang-stanford/Awesome-Journal-Skills --skill aamas-artifact-evaluation -a codex`. Or copy the skill folder (AAMAS-Skills/skills/aamas-artifact-evaluation in brycewang-stanford/Awesome-Journal-Skills) into .agents/skills/aamas-artifact-evaluation in your project. Codex loads it when a task matches its description.
Can I use Aamas 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 aamas-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/aamas-artifact-evaluation, .gemini/skills/aamas-artifact-evaluation, .github/skills/aamas-artifact-evaluation and .opencode/skills/aamas-artifact-evaluation in your project.
What does Aamas Artifact Evaluation need to run?
SKILL.md names no scripts, command-line tools or credentials: Aamas Artifact Evaluation is instructions for the agent only.
Does Aamas 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 Aamas 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 Aamas Artifact Evaluation use?
Aamas 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 Aamas Artifact Evaluation use?
About 958 tokens (SKILL.md is roughly 3.8k 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 Aamas Artifact Evaluation?
Skills that share tags, products or a category with Aamas Artifact Evaluation: Arize Evaluator (github/awesome-copilot, 40k stars), Artifacts Builder (nexu-io/open-design, 100k stars), Flox Environments (affaan-m/ECC, 276k stars) and Ccs 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 Aamas 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.