aaai-artifact-evaluation
Use when packaging AAAI code, data, multimedia appendices, technical appendices, reproducibility evidence, and post-acceptance artifact releases without violating double-blind or immutable-supplement rules.
Install / Use
npx skills add brycewang-stanford/Awesome-Journal-Skills --skill aaai-artifact-evaluationInstalls into whichever agent you are using.
SKILL.md
Installable skill definition
Quality Score
Category
Development & EngineeringSupported Platforms
Our assessment of aaai-artifact-evaluation
aaai-artifact-evaluation scores 83/100 on our quality scale, 3175th of 4,702 Development & Engineering skills we index.
Its SKILL.md is 3.5 KB long, split into 7 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.
Maintenance, license and trust
- The repository was last updated about 2 months ago, so aaai-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 foundOur 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.
aaai-artifact-evaluation compared with similar skills
All 4 of these similar skills score higher than aaai-artifact-evaluation; compare them before choosing.
| Skill | Score | Stars | Updated | Format |
|---|---|---|---|---|
| aaai-artifact-evaluation (this skill)by brycewang-stanford | 83 | 1.2k | 2mo ago | SKILL.md |
| taste-skillby Leonxlnx | 100 | 117.6k | 9d ago | CLAUDE.md |
| ai-job-searchby ai-job-search-dev | 100 | 72.3k | today | CLAUDE.md |
| claude-howtoby luongnv89 | 100 | 47.4k | 3d ago | CLAUDE.md |
| lobehubby lobehub | 100 | 85.7k | today | MCP Server |
Frequently asked questions
- How do I install aaai-artifact-evaluation?
- Run
npx skills add brycewang-stanford/Awesome-Journal-Skills --skill aaai-artifact-evaluation. The install tabs above show the steps for each supported agent. - Which AI agents does aaai-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 aaai-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 aaai-artifact-evaluation still maintained?
- The repository was last updated about 2 months ago, so aaai-artifact-evaluation is actively maintained.
Skill content
View source on GitHubname: aaai-artifact-evaluation description: Use when packaging AAAI code, data, multimedia appendices, technical appendices, reproducibility evidence, and post-acceptance artifact releases without violating double-blind or immutable-supplement rules.
AAAI Artifact Evaluation
Use this to prepare artifacts that reviewers can use to assess reproducibility. AAAI supplementary material is part of the submission record; after review starts, do not assume it can be updated.
Artifact package
- Provide a technical appendix for proofs, algorithms, assumptions, hyperparameters, and extended experiments.
- Provide code/data ZIPs that reproduce main tables or figures, with a short README, environment, commands, seeds, expected outputs, and runtime.
- Provide multimedia appendices only when they support the technical claim.
- Remove author names, usernames, paths, repository history, cloud buckets, API keys, and metadata.
- Avoid web pointers in the reviewed submission unless current rules explicitly allow them.
- Include licensing and access notes for datasets, models, and third-party code.
AAAI-specific discipline
- Treat the supplementary deadline as final.
- Verify ZIP integrity before submission; missing or corrupted files may not be fixable during rebuttal.
- Make the reproducibility checklist consistent with the artifact package.
- Prepare a post-acceptance public release path but keep review artifacts anonymous.
What an AAAI reviewer actually opens
AAAI does not run a separate badged artifact-evaluation committee the way some systems venues do; the same broad-AI reviewer who scores the paper also inspects whatever supplement you attach. That reviewer may be a planning, knowledge-representation, or constraint-satisfaction specialist rather than a deep-learning engineer, so the artifact has to be legible without insider tooling. Optimize for a reviewer who skims, not one who will spend an afternoon configuring a cluster.
| Reviewer action | Passes | Fails | | --- | --- | --- | | Opens the ZIP | sane tree, top README | nested archives, 0-byte files | | Reads appendix | maps to numbered claims | contradicts the paper | | Tries one command | reproduces one headline number | needs private data or credentials | | Scans for identity | nothing reveals authors | Git logs or home paths leak |
Phase-1 artifact red flags
Because clearly-below-bar papers can be cut before author feedback, a supplement that looks thin or unrunnable is a cheap reason to summary-reject. Avoid these:
- Checklist promises released code, but the ZIP only holds figures and no scripts.
- A "see our repository" pointer to a mutable, deanonymizing URL.
- Multimedia attached for spectacle that carries no technical claim, inflating size with no rigor.
- Datasets shipped with no license note, leaving reuse legality unverifiable.
Worked vignette
A constraint-solving paper claims a 30% node-expansion reduction. The team ships a large ZIP of raw
solver logs but no driver script. The reproduction path is empty, so artifact status is "risky"; the
fix is a small run_main.py that regenerates Table 2 from seeds, a trimmed log sample, and a license
for the benchmark instances. The raw dump moves to the post-acceptance release.
Output format
[Artifact status] complete / partial / risky / unavailable
[Submitted files] technical appendix / multimedia appendix / code-data ZIP
[Reviewer reproduction path] <commands and expected output>
[Anonymity risks] <metadata, links, paths, logs>
[Missing items] <data, code, seeds, licenses, hardware>
Related Skills
taste-skill
117.6kAgent skills that give coding agents taste: art direction, reference images and a browser check instead of generic AI pages
ai-job-search
72.3kThe job search that runs on your machine. AI job application framework built on Claude Code: evaluate postings, tailor CVs, write cover letters, prep interviews. Fork it and own it.
claude-howto
47.4kA visual, example-driven guide to Claude Code — from basic concepts to advanced agents, with copy-paste templates that bring immediate value.
lobehub
85.7k🤯 LobeHub - Super-Agents on Your Team. Add super-agents to the chats your team already uses.They take on work by themselves and get better every week.
Languages
Trust signals
From repository metadata: license, adoption, age and documentation. Not a code audit — see the Safety scan above for what the skill file itself contains.
