SkillAgentSearch skills...

aamas-artifact-evaluation

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-ru…

Install / Use

npx skills add brycewang-stanford/Awesome-Journal-Skills --skill aamas-artifact-evaluation

Installs into whichever agent you are using.

About this skill
πŸ“„

SKILL.md

Installable skill definition

Quality Score

83/100

Category

Other

Supported Platforms

Universal

Our assessment of aamas-artifact-evaluation

aamas-artifact-evaluation scores 83/100 on our quality scale, 261st of 331 Other skills we index.

Its SKILL.md is 3.7 KB long, split into 6 sections with 1 code example: a solid amount of guidance for an agent.

With 1,158 GitHub stars, it is one of the more widely adopted skills in the catalogue.

Substance
26/30
Structure
15/20
Description
15/15
Adoption
13/20
Freshness
15/15

Maintenance, license and trust

  • The repository was last updated about 2 months ago, so aamas-artifact-evaluation is actively maintained.
  • Our last check on 2026-11-07 found the source still online.
  • It is released under the MIT license, a permissive license that allows use, modification and commercial use with attribution.
  • Its trust signals score 100/100, with no cautions. These come from repository metadata, not a code audit β€” read the skill file before letting an agent act on it.

Safety scan

No issues found

Our scan of the whole file found no instruction hijacking, hidden characters, credential access, data exfiltration or destructive commands. An AI review of the same text found nothing harmful.

AI review by kimi-k2.7-code on 2026-10-04. Automated pattern scan on 2026-10-04. It catches known dangerous patterns, not every risk β€” read a skill before letting an agent act on it.

aamas-artifact-evaluation compared with similar skills

All 4 of these similar skills score higher than aamas-artifact-evaluation; compare them before choosing.

SkillScoreStarsUpdatedFormat
aamas-artifact-evaluation (this skill)by brycewang-stanford831.2k2mo agoSKILL.md
x402by browser-use100121.0k4d agoSKILL.md
algorithmic-artby anthropics100177.9k56d agoSKILL.md
pptxby anthropics100177.9k56d agoSKILL.md
prospectingby coreyhaines3110060.1k6d agoSKILL.md

Frequently asked questions

How do I install aamas-artifact-evaluation?
Run npx skills add brycewang-stanford/Awesome-Journal-Skills --skill aamas-artifact-evaluation. The install tabs above show the steps for each supported agent.
Which AI agents does aamas-artifact-evaluation work with?
It is written for Universal, as a SKILL.md file. Other agents that read the same format can often use it too.
Is aamas-artifact-evaluation safe to use?
Our scan of the whole file found no instruction hijacking, hidden characters, credential access, data exfiltration or destructive commands. An AI review of the same text found nothing harmful. It is MIT-licensed and scores 100/100 on trust signals. Skills are instructions an agent will follow, so read the file before installing it and do not approve commands you do not understand.
Is aamas-artifact-evaluation still maintained?
The repository was last updated about 2 months ago, so aamas-artifact-evaluation is actively maintained.

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 |

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>

Related Skills

View on GitHub
GitHub Stars1.2k
CategoryOther
Updated2mo ago
Forks153

Languages

Stata

Trust signals

100/100

From repository metadata: license, adoption, age and documentation. Not a code audit β€” see the Safety scan above for what the skill file itself contains.

No cautions
aamas-artifact-evaluation β€” Universal Skill: Install & Safety Check | SkillAgent