cikm-artifact-evaluation
Use when packaging the code, datasets, knowledge graphs, prompts, and demo systems around a CIKM paper — choosing the artifact form per track (research, applied, resource, demo), meeting the resource track's reuse-and-documentation bar, and staging anonymous review artifacts into citable public releases.
Profile →npx skills add brycewang-stanford/Awesome-Journal-Skills --skill cikm-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.
# CIKM Artifact Evaluation CIKM has no verified badge-granting artifact track (2026 lineup: full, short, applied, resource, demo — source map, 2026-07-08), but artifacts do more work here than at most venues, because two of the five tracks are *about* artifacts: Resource papers publish them, and Demonstration papers perform them. This skill covers the artifact strategy per track and the staging from anonymous review object to public citable release. ## Artifact role by track | Track | The artifact is... | Bar it must clear | |---|---|---| | Full / Short Research | Supporting evidence, cited anonymously | Regenerates headline results; survives a ten-minute inspection | | Applied Research | Proof of practice | Substantiates the launch/deployment claim the track requires | | Resource | **The contribution itself** | Documented, licensed, maintained, adoptable by strangers | | Demonstration | The thing being demonstrated | Runs live, in front of people, on conference-venue conditions | ## Resource-track packaging bar A CIKM resource paper is graded on whether others will build on the object. The verified call names data resources, software, evaluation tasks, and open-source frameworks.
- Artifact role by track
- Resource-track packaging bar
- KG-specific packaging
- Demo systems as artifacts
- Licensing quick guide
- Hosting for the decade, not the deadline
- Anonymous-to-public staging
- Naming and versioning conventions
- Output format
What does the cikm-artifact-evaluation skill do?
Use when packaging the code, datasets, knowledge graphs, prompts, and demo systems around a CIKM paper — choosing the artifact form per track (research, applied, resource, demo), meeting the resource track's reuse-and-documentation bar, and staging anonymous review artifacts into citable public releases.
How do I install it?
Run `npx skills add brycewang-stanford/Awesome-Journal-Skills --skill cikm-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 909 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.