Agent skill

Dac Writing Style

by brycewang-stanford in brycewang-stanford/Awesome-Journal-Skills

A skill your agent uses when drafting or tightening the prose of an ACM/IEEE Design Automation Conference (DAC) Research Manuscript, covering the QoR-forward first-page arc, stating the…

MITAuto-check passedResearch & Science

Install Dac Writing Style

skills CLI

$ npx skills add brycewang-stanford/Awesome-Journal-Skills --skill dac-writing-style -a claude-code

Project install by default; add -g for ~/.claude/skills/.

GitHub CLI

$ gh skill install brycewang-stanford/Awesome-Journal-Skills dac-writing-style --agent claude-code

Project scope by default; add --scope user for a personal install. Needs GitHub CLI 2.90.0 or later (public preview).

Manual copy

$ 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-writing-style .claude/skills/dac-writing-style && rm -rf skills-src

Use ~/.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/

Paste into Claude Code

Install the "dac-writing-style" agent skill from https://github.com/brycewang-stanford/Awesome-Journal-Skills/tree/main/DAC-Skills/skills/dac-writing-style into .claude/skills/dac-writing-style/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "dac-writing-style", 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

$skill-installer install https://github.com/brycewang-stanford/Awesome-Journal-Skills/tree/main/DAC-Skills/skills/dac-writing-style

Type 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.

skills CLI

$ npx skills add brycewang-stanford/Awesome-Journal-Skills --skill dac-writing-style -a codex

Project install goes to .agents/skills/; add -g for ~/.codex/skills/.

GitHub CLI

$ gh skill install brycewang-stanford/Awesome-Journal-Skills dac-writing-style --agent codex

Project scope by default (.agents/skills/); add --scope user for a personal install.

Manual copy

$ 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-writing-style .agents/skills/dac-writing-style && rm -rf skills-src

Use ~/.agents/skills/ instead of .agents/skills for a personal install.

Codex skills documentation · loads skills from .agents/skills/

Paste into Codex

Install the "dac-writing-style" agent skill from https://github.com/brycewang-stanford/Awesome-Journal-Skills/tree/main/DAC-Skills/skills/dac-writing-style into .agents/skills/dac-writing-style/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "dac-writing-style", 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.

skills CLI

$ npx skills add brycewang-stanford/Awesome-Journal-Skills --skill dac-writing-style -a cursor

Project install goes to .agents/skills/; add -g for ~/.cursor/skills/.

GitHub CLI

$ gh skill install brycewang-stanford/Awesome-Journal-Skills dac-writing-style --agent cursor

Project scope by default (.agents/skills/); add --scope user for a personal install.

Manual copy

$ 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-writing-style .cursor/skills/dac-writing-style && rm -rf skills-src

Use ~/.cursor/skills/ instead of .cursor/skills for a personal install.

Cursor skills documentation · loads skills from .cursor/skills/, .agents/skills/, .claude/skills/, .codex/skills/

Paste into Cursor

Install the "dac-writing-style" agent skill from https://github.com/brycewang-stanford/Awesome-Journal-Skills/tree/main/DAC-Skills/skills/dac-writing-style into .cursor/skills/dac-writing-style/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "dac-writing-style", 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

$ gemini skills install https://github.com/brycewang-stanford/Awesome-Journal-Skills.git --path DAC-Skills/skills/dac-writing-style

--scope user (default) or --scope workspace; --path is the subfolder of the repo that holds the skill; --consent skips the security confirmation prompt.

skills CLI

$ npx skills add brycewang-stanford/Awesome-Journal-Skills --skill dac-writing-style -a gemini-cli

Project install goes to .agents/skills/; add -g for ~/.gemini/skills/.

GitHub CLI

$ gh skill install brycewang-stanford/Awesome-Journal-Skills dac-writing-style --agent gemini-cli

Project scope by default (.agents/skills/); add --scope user for a personal install.

Manual copy

$ 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-writing-style .gemini/skills/dac-writing-style && rm -rf skills-src

Use ~/.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/

