Review Pending PR Reviews
nrwl/nx
Review, grill, edit, and post pending PR review drafts saved by /review-pr (or its batch/cron runners).
A skill your agent uses 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…
MITAuto-check passed
Install Dac Supplementary
$ npx skills add brycewang-stanford/Awesome-Journal-Skills --skill dac-supplementary -a claude-codeProject install by default; add -g for ~/.claude/skills/.
$ gh skill install brycewang-stanford/Awesome-Journal-Skills dac-supplementary --agent claude-codeProject scope by default; add --scope user for a personal install. Needs GitHub CLI 2.90.0 or later (public preview).
$ git clone --depth 1 https://github.com/brycewang-stanford/Awesome-Journal-Skills.git skills-src && mkdir -p .claude/skills && cp -r skills-src/DAC-Skills/skills/dac-supplementary .claude/skills/dac-supplementary && rm -rf skills-srcUse ~/.claude/skills/ instead of .claude/skills for a personal install. The folder must contain SKILL.md.
Claude Code skills documentation · loads skills from .claude/skills/
Install the "dac-supplementary" agent skill from https://github.com/brycewang-stanford/Awesome-Journal-Skills/tree/main/DAC-Skills/skills/dac-supplementary into .claude/skills/dac-supplementary/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "dac-supplementary", then confirm the skill loads.Claude Code copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$skill-installer install https://github.com/brycewang-stanford/Awesome-Journal-Skills/tree/main/DAC-Skills/skills/dac-supplementaryType this inside Codex. $skill-installer <name> installs a curated skill from openai/skills. The installer writes to $CODEX_HOME/skills (default ~/.codex/skills). Restart Codex if the skill does not show up.
$ npx skills add brycewang-stanford/Awesome-Journal-Skills --skill dac-supplementary -a codexProject install goes to .agents/skills/; add -g for ~/.codex/skills/.
$ gh skill install brycewang-stanford/Awesome-Journal-Skills dac-supplementary --agent codexProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/brycewang-stanford/Awesome-Journal-Skills.git skills-src && mkdir -p .agents/skills && cp -r skills-src/DAC-Skills/skills/dac-supplementary .agents/skills/dac-supplementary && rm -rf skills-srcUse ~/.agents/skills/ instead of .agents/skills for a personal install.
Codex skills documentation · loads skills from .agents/skills/
Install the "dac-supplementary" agent skill from https://github.com/brycewang-stanford/Awesome-Journal-Skills/tree/main/DAC-Skills/skills/dac-supplementary into .agents/skills/dac-supplementary/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "dac-supplementary", then confirm the skill loads.Codex copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ npx skills add brycewang-stanford/Awesome-Journal-Skills --skill dac-supplementary -a cursorProject install goes to .agents/skills/; add -g for ~/.cursor/skills/.
$ gh skill install brycewang-stanford/Awesome-Journal-Skills dac-supplementary --agent cursorProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/brycewang-stanford/Awesome-Journal-Skills.git skills-src && mkdir -p .cursor/skills && cp -r skills-src/DAC-Skills/skills/dac-supplementary .cursor/skills/dac-supplementary && rm -rf skills-srcUse ~/.cursor/skills/ instead of .cursor/skills for a personal install.
Cursor skills documentation · loads skills from .cursor/skills/, .agents/skills/, .claude/skills/, .codex/skills/
Install the "dac-supplementary" agent skill from https://github.com/brycewang-stanford/Awesome-Journal-Skills/tree/main/DAC-Skills/skills/dac-supplementary into .cursor/skills/dac-supplementary/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "dac-supplementary", then confirm the skill loads.Cursor copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ gemini skills install https://github.com/brycewang-stanford/Awesome-Journal-Skills.git --path DAC-Skills/skills/dac-supplementary--scope user (default) or --scope workspace; --path is the subfolder of the repo that holds the skill; --consent skips the security confirmation prompt.
$ npx skills add brycewang-stanford/Awesome-Journal-Skills --skill dac-supplementary -a gemini-cliProject install goes to .agents/skills/; add -g for ~/.gemini/skills/.
$ gh skill install brycewang-stanford/Awesome-Journal-Skills dac-supplementary --agent gemini-cliProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/brycewang-stanford/Awesome-Journal-Skills.git skills-src && mkdir -p .gemini/skills && cp -r skills-src/DAC-Skills/skills/dac-supplementary .gemini/skills/dac-supplementary && rm -rf skills-srcUse ~/.gemini/skills/ instead of .gemini/skills for a personal install, then run /skills reload.
Gemini CLI skills documentation · loads skills from .gemini/skills/, .agents/skills/
Install the "dac-supplementary" agent skill from https://github.com/brycewang-stanford/Awesome-Journal-Skills/tree/main/DAC-Skills/skills/dac-supplementary into .gemini/skills/dac-supplementary/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "dac-supplementary", then confirm the skill loads.Gemini CLI copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ gh skill install brycewang-stanford/Awesome-Journal-Skills dac-supplementaryInstalls for Copilot at project scope by default; add --scope user for a personal install. Preview a skill first with gh skill preview. Needs GitHub CLI 2.90.0 or later (public preview).
$ npx skills add brycewang-stanford/Awesome-Journal-Skills --skill dac-supplementary -a github-copilotProject install goes to .agents/skills/; add -g for ~/.copilot/skills/.
$ git clone --depth 1 https://github.com/brycewang-stanford/Awesome-Journal-Skills.git skills-src && mkdir -p .github/skills && cp -r skills-src/DAC-Skills/skills/dac-supplementary .github/skills/dac-supplementary && rm -rf skills-srcUse ~/.copilot/skills/ instead of .github/skills for a personal install. Commit .github/skills so cloud agent and code review can use it.
GitHub Copilot skills documentation · loads skills from .github/skills/, .claude/skills/, .agents/skills/
Install the "dac-supplementary" agent skill from https://github.com/brycewang-stanford/Awesome-Journal-Skills/tree/main/DAC-Skills/skills/dac-supplementary into .github/skills/dac-supplementary/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "dac-supplementary", then confirm the skill loads.GitHub Copilot copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ npx skills add brycewang-stanford/Awesome-Journal-Skills --skill dac-supplementary -a opencodeOpenCode documents no install command of its own. Project install goes to .agents/skills/; add -g for ~/.config/opencode/skills/.
$ gh skill install brycewang-stanford/Awesome-Journal-Skills dac-supplementary --agent opencodeProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/brycewang-stanford/Awesome-Journal-Skills.git skills-src && mkdir -p .opencode/skills && cp -r skills-src/DAC-Skills/skills/dac-supplementary .opencode/skills/dac-supplementary && rm -rf skills-srcUse ~/.config/opencode/skills/ instead of .opencode/skills for a personal install.
OpenCode skills documentation · loads skills from .opencode/skills/, .claude/skills/, .agents/skills/
Install the "dac-supplementary" agent skill from https://github.com/brycewang-stanford/Awesome-Journal-Skills/tree/main/DAC-Skills/skills/dac-supplementary into .opencode/skills/dac-supplementary/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "dac-supplementary", then confirm the skill loads.OpenCode copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
Facts
- Skill name
dac-supplementary- GitHub stars
- 1.2k
- Token cost
- ~1k tokens
- SKILL.md length
- 486 words
- Files
- 1
- Skills in repo
- 2,387
- Repo updated
- First seen
- Licence
- MIT
At a glance
A skill your agent uses 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…
- Given DACs tight 6+1 budget
- SKILL.md covers The decision-criticality test, The seventh page is references…, External material under… and What DAC does not have (plan…, plus 2 more sections
- Instructions only: no scripts, shell commands, URLs or credentials in SKILL.md
- Its references-only seventh page
What it does
Dac Supplementary is an agent skill from brycewang-stanford/Awesome-Journal-Skills. 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.
Its SKILL.md is about 1k tokens, which your agent loads only when the skill is triggered. It is a single SKILL.md file with no bundled scripts.
The repository describes itself as: Journal-specific Claude Code/Codex skill packs covering mainstream journals — AER, QJE, Nature, Cell, 管理世界, 经济研究 & 200+ more — your fast track to getting published. ｜ 覆盖主流期刊的… The licence is MIT.
When your agent uses it
- Given DACs tight 6+1 budget
- Its references-only seventh page
- The double-blind constraint on any linked material
- The absence of a formal reviewed-appendix
Example prompts
- “/dac-supplementary”
What it can do on your machine
Read from SKILL.md and the folder at commit 932eb23. It shows what the files ask for, not the result of running them.
Tool permissions
Pre-approves nothing: there is no allowed-tools line, so your agent's usual permission prompts apply.
From allowed-tools in the SKILL.md frontmatter.
Runs code
No scripts in the folder and no shell commands in SKILL.md.
From the folder's file list and the shell code blocks in SKILL.md.
Network
No URLs in SKILL.md.
From URLs in SKILL.md, links to its own repository left out.
Credentials
Names no API keys, tokens, secrets or passwords.
From names ending in _API_KEY, _TOKEN, _SECRET, _KEY or _PASSWORD in SKILL.md.
Context cost
Dac Supplementary loads about 1k tokens when it runs. Until then it costs about 93 tokens; SKILL.md has 486 words of instructions outside code blocks.
Estimates: characters ÷ 4, the usual rule of thumb; real counts depend on the model's tokenizer. Scripts and assets cost tokens only if the agent reads them.
Safety
Auto-check passed
The automated check found no risky patterns in SKILL.md.
Automated static check — not a guarantee. Review scripts before installing. It scans the text of SKILL.md for risky patterns (piping downloads into a shell, reading credential files, hidden Unicode, destructive commands); files beside SKILL.md are not scanned.
SKILL.md
The full file from brycewang-stanford/Awesome-Journal-Skills at commit 932eb23, republished under its MIT licence (© brycewang-stanford). 486 words, ~1,037 tokens.
Download SKILL.mdSave it as
.claude/skills/dac-supplementary/SKILL.md (or your agent's skills folder).- name
- dac-supplementary
- description
- 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.
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, extra corners, exhaustive per-instance logs | External repo | Supports reproduction, does not decide acceptance |
| Source code, scripts, generated datasets | External repo | Reproducibility, not a reviewed deliverable |
| Extra proofs/derivations too long for six pages | External repo, with the result stated in-body | The claim must stand in-body; detail can be external |
The seventh page is references only
DAC's most mechanical rule: the one extra page holds references and nothing else. Do not treat
it as an appendix — an extra figure, a paragraph, or a table there is grounds for desk rejection
(../dac-submission). Plan the technical argument to end cleanly at page six.
Show full SKILL.md (207 more words)Show less
External material under double-blind
If you link a repository, dataset, or artifact at review time, it must be anonymized exactly like the PDF:
- No author names, institution names, or lab-named tools in the repo, README, or commit metadata.
- Host on an anonymizing service or a fresh anonymous mirror; a personal GitHub URL de-anonymizes.
- Strip cluster paths, internal server names, and vendor-flow fingerprints from any logs or scripts you include.
- Remember reviewers may not open it — so external material can only strengthen a paper that already stands on its six pages, never rescue one that does not.
What DAC does not have (plan accordingly)
- No formal reviewed appendix — do not write "see the appendix" for anything decision-critical; there is no guaranteed extra reviewed space beyond the six pages.
- No standing ACM artifact-badging track for research manuscripts (待核实) — so an artifact
earns you credibility and citations, not a badge; build it for reproducibility and community use,
not for a review score (
../dac-artifact-evaluation,../dac-reproducibility).
Compression before relegation
Before moving something out, try to earn its space in the body: convert a prose result to a compact table, merge two figures, cut standard EDA background the reviewers already know. Six dense double-column pages hold more than first drafts assume.
Output format
[Split audit] each item -> body (decision-critical) / external (reproduction) / cut
[Seventh page] references only, no body content? yes/no
[External anon] linked repo/dataset/artifact anonymized? reviewer-optional acknowledged? yes/no
[Stands alone] does the paper convince on its six pages without external material? yes/no
[Compression] space reclaimed before relegating anything? yes/no© brycewang-stanford, MIT. Rendered from Markdown: HTML in the file is shown as text, images as links, and headings moved down two levels. Raw file
Files
Just SKILL.md in DAC-Skills/skills/dac-supplementary of brycewang-stanford/Awesome-Journal-Skills.
Open the folder on GitHubat commit 932eb23
Compare with similar skills
Dac Supplementary next to the 5 skills that share the most tags, products or categories with it. Stars are the repository's; “used in” counts other GitHub owners with a copy.
| Skill | Stars | Used in | Tokens | Auto-check | Licence | Repo updated |
|---|---|---|---|---|---|---|
| Dac Supplementary this skillbrycewang-stanford/Awesome-Journal-Skills | 1.2k | — | ~1k | Automated safety check: Pass | MIT | |
| Review Pending PR Reviewsnrwl/nx | 29k | — | ~3.9k | Automated safety check: Pass | MIT | |
| Reviewthedaviddias/Front-End-Checklist | 74k | — | ~556 | Automated safety check: Pass | MIT | |
| ReviewClickHouse/ClickHouse | 50k | — | ~8k | Automated safety check: Notes | Apache-2.0 | |
| Docling Pull Request Reviewdocling-project/docling | 69k | — | ~1k | Automated safety check: Pass | MIT | |
| Pre-Landing PR Reviewgarrytan/gstack | 136k | — | ~19k | Automated safety check: Notes | MIT |
Similar skills
Review
thedaviddias/Front-End-Checklist
A skill your agent uses when applies to product pages, local business pages, recipes, apps, books, and any page that aggregates user reviews.
Review
ClickHouse/ClickHouse
Review a ClickHouse Pull Request for correctness, safety, performance, and compliance.
Docling Pull Request Review
docling-project/docling
Reviews or re-reviews a Docling pull request in fixed stages, with findings that can be reproduced and an explicit record of every check that was run.
Pre-Landing PR Review
garrytan/gstack
Reviews your diff against the base branch before merge, looking for SQL safety problems, LLM trust boundary violations, conditional side effects and other structural issues.
Code Review Checklist
shareAI-lab/learn-claude-code
Reviews code against a five-part checklist covering security, correctness, performance, maintainability and testing, and reports findings in a fixed format.
More from brycewang-stanford/Awesome-Journal-Skills
All 2,387 skills in this repoAaag Data Analysis
brycewang-stanford/Awesome-Journal-Skills
A skill your agent uses when running and reporting the analysis for an Annals of the American Association of Geographers manuscript — spatial statistics and modeling, remote-sensing accuracy, or…
Aaag Literature Positioning
brycewang-stanford/Awesome-Journal-Skills
A skill your agent uses when positioning an Annals of the American Association of Geographers manuscript in the literature — engaging geographic scholarship across the relevant area and the…
Aaag Rebuttal
brycewang-stanford/Awesome-Journal-Skills
A skill your agent uses when responding to an Annals of the American Association of Geographers decision letter (major/minor revision) — building a point-by-point response to the subject editor and…
Aaag Research Design
brycewang-stanford/Awesome-Journal-Skills
A skill your agent uses when defending the research design of an Annals of the American Association of Geographers manuscript — spatial/quantitative analysis and GIScience, remote-sensing and…
Aaag Review Process
brycewang-stanford/Awesome-Journal-Skills
A skill your agent uses when you need to understand how the Annals of the American Association of Geographers evaluates a manuscript — double-anonymous review routed through a subject editor by…
Aaag Submission
brycewang-stanford/Awesome-Journal-Skills
A skill your agent uses when running the final pre-submission preflight for the Annals of the American Association of Geographers via ScholarOne Manuscripts — area/article-type selection…
Questions about Dac Supplementary
What does Dac Supplementary do?
A skill your agent uses 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…. Dac Supplementary is an agent skill from brycewang-stanford/Awesome-Journal-Skills. 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.
When should I use Dac Supplementary?
Dac Supplementary fits situations like: given DACs tight 6+1 budget; its references-only seventh page; the double-blind constraint on any linked material; the absence of a formal reviewed-appendix.
How do I install Dac Supplementary in Claude Code?
Run `npx skills add brycewang-stanford/Awesome-Journal-Skills --skill dac-supplementary -a claude-code`. Or copy the skill folder (DAC-Skills/skills/dac-supplementary in brycewang-stanford/Awesome-Journal-Skills) into .claude/skills/dac-supplementary in your project. Claude Code loads it when a task matches its description.
How do I install Dac Supplementary in Codex?
Run `npx skills add brycewang-stanford/Awesome-Journal-Skills --skill dac-supplementary -a codex`. Or copy the skill folder (DAC-Skills/skills/dac-supplementary in brycewang-stanford/Awesome-Journal-Skills) into .agents/skills/dac-supplementary in your project. Codex loads it when a task matches its description.
Can I use Dac Supplementary in Cursor, Gemini CLI or GitHub Copilot?
Cursor, Gemini CLI, GitHub Copilot and OpenCode also load SKILL.md folders. With the skills CLI, run `npx skills add brycewang-stanford/Awesome-Journal-Skills --skill dac-supplementary -a cursor` (or -a gemini-cli, github-copilot or opencode for the others). To copy it by hand, put the folder in .cursor/skills/dac-supplementary, .gemini/skills/dac-supplementary, .github/skills/dac-supplementary and .opencode/skills/dac-supplementary in your project.
What does Dac Supplementary need to run?
SKILL.md names no scripts, command-line tools or credentials: Dac Supplementary is instructions for the agent only.
Does Dac Supplementary access the network?
SKILL.md contains no URLs. Any network use would come from the scripts or tools the agent runs. This is read from the text; nothing was executed.
Is Dac Supplementary safe to install?
Our automated static check of SKILL.md found no risky patterns, such as piping downloads into a shell, reading credential files or hidden Unicode. It is not a guarantee. Review the folder before installing.
What licence does Dac Supplementary use?
Dac Supplementary is published under the MIT licence (the repository's licence). It allows redistribution, so the full SKILL.md is shown on this page.
How many tokens does Dac Supplementary use?
About 1k tokens (SKILL.md is roughly 4.1k characters). Agents keep only the skill's name and description in context until a task matches; then they load SKILL.md in full.
What are the alternatives to Dac Supplementary?
Skills that share tags, products or a category with Dac Supplementary: Review Pending PR Reviews (nrwl/nx, 29k stars), Review (thedaviddias/Front-End-Checklist, 74k stars), Review (ClickHouse/ClickHouse, 50k stars) and Docling Pull Request Review (docling-project/docling, 69k stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.
Who maintains Dac Supplementary?
brycewang-stanford (a GitHub user) maintains it in brycewang-stanford/Awesome-Journal-Skills, which has 1,231 GitHub stars. The repository holds 2,387 skills in this directory. The repository was last updated on September 27, 2026.
Source: brycewang-stanford/Awesome-Journal-Skills on GitHub. Facts on this page come from the repository at the commit we read; the author's words are quoted as theirs.