Individual skill

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-run the interaction claims.

AAMAS-Skills/skills/aamas-artifact-evaluation/SKILL.md

Read pinned source

Source commit 932eb23331721b16e967c59f093781be1928b498

What was checked

Matches the observed repository HEAD
Yes
Scanner rules are current
Yes
Repository scan complete
No
Skill scan complete
Yes
Observed behavior
Network or broad shell
Last checked
Nov 9, 2026

These are observations at the recorded commit, not a guarantee of safety. Review the source before running it.

Install this skill

Choose an agent in your Stack or copy a command below. Commands fetch the pinned commit and copy only this skill directory. Existing destinations are refused. Copying a command does not install anything.

An install command is unavailable: current rules, complete repository and skill scans, an eligible behavior level and a permitted license are required.

Repository context

Repository stars (not skill ratings)
1,405
Repository last updated
Sep 27, 2026
License
MIT

Observed agent integration: No specific integration evidence. Standard SKILL.md installation does not imply verified compatibility.

Files and excerpt

File metadata and permitted, redacted excerpts come from the recorded scan. Source links are pinned to that commit.

Browse files
Read excerpt

# 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
Back to top