dac-artifact-evaluation
Use when packaging the code, benchmarks, and flows behind an ACM/IEEE Design Automation Conference (DAC) Research Manuscript into a credible, reusable artifact — given that DAC has historically run no formal artifact-evaluation or badge-issuing track (verify per cycle), so the goal is reviewer credibility and community reuse via open EDA flows and DOI-archived releases, not an ACM badge.
Profile →npx skills add brycewang-stanford/Awesome-Journal-Skills --skill dac-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.
# DAC Artifact Evaluation Read the venue reality first. Unlike the software-engineering venues (FSE/ICSE/ISSTA) and the computer-architecture venues (MICRO/ISCA/HPCA), **DAC has historically not operated a standing, badge-issuing artifact-evaluation track** for research manuscripts; whether the current cycle adds one is **待核实** (`resources/official-source-map.md`). So do not build for an ACM badge that DAC does not award. Build instead for the two things that actually matter at DAC: **making a skeptical reviewer trust your QoR numbers** and **making the community able to reuse and cite your work**. ## What an EDA artifact is for at DAC | Goal | What it buys you | How it is earned | |---|---|---| | Reviewer credibility | A QoR claim that reads as real, not cherry-picked | Standard benchmarks, disclosed flow, a runnable path | | Community reuse | Citations and follow-on work built on your tool | Clean open-source release, good docs, a license | | Contest/leaderboard standing | Recognition on ISPD/TAU/CAD-contest tasks | A tool that runs on the contest harness | There is no badge to chase, so the design target is a package a stranger can run and a reviewer would believe — not a checkl
- What an EDA artifact is for at DAC
- Packaging plan for an EDA artifact
- The clean-machine, bounded-time test
- Anonymized review artifact vs public release
- Worked vignette: packaging a placement tool + benchmarks
- Calibration
- Output format
What does the dac-artifact-evaluation skill do?
Use when packaging the code, benchmarks, and flows behind an ACM/IEEE Design Automation Conference (DAC) Research Manuscript into a credible, reusable artifact — given that DAC has historically run no formal artifact-evaluation or badge-issuing track (verify per cycle), so the goal is reviewer credibility and community reuse via open EDA flows and DOI-archived releases, not an ACM badge.
How do I install it?
Run `npx skills add brycewang-stanford/Awesome-Journal-Skills --skill dac-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.