dac-supplementary
Use when deciding what belongs inside the six reviewed pages of an ACM/IEEE Design Automation Conference (DAC) Research Manuscript versus in an external repository, given DAC's tight 6+1 budget, its references-only seventh page, the double-blind constraint on any linked material, and the absence of a formal reviewed-appendix or artifact-badging track.
Profile →npx skills add brycewang-stanford/Awesome-Journal-Skills --skill dac-supplementary --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 Supplementary Material Use this to split content between the reviewed pages and anything external. DAC's constraint is severe and specific: the manuscript is **6 pages of body plus one references-only page**, and unlike some venues DAC does **not** provide an unlimited reviewed appendix or a formal artifact-evaluation track (**待核实** per cycle). The governing rule follows directly: **anything that decides acceptance must fit inside the six body pages**, because a reviewer is neither obligated to nor guaranteed to open external material. ## The decision-criticality test For each piece of content, ask: *would a reviewer need this to be convinced the contribution is real and the QoR claim is fair?* If yes, it belongs in the body. If it merely lets a motivated reader reproduce or extend the work, it can live externally. | Content | Where it goes | Why | |---|---|---| | The headline QoR results and the mechanism | Body (6 pages) | Decision-critical; reviewers judge on these | | Per-benchmark result table for the main claim | Body | The fairness of the comparison is the paper | | The key ablation | Body | Attribution of the gain is decision-critical | | Full hyperparameter grids, ex
- The decision-criticality test
- The seventh page is references only
- External material under double-blind
- What DAC does not have (plan accordingly)
- Compression before relegation
- Output format
What does the dac-supplementary skill do?
Use when deciding what belongs inside the six reviewed pages of an ACM/IEEE Design Automation Conference (DAC) Research Manuscript versus in an external repository, given DAC's tight 6+1 budget, its references-only seventh page, the double-blind constraint on any linked material, and the absence of a formal reviewed-appendix or artifact-badging track.
How do I install it?
Run `npx skills add brycewang-stanford/Awesome-Journal-Skills --skill dac-supplementary --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.