Paste into Gemini CLI

Install the "dac-writing-style" agent skill from https://github.com/brycewang-stanford/Awesome-Journal-Skills/tree/main/DAC-Skills/skills/dac-writing-style into .gemini/skills/dac-writing-style/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "dac-writing-style", 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.

GitHub CLI

$ gh skill install brycewang-stanford/Awesome-Journal-Skills dac-writing-style

Installs 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).

skills CLI

$ npx skills add brycewang-stanford/Awesome-Journal-Skills --skill dac-writing-style -a github-copilot

Project install goes to .agents/skills/; add -g for ~/.copilot/skills/.

Manual copy

$ 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-writing-style .github/skills/dac-writing-style && rm -rf skills-src

Use ~/.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/

Paste into GitHub Copilot

Install the "dac-writing-style" agent skill from https://github.com/brycewang-stanford/Awesome-Journal-Skills/tree/main/DAC-Skills/skills/dac-writing-style into .github/skills/dac-writing-style/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "dac-writing-style", 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.

skills CLI

$ npx skills add brycewang-stanford/Awesome-Journal-Skills --skill dac-writing-style -a opencode

OpenCode documents no install command of its own. Project install goes to .agents/skills/; add -g for ~/.config/opencode/skills/.

GitHub CLI

$ gh skill install brycewang-stanford/Awesome-Journal-Skills dac-writing-style --agent opencode

Project scope by default (.agents/skills/); add --scope user for a personal install.

Manual copy

$ 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-writing-style .opencode/skills/dac-writing-style && rm -rf skills-src

Use ~/.config/opencode/skills/ instead of .opencode/skills for a personal install.

OpenCode skills documentation · loads skills from .opencode/skills/, .claude/skills/, .agents/skills/

Paste into OpenCode

Install the "dac-writing-style" agent skill from https://github.com/brycewang-stanford/Awesome-Journal-Skills/tree/main/DAC-Skills/skills/dac-writing-style into .opencode/skills/dac-writing-style/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "dac-writing-style", 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-writing-style
GitHub stars: 1.2k
Token cost: ~1.3k tokens
SKILL.md length: 658 words
Files: 1
Skills in repo: 2,387
Repo updated: Sep 27, 2026
First seen: Oct 7, 2026
Licence: MIT

At a glance

A skill your agent uses when drafting or tightening the prose of an ACM/IEEE Design Automation Conference (DAC) Research Manuscript, covering the QoR-forward first-page arc, stating the…

Works in 4 steps: The design problem — a concrete… → Why the current state is inadequate —… → The contribution as a measured delta —… → …
Tightening the prose of an ACM/IEEE Design Automation Conference (DAC) Research Manuscript
SKILL.md covers The DAC first-page arc, State the contribution as a…, Living in six double-column… and EDA figures that survive…, plus 3 more sections
Instructions only: no scripts, shell commands, URLs or credentials in SKILL.md

What it does

Dac Writing Style is an agent skill from brycewang-stanford/Awesome-Journal-Skills. Use when drafting or tightening the prose of an ACM/IEEE Design Automation Conference (DAC) Research Manuscript, covering the QoR-forward first-page arc, stating the design-automation contribution as a measured delta, fitting a complete argument into six double-column pages plus a references-only page, building column-width EDA figures, and third-person self-citation for double-blind review.

Its SKILL.md is about 1.3k tokens, which your agent loads only when the skill is triggered. It is a single SKILL.md file with no bundled scripts.

It sits in Research & Science, covering Brand voice and tone and Citation management. 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

Tightening the prose of an ACM/IEEE Design Automation Conference (DAC) Research Manuscript
Covering the QoR-forward first-page arc
Stating the design-automation contribution as a measured delta
Fitting a complete argument into six double-column pages plus a references-only page

Example prompts

“/dac-writing-style”

Workflow steps

4 steps, taken from the first numbered list in SKILL.md.

