dac-submission
Use when auditing an ACM/IEEE Design Automation Conference (DAC) Research-Manuscript submission for Softconf readiness, covering the two-stage abstract-then-manuscript deadline, the 6+1-page ACM double-column page budget with its references-only last page, the double-blind anonymization sweep, TPC conflict-of-interest declaration, and desk-reject triage before the mid-to-late-November cutoff.
Profile →npx skills add brycewang-stanford/Awesome-Journal-Skills --skill dac-submission --agent claude-code
Same command for any agent — swap --agent for codex, cursor, copilot.
Weekly change comes from our own snapshots, not the repository page — it measures attention, not adoption.
# DAC Submission Run this audit before uploading to the DAC Softconf/START site. DAC Research Manuscripts are **double-blind, archival** papers published on the **ACM Digital Library**, judged on novelty and measured design-quality impact. Every number below was read from the DAC 2026 Call and Research Manuscripts Guidelines on 2026-07-09 via search renderings of the `dac.com/2026` pages (see `resources/official-source-map.md`); treat them as a one-cycle snapshot and reopen the live call first. ## The two-stage deadline DAC separates **abstract submission** from **manuscript submission**, and both matter: - **Abstract stage** (~one week early): title, full abstract, and **every co-author** go into Softconf. This seeds TPC bidding and conflict detection. Miss it and the system will not take your PDF. - **Manuscript stage** (DAC 2026: ~19 November 2025): the anonymized 6+1-page PDF. There is **no grace period** to repair a malformed or de-anonymized file after the cutoff. Register the *real* title and abstract — a placeholder abstract worsens your reviewer match, which is the single largest lever you control (see `dac-review-process`). ## Format and page budget (the 6+1 rule) - **ACM
- The two-stage deadline
- Format and page budget (the 6+1 rule)
- Double-blind anonymization sweep
- TPC conflict-of-interest declaration
- Desk-risk triage
- Final-week order of operations
- Reverify each cycle
- Output format
Mechanical pass on the submission PDF pdfinfo paper.pdf | grep -Ei 'author|creator|producer' pdftotext paper.pdf - | grep -nEi 'university|institute|@[a-z0-9.]+\.edu|acknowledg|funded|grant' | head pdftotext paper.pdf - | grep -nEi 'our (tool|lab|group|flow)|github\.com/[a-z0-9-]+|gitlab' | head
What does the dac-submission skill do?
Use when auditing an ACM/IEEE Design Automation Conference (DAC) Research-Manuscript submission for Softconf readiness, covering the two-stage abstract-then-manuscript deadline, the 6+1-page ACM double-column page budget with its references-only last page, the double-blind anonymization sweep, TPC conflict-of-interest declaration, and desk-reject triage before the mid-to-late-November cutoff.
How do I install it?
Run `npx skills add brycewang-stanford/Awesome-Journal-Skills --skill dac-submission --agent claude-code` — it drops the skill into your project so the agent can pick it up. Swap the --agent value for codex, cursor or copilot if you use one of those.
Where does this skill come from?
From brycewang-stanford/Awesome-Journal-Skills, a repository with 909 stars. We read it straight from the repository tree rather than a submitted listing, so what you see here is what is actually published.
Is a popular skill a good skill?
Not necessarily. Stars measure attention, not adoption — a repository can trend for a week and be abandoned. That is why we show the weekly change from our own snapshots next to the total, instead of a single flattering number.