Academic Venue Research
joshua-zyy/academic-paper-writer
Research target venue requirements and writing style for CS/AI/ML papers.
A skill your agent uses when shaping the prose and structure of an ASE (IEEE/ACM Automated Software Engineering) research paper, covering the automation-first first-page arc, stating the automated…
Install Ase Writing Style
$ npx skills add brycewang-stanford/Awesome-Journal-Skills --skill ase-writing-style -a claude-codeProject install by default; add -g for ~/.claude/skills/.
$ gh skill install brycewang-stanford/Awesome-Journal-Skills ase-writing-style --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/ASE-Skills/skills/ase-writing-style .claude/skills/ase-writing-style && 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 "ase-writing-style" agent skill from https://github.com/brycewang-stanford/Awesome-Journal-Skills/tree/main/ASE-Skills/skills/ase-writing-style into .claude/skills/ase-writing-style/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "ase-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 install https://github.com/brycewang-stanford/Awesome-Journal-Skills/tree/main/ASE-Skills/skills/ase-writing-styleType 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 ase-writing-style -a codexProject install goes to .agents/skills/; add -g for ~/.codex/skills/.
$ gh skill install brycewang-stanford/Awesome-Journal-Skills ase-writing-style --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/ASE-Skills/skills/ase-writing-style .agents/skills/ase-writing-style && rm -rf skills-srcUse ~/.agents/skills/ instead of .agents/skills for a personal install.
Codex skills documentation · loads skills from .agents/skills/
Install the "ase-writing-style" agent skill from https://github.com/brycewang-stanford/Awesome-Journal-Skills/tree/main/ASE-Skills/skills/ase-writing-style into .agents/skills/ase-writing-style/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "ase-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.
$ npx skills add brycewang-stanford/Awesome-Journal-Skills --skill ase-writing-style -a cursorProject install goes to .agents/skills/; add -g for ~/.cursor/skills/.
$ gh skill install brycewang-stanford/Awesome-Journal-Skills ase-writing-style --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/ASE-Skills/skills/ase-writing-style .cursor/skills/ase-writing-style && 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 "ase-writing-style" agent skill from https://github.com/brycewang-stanford/Awesome-Journal-Skills/tree/main/ASE-Skills/skills/ase-writing-style into .cursor/skills/ase-writing-style/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "ase-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 https://github.com/brycewang-stanford/Awesome-Journal-Skills.git --path ASE-Skills/skills/ase-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.
$ npx skills add brycewang-stanford/Awesome-Journal-Skills --skill ase-writing-style -a gemini-cliProject install goes to .agents/skills/; add -g for ~/.gemini/skills/.
$ gh skill install brycewang-stanford/Awesome-Journal-Skills ase-writing-style --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/ASE-Skills/skills/ase-writing-style .gemini/skills/ase-writing-style && 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 "ase-writing-style" agent skill from https://github.com/brycewang-stanford/Awesome-Journal-Skills/tree/main/ASE-Skills/skills/ase-writing-style into .gemini/skills/ase-writing-style/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "ase-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.
$ gh skill install brycewang-stanford/Awesome-Journal-Skills ase-writing-styleInstalls 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 ase-writing-style -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/ASE-Skills/skills/ase-writing-style .github/skills/ase-writing-style && 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 "ase-writing-style" agent skill from https://github.com/brycewang-stanford/Awesome-Journal-Skills/tree/main/ASE-Skills/skills/ase-writing-style into .github/skills/ase-writing-style/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "ase-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.
$ npx skills add brycewang-stanford/Awesome-Journal-Skills --skill ase-writing-style -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 ase-writing-style --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/ASE-Skills/skills/ase-writing-style .opencode/skills/ase-writing-style && 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 "ase-writing-style" agent skill from https://github.com/brycewang-stanford/Awesome-Journal-Skills/tree/main/ASE-Skills/skills/ase-writing-style into .opencode/skills/ase-writing-style/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "ase-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
ase-writing-style- GitHub stars
- 1.2k
- Token cost
- ~1.5k tokens
- SKILL.md length
- 716 words
- Files
- 1
- Skills in repo
- 2,387
- Repo updated
- First seen
- Licence
- MIT
At a glance
A skill your agent uses when shaping the prose and structure of an ASE (IEEE/ACM Automated Software Engineering) research paper, covering the automation-first first-page arc, stating the automated…
- Works in 5 steps: The automatable task — a… → Why current automation (or manual… → The contribution as an automation design… → …
- Shaping the prose and structure of an ASE (IEEE/ACM Automated Software Engineering) research paper
- SKILL.md covers The ASE first-page arc, State the automated task…, Keep the model-swap test in view and Evidence proportional to the…, plus 5 more sections
- Instructions only: no scripts, shell commands, URLs or credentials in SKILL.md
What it does
Ase Writing Style is an agent skill from brycewang-stanford/Awesome-Journal-Skills. Use when shaping the prose and structure of an ASE (IEEE/ACM Automated Software Engineering) research paper, covering the automation-first first-page arc, stating the automated task precisely, keeping the tool runnable and the model-swap test in mind, threats-as-argument, and the 10+2 page discipline on the ACM acmart template.
Its SKILL.md is about 1.5k 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. 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
- Shaping the prose and structure of an ASE (IEEE/ACM Automated Software Engineering) research paper
- Covering the automation-first first-page arc
- Stating the automated task precisely
- Keeping the tool runnable and the model-swap test in mind
Example prompts
- “/ase-writing-style”
Workflow steps
5 steps, taken from the first numbered list in SKILL.md.
- The automatable task — a software-engineering task the reader recognizes (detect X, generate
- Why current automation (or manual practice) is inadequate — what existing tools do not do,
- The contribution as an automation design — the technique (analysis, generator, synthesizer,
- Evidence on real subjects — real systems, credible tool baselines, and the metric that
- What it automates for practice + threats posture — the payoff, with the central threat named
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
Ase Writing Style loads about 1.5k tokens when it runs. Until then it costs about 87 tokens; SKILL.md has 716 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). 716 words, ~1,481 tokens.
Download SKILL.mdSave it as
.claude/skills/ase-writing-style/SKILL.md (or your agent's skills folder).- name
- ase-writing-style
- description
- Use when shaping the prose and structure of an ASE (IEEE/ACM Automated Software Engineering) research paper, covering the automation-first first-page arc, stating the automated task precisely, keeping the tool runnable and the model-swap test in mind, threats-as-argument, and the 10+2 page discipline on the ACM acmart template.
ASE Writing Style
Write the paper so an automated-SE reviewer sees, on the first page, what task you automate, how
you automate it, and that it runs on real subjects. ASE rewards a clearly stated automation with
evidence proportional to the claim — not a systems win, not a leaderboard, and not a broad finding
that would read better at FSE. The worked example in resources/worked-examples/01-introduction.md
shows the arc before → after.
The ASE first-page arc
Lead with the automation, in this order:
- The automatable task — a software-engineering task the reader recognizes (detect X, generate Y, repair Z, comprehend W), named precisely enough that a reviewer knows what "success" is.
- Why current automation (or manual practice) is inadequate — what existing tools do not do, stated as a gap, not a literature tour.
- The contribution as an automation design — the technique (analysis, generator, synthesizer, repair, learned model) and, ideally, the tool that embodies it.
- Evidence on real subjects — real systems, credible tool baselines, and the metric that matches the task (not a proxy).
- What it automates for practice + threats posture — the payoff, with the central threat named where it lives, not deferred to a closing paragraph.
Put the automation and the first evidence within the first three pages; the early-rejection gate means a weak opening can end the process before rebuttal.
State the automated task precisely
- Name the input, the output, and the success criterion of the automation. "We improve code quality" is not a task; "given a flaky test, synthesize a patch that makes it deterministic without weakening its assertions" is.
- Say what the tool takes as input in practice (source? bytecode? traces? a repository?) and what it produces — reviewers map this straight to feasibility.
Keep the model-swap test in view
If a learned component is involved, write so the automation design is the contribution, not the
model. Report an ablation that isolates the learned part from the analysis/oracle, and phrase
claims so the software-engineering lesson survives a model swap. A paper whose lesson evaporates
when the model changes reads as an ML re-route (see ase-topic-selection).
Evidence proportional to the claim
- A detection claim needs precision/recall on real defects with a defined ground truth.
- A generation/synthesis claim needs validity of the generated artifact (does it compile, pass, hold the property?), not just similarity to a reference.
- A repair claim needs verified behavior change (re-run, oracle), not a classification score.
- A speed/scalability claim needs real-system sizes and a fair baseline configuration.
Pair every claim in the abstract with a table or figure it points to. Match evidence to claim shape;
see ase-experiments.
Show full SKILL.md (282 more words)Show less
Threats as argument, not boilerplate
Argue construct, internal, and external validity where they arise. For automated-SE tools the usual suspects: the oracle (how do you know a "repair" is correct?), subject selection (are the systems representative or self-selected?), baseline fairness (equal budgets/tuning?), and overfitting to the evaluation set. Name the residual threat plainly and bound it (an audited subsample, a held-out subject set) rather than reciting a checklist.
Page-budget discipline (10 + 2)
- 10 pages for everything readable — text, figures, tables, appendices — plus 2 for references only. The mandatory Data Availability Statement after Conclusions counts inside the 10 pages.
- Recover space editorially, not by shrinking the template. Move reproducible detail (full
configs, extra tables, proofs) to the artifact, but nothing that decides acceptance may live
outside the body (see
ase-supplementary). - Figures earn their space by carrying an argument (the automation's pipeline, a per-root-cause breakdown), not by decorating it.
Prose conventions
- Present tense for what the tool does; past tense for what you did in the study.
- Name the tool once, early, and use it consistently (anonymized at submission).
- Prefer concrete verbs of automation — detects, synthesizes, localizes, repairs, infers — over vague ones like leverages or explores.
- Third-person self-citation throughout, for double-anonymity.
Common ASE writing failures
| Failure | Why it hurts at ASE | Fix |
|---|---|---|
| Model/leaderboard framing | Reads as ML, not automated SE | Foreground the automation design; add the ablation |
| Vague task statement | Reviewer cannot judge success | Give input/output/success criterion in ¶1 |
| Proxy-metric evaluation | Evidence does not match a repair/synthesis claim | Verify the produced artifact directly (re-run/oracle) |
| Threats as a closing recital | Construct/oracle validity never engaged | Argue each threat where it arises; bound it |
| Body over 10 pages | Desk-reject-grade | Move reproducible detail to the artifact |
Output format
[Task] input -> output -> success criterion (one sentence, on page 1?)
[Automation-first arc] task / inadequacy / technique+tool / real-subject evidence / payoff+threats — all present?
[Model-swap] ablation isolating the learned component present? lesson survives a model swap?
[Evidence-claim pairing] each abstract claim -> a table/figure with a matching metric
[Budget] content pages / reference pages / Data Availability inside 10pp?© 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 ASE-Skills/skills/ase-writing-style of brycewang-stanford/Awesome-Journal-Skills.
Open the folder on GitHubat commit 932eb23
Compare with similar skills
Ase 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.
| Skill | Stars | Used in | Tokens | Auto-check | Licence | Repo updated |
|---|---|---|---|---|---|---|
| Ase Writing Style this skillbrycewang-stanford/Awesome-Journal-Skills | 1.2k | — | ~1.5k | Automated safety check: Pass | MIT | |
| Academic Venue Researchjoshua-zyy/academic-paper-writer | 115 | — | ~626 | Automated safety check: Pass | MIT | |
| Agsy Writing Stylefranklee16/academic-research-skills | 223 | 1 repos | ~1k | Automated safety check: Pass | None | |
| Artbull Writing Style And Citationfranklee16/academic-research-skills | 223 | 1 repos | ~848 | Automated safety check: Pass | None | |
| Ectheory Writing Stylefranklee16/academic-research-skills | 223 | 1 repos | ~874 | Automated safety check: Pass | None | |
| Io Writing Stylefranklee16/academic-research-skills | 223 | 1 repos | ~1.1k | Automated safety check: Pass | None |
Similar skills
Agsy Writing Style
franklee16/academic-research-skills
A skill your agent uses when drafting or polishing an Agricultural Systems (AgSy) manuscript so it reads clearly for a systems-science audience, follows the journal's format, and meets front-matter…
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…
Ectheory Writing Style
franklee16/academic-research-skills
A skill your agent uses to polish the prose, notation, and proof exposition of an Econometric Theory (ET) manuscript — theorem-proof clarity, consistent notation, APA author-date references, and ET…
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…
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…
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…
Related
Categories
Questions about Ase Writing Style
What does Ase Writing Style do?
A skill your agent uses when shaping the prose and structure of an ASE (IEEE/ACM Automated Software Engineering) research paper, covering the automation-first first-page arc, stating the automated…. Ase Writing Style is an agent skill from brycewang-stanford/Awesome-Journal-Skills. Use when shaping the prose and structure of an ASE (IEEE/ACM Automated Software Engineering) research paper, covering the automation-first first-page arc, stating the automated task precisely, keeping the tool runnable and the model-swap test in mind, threats-as-argument, and the 10+2 page discipline on the ACM acmart template.
When should I use Ase Writing Style?
Ase Writing Style fits situations like: shaping the prose and structure of an ASE (IEEE/ACM Automated Software Engineering) research paper; covering the automation-first first-page arc; stating the automated task precisely; keeping the tool runnable and the model-swap test in mind.
How do I install Ase Writing Style in Claude Code?
Run `npx skills add brycewang-stanford/Awesome-Journal-Skills --skill ase-writing-style -a claude-code`. Or copy the skill folder (ASE-Skills/skills/ase-writing-style in brycewang-stanford/Awesome-Journal-Skills) into .claude/skills/ase-writing-style in your project. Claude Code loads it when a task matches its description.
How do I install Ase Writing Style in Codex?
Run `npx skills add brycewang-stanford/Awesome-Journal-Skills --skill ase-writing-style -a codex`. Or copy the skill folder (ASE-Skills/skills/ase-writing-style in brycewang-stanford/Awesome-Journal-Skills) into .agents/skills/ase-writing-style in your project. Codex loads it when a task matches its description.
Can I use Ase 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 ase-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/ase-writing-style, .gemini/skills/ase-writing-style, .github/skills/ase-writing-style and .opencode/skills/ase-writing-style in your project.
What does Ase Writing Style need to run?
SKILL.md names no scripts, command-line tools or credentials: Ase Writing Style is instructions for the agent only.
Does Ase 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 Ase 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 Ase Writing Style use?
Ase 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 Ase Writing Style use?
About 1.5k tokens (SKILL.md is roughly 5.9k 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 Ase Writing Style?
Skills that share tags, products or a category with Ase Writing Style: Academic Venue Research (joshua-zyy/academic-paper-writer, 115 stars), Agsy Writing Style (franklee16/academic-research-skills, 223 stars), Artbull Writing Style And Citation (franklee16/academic-research-skills, 223 stars) and Ectheory Writing Style (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 Ase 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.