Production Audit
affaan-m/ECC
Local-evidence production readiness audit for shipped apps, pre-launch reviews, post-merge checks, and "what breaks in prod?" questions without sending repo data to an external audit service.
A skill your agent uses when auditing an ACM/IEEE Design Automation Conference (DAC) Research-Manuscript submission for Softconf readiness, covering the two-stage abstract-then-manuscript deadline…
MITAuto-check passed
Install Dac Submission
$ npx skills add brycewang-stanford/Awesome-Journal-Skills --skill dac-submission -a claude-codeProject install by default; add -g for ~/.claude/skills/.
$ gh skill install brycewang-stanford/Awesome-Journal-Skills dac-submission --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-submission .claude/skills/dac-submission && 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-submission" agent skill from https://github.com/brycewang-stanford/Awesome-Journal-Skills/tree/main/DAC-Skills/skills/dac-submission into .claude/skills/dac-submission/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "dac-submission", 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-submissionType 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-submission -a codexProject install goes to .agents/skills/; add -g for ~/.codex/skills/.
$ gh skill install brycewang-stanford/Awesome-Journal-Skills dac-submission --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-submission .agents/skills/dac-submission && 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-submission" agent skill from https://github.com/brycewang-stanford/Awesome-Journal-Skills/tree/main/DAC-Skills/skills/dac-submission into .agents/skills/dac-submission/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "dac-submission", 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-submission -a cursorProject install goes to .agents/skills/; add -g for ~/.cursor/skills/.
$ gh skill install brycewang-stanford/Awesome-Journal-Skills dac-submission --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-submission .cursor/skills/dac-submission && 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-submission" agent skill from https://github.com/brycewang-stanford/Awesome-Journal-Skills/tree/main/DAC-Skills/skills/dac-submission into .cursor/skills/dac-submission/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "dac-submission", 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-submission--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-submission -a gemini-cliProject install goes to .agents/skills/; add -g for ~/.gemini/skills/.
$ gh skill install brycewang-stanford/Awesome-Journal-Skills dac-submission --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-submission .gemini/skills/dac-submission && 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-submission" agent skill from https://github.com/brycewang-stanford/Awesome-Journal-Skills/tree/main/DAC-Skills/skills/dac-submission into .gemini/skills/dac-submission/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "dac-submission", 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-submissionInstalls 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-submission -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-submission .github/skills/dac-submission && 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-submission" agent skill from https://github.com/brycewang-stanford/Awesome-Journal-Skills/tree/main/DAC-Skills/skills/dac-submission into .github/skills/dac-submission/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "dac-submission", 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-submission -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-submission --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-submission .opencode/skills/dac-submission && 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-submission" agent skill from https://github.com/brycewang-stanford/Awesome-Journal-Skills/tree/main/DAC-Skills/skills/dac-submission into .opencode/skills/dac-submission/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "dac-submission", 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-submission- GitHub stars
- 1.2k
- Token cost
- ~1.6k tokens
- SKILL.md length
- 727 words
- Files
- 1
- Skills in repo
- 2,387
- Repo updated
- First seen
- Licence
- MIT
At a glance
A skill your agent uses when auditing an ACM/IEEE Design Automation Conference (DAC) Research-Manuscript submission for Softconf readiness, covering the two-stage abstract-then-manuscript deadline…
- Works in 6 steps: Freeze the contribution and the QoR… → Complete the abstract stage… → Compile to the ACM double-column… → …
- Auditing an ACM/IEEE Design Automation Conference (DAC) Research-Manuscript submission for Softconf readiness
- SKILL.md covers The two-stage deadline, Format and page budget (the…, Double-blind anonymization sweep and TPC conflict-of-interest…, plus 4 more sections
- Calls pdftotext
What it does
Dac Submission is an agent skill from brycewang-stanford/Awesome-Journal-Skills. 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.
Its SKILL.md is about 1.6k 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
- 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
Example prompts
- “/dac-submission”
Workflow steps
6 steps, taken from the first numbered list in SKILL.md.
- Freeze the contribution and the QoR numbers; the argument cannot churn in the last week.
- Complete the abstract stage (title/abstract/all co-authors) well before its cutoff.
- Compile to the ACM double-column template and confirm the 6-page body / 1-page references
- Run the double-blind sweep on the final PDF — metadata, self-citations, tool names, acks.
- Enter TPC conflicts and topic areas in Softconf a day early; late conflicts are a classic
- Upload, re-download, and read the PDF cold to confirm it is the file you meant.
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
Shell commands in SKILL.md call:
pdftotext
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 Submission loads about 1.6k tokens when it runs. Until then it costs about 103 tokens; SKILL.md has 727 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). 727 words, ~1,636 tokens.
Download SKILL.mdSave it as
.claude/skills/dac-submission/SKILL.md (or your agent's skills folder).- name
- dac-submission
- description
- 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.
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 template, double-column, 9 or 10-pt font, single PDF. This is DAC's current requirement; ACM is the 2026 copyright holder and the paper is archived on ACM DL.
- Page budget: the manuscript is within 6 pages excluding references, plus one additional page for references only. This is the "6+1" budget — six double-column pages carry the entire technical argument, figures, and tables.
- The extra page is references-only. Putting any non-reference content (an extra figure, a paragraph of text, an appendix) on that seventh page is grounds for desk rejection. Do not try to smuggle body content there.
- Margins, columns, and font are fixed by the template; recover space by editorial compression and tighter figures, never by template tampering.
Double-blind anonymization sweep
DAC review is double-blind: author names and affiliations must not appear anywhere on the manuscript. Because EDA papers lean on tools, benchmark runs, and vendor flows, the leak surface is wide:
# 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' | headDAC-specific leaks to hunt for:
- Self-citations in the first person — "in our prior work [7] we..." de-anonymizes. Cite your own prior papers in the third person ("Prior work [7] showed...").
- A tool named after your lab or a public repo that discloses authorship — rename or anonymize the tool for review.
- A commercial-flow fingerprint (a vendor tool version string, a proprietary PDK/library name under NDA) that both leaks identity and can raise a confidentiality flag.
- Acknowledgements, funding, or grant numbers left in the review version — remove them; they return in the camera-ready.
- Benchmark or cluster paths (
/home/username/..., an internal server name) in a figure or log excerpt.
Show full SKILL.md (301 more words)Show less
TPC conflict-of-interest declaration
DAC asks authors to declare conflicts of interest with Technical Program Committee members at submission and assumes none beyond those declared. Declare every co-author's advisor/advisee, recent (typically last-few-years) collaborators and co-authors, same-institution members, and close family — under-declaring a real COI is an integrity problem, not a shortcut to a friendlier reviewer.
Desk-risk triage
| Finding at audit time | Severity | Real fix |
|---|---|---|
| Body over 6 pages, or content on the references-only page | Named desk-reject ground | Cut/compress; the 7th page is references only |
| Template altered (columns, shrunk font, margins) | Desk-reject-grade | Recompile clean ACM double-column; recover space editorially |
| Author identity leak (PDF metadata, first-person self-cite, tool name) | Anonymity violation | Re-anonymize; scrub metadata; third-person self-citations |
| Abstract stage not completed by the earlier date | No submission slot exists | Nothing fixes this post-cutoff — calendar it now |
| No standard benchmark / private-data-only evaluation | Scored weakness | Add a recognized suite (ISPD/EPFL/ISCAS/ITC/TAU) or justify explicitly |
| Same result under review at ICCAD/DATE/ASP-DAC | Dual-submission exposure | Withdraw one; verify DAC's concurrent-submission wording |
Final-week order of operations
- Freeze the contribution and the QoR numbers; the argument cannot churn in the last week.
- Complete the abstract stage (title/abstract/all co-authors) well before its cutoff.
- Compile to the ACM double-column template and confirm the 6-page body / 1-page references split on the final PDF.
- Run the double-blind sweep on the final PDF — metadata, self-citations, tool names, acks.
- Enter TPC conflicts and topic areas in Softconf a day early; late conflicts are a classic midnight failure.
- Upload, re-download, and read the PDF cold to confirm it is the file you meant.
Reverify each cycle
- Exact abstract and manuscript deadlines and time-zone/AoE convention.
- Page budget and ACM template revision (DAC 2026: 6+1, double-column).
- Whether a rebuttal/response period exists (待核实 for DAC 2026).
- Concurrent-submission wording versus ICCAD/DATE/ASP-DAC, and any generative-AI disclosure rule.
Output format
[DAC submission status] ready / blocked / needs work
[Abstract stage] title/abstract/all co-authors locked by the earlier deadline? yes/no
[Format] body pages used / references-only page clean? ACM double-column compliance
[Anonymity] clean / leaks: <where>
[Evidence] standard benchmark suite present? baselines named?
[COI] TPC conflicts declared for every co-author? yes/no
[Fix queue] <ordered, with owners and dates before the November cutoff>© 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-submission of brycewang-stanford/Awesome-Journal-Skills.
Open the folder on GitHubat commit 932eb23
Compare with similar skills
Dac Submission 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 Submission this skillbrycewang-stanford/Awesome-Journal-Skills | 1.2k | — | ~1.6k | Automated safety check: Pass | MIT | |
| Production Auditaffaan-m/ECC | 277k | 1 repos | ~1.9k | Automated safety check: Pass | MIT | |
| Acm Ieee Joint Conference On Digital Librariesfranklee16/academic-research-skills | 223 | 1 repos | ~2k | Automated safety check: Pass | None | |
| Aims Auditalirezarezvani/claude-skills | 28k | — | ~1.3k | Automated safety check: Pass | MIT | |
| Acm Ieee International Conference On Human Robot Interactionfranklee16/academic-research-skills | 223 | 1 repos | ~2k | Automated safety check: Pass | None | |
| Geo Auditsickn33/agentic-awesome-skills | 47k | 1 repos | ~3.4k | Automated safety check: Notes | MIT |
Similar skills
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.
Aims Audit
alirezarezvani/claude-skills
/cs:aims-audit <scope — ISO/IEC 42001 AIMS internal-audit 6-question forcing interrogation.
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.
Geo Audit
sickn33/agentic-awesome-skills
Full website GEO+SEO audit with parallel subagent delegation.
OmniRoute Audit and Policy CLI
diegosouzapw/OmniRoute
Command reference for omniroute's audit, logs, policy and telemetry commands: search and export audit trails, manage access policies and review request history for compliance work.
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 Submission
What does Dac Submission do?
A skill your agent uses when auditing an ACM/IEEE Design Automation Conference (DAC) Research-Manuscript submission for Softconf readiness, covering the two-stage abstract-then-manuscript deadline…. Dac Submission is an agent skill from brycewang-stanford/Awesome-Journal-Skills. 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.
When should I use Dac Submission?
Dac Submission fits situations like: 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.
How do I install Dac Submission in Claude Code?
Run `npx skills add brycewang-stanford/Awesome-Journal-Skills --skill dac-submission -a claude-code`. Or copy the skill folder (DAC-Skills/skills/dac-submission in brycewang-stanford/Awesome-Journal-Skills) into .claude/skills/dac-submission in your project. Claude Code loads it when a task matches its description.
How do I install Dac Submission in Codex?
Run `npx skills add brycewang-stanford/Awesome-Journal-Skills --skill dac-submission -a codex`. Or copy the skill folder (DAC-Skills/skills/dac-submission in brycewang-stanford/Awesome-Journal-Skills) into .agents/skills/dac-submission in your project. Codex loads it when a task matches its description.
Can I use Dac Submission 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-submission -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-submission, .gemini/skills/dac-submission, .github/skills/dac-submission and .opencode/skills/dac-submission in your project.
What does Dac Submission need to run?
Going by SKILL.md and its folder, Dac Submission needs the command-line tools its instructions call (pdftotext).
Does Dac Submission 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 Submission 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 Submission use?
Dac Submission 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 Submission use?
About 1.6k tokens (SKILL.md is roughly 6.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 Submission?
Skills that share tags, products or a category with Dac Submission: Production Audit (affaan-m/ECC, 277k stars), Acm Ieee Joint Conference On Digital Libraries (franklee16/academic-research-skills, 223 stars), Aims Audit (alirezarezvani/claude-skills, 28k stars) and Acm Ieee International Conference On Human Robot Interaction (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 Submission?
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.