Individual skill

ase-writing-style

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-Skills/skills/ase-writing-style/SKILL.md

Read pinned source

Source commit 932eb23331721b16e967c59f093781be1928b498

What was checked

Matches the observed repository HEAD: Yes
Scanner rules are current: Yes
Repository scan complete: No
Skill scan complete: Yes
Observed behavior: Network or broad shell
Last checked: Nov 9, 2026

These are observations at the recorded commit, not a guarantee of safety. Review the source before running it.

Install this skill

Choose an agent in your Stack or copy a command below. Commands fetch the pinned commit and copy only this skill directory. Existing destinations are refused. Copying a command does not install anything.

An install command is unavailable: current rules, complete repository and skill scans, an eligible behavior level and a permitted license are required.

Repository context

Repository stars (not skill ratings): 1,405
Repository last updated: Sep 27, 2026
License: MIT

Observed agent integration: No specific integration evidence. Standard SKILL.md installation does not imply verified compatibility.

academic-writing Repository topic
agent-skills Repository topic
journal Repository topic
academic-research Repository topic
ai-agents Repository topic
anthropic Repository topic
awesome-list Repository topic
claude Repository topic
claude-code Repository topic
economics Repository topic
engineering Derived category
research Derived category
writing Derived category
testing Derived category

Files and excerpt

File metadata and permitted, redacted excerpts come from the recorded scan. Source links are pinned to that commit.

Browse files

SKILL.mdcore · 5,948 bytes

Read excerpt


# 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:

1. **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.