Eda
brycewang-stanford/Auto-Empirical-Research-Skills
Comprehensive exploratory data analysis with publication-quality descriptive tables, correlation matrices, distribution plots, and assumption testing.
A skill your agent uses when deciding whether an EDA or chip-design project belongs at the ACM/IEEE Design Automation Conference (DAC) and, if so, in the double-blind archival Research Manuscript…
MITAuto-check passed
Install Dac Topic Selection
$ npx skills add brycewang-stanford/Awesome-Journal-Skills --skill dac-topic-selection -a claude-codeProject install by default; add -g for ~/.claude/skills/.
$ gh skill install brycewang-stanford/Awesome-Journal-Skills dac-topic-selection --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-topic-selection .claude/skills/dac-topic-selection && 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-topic-selection" agent skill from https://github.com/brycewang-stanford/Awesome-Journal-Skills/tree/main/DAC-Skills/skills/dac-topic-selection into .claude/skills/dac-topic-selection/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "dac-topic-selection", 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-topic-selectionType 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-topic-selection -a codexProject install goes to .agents/skills/; add -g for ~/.codex/skills/.
$ gh skill install brycewang-stanford/Awesome-Journal-Skills dac-topic-selection --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-topic-selection .agents/skills/dac-topic-selection && 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-topic-selection" agent skill from https://github.com/brycewang-stanford/Awesome-Journal-Skills/tree/main/DAC-Skills/skills/dac-topic-selection into .agents/skills/dac-topic-selection/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "dac-topic-selection", 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-topic-selection -a cursorProject install goes to .agents/skills/; add -g for ~/.cursor/skills/.
$ gh skill install brycewang-stanford/Awesome-Journal-Skills dac-topic-selection --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-topic-selection .cursor/skills/dac-topic-selection && 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-topic-selection" agent skill from https://github.com/brycewang-stanford/Awesome-Journal-Skills/tree/main/DAC-Skills/skills/dac-topic-selection into .cursor/skills/dac-topic-selection/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "dac-topic-selection", 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-topic-selection--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-topic-selection -a gemini-cliProject install goes to .agents/skills/; add -g for ~/.gemini/skills/.
$ gh skill install brycewang-stanford/Awesome-Journal-Skills dac-topic-selection --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-topic-selection .gemini/skills/dac-topic-selection && 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-topic-selection" agent skill from https://github.com/brycewang-stanford/Awesome-Journal-Skills/tree/main/DAC-Skills/skills/dac-topic-selection into .gemini/skills/dac-topic-selection/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "dac-topic-selection", 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-topic-selectionInstalls 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-topic-selection -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-topic-selection .github/skills/dac-topic-selection && 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-topic-selection" agent skill from https://github.com/brycewang-stanford/Awesome-Journal-Skills/tree/main/DAC-Skills/skills/dac-topic-selection into .github/skills/dac-topic-selection/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "dac-topic-selection", 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-topic-selection -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-topic-selection --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-topic-selection .opencode/skills/dac-topic-selection && 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-topic-selection" agent skill from https://github.com/brycewang-stanford/Awesome-Journal-Skills/tree/main/DAC-Skills/skills/dac-topic-selection into .opencode/skills/dac-topic-selection/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "dac-topic-selection", 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-topic-selection- GitHub stars
- 1.2k
- Token cost
- ~1.8k tokens
- SKILL.md length
- 751 words
- Files
- 1
- Skills in repo
- 2,387
- Repo updated
- First seen
- Licence
- MIT
At a glance
A skill your agent uses when deciding whether an EDA or chip-design project belongs at the ACM/IEEE Design Automation Conference (DAC) and, if so, in the double-blind archival Research Manuscript…
- Works in 2 steps: Is this a DAC contribution at all? DAC… → Research Manuscript or Engineering…
- Deciding whether an EDA
- SKILL.md covers The two questions, in order, Research Manuscript vs…, Sibling-venue routing (EDA and… and Contribution shapes DAC…, plus 3 more sections
- Instructions only: no scripts, shell commands, URLs or credentials in SKILL.md
What it does
Dac Topic Selection is an agent skill from brycewang-stanford/Awesome-Journal-Skills. Use when deciding whether an EDA or chip-design project belongs at the ACM/IEEE Design Automation Conference (DAC) and, if so, in the double-blind archival Research Manuscript track versus the industry-facing Engineering Track — or whether it should route to a sibling EDA venue (ICCAD, DATE, ASP-DAC) or a computer-architecture venue (ISCA/MICRO/HPCA), decided by contribution shape, QoR evidence maturity, and the November calendar.
Its SKILL.md is about 1.8k 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
- Deciding whether an EDA
- Chip-design project belongs at the ACM/IEEE Design Automation Conference (DAC) and
- In the double-blind archival Research Manuscript track versus the industry-facing Engineering Track —
- Whether it should route to a sibling EDA venue (ICCAD
Example prompts
- “/dac-topic-selection”
Workflow steps
2 steps, taken from the first numbered list in SKILL.md.
- Is this a DAC contribution at all? DAC rewards work that advances how chips and systems are
- Research Manuscript or Engineering Track? This is the DAC-specific fork. Route by whether the
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 Topic Selection loads about 1.8k tokens when it runs. Until then it costs about 114 tokens; SKILL.md has 751 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). 751 words, ~1,839 tokens.
Download SKILL.mdSave it as
.claude/skills/dac-topic-selection/SKILL.md (or your agent's skills folder).- name
- dac-topic-selection
- description
- Use when deciding whether an EDA or chip-design project belongs at the ACM/IEEE Design Automation Conference (DAC) and, if so, in the double-blind archival Research Manuscript track versus the industry-facing Engineering Track — or whether it should route to a sibling EDA venue (ICCAD, DATE, ASP-DAC) or a computer-architecture venue (ISCA/MICRO/HPCA), decided by contribution shape, QoR evidence maturity, and the November calendar.
DAC Topic Selection
Decide the venue and the track before drafting. DAC — the ACM/IEEE Design Automation Conference, "The Chips to Systems Conference" — is the premier forum for electronic design automation (EDA) and chip/system design. Its distinguishing structural fact, absent from the academic architecture venues, is that DAC hosts two peer-reviewed paper tracks with different review models: the double-blind, archival Research Manuscript track and the industry-facing Engineering Track. Picking the wrong track wastes a full cycle just as surely as picking the wrong conference.
The two questions, in order
- Is this a DAC contribution at all? DAC rewards work that advances how chips and systems are designed, automated, verified, or secured — a new placement/routing algorithm, a synthesis or verification technique, an ML-for-EDA method, a hardware-security defense, a design methodology with measured QoR impact. A pure computer-architecture result (a new microarchitecture, a cache policy) whose EDA/automation angle is incidental is respected and then routed to ISCA/MICRO/HPCA.
- Research Manuscript or Engineering Track? This is the DAC-specific fork. Route by whether the core deliverable is a novel, archival research contribution evaluated against baselines (Research) or a deployed industrial design/flow/methodology lesson from practice (Engineering).
Research Manuscript vs Engineering Track
| Signal in your project | Track | Why |
|---|---|---|
| Novel algorithm/technique with QoR gains vs prior art, generalizable | Research Manuscript | Double-blind, archival on ACM DL; judged on novelty + evidence |
| An empirical or ML-for-EDA study that changes what the field believes | Research Manuscript | Archival research contribution |
| A real tapeout/flow experience, tool-deployment lesson, or methodology from industry | Engineering Track | Practitioner audience; separate committee; presentation-first |
| Front-end design, back-end design, IP, or embedded SW/HW practice you want peers to learn from | Engineering Track | Its named scope; not required to out-QoR a baseline |
| Result too early/small for archival novelty but timely | Late Breaking Results | Short poster-style track, later deadline |
The trap for academics: submitting a solid-but-incremental flow improvement to the Research track where it dies on novelty, when the Engineering Track would have welcomed it as a practice lesson. The trap for practitioners: hiding a genuinely novel algorithm in the Engineering Track and losing the archival citation record.
Sibling-venue routing (EDA and architecture)
| Signal in your project | Better home | Why |
|---|---|---|
| Broad EDA/chip-design contribution, ready now, DAC deadline nearer | DAC Research | The flagship EDA venue; largest audience and industry reach |
| Deeper CAD-algorithm focus, or DAC deadline already passed | ICCAD | The other top EDA venue; complementary fall calendar |
| European community, design-and-test emphasis | DATE | Design, Automation and Test in Europe (distinct venue) |
| Asia-Pacific community, ASP-DAC's January cycle fits | ASP-DAC | Asia and South Pacific DAC (distinct venue) |
| Core is a microarchitecture / accelerator idea, EDA is incidental | ISCA / MICRO / HPCA | Computer-architecture flagships, different reviewer pool |
| Test/reliability depth | ITC / VTS | Test-community venues |
| Analog/RF circuit design as the contribution | ISSCC / CICC / VLSI | Circuits venues, not the EDA-algorithm venue |
Name-collision guard: ASP-DAC and DATE are not DAC; they have their own calls and deadlines. And "DAC" in a circuits paper often means digital-to-analog converter — a valid DAC research topic, not the conference.
Show full SKILL.md (259 more words)Show less
Contribution shapes DAC Research rewards
- A new EDA algorithm + tool + QoR evaluation — synthesis, placement, routing, timing, power, verification, or test, showing measured PPA (power/performance/area), wirelength, timing slack, or runtime gains over the strongest prior technique on standard benchmarks.
- ML for EDA — learning-based placement, routing, synthesis, timing/IR-drop prediction, or an agentic/foundation-model approach to a design task, with a fair non-ML or prior-ML baseline.
- Hardware security — a concrete attack or defense (side-channel, Trojan, IP protection, post-quantum primitive, supply-chain integrity) with a threat model and measured overhead.
- Design methodology / system-level — chiplet integration, 3D-IC, near-memory, or a cross-layer methodology whose payoff is demonstrated on a realistic design.
- Emerging technology — quantum EDA, in-memory/neuromorphic, or approximate computing, with an automation or design-quality contribution rather than a device-physics one.
The QoR-impact and model-swap tests
- QoR-impact test: state your gain in the field's own currency — "X% wirelength / Y% total negative slack / Z× runtime at equal quality." If you cannot phrase the contribution as a measured QoR delta or a new capability, the Research track will read it as incremental.
- Model-swap test (for ML-for-EDA): if you swap the learner for another, does the EDA lesson survive? If the paper is really about a model architecture with a toy EDA wrapper, it is an ML paper and routes to an ML venue; DAC wants the design-automation lesson.
Cheap reconnaissance before committing
[Scope] scan the last two DAC programs (dblp, ACM DL) for your subarea
-> 3+ recent papers = a reviewer pool exists; 0 = mismatch or ICCAD/DATE fit
[Benchmarks] does a standard suite exist for your problem (ISPD, EPFL, ISCAS/ITC, TAU, CircuitNet)?
-> reviewers expect it; a private-benchmark-only evaluation is a scored weakness
[Calendar] DAC manuscript deadline is ~November; ICCAD is later, ASP-DAC is January, DATE differs
-> route to the nearest honest fit rather than idling a cycleDecision procedure
[Is it EDA/chip-design?] automation/verification/security/methodology contribution? -> DAC candidate
[Track fork] novel + archival + baselined -> Research Manuscript
industrial practice/deployment lesson -> Engineering Track
timely but early -> Late Breaking Results
[Sibling check] CAD-algorithm depth & fall timing -> ICCAD; architecture core -> ISCA/MICRO/HPCA;
circuits core -> ISSCC/CICC
[Verdict] DAC Research / DAC Engineering / sibling venue, with a one-line QoR-framed reasonRun this before the writing skills; a wrong track or venue decision wastes every later step. When
the verdict is DAC Research, continue with dac-workflow for the November-anchored calendar and
dac-writing-style for the 6+1-page paper shape.
© 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-topic-selection of brycewang-stanford/Awesome-Journal-Skills.
Open the folder on GitHubat commit 932eb23
Compare with similar skills
Dac Topic Selection 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 Topic Selection this skillbrycewang-stanford/Awesome-Journal-Skills | 1.2k | — | ~1.8k | Automated safety check: Pass | MIT | |
| Edabrycewang-stanford/Auto-Empirical-Research-Skills | 4.5k | — | ~1.5k | Automated safety check: Pass | Custom licence | |
| TopicsZimoLiao/scholaraio | 576 | — | ~294 | Automated safety check: Pass | MIT | |
| Topic Modelingbrycewang-stanford/Auto-Empirical-Research-Skills | 4.5k | — | ~3.7k | Automated safety check: Pass | Custom licence | |
| Bestblogs Topicginobefun/BestBlogs | 4k | — | ~670 | Automated safety check: Pass | None | |
| Zsxq Topicitwanger/toBeBetterJavaer | 18k | — | ~564 | Automated safety check: Pass | None |
Similar skills
Topics
ZimoLiao/scholaraio
A skill your agent uses when the user asks about research themes, topic distribution, BERTopic clustering, topic overview, topic papers, topic merges, or HTML topic visualizations.
Topic Modeling
brycewang-stanford/Auto-Empirical-Research-Skills
Structural topic modeling: STM spec, topic count, coherence-exclusivity.
Bestblogs Topic
ginobefun/BestBlogs
A skill your agent uses when the user asks about a specific topic, subject area, or wants to explore curated topic pages on BestBlogs.
Zsxq Topic
itwanger/toBeBetterJavaer
知识星球主题管理：搜索主题、查看主题详情、发布帖子、编辑主题、发表评论、回复某条评论（楼中楼）、回答提问、删除主题；通过 api call 查看主题评论列表、设置精华、设置标签、查看自己提的问题与已回答记录。当用户需要查找内容、发帖、编辑主题、评论、回复评论、回答问题、删除主题、查看主题评论、查看自己的提问记录、或管理主题精华和标签时使用。
Pubmed Topic Recommend
aipoch/medical-research-skills
Generate ~5 actionable research topic recommendations by querying PubMed E-utilities; use when a user provides a research direction/constraints and needs evidence-backed topic ideas quickly.
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 Topic Selection
What does Dac Topic Selection do?
A skill your agent uses when deciding whether an EDA or chip-design project belongs at the ACM/IEEE Design Automation Conference (DAC) and, if so, in the double-blind archival Research Manuscript…. Dac Topic Selection is an agent skill from brycewang-stanford/Awesome-Journal-Skills. Use when deciding whether an EDA or chip-design project belongs at the ACM/IEEE Design Automation Conference (DAC) and, if so, in the double-blind archival Research Manuscript track versus the industry-facing Engineering Track — or whether it should route to a sibling EDA venue (ICCAD, DATE, ASP-DAC) or a computer-architecture venue (ISCA/MICRO/HPCA), decided by contribution shape, QoR evidence maturity, and the November calendar.
When should I use Dac Topic Selection?
Dac Topic Selection fits situations like: deciding whether an EDA; chip-design project belongs at the ACM/IEEE Design Automation Conference (DAC) and; in the double-blind archival Research Manuscript track versus the industry-facing Engineering Track —; whether it should route to a sibling EDA venue (ICCAD.
How do I install Dac Topic Selection in Claude Code?
Run `npx skills add brycewang-stanford/Awesome-Journal-Skills --skill dac-topic-selection -a claude-code`. Or copy the skill folder (DAC-Skills/skills/dac-topic-selection in brycewang-stanford/Awesome-Journal-Skills) into .claude/skills/dac-topic-selection in your project. Claude Code loads it when a task matches its description.
How do I install Dac Topic Selection in Codex?
Run `npx skills add brycewang-stanford/Awesome-Journal-Skills --skill dac-topic-selection -a codex`. Or copy the skill folder (DAC-Skills/skills/dac-topic-selection in brycewang-stanford/Awesome-Journal-Skills) into .agents/skills/dac-topic-selection in your project. Codex loads it when a task matches its description.
Can I use Dac Topic Selection 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-topic-selection -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-topic-selection, .gemini/skills/dac-topic-selection, .github/skills/dac-topic-selection and .opencode/skills/dac-topic-selection in your project.
What does Dac Topic Selection need to run?
SKILL.md names no scripts, command-line tools or credentials: Dac Topic Selection is instructions for the agent only.
Does Dac Topic Selection 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 Topic Selection 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 Topic Selection use?
Dac Topic Selection 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 Topic Selection use?
About 1.8k tokens (SKILL.md is roughly 7.4k 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 Topic Selection?
Skills that share tags, products or a category with Dac Topic Selection: Eda (brycewang-stanford/Auto-Empirical-Research-Skills, 4.5k stars), Topics (ZimoLiao/scholaraio, 576 stars), Topic Modeling (brycewang-stanford/Auto-Empirical-Research-Skills, 4.5k stars) and Bestblogs Topic (ginobefun/BestBlogs, 4k stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.
Who maintains Dac Topic Selection?
brycewang-stanford (a GitHub user) maintains it in brycewang-stanford/Awesome-Journal-Skills, which has 1,219 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.