Acm Ieee Joint Conference On Digital Libraries
franklee16/academic-research-skills
A skill your agent uses when targeting ACM/IEEE Joint Conference on Digital Libraries (JCDL) or deciding whether a computer-science manuscript fits this venue.
A skill your agent uses to plan a full ACM/IEEE Design Automation Conference (DAC) Research-Manuscript campaign backward from the mid-to-late-November manuscript deadline through the two-stage…
MITAuto-check passed
Install Dac Workflow
$ npx skills add brycewang-stanford/Awesome-Journal-Skills --skill dac-workflow -a claude-codeProject install by default; add -g for ~/.claude/skills/.
$ gh skill install brycewang-stanford/Awesome-Journal-Skills dac-workflow --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-workflow .claude/skills/dac-workflow && 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-workflow" agent skill from https://github.com/brycewang-stanford/Awesome-Journal-Skills/tree/main/DAC-Skills/skills/dac-workflow into .claude/skills/dac-workflow/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "dac-workflow", 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-workflowType 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-workflow -a codexProject install goes to .agents/skills/; add -g for ~/.codex/skills/.
$ gh skill install brycewang-stanford/Awesome-Journal-Skills dac-workflow --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-workflow .agents/skills/dac-workflow && 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-workflow" agent skill from https://github.com/brycewang-stanford/Awesome-Journal-Skills/tree/main/DAC-Skills/skills/dac-workflow into .agents/skills/dac-workflow/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "dac-workflow", 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-workflow -a cursorProject install goes to .agents/skills/; add -g for ~/.cursor/skills/.
$ gh skill install brycewang-stanford/Awesome-Journal-Skills dac-workflow --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-workflow .cursor/skills/dac-workflow && 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-workflow" agent skill from https://github.com/brycewang-stanford/Awesome-Journal-Skills/tree/main/DAC-Skills/skills/dac-workflow into .cursor/skills/dac-workflow/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "dac-workflow", 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-workflow--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-workflow -a gemini-cliProject install goes to .agents/skills/; add -g for ~/.gemini/skills/.
$ gh skill install brycewang-stanford/Awesome-Journal-Skills dac-workflow --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-workflow .gemini/skills/dac-workflow && 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-workflow" agent skill from https://github.com/brycewang-stanford/Awesome-Journal-Skills/tree/main/DAC-Skills/skills/dac-workflow into .gemini/skills/dac-workflow/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "dac-workflow", 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-workflowInstalls 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-workflow -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-workflow .github/skills/dac-workflow && 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-workflow" agent skill from https://github.com/brycewang-stanford/Awesome-Journal-Skills/tree/main/DAC-Skills/skills/dac-workflow into .github/skills/dac-workflow/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "dac-workflow", 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-workflow -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-workflow --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-workflow .opencode/skills/dac-workflow && 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-workflow" agent skill from https://github.com/brycewang-stanford/Awesome-Journal-Skills/tree/main/DAC-Skills/skills/dac-workflow into .opencode/skills/dac-workflow/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "dac-workflow", 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-workflow- GitHub stars
- 1.2k
- Token cost
- ~1.4k tokens
- SKILL.md length
- 428 words
- Files
- 1
- Skills in repo
- 2,387
- Repo updated
- First seen
- Licence
- MIT
At a glance
A skill your agent uses to plan a full ACM/IEEE Design Automation Conference (DAC) Research-Manuscript campaign backward from the mid-to-late-November manuscript deadline through the two-stage…
- The winter review
- SKILL.md covers The two-stage submission (do…, The DAC 2026 research calendar…, Side calendars (different… and Backward plan from the…, plus 3 more sections
- Instructions only: no scripts, shell commands, URLs or credentials in SKILL.md
- The March notification
What it does
Dac Workflow is an agent skill from brycewang-stanford/Awesome-Journal-Skills. Use to plan a full ACM/IEEE Design Automation Conference (DAC) Research-Manuscript campaign backward from the mid-to-late-November manuscript deadline through the two-stage abstract-then-manuscript submission on Softconf, the winter review, the March notification, the April camera-ready and copyright for the ACM Digital Library, and the July conference in Long Beach — with the Engineering-Track and Late-Breaking-Results side calendars.
Its SKILL.md is about 1.4k 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
- The winter review
- The March notification
- The April camera-ready and copyright for the ACM Digital Library
- The July conference in Long Beach — with the Engineering-Track and Late-Breaking-Results side calendars
Example prompts
- “/dac-workflow”
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 Workflow loads about 1.4k tokens when it runs. Until then it costs about 113 tokens; SKILL.md has 428 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). 428 words, ~1,366 tokens.
Download SKILL.mdSave it as
.claude/skills/dac-workflow/SKILL.md (or your agent's skills folder).- name
- dac-workflow
- description
- Use to plan a full ACM/IEEE Design Automation Conference (DAC) Research-Manuscript campaign backward from the mid-to-late-November manuscript deadline through the two-stage abstract-then-manuscript submission on Softconf, the winter review, the March notification, the April camera-ready and copyright for the ACM Digital Library, and the July conference in Long Beach — with the Engineering-Track and Late-Breaking-Results side calendars.
DAC Workflow
Run the DAC year backward from the deadline. DAC's Research-Manuscript cycle is a single annual
deadline in mid-to-late November (DAC 2026: manuscript ~19 November 2025) leading to a July
conference (DAC 2026: Long Beach, California, 26-29 July 2026). Unlike the two-cycle software
venues, DAC gives you one archival shot per year, so the calendar is unforgiving. Every date below
is a DAC 2026 snapshot read on 2026-07-09; reopen the live event pages first
(resources/official-source-map.md).
The two-stage submission (do not miss stage one)
DAC splits the research submission into two stages on the Softconf/START system (dac26):
- Stage 1 — Abstract. Register title, full abstract, and all co-authors roughly a week before the manuscript deadline. This stage seeds reviewer assignment and conflict detection; if you skip it, the system will not accept your PDF later.
- Stage 2 — Manuscript. Upload the anonymized 6+1-page PDF by the manuscript deadline. There is no grace period to fix a malformed or non-anonymous PDF after the cutoff.
Register with the real title and abstract, not a placeholder — the abstract drives which TPC members bid on and are assigned to your paper.
The DAC 2026 research calendar (snapshot — verify each cycle)
[~Nov 12, 2025] Abstract stage closes (title/abstract/co-authors on Softconf) 待核实 exact day
[Nov 19, 2025] Research Manuscript deadline (final anonymized 6+1 PDF) 待核实 exact day
[Nov 2025-Feb] Double-blind TPC review + program-committee discussion
[Feb 23, 2026] Accepted research-manuscript IDs published
[Mar 9, 2026] Accept / reject notifications
[Mar 23, 2026] Acceptance confirmation forms due
[Apr 14, 2026] Copyright form + final (proceedings) manuscript due — ACM DL camera-ready
[Jul 26-29, 2026] DAC 2026, Long Beach Convention Center — presentation + exhibitionWhether DAC 2026 runs an author rebuttal / response period between review and notification is 待核实 — DAC's research review has historically been TPC-driven without the ISCA/MICRO-style author response. Do not plan a rebuttal window into your calendar until the live cycle confirms one.
Show full SKILL.md (192 more words)Show less
Side calendars (different deadlines — do not conflate)
- Engineering Track: separate call, separate committee, later Call-for-Contributions deadline
(DAC 2026 extended to ~20 January 2026). Presentation-oriented; see
dac-topic-selection. - Late Breaking Results (LBR): short poster-style track on
softconf.com/dac26/lbr26, deadline in early 2026 (extended in past cycles into ~March). Good for a timely, early result that is not yet an archival Research Manuscript. - Special Sessions / Panels / Tutorials / Workshops: proposal-based, their own timelines.
Backward plan from the November manuscript deadline
[Deadline − 12 wk] Lock the contribution and the QoR claim; pick benchmark suites (ISPD/EPFL/
ISCAS/ITC/TAU/CircuitNet) and the baselines you must beat
[Deadline − 8 wk] Freeze the experimental harness; start the runs that take longest (full-flow
P&R, large-benchmark sweeps) — these cannot be compressed at the end
[Deadline − 4 wk] Full draft in the ACM double-column template; check the 6-page body budget early
[Deadline − 2 wk] Internal review; tighten to 6+1; build every figure at column width and legible
[Deadline − 1 wk] Complete the abstract stage on Softconf with the real title/abstract/co-authors
[Deadline − 3 day] Double-blind sweep on the PDF; re-run the headline numbers on a clean checkout
[Deadline − 1 day] Upload; re-download and read the PDF cold; confirm it is the intended fileBetween notification and camera-ready
- Accept: de-anonymize, apply the ACM template's final-version rules, complete metadata and the
copyright form, and hit the April proceedings deadline for the ACM Digital Library archival
version (
dac-camera-ready). - Reject: DAC has no formal appeal; reroute promptly — ICCAD (fall), DATE (Europe),
ASP-DAC (January), or a journal (TCAD/TODAES) — using
dac-topic-selection.
Standing reminders
- One archival deadline a year: a missed November means a full year, so calendar the abstract stage, not just the manuscript stage.
- The 6-page body budget is tight; plan the paper's argument to fit six double-column pages rather than writing long and cutting.
- Track choice (Research vs Engineering) is a workflow decision made before the deadline, not a fallback after rejection.
Output format
[Cycle target] DAC 20XX research manuscript / engineering track / LBR
[Abstract stage] locked by the earlier cutoff? yes/no
[Manuscript stage] on track for the November deadline? blockers?
[Longest runs] which experiments gate the deadline; started? yes/no
[Post-decision] camera-ready plan (ACM DL, April) or reroute target (ICCAD/DATE/ASP-DAC)© 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-workflow of brycewang-stanford/Awesome-Journal-Skills.
Open the folder on GitHubat commit 932eb23
Compare with similar skills
Dac Workflow 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 Workflow this skillbrycewang-stanford/Awesome-Journal-Skills | 1.2k | — | ~1.4k | Automated safety check: Pass | MIT | |
| Acm Ieee Joint Conference On Digital Librariesfranklee16/academic-research-skills | 223 | 1 repos | ~2k | Automated safety check: Pass | None | |
| Acm Ieee International Conference On Human Robot Interactionfranklee16/academic-research-skills | 223 | 1 repos | ~2k | Automated safety check: Pass | None | |
| Ieee Visualization Conferencefranklee16/academic-research-skills | 223 | 1 repos | ~2k | Automated safety check: Pass | None | |
| Acm International Conference On Multimediafranklee16/academic-research-skills | 223 | 1 repos | ~2k | Automated safety check: Pass | None | |
| Acm Conference On Recommender Systemsfranklee16/academic-research-skills | 223 | 1 repos | ~1.9k | Automated safety check: Pass | None |
Similar skills
Acm Ieee International Conference On Human Robot Interaction
franklee16/academic-research-skills
A skill your agent uses when targeting ACM/IEEE International Conference on Human-Robot Interaction (HRI) or deciding whether a computer-science manuscript fits this venue.
Ieee Visualization Conference
franklee16/academic-research-skills
A skill your agent uses when targeting IEEE Visualization Conference (IEEE VIS) or deciding whether a computer-science manuscript fits this venue.
Acm International Conference On Multimedia
franklee16/academic-research-skills
A skill your agent uses when targeting ACM International Conference on Multimedia (ACM MM) or deciding whether a computer-science manuscript fits this venue.
Acm Conference On Recommender Systems
franklee16/academic-research-skills
A skill your agent uses when targeting ACM Conference on Recommender Systems (RecSys) or deciding whether a computer-science manuscript fits this venue.
Ieee Conference On Virtual Reality And 3D User Interfaces
franklee16/academic-research-skills
A skill your agent uses when targeting IEEE Conference on Virtual Reality and 3D User Interfaces (IEEE VR) or deciding whether a computer-science manuscript fits this venue.
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 Workflow
What does Dac Workflow do?
A skill your agent uses to plan a full ACM/IEEE Design Automation Conference (DAC) Research-Manuscript campaign backward from the mid-to-late-November manuscript deadline through the two-stage…. Dac Workflow is an agent skill from brycewang-stanford/Awesome-Journal-Skills. Use to plan a full ACM/IEEE Design Automation Conference (DAC) Research-Manuscript campaign backward from the mid-to-late-November manuscript deadline through the two-stage abstract-then-manuscript submission on Softconf, the winter review, the March notification, the April camera-ready and copyright for the ACM Digital Library, and the July conference in Long Beach — with the Engineering-Track and Late-Breaking-Results side calendars.
When should I use Dac Workflow?
Dac Workflow fits situations like: the winter review; the March notification; the April camera-ready and copyright for the ACM Digital Library; the July conference in Long Beach — with the Engineering-Track and Late-Breaking-Results side calendars.
How do I install Dac Workflow in Claude Code?
Run `npx skills add brycewang-stanford/Awesome-Journal-Skills --skill dac-workflow -a claude-code`. Or copy the skill folder (DAC-Skills/skills/dac-workflow in brycewang-stanford/Awesome-Journal-Skills) into .claude/skills/dac-workflow in your project. Claude Code loads it when a task matches its description.
How do I install Dac Workflow in Codex?
Run `npx skills add brycewang-stanford/Awesome-Journal-Skills --skill dac-workflow -a codex`. Or copy the skill folder (DAC-Skills/skills/dac-workflow in brycewang-stanford/Awesome-Journal-Skills) into .agents/skills/dac-workflow in your project. Codex loads it when a task matches its description.
Can I use Dac Workflow 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-workflow -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-workflow, .gemini/skills/dac-workflow, .github/skills/dac-workflow and .opencode/skills/dac-workflow in your project.
What does Dac Workflow need to run?
SKILL.md names no scripts, command-line tools or credentials: Dac Workflow is instructions for the agent only.
Does Dac Workflow 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 Workflow 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 Workflow use?
Dac Workflow 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 Workflow use?
About 1.4k tokens (SKILL.md is roughly 5.5k 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 Workflow?
Skills that share tags, products or a category with Dac Workflow: Acm Ieee Joint Conference On Digital Libraries (franklee16/academic-research-skills, 223 stars), Acm Ieee International Conference On Human Robot Interaction (franklee16/academic-research-skills, 223 stars), Ieee Visualization Conference (franklee16/academic-research-skills, 223 stars) and Acm International Conference On Multimedia (franklee16/academic-research-skills, 223 stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.
Who maintains Dac Workflow?
brycewang-stanford (a GitHub user) maintains it in brycewang-stanford/Awesome-Journal-Skills, which has 1,228 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.