The design problem — a concrete EDA/chip-design task (placement, timing closure, functional
Why the current state is inadequate — the specific limitation of the best existing tool or
The contribution as a measured delta — the new mechanism and the headline QoR result
Why it generalizes — that the mechanism is not a one-benchmark trick.

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 Writing Style loads about 1.3k tokens when it runs. Until then it costs about 103 tokens; SKILL.md has 658 words of instructions outside code blocks.

Always · name and description, kept in context so the agent knows when to use it: ~103
When it runs · the whole SKILL.md, loaded when a task matches: ~1.3k

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). 658 words, ~1,333 tokens.

Download SKILL.mdSave it as .claude/skills/dac-writing-style/SKILL.md (or your agent's skills folder).

name: dac-writing-style
description: Use when drafting or tightening the prose of an ACM/IEEE Design Automation Conference (DAC) Research Manuscript, covering the QoR-forward first-page arc, stating the design-automation contribution as a measured delta, fitting a complete argument into six double-column pages plus a references-only page, building column-width EDA figures, and third-person self-citation for double-blind review.

DAC Writing Style

Use this while writing the body. DAC Research Manuscripts live inside a 6-page double-column budget (plus a references-only page), so the writing discipline is not "explain everything" but "prove one design-automation contribution, in the field's own QoR currency, in six dense pages." DAC reviewers are EDA experts under time pressure; they decide fast whether the paper has a real, measured advance.

The DAC first-page arc

Front-load the contribution. By the end of the first column-and-a-half a reviewer should know:

The design problem — a concrete EDA/chip-design task (placement, timing closure, functional verification, IR-drop prediction, IP protection) that the community recognizes.
Why the current state is inadequate — the specific limitation of the best existing tool or technique, ideally with a number (it does not scale past N cells, it leaves X% negative slack).
The contribution as a measured delta — the new mechanism and the headline QoR result: "we reduce total negative slack by X% at equal area with Y× lower runtime versus [state of the art] on [standard benchmark]."
Why it generalizes — that the mechanism is not a one-benchmark trick.

Do not open with "AI has transformed chip design." Open with the design problem and the number.

State the contribution as a QoR claim

The EDA community speaks in PPA (power, performance, area), plus wirelength, timing slack (WNS/TNS), routability/DRC, coverage, and runtime. A DAC contribution is strongest when phrased as a delta in those units against a named baseline:

Weak: "Our method improves quality and is efficient."
Strong: "On the ISPD placement benchmarks our router reduces total wirelength by X% and DRC violations by Y% while completing in Z× less runtime than [baseline]."

Every headline claim in the abstract and introduction should reappear as a per-benchmark row in a results table, not just an average.

Living in six double-column pages

The budget is the constraint that shapes the paper:

One contribution, deep. Six pages cannot carry three loosely related ideas; pick the strongest and develop it fully. A sprawling paper reads as thin at DAC.
Method before menagerie. Spend pages on the mechanism and the evaluation, not on a long taxonomy or a tutorial of standard EDA background the reviewers already know.
Tables over prose for results. A compact per-benchmark table communicates more per square inch than paragraphs; DAC reviewers read tables first.
Cut the roadmap. "Section 2 covers... Section 3 covers..." is dead weight at six pages; let section headings do that work.
References go on the seventh page only. Body content there is a desk-reject; plan the argument to end at page six.

Show full SKILL.md (228 more words)Show less

EDA figures that survive double-column at 9-10 pt

Design figures (floorplans, layouts, congestion/heatmaps, netlist graphs) must be legible at column width — roughly half of a US-letter page wide. Test every figure at final size.
Label axes with the real QoR units; a curve with no units persuades no one.
Prefer a clear flow diagram of the technique over a dense algorithm listing when space is scarce; move full pseudocode to the body only if it earns its space.
Color heatmaps must still read in grayscale and for color-blind reviewers.

Because review is double-blind, refer to your own prior work in the third person: not "in our earlier tool [7]" but "the prior technique [7]." Keep acknowledgements, funding, and grant numbers out of the review version entirely; they return in the camera-ready.

Common DAC prose failures

Failure	Why it costs you	Fix
QoR claim only as an average	Reviewers suspect a few benchmarks carry it	Per-benchmark table; report all circuits
Baseline unnamed or "a standard method"	Reads as evasive about the real state of the art	Name the strongest prior tool and its tuning
Background eats two pages	Leaves no room for the contribution	Assume EDA literacy; cut to the delta
Figures illegible at column width	Reviewer cannot verify the claim	Rebuild at final size, real units
First-person self-citation	De-anonymizes under double-blind	Third-person throughout

Output format

text

[First-page arc]  design problem -> inadequacy (with a number) -> QoR delta -> generality? present?
[QoR framing]     headline claim stated in PPA/wirelength/slack/runtime vs a named baseline? yes/no
[Budget]          body within 6 double-column pages? references-only 7th page clean?
[Figures]         legible at column width, real units, grayscale-safe? yes/no
[Anonymity]       self-citations third-person; acks/funding removed? yes/no
[Cut list]        <lowest-value paragraphs/figures to reclaim space>

Files

Just SKILL.md in DAC-Skills/skills/dac-writing-style of brycewang-stanford/Awesome-Journal-Skills.

Open the folder on GitHubat commit 932eb23

Compare with similar skills

Dac Writing Style 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.

Dac Writing Style compared with similar skills
Skill	Stars	Used in	Tokens	Auto-check	Licence	Repo updated
Dac Writing Style this skillbrycewang-stanford/Awesome-Journal-Skills	1.2k	—	~1.3k	Automated safety check: Pass	MIT	14 days ago
Artbull Writing Style And Citationfranklee16/academic-research-skills	223	1 repos	~848	Automated safety check: Pass	None	22 days ago
Io Writing Stylefranklee16/academic-research-skills	223	1 repos	~1.1k	Automated safety check: Pass	None	22 days ago
Jape Writing Stylefranklee16/academic-research-skills	223	1 repos	~598	Automated safety check: Pass	None	22 days ago
Scholar Polishjoshzyj/open-scholar-skill	168	—	~12k	Automated safety check: Pass	Custom licence	22 days ago
Research Paper Writerailabs-393/ai-labs-claude-skills	455	2 repos	~2.4k	Automated safety check: Pass	MIT	11 mo ago

Similar skills

Artbull Writing Style And Citation
franklee16/academic-research-skills
A skill your agent uses when polishing prose and formatting citations for an Art Bulletin article to The Chicago Manual of Style — endnotes (not author-date), full credit-line captions, and…
223 GitHub starsUsed in 1 repo~848 tokens
Research & ScienceAuto-check passed
Io Writing Style
franklee16/academic-research-skills
A skill your agent uses when drafting or polishing an International Organization (IO) manuscript so it reads for international-relations scholars across paradigms, fits the word caps (Research…
223 GitHub starsUsed in 1 repo~1.1k tokens
Research & ScienceAuto-check passed
Jape Writing Style
franklee16/academic-research-skills
A skill your agent uses when drafting or polishing prose for a Journal of Applied Econometrics (JAE) manuscript to its house conventions — a 100-word citation-free summary, up to six keywords…
223 GitHub starsUsed in 1 repo~598 tokens
Research & ScienceAuto-check passed
Scholar Polish
joshzyj/open-scholar-skill
Personalize and refine academic manuscript writing style by injecting distinctive authorial micro-patterns (tiny topos).
168 GitHub stars~12k tokensUpdated 22 days ago
Research & ScienceAuto-check passed
Research Paper Writer
ailabs-393/ai-labs-claude-skills
Creates formal academic research papers following IEEE/ACM formatting standards with proper structure, citations, and scholarly writing style.
455 GitHub starsUsed in 2 repos~2.4k tokens
Research & ScienceAuto-check passed
Inno Paper Writing
LigphiDonk/Oh-my--paper
Creates formal academic research papers following IEEE/ACM formatting standards with proper structure, citations, and scholarly writing style.
739 GitHub stars~2.9k tokensUpdated 5 mo ago
Research & ScienceAuto-check passed

More from brycewang-stanford/Awesome-Journal-Skills

All 2,387 skills in this repo

Aaag 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…
1.2k GitHub stars~1.3k tokensUpdated 14 days ago
Auto-check passed
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…
1.2k GitHub stars~1.3k tokensUpdated 14 days ago
Auto-check passed
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…
1.2k GitHub stars~1.4k tokensUpdated 14 days ago
Auto-check passed
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…
1.2k GitHub stars~1.4k tokensUpdated 14 days ago
Auto-check passed
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…
1.2k GitHub stars~1.3k tokensUpdated 14 days ago
Auto-check passed
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…
1.2k GitHub stars~1.6k tokensUpdated 14 days ago
Auto-check passed

Questions about Dac Writing Style

What does Dac Writing Style do?

A skill your agent uses when drafting or tightening the prose of an ACM/IEEE Design Automation Conference (DAC) Research Manuscript, covering the QoR-forward first-page arc, stating the…. Dac Writing Style is an agent skill from brycewang-stanford/Awesome-Journal-Skills. Use when drafting or tightening the prose of an ACM/IEEE Design Automation Conference (DAC) Research Manuscript, covering the QoR-forward first-page arc, stating the design-automation contribution as a measured delta, fitting a complete argument into six double-column pages plus a references-only page, building column-width EDA figures, and third-person self-citation for double-blind review.

When should I use Dac Writing Style?

Dac Writing Style fits situations like: tightening the prose of an ACM/IEEE Design Automation Conference (DAC) Research Manuscript; covering the QoR-forward first-page arc; stating the design-automation contribution as a measured delta; fitting a complete argument into six double-column pages plus a references-only page.

How do I install Dac Writing Style in Claude Code?

Run `npx skills add brycewang-stanford/Awesome-Journal-Skills --skill dac-writing-style -a claude-code`. Or copy the skill folder (DAC-Skills/skills/dac-writing-style in brycewang-stanford/Awesome-Journal-Skills) into .claude/skills/dac-writing-style in your project. Claude Code loads it when a task matches its description.

How do I install Dac Writing Style in Codex?

Run `npx skills add brycewang-stanford/Awesome-Journal-Skills --skill dac-writing-style -a codex`. Or copy the skill folder (DAC-Skills/skills/dac-writing-style in brycewang-stanford/Awesome-Journal-Skills) into .agents/skills/dac-writing-style in your project. Codex loads it when a task matches its description.

Can I use Dac Writing Style 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-writing-style -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-writing-style, .gemini/skills/dac-writing-style, .github/skills/dac-writing-style and .opencode/skills/dac-writing-style in your project.

What does Dac Writing Style need to run?

SKILL.md names no scripts, command-line tools or credentials: Dac Writing Style is instructions for the agent only.

Does Dac Writing Style 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 Writing Style 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 Writing Style use?

Dac Writing Style 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 Writing Style use?

About 1.3k tokens (SKILL.md is roughly 5.3k 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 Writing Style?

Skills that share tags, products or a category with Dac Writing Style: Artbull Writing Style And Citation (franklee16/academic-research-skills, 223 stars), Io Writing Style (franklee16/academic-research-skills, 223 stars), Jape Writing Style (franklee16/academic-research-skills, 223 stars) and Scholar Polish (joshzyj/open-scholar-skill, 168 stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.

Who maintains Dac Writing Style?

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.

Install Dac Writing Style

Facts

At a glance

What it does

When your agent uses it

Example prompts

Workflow steps

What it can do on your machine

Tool permissions

Runs code

Network

Credentials

Context cost

Safety

SKILL.md

DAC Writing Style

The DAC first-page arc

State the contribution as a QoR claim

Living in six double-column pages

EDA figures that survive double-column at 9-10 pt

Third-person self-citation (double-blind)

Common DAC prose failures

Output format

Files

Compare with similar skills

Similar skills

More from brycewang-stanford/Awesome-Journal-Skills

Related

Questions about Dac Writing Style