Ieee Paper Reader
CloudWave818/ieee-skills
Read, decompose, and analyze IEEE-style papers using routed technical-reading workflows.
A skill your agent uses when writing or auditing the related-work and positioning of an ACM/IEEE Design Automation Conference (DAC) Research Manuscript, covering the EDA literature lanes…
Install Dac Related Work
$ npx skills add brycewang-stanford/Awesome-Journal-Skills --skill dac-related-work -a claude-codeProject install by default; add -g for ~/.claude/skills/.
$ gh skill install brycewang-stanford/Awesome-Journal-Skills dac-related-work --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-related-work .claude/skills/dac-related-work && 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-related-work" agent skill from https://github.com/brycewang-stanford/Awesome-Journal-Skills/tree/main/DAC-Skills/skills/dac-related-work into .claude/skills/dac-related-work/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "dac-related-work", 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-related-workType 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-related-work -a codexProject install goes to .agents/skills/; add -g for ~/.codex/skills/.
$ gh skill install brycewang-stanford/Awesome-Journal-Skills dac-related-work --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-related-work .agents/skills/dac-related-work && 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-related-work" agent skill from https://github.com/brycewang-stanford/Awesome-Journal-Skills/tree/main/DAC-Skills/skills/dac-related-work into .agents/skills/dac-related-work/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "dac-related-work", 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-related-work -a cursorProject install goes to .agents/skills/; add -g for ~/.cursor/skills/.
$ gh skill install brycewang-stanford/Awesome-Journal-Skills dac-related-work --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-related-work .cursor/skills/dac-related-work && 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-related-work" agent skill from https://github.com/brycewang-stanford/Awesome-Journal-Skills/tree/main/DAC-Skills/skills/dac-related-work into .cursor/skills/dac-related-work/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "dac-related-work", 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-related-work--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-related-work -a gemini-cliProject install goes to .agents/skills/; add -g for ~/.gemini/skills/.
$ gh skill install brycewang-stanford/Awesome-Journal-Skills dac-related-work --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-related-work .gemini/skills/dac-related-work && 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-related-work" agent skill from https://github.com/brycewang-stanford/Awesome-Journal-Skills/tree/main/DAC-Skills/skills/dac-related-work into .gemini/skills/dac-related-work/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "dac-related-work", 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-related-workInstalls 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-related-work -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-related-work .github/skills/dac-related-work && 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-related-work" agent skill from https://github.com/brycewang-stanford/Awesome-Journal-Skills/tree/main/DAC-Skills/skills/dac-related-work into .github/skills/dac-related-work/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "dac-related-work", 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-related-work -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-related-work --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-related-work .opencode/skills/dac-related-work && 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-related-work" agent skill from https://github.com/brycewang-stanford/Awesome-Journal-Skills/tree/main/DAC-Skills/skills/dac-related-work into .opencode/skills/dac-related-work/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "dac-related-work", 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-related-work- GitHub stars
- 1.2k
- Token cost
- ~1.2k tokens
- SKILL.md length
- 584 words
- Files
- 1
- Skills in repo
- 2,387
- Repo updated
- First seen
- Licence
- MIT
At a glance
A skill your agent uses when writing or auditing the related-work and positioning of an ACM/IEEE Design Automation Conference (DAC) Research Manuscript, covering the EDA literature lanes…
- Auditing the related-work and positioning of an ACM/IEEE Design Automation Conference (DAC) Research Manuscript
- SKILL.md covers The EDA literature lanes, Delta-first positioning, Name the strongest baseline as… and Honest benchmark and…, plus 3 more sections
- Instructions only: no scripts, shell commands, URLs or credentials in SKILL.md
- Covering the EDA literature lanes (DAC/ICCAD/DATE/ASP-DAC/TCAD/TODAES)
What it does
Dac Related Work is an agent skill from brycewang-stanford/Awesome-Journal-Skills. Use when writing or auditing the related-work and positioning of an ACM/IEEE Design Automation Conference (DAC) Research Manuscript, covering the EDA literature lanes (DAC/ICCAD/DATE/ASP-DAC/TCAD/TODAES), delta-first positioning against the strongest prior tool, honest benchmark-suite lineage, and third-person self-citation under double-blind review within the six-page budget.
Its SKILL.md is about 1.2k tokens, which your agent loads only when the skill is triggered. It is a single SKILL.md file with no bundled scripts.
It sits in Research & Science, covering Literature review, Positioning and messaging and Citation management. 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
- Auditing the related-work and positioning of an ACM/IEEE Design Automation Conference (DAC) Research Manuscript
- Covering the EDA literature lanes (DAC/ICCAD/DATE/ASP-DAC/TCAD/TODAES)
- Delta-first positioning against the strongest prior tool
- Honest benchmark-suite lineage
Example prompts
- “/dac-related-work”
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 Related Work loads about 1.2k tokens when it runs. Until then it costs about 99 tokens; SKILL.md has 584 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). 584 words, ~1,217 tokens.
Download SKILL.mdSave it as
.claude/skills/dac-related-work/SKILL.md (or your agent's skills folder).- name
- dac-related-work
- description
- Use when writing or auditing the related-work and positioning of an ACM/IEEE Design Automation Conference (DAC) Research Manuscript, covering the EDA literature lanes (DAC/ICCAD/DATE/ASP-DAC/TCAD/TODAES), delta-first positioning against the strongest prior tool, honest benchmark-suite lineage, and third-person self-citation under double-blind review within the six-page budget.
DAC Related Work
Position the paper against the EDA literature a DAC reviewer already knows. At six double-column pages, related work is not a survey — it is a delta statement: here is the best prior technique for this design task, here is precisely what it cannot do, here is what we add, measured in QoR. DAC reviewers are drawn from exactly the subcommittee whose prior work you are extending, so an incomplete or unfair positioning is caught immediately.
The EDA literature lanes
Cover the lanes your contribution touches; do not pad with distant ones:
- The top EDA venues — DAC, ICCAD, DATE, ASP-DAC — the conference record of your problem. A physical-design paper that cites no recent DAC/ICCAD placement work reads as disconnected.
- The EDA journals — IEEE TCAD (Transactions on CAD) and ACM TODAES — where the extended and most authoritative versions of techniques live; cite the journal version when it is the canonical reference.
- Adjacent communities when relevant — ISCA/MICRO/HPCA for architecture-facing work, ITC/VTS for test, ISSCC/CICC for circuits, and the ML venues (NeurIPS/ICML/ICLR) only when your ML-for-EDA method genuinely builds on a learning advance.
- The benchmark and tool lineage — the paper introducing the suite you evaluate on (ISPD contests, EPFL benchmarks, ISCAS/ITC circuits, TAU contest, CircuitNet) and the open flow you use (OpenROAD). Miscrediting a benchmark's origin is an easy, avoidable reviewer irritant.
Delta-first positioning
For each closely related technique, write the comparison in one move: what it does → its specific limitation → your advance.
- Weak: "Prior work has studied placement extensively [3-15]." (A citation dump; it positions nothing.)
- Strong: "The analytic placer [8] minimizes wirelength but degrades on macro-heavy designs because it treats macros as movable cells; we handle macros with [mechanism], cutting congestion by X% on the macro-dominated ISPD circuits."
The reviewer's implicit question is always "why is this not just [the obvious prior tool] plus tuning?" Answer it explicitly, early, and in QoR terms.
Show full SKILL.md (270 more words)Show less
Name the strongest baseline as the thing to beat
DAC papers are won and lost on the baseline. In related work, identify the current state of the art for your exact task and commit to comparing against it in the evaluation. Comparing only to an old or weak method — while a stronger, well-known tool exists and goes uncited — is the fastest way to a reject, because the assigned reviewer very likely authored or uses that stronger tool.
Honest benchmark and reproducibility lineage
- Credit the benchmark suite correctly and use its standard metrics; reporting a nonstandard metric on a standard suite invites "why not the usual QoR numbers?"
- If you use an open-source flow (OpenROAD, ABC, Yosys) or a public dataset (CircuitNet), cite it and state the version — this both positions you honestly and helps reproducibility.
- Distinguish contest results (ISPD/TAU/CAD-contest rankings) from peer-reviewed papers when you invoke them as prior art.
Third-person self-citation under double-blind
Cite your own prior papers as if written by others: "Prior work [7] proposed..." not "in our previous paper [7] we proposed...". A first-person self-citation de-anonymizes the submission. If your new paper is an extension of your own DAC/ICCAD paper, position the delta in the third person and let the camera-ready restore ownership.
Fitting related work into six pages
- No standalone two-column "Section 2: Related Work" wall if space is tight — weave positioning into the introduction and method, citing at the point of contrast.
- Group distant references (a whole subfield you merely acknowledge) into a single sentence with a bundled citation; spend individual sentences only on the techniques you actually beat or build on.
Output format
[Lanes covered] DAC/ICCAD/DATE/ASP-DAC + TCAD/TODAES + benchmark/tool lineage present?
[Strongest baseline] named and committed to in the evaluation? yes/no
[Delta statements] each close technique -> its limitation -> your QoR advance? yes/no
[Benchmark credit] suite + version + standard metrics correctly attributed? yes/no
[Anonymity] self-citations third-person? yes/no
[Space] positioning woven to fit the six-page budget? 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-related-work of brycewang-stanford/Awesome-Journal-Skills.
Open the folder on GitHubat commit 932eb23
Compare with similar skills
Dac Related Work 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 Related Work this skillbrycewang-stanford/Awesome-Journal-Skills | 1.2k | — | ~1.2k | Automated safety check: Pass | MIT | |
| Ieee Paper ReaderCloudWave818/ieee-skills | 359 | — | ~591 | Automated safety check: Pass | MIT | |
| Gec Literature Positioningfranklee16/academic-research-skills | 223 | 1 repos | ~855 | Automated safety check: Pass | None | |
| Jpe Literature Positioningfranklee16/academic-research-skills | 223 | 1 repos | ~1.1k | Automated safety check: Pass | None | |
| Systematic Review ScreenerImbad0202/academic-research-skills | 51k | — | ~8.4k | Automated safety check: Pass | Custom licence | |
| Literature Reviewneflibata-feng/MyArxiv-Agent | 126 | 20 repos | ~5.9k | Automated safety check: Notes | MIT |
Similar skills
Gec Literature Positioning
franklee16/academic-research-skills
A skill your agent uses when positioning a Global Environmental Change (GEC) manuscript against the relevant literatures.
Jpe Literature Positioning
franklee16/academic-research-skills
A skill your agent uses when writing or repairing the introduction and related-work framing for a Journal of Political Economy (JPE) manuscript — situating the contribution in the economics…
Systematic Review Screener
Imbad0202/academic-research-skills
Screens records for systematic, scoping and rapid reviews against fixed eligibility rules, using two blinded AI reviewers and a third adjudicator, with traceable PRISMA counts.
Literature Review
neflibata-feng/MyArxiv-Agent
Conduct comprehensive, systematic literature reviews using multiple academic databases (PubMed, arXiv, bioRxiv, Semantic Scholar, etc.).
Preprint Search on bioRxiv
LigphiDonk/Oh-my--paper
Searches bioRxiv life sciences preprints by keyword, author, date range or category with a Python script, returning JSON metadata and optional PDF downloads.
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…
Related
Categories
Questions about Dac Related Work
What does Dac Related Work do?
A skill your agent uses when writing or auditing the related-work and positioning of an ACM/IEEE Design Automation Conference (DAC) Research Manuscript, covering the EDA literature lanes…. Dac Related Work is an agent skill from brycewang-stanford/Awesome-Journal-Skills. Use when writing or auditing the related-work and positioning of an ACM/IEEE Design Automation Conference (DAC) Research Manuscript, covering the EDA literature lanes (DAC/ICCAD/DATE/ASP-DAC/TCAD/TODAES), delta-first positioning against the strongest prior tool, honest benchmark-suite lineage, and third-person self-citation under double-blind review within the six-page budget.
When should I use Dac Related Work?
Dac Related Work fits situations like: auditing the related-work and positioning of an ACM/IEEE Design Automation Conference (DAC) Research Manuscript; covering the EDA literature lanes (DAC/ICCAD/DATE/ASP-DAC/TCAD/TODAES); delta-first positioning against the strongest prior tool; honest benchmark-suite lineage.
How do I install Dac Related Work in Claude Code?
Run `npx skills add brycewang-stanford/Awesome-Journal-Skills --skill dac-related-work -a claude-code`. Or copy the skill folder (DAC-Skills/skills/dac-related-work in brycewang-stanford/Awesome-Journal-Skills) into .claude/skills/dac-related-work in your project. Claude Code loads it when a task matches its description.
How do I install Dac Related Work in Codex?
Run `npx skills add brycewang-stanford/Awesome-Journal-Skills --skill dac-related-work -a codex`. Or copy the skill folder (DAC-Skills/skills/dac-related-work in brycewang-stanford/Awesome-Journal-Skills) into .agents/skills/dac-related-work in your project. Codex loads it when a task matches its description.
Can I use Dac Related Work 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-related-work -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-related-work, .gemini/skills/dac-related-work, .github/skills/dac-related-work and .opencode/skills/dac-related-work in your project.
What does Dac Related Work need to run?
SKILL.md names no scripts, command-line tools or credentials: Dac Related Work is instructions for the agent only.
Does Dac Related Work 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 Related Work 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 Related Work use?
Dac Related Work 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 Related Work use?
About 1.2k tokens (SKILL.md is roughly 4.9k 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 Related Work?
Skills that share tags, products or a category with Dac Related Work: Ieee Paper Reader (CloudWave818/ieee-skills, 359 stars), Gec Literature Positioning (franklee16/academic-research-skills, 223 stars), Jpe Literature Positioning (franklee16/academic-research-skills, 223 stars) and Systematic Review Screener (Imbad0202/academic-research-skills, 51k stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.
Who maintains Dac Related Work?
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.