eacl-writing-style
Use when revising an EACL paper's prose for a task-first first page, a concrete page-one example, scoped LLM-era claims, quantified error analysis, an anonymity-safe voice, honest Limitations, and compression into the 8-page long or 4-page short content budget without pushing the argument into appendices.
Profile →npx skills add brycewang-stanford/Awesome-Journal-Skills --skill eacl-writing-style --agent claude-code
Same command for any agent — swap --agent for codex, cursor, copilot.
Weekly change comes from our own snapshots, not the repository page — it measures attention, not adoption.
# EACL Writing Style Use this to revise an EACL paper so its contribution is legible fast and its claims are scoped. EACL reviewers read many papers in a short window; the ones that land put the **task and the result on the first page**, quantify rather than assert, and name their limits. Pair this with the worked example in `../../resources/worked-examples/01-introduction.md`. ## The EACL first-page arc 1. **Task** — the specific problem, in the first breath, not "great progress in NLP." 2. **Gap** — why current methods fall short, each reason nameable. 3. **What we do** — the contribution, stated plainly. 4. **Measured result** — a number tied to a table, with variance. 5. **Honest scope** — what the result does and does not cover. ## Habits to cut, habits to keep | Cut | Keep | |---|---| | "Achieves strong performance" | "Improves F1 by X (95% CI ...) over baseline B" | | Generic "prior work is limited" | A specific failure per cited approach | | A concrete example only on page 5 | A worked example on page 1 | | Unscoped "our method generalizes" | "On the six languages tested; see Limitations" | | Roadmap standing in for an argument | A one-line roadmap after the argument | ## S
- The EACL first-page arc
- Habits to cut, habits to keep
- Scope the LLM-era claim
- Quantify the error analysis
- Anonymity-safe voice
- Multilingual clarity
- Compression discipline
- Output format
What does the eacl-writing-style skill do?
Use when revising an EACL paper's prose for a task-first first page, a concrete page-one example, scoped LLM-era claims, quantified error analysis, an anonymity-safe voice, honest Limitations, and compression into the 8-page long or 4-page short content budget without pushing the argument into appendices.
How do I install it?
Run `npx skills add brycewang-stanford/Awesome-Journal-Skills --skill eacl-writing-style --agent claude-code` — it drops the skill into your project so the agent can pick it up. Swap the --agent value for codex, cursor or copilot if you use one of those.
Where does this skill come from?
From brycewang-stanford/Awesome-Journal-Skills, a repository with 909 stars. We read it straight from the repository tree rather than a submitted listing, so what you see here is what is actually published.
Is a popular skill a good skill?
Not necessarily. Stars measure attention, not adoption — a repository can trend for a week and be abandoned. That is why we show the weekly change from our own snapshots next to the total, instead of a single flattering number.