Individual skill
ecai-artifact-evaluation
Use when planning the reproducibility/artifact story for an ECAI paper — noting that ECAI/FAIA has NO ACM/IEEE-style artifact-badging committee, so credibility is carried by the paper and its supplement and judged by the same reviewers, and adapting an ML-style reproducibility package (or a complete proof appendix for theory work) to that reality.
ECAI-Skills/skills/ecai-artifact-evaluation/SKILL.md
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.
- academic-writing Repository topic
- agent-skills Repository topic
- journal Repository topic
- academic-research Repository topic
- ai-agents Repository topic
- anthropic Repository topic
- awesome-list Repository topic
- claude Repository topic
- claude-code Repository topic
- economics Repository topic
- research Derived category
Files and excerpt
File metadata and permitted, redacted excerpts come from the recorded scan. Source links are pinned to that commit.
Browse files
SKILL.mdcore · 5,101 bytes
Read excerpt
# ECAI Artifact Evaluation
Start with a correction that saves authors from importing the wrong workflow: **ECAI does not run an
ACM/IEEE-style artifact-evaluation track with a separate badge committee.** There is no
"Artifacts Available / Functional / Reusable / Reproduced" pipeline as at ACM SIGSOFT venues, and
no separate artifact deadline to hit after acceptance. In ECAI, the reproducibility story is
**carried by the paper and its supplement and judged by the same reviewers** who read the paper,
during the one review round.
That makes the "artifact" a **submission-time asset**, not a post-acceptance badge chase. Its job is
to make the reviewer trust the claim inside a 7-page body. (Confirm on the current call whether the
edition adds any optional reproducibility checklist or appendix mechanism — this is **待核实** per
cycle and can differ between a standalone ECAI and the joint IJCAI-ECAI 2026.)
