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 when preparing the final ACM/IEEE Design Automation Conference (DAC) Research-Manuscript camera-ready after acceptance, covering de-anonymization, restoring…
MITAuto-check passed
Install Dac Camera Ready
$ npx skills add brycewang-stanford/Awesome-Journal-Skills --skill dac-camera-ready -a claude-codeProject install by default; add -g for ~/.claude/skills/.
$ gh skill install brycewang-stanford/Awesome-Journal-Skills dac-camera-ready --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-camera-ready .claude/skills/dac-camera-ready && 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-camera-ready" agent skill from https://github.com/brycewang-stanford/Awesome-Journal-Skills/tree/main/DAC-Skills/skills/dac-camera-ready into .claude/skills/dac-camera-ready/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "dac-camera-ready", 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-camera-readyType 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-camera-ready -a codexProject install goes to .agents/skills/; add -g for ~/.codex/skills/.
$ gh skill install brycewang-stanford/Awesome-Journal-Skills dac-camera-ready --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-camera-ready .agents/skills/dac-camera-ready && 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-camera-ready" agent skill from https://github.com/brycewang-stanford/Awesome-Journal-Skills/tree/main/DAC-Skills/skills/dac-camera-ready into .agents/skills/dac-camera-ready/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "dac-camera-ready", 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-camera-ready -a cursorProject install goes to .agents/skills/; add -g for ~/.cursor/skills/.
$ gh skill install brycewang-stanford/Awesome-Journal-Skills dac-camera-ready --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-camera-ready .cursor/skills/dac-camera-ready && 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-camera-ready" agent skill from https://github.com/brycewang-stanford/Awesome-Journal-Skills/tree/main/DAC-Skills/skills/dac-camera-ready into .cursor/skills/dac-camera-ready/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "dac-camera-ready", 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-camera-ready--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-camera-ready -a gemini-cliProject install goes to .agents/skills/; add -g for ~/.gemini/skills/.
$ gh skill install brycewang-stanford/Awesome-Journal-Skills dac-camera-ready --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-camera-ready .gemini/skills/dac-camera-ready && 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-camera-ready" agent skill from https://github.com/brycewang-stanford/Awesome-Journal-Skills/tree/main/DAC-Skills/skills/dac-camera-ready into .gemini/skills/dac-camera-ready/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "dac-camera-ready", 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-camera-readyInstalls 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-camera-ready -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-camera-ready .github/skills/dac-camera-ready && 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-camera-ready" agent skill from https://github.com/brycewang-stanford/Awesome-Journal-Skills/tree/main/DAC-Skills/skills/dac-camera-ready into .github/skills/dac-camera-ready/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "dac-camera-ready", 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-camera-ready -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-camera-ready --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-camera-ready .opencode/skills/dac-camera-ready && 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-camera-ready" agent skill from https://github.com/brycewang-stanford/Awesome-Journal-Skills/tree/main/DAC-Skills/skills/dac-camera-ready into .opencode/skills/dac-camera-ready/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "dac-camera-ready", 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-camera-ready- GitHub stars
- 1.2k
- Token cost
- ~1.1k tokens
- SKILL.md length
- 440 words
- Files
- 1
- Skills in repo
- 2,387
- Repo updated
- First seen
- Licence
- MIT
At a glance
A skill your agent uses when preparing the final ACM/IEEE Design Automation Conference (DAC) Research-Manuscript camera-ready after acceptance, covering de-anonymization, restoring…
- Preparing the final ACM/IEEE Design Automation Conference (DAC) Research-Manuscript camera-ready after acceptance
- SKILL.md covers De-anonymize systematically, ACM copyright and rights stamp, The page budget still binds and ACM DL metadata and archival…, plus 3 more sections
- Instructions only: no scripts, shell commands, URLs or credentials in SKILL.md
- Covering de-anonymization
What it does
Dac Camera Ready is an agent skill from brycewang-stanford/Awesome-Journal-Skills. Use when preparing the final ACM/IEEE Design Automation Conference (DAC) Research-Manuscript camera-ready after acceptance, covering de-anonymization, restoring author/affiliation/acknowledgement/funding blocks, the ACM copyright form and rights stamp, the April proceedings deadline, ACM Digital Library metadata and archival-flow checks, and the still-fixed 6+1 page budget.
Its SKILL.md is about 1.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
- Preparing the final ACM/IEEE Design Automation Conference (DAC) Research-Manuscript camera-ready after acceptance
- Covering de-anonymization
- Restoring author/affiliation/acknowledgement/funding blocks
- The ACM copyright form and rights stamp
Example prompts
- “/dac-camera-ready”
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 Camera Ready loads about 1.1k tokens when it runs. Until then it costs about 98 tokens; SKILL.md has 440 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). 440 words, ~1,111 tokens.
Download SKILL.mdSave it as
.claude/skills/dac-camera-ready/SKILL.md (or your agent's skills folder).- name
- dac-camera-ready
- description
- Use when preparing the final ACM/IEEE Design Automation Conference (DAC) Research-Manuscript camera-ready after acceptance, covering de-anonymization, restoring author/affiliation/acknowledgement/funding blocks, the ACM copyright form and rights stamp, the April proceedings deadline, ACM Digital Library metadata and archival-flow checks, and the still-fixed 6+1 page budget.
DAC Camera-Ready
Use this after an accept decision to produce the archival version. The DAC camera-ready is an ACM Digital Library deliverable: ACM is the 2026 copyright holder, and the final manuscript plus copyright form are due at the April proceedings deadline (DAC 2026: ~14 April 2026, after the ~9 March notification). The camera-ready is a controlled edit of the accepted paper, not a rewrite — scope, claims, and QoR numbers are fixed by what was reviewed.
De-anonymize systematically
The review version was double-blind; the camera-ready restores identity. Do it as a checklist so nothing is missed and nothing new leaks in:
- Author block — full author list, affiliations, and contact, in the order and form you want cited for years.
- Self-citations — convert third-person references to your own prior work back to first person where natural ("in our earlier work [7]"), now that identity is public.
- Acknowledgements and funding — restore the acknowledgements and grant numbers you stripped for review; funders often require exact wording.
- Tool/repository names — restore the real tool name and any public artifact/OpenROAD-flow link you anonymized.
ACM copyright and rights stamp
- Complete the ACM copyright/e-rights form when it arrives; it returns the rights text and DOI stamp that must appear on the first page.
- Insert the rights block exactly as ACM specifies using the current ACM template; a missing or wrong rights stamp is a common production bounce.
- Confirm the conference/proceedings string and volume ACM assigns for the 63rd DAC so the citation and DOI resolve correctly on ACM DL.
Show full SKILL.md (190 more words)Show less
The page budget still binds
- The final version keeps the 6-page body + 1 references-only page budget; de-anonymization adds the author block and acknowledgements, which can push the body over — reclaim space editorially, do not shrink fonts or alter the template.
- The seventh page remains references only; acknowledgements belong in the body, not on the reference page.
- Re-check every figure is legible at final column width after any reflow.
ACM DL metadata and archival flow
- Title and author metadata must match the PDF exactly — mismatches break indexing and citation.
- Supply ACM CCS concepts and keywords if the template/portal requests them; they drive discoverability in the ACM DL.
- Verify references resolve (DOIs where available) — the archival version is what the field will cite.
- If your paper is a Best-Paper candidate or in a special session, confirm any additional presentation or final-version requirements the track adds.
Production checklist
[De-anon] authors/affiliations/acks/funding restored; tool + artifact links de-anonymized
[Rights] ACM copyright form submitted; rights text + DOI stamp on page 1
[Template] current ACM double-column; 6+1 budget still met after reflow
[Figures] legible at final size; grayscale/color-blind safe
[Metadata] title/authors match PDF; CCS + keywords supplied; references resolve
[Fonts] all fonts embedded; PDF passes the portal's readability check
[Deadline] final manuscript + copyright by the April proceedings cutoffReverify each cycle
- The exact proceedings/copyright deadline and which ACM template revision is required.
- Whether DAC 2026 also deposits to IEEE Xplore (待核实) in addition to ACM DL, which can add a second rights/metadata step.
- Any AI-authorship/disclosure statement required on the final version.
Output format
[Camera-ready status] ready / blocked
[De-anonymization] authors/acks/funding/tool links restored? yes/no
[Rights] ACM copyright form + first-page stamp done? yes/no
[Budget] 6-page body + references-only page still met? yes/no
[Metadata] ACM DL title/authors/CCS/keywords/DOIs correct? yes/no
[Fix queue] <ordered items before the April proceedings deadline>© 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-camera-ready of brycewang-stanford/Awesome-Journal-Skills.
Open the folder on GitHubat commit 932eb23
Compare with similar skills
Dac Camera Ready 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 Camera Ready this skillbrycewang-stanford/Awesome-Journal-Skills | 1.2k | — | ~1.1k | 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 | |
| Audit Preparationsickn33/agentic-awesome-skills | 47k | 1 repos | ~5.3k | Automated safety check: Pass | MIT | |
| Release PreparationCherryHQ/cherry-studio | 52k | — | ~4.3k | Automated safety check: Pass | AGPL-3.0 | |
| Prepare Paperclip PRpaperclipai/paperclip | 99k | — | ~954 | Automated safety check: Pass | MIT |
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.
Audit Preparation
sickn33/agentic-awesome-skills
Audit preparation register: required document, period covered, request and receipt dates, preparer and reviewer, auditor queries and adjustments.
Release Preparation
CherryHQ/cherry-studio
Prepares a Cherry Studio release by resolving the version, collecting commits, writing bilingual release notes, updating version files and creating a release branch.
Prepare Paperclip PR
paperclipai/paperclip
Prepare a Paperclip branch for PR with commits, template body, and checks.
Prepare MCP Integration
paperclipai/paperclip
Prepare MCP/vendor integrations through cited research, a content PR, exact-revision human approval, and one governed Paperclip connector PR per approved connection.
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 Camera Ready
What does Dac Camera Ready do?
A skill your agent uses when preparing the final ACM/IEEE Design Automation Conference (DAC) Research-Manuscript camera-ready after acceptance, covering de-anonymization, restoring…. Dac Camera Ready is an agent skill from brycewang-stanford/Awesome-Journal-Skills. Use when preparing the final ACM/IEEE Design Automation Conference (DAC) Research-Manuscript camera-ready after acceptance, covering de-anonymization, restoring author/affiliation/acknowledgement/funding blocks, the ACM copyright form and rights stamp, the April proceedings deadline, ACM Digital Library metadata and archival-flow checks, and the still-fixed 6+1 page budget.
When should I use Dac Camera Ready?
Dac Camera Ready fits situations like: preparing the final ACM/IEEE Design Automation Conference (DAC) Research-Manuscript camera-ready after acceptance; covering de-anonymization; restoring author/affiliation/acknowledgement/funding blocks; the ACM copyright form and rights stamp.
How do I install Dac Camera Ready in Claude Code?
Run `npx skills add brycewang-stanford/Awesome-Journal-Skills --skill dac-camera-ready -a claude-code`. Or copy the skill folder (DAC-Skills/skills/dac-camera-ready in brycewang-stanford/Awesome-Journal-Skills) into .claude/skills/dac-camera-ready in your project. Claude Code loads it when a task matches its description.
How do I install Dac Camera Ready in Codex?
Run `npx skills add brycewang-stanford/Awesome-Journal-Skills --skill dac-camera-ready -a codex`. Or copy the skill folder (DAC-Skills/skills/dac-camera-ready in brycewang-stanford/Awesome-Journal-Skills) into .agents/skills/dac-camera-ready in your project. Codex loads it when a task matches its description.
Can I use Dac Camera Ready 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-camera-ready -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-camera-ready, .gemini/skills/dac-camera-ready, .github/skills/dac-camera-ready and .opencode/skills/dac-camera-ready in your project.
What does Dac Camera Ready need to run?
SKILL.md names no scripts, command-line tools or credentials: Dac Camera Ready is instructions for the agent only.
Does Dac Camera Ready 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 Camera Ready 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 Camera Ready use?
Dac Camera Ready 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 Camera Ready use?
About 1.1k tokens (SKILL.md is roughly 4.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 Camera Ready?
Skills that share tags, products or a category with Dac Camera Ready: 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), Audit Preparation (sickn33/agentic-awesome-skills, 47k stars) and Release Preparation (CherryHQ/cherry-studio, 52k stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.
Who maintains Dac Camera Ready?
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.