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.
Profile →npx skills add brycewang-stanford/Awesome-Journal-Skills --skill ecai-artifact-evaluation --agent claude-code
Same command for any agent — swap --agent for codex, cursor, copilot.
Weekly change comes from our own snapshots, not the repository page — it measures attention, not adoption.
# 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.) ## Match the artifact to the contribution shape ECAI is a **general-AI** venue, so "artifact" means different things: | Contribution shape | The credibility artifact is... | |---|---| | Theory / KR / argumentation | A **complete proof appendix** (full proofs the body only sketches) plus, if
- Match the artifact to the contribution shape
- What "good" looks like at review time
- A pragmatic checklist (adapt, don't badge-chase)
- Do not import the wrong machinery
- Post-acceptance: make it permanent and open
- Output format
What does the ecai-artifact-evaluation skill do?
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.
How do I install it?
Run `npx skills add brycewang-stanford/Awesome-Journal-Skills --skill ecai-artifact-evaluation --agent claude-code` — it drops the skill into your project so the agent can pick it up. Swap the --agent value for codex, cursor or copilot if you use one of those.
Where does this skill come from?
From brycewang-stanford/Awesome-Journal-Skills, a repository with 984 stars. We read it straight from the repository tree rather than a submitted listing, so what you see here is what is actually published.
Is a popular skill a good skill?
Not necessarily. Stars measure attention, not adoption — a repository can trend for a week and be abandoned. That is why we show the weekly change from our own snapshots next to the total, instead of a single flattering number.