Avoid AI Writing
conorbronsdon/avoid-ai-writing
Audit and rewrite content to remove AI writing patterns ("AI-isms").
A skill your agent uses when revising an EMNLP draft for the venue's empirical voice — phenomenon-first framing, claims scoped to tested languages and domains, examples tied to counted errors, a…
Install Emnlp Writing Style
$ npx skills add brycewang-stanford/Awesome-Journal-Skills --skill emnlp-writing-style -a claude-codeProject install by default; add -g for ~/.claude/skills/.
$ gh skill install brycewang-stanford/Awesome-Journal-Skills emnlp-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/EMNLP-Skills/skills/emnlp-writing-style .claude/skills/emnlp-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 "emnlp-writing-style" agent skill from https://github.com/brycewang-stanford/Awesome-Journal-Skills/tree/main/EMNLP-Skills/skills/emnlp-writing-style into .claude/skills/emnlp-writing-style/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "emnlp-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/EMNLP-Skills/skills/emnlp-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 emnlp-writing-style -a codexProject install goes to .agents/skills/; add -g for ~/.codex/skills/.
$ gh skill install brycewang-stanford/Awesome-Journal-Skills emnlp-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/EMNLP-Skills/skills/emnlp-writing-style .agents/skills/emnlp-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 "emnlp-writing-style" agent skill from https://github.com/brycewang-stanford/Awesome-Journal-Skills/tree/main/EMNLP-Skills/skills/emnlp-writing-style into .agents/skills/emnlp-writing-style/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "emnlp-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 emnlp-writing-style -a cursorProject install goes to .agents/skills/; add -g for ~/.cursor/skills/.
$ gh skill install brycewang-stanford/Awesome-Journal-Skills emnlp-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/EMNLP-Skills/skills/emnlp-writing-style .cursor/skills/emnlp-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 "emnlp-writing-style" agent skill from https://github.com/brycewang-stanford/Awesome-Journal-Skills/tree/main/EMNLP-Skills/skills/emnlp-writing-style into .cursor/skills/emnlp-writing-style/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "emnlp-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 EMNLP-Skills/skills/emnlp-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 emnlp-writing-style -a gemini-cliProject install goes to .agents/skills/; add -g for ~/.gemini/skills/.
$ gh skill install brycewang-stanford/Awesome-Journal-Skills emnlp-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/EMNLP-Skills/skills/emnlp-writing-style .gemini/skills/emnlp-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 "emnlp-writing-style" agent skill from https://github.com/brycewang-stanford/Awesome-Journal-Skills/tree/main/EMNLP-Skills/skills/emnlp-writing-style into .gemini/skills/emnlp-writing-style/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "emnlp-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 emnlp-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 emnlp-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/EMNLP-Skills/skills/emnlp-writing-style .github/skills/emnlp-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 "emnlp-writing-style" agent skill from https://github.com/brycewang-stanford/Awesome-Journal-Skills/tree/main/EMNLP-Skills/skills/emnlp-writing-style into .github/skills/emnlp-writing-style/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "emnlp-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 emnlp-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 emnlp-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/EMNLP-Skills/skills/emnlp-writing-style .opencode/skills/emnlp-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 "emnlp-writing-style" agent skill from https://github.com/brycewang-stanford/Awesome-Journal-Skills/tree/main/EMNLP-Skills/skills/emnlp-writing-style into .opencode/skills/emnlp-writing-style/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "emnlp-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
emnlp-writing-style- GitHub stars
- 1.2k
- Token cost
- ~1.7k tokens
- SKILL.md length
- 854 words
- Files
- 1
- Skills in repo
- 2,387
- Repo updated
- First seen
- Licence
- MIT
At a glance
A skill your agent uses when revising an EMNLP draft for the venue's empirical voice — phenomenon-first framing, claims scoped to tested languages and domains, examples tied to counted errors, a…
- Revising an EMNLP draft for the venues empirical voice — phenomenon-first framing
- SKILL.md covers The scoping discipline, Examples must be load-bearing, First-page architecture and Writing the Limitations section, plus 6 more sections
- Instructions only: no scripts, shell commands, URLs or credentials in SKILL.md
- Claims scoped to tested languages and domains
What it does
Emnlp Writing Style is an agent skill from brycewang-stanford/Awesome-Journal-Skills. Use when revising an EMNLP draft for the venue's empirical voice — phenomenon-first framing, claims scoped to tested languages and domains, examples tied to counted errors, a Limitations section with content, honest hedging calibrated to evidence strength, and ACL two-column discipline for long and short formats.
Its SKILL.md is about 1.7k 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 Writing & Content, 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
- Revising an EMNLP draft for the venues empirical voice — phenomenon-first framing
- Claims scoped to tested languages and domains
- Examples tied to counted errors
- A Limitations section with content
Example prompts
- “/emnlp-writing-style”
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
Emnlp Writing Style loads about 1.7k tokens when it runs. Until then it costs about 84 tokens; SKILL.md has 854 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). 854 words, ~1,732 tokens.
Download SKILL.mdSave it as
.claude/skills/emnlp-writing-style/SKILL.md (or your agent's skills folder).- name
- emnlp-writing-style
- description
- Use when revising an EMNLP draft for the venue's empirical voice — phenomenon-first framing, claims scoped to tested languages and domains, examples tied to counted errors, a Limitations section with content, honest hedging calibrated to evidence strength, and ACL two-column discipline for long and short formats.
EMNLP Writing Style
Use this during revision. EMNLP's house voice is that of a careful experimentalist: the paper reports what was measured, in prose that never outruns the tables. The most common style failure at this venue is not bad English — it is claim inflation, where the abstract promises "understanding" and the evidence delivers accuracy on four datasets.
The scoping discipline
Every empirical claim carries an implicit quantifier, and EMNLP reviewers expand it:
| Draft sentence | What a reviewer hears | Scoped rewrite |
|---|---|---|
| "LLMs cannot track negation" | All LLMs, all negation, all languages | "The three 7-13B models we test fail on double negation in English and German (Table 4)" |
| "Our method improves summarization" | Everywhere, always | "…improves faithfulness on news summarization in two of three datasets; gains do not transfer to dialogue (§6.3)" |
| "This is a multilingual benchmark" | Typologically broad | "…covering five Indo-European languages; we discuss this limit in §Limitations" |
| "significantly better" | A statistical test exists | "+1.8 F1, paired bootstrap p<0.01 over 5 seeds" — or delete "significantly" |
The rewrites are not weaker papers; they are the same paper with its evidence and its prose in agreement — which is precisely what the soundness score measures.
Examples must be load-bearing
NLP papers live on examples, and EMNLP reviewers distinguish two uses sharply. Decorative: a cherry-picked output demonstrating the method at its best. Load-bearing: an example representing a counted category — "the model hedges the modal verb, an error type accounting for 34% of failures (Table 6, row 2)." Convert every decorative example to a load-bearing one or cut it; an example without a frequency is an anecdote, and the CFP-era reviewer culture treats anecdotes as filler.
First-page architecture
The opening should let a tired area chair reconstruct the paper: the phenomenon or task failure (with a number), why existing evaluation misses it, what you did, what you found, and where it breaks. Two structural rules follow. First, name the language behavior before the model: "summarizers delete speaker commitments" precedes any mention of architecture. Second, contribution bullets must be falsifiable — "we show X holds in Y setting but not Z" survives review; "we propose a novel framework" is unfalsifiable and reads as such.
Writing the Limitations section
The mandatory, uncounted Limitations section is the most misused free real estate in the format. Ritual limitations ("results may not generalize") waste it. Content limitations do reviewer-defusing work:
Weak: "Our approach may not work for all languages."
Strong: "All six test languages are written in Latin or Hangul scripts with
whitespace tokenization; our segmentation-dependent method has no
evidence for Thai or Chinese. Annotator pool was US-based crowdworkers,
so the politeness judgments encode one cultural frame (§5.4)."The strong version names the boundary, the mechanism behind it, and where the paper already discusses it. Reviewers routinely check whether the Limitations section admits the weakness they independently found — matching it is credibility; missing it is a soundness deduction.
Hedging calibration
Empirical prose needs exactly one hedging level per claim, chosen by evidence:
- Demonstrated on your data: indicative mood, no hedge — "the effect reverses on dialogue data."
- Supported but unproven mechanism: "consistent with", "suggests" — once, not stacked.
- Speculation: fence it explicitly ("we speculate…") or move it to future work.
Stacked hedges ("may potentially suggest") and false confidence ("proves") are equal and opposite failures; both misreport evidence strength.
Show full SKILL.md (358 more words)Show less
Titles and abstracts, venue idiom
EMNLP titles carry information, and the program is searched by task: name the phenomenon or task in the title, not just the system ("Pragmatic Drift in Multilingual Summarizers" beats "PoliteSumm: A Novel Framework for Better Summaries"). System names are fine as prefixes when the system is the release; they are dead weight when the finding is the contribution. In abstracts, the venue idiom is numbers early: the best EMNLP abstracts contain the headline measurement, the languages or datasets, and the significance posture — a reader should be able to referee the claim's scope from the abstract alone.
Terminology honesty
Two lexical habits mark careful empirical writing here:
- "Understanding," "reasoning," "knows" — mentalistic verbs applied to models get flagged unless operationalized; prefer the measured behavior ("answers correctly under paraphrase") or define the construct once and stick to it.
- "State-of-the-art" — a comparative claim against a moving population; if used, date it and bound it ("among open models under 13B evaluated on X as of May 2026"), or replace it with the actual comparison made.
Two-column craft, ACL flavor
- Long papers get 8 content pages, short papers 4, references free, Limitations and ethics uncounted — design the argument for the cap instead of compressing at the end.
- Wide comparison tables dominate NLP papers: prefer one decision-relevant table in the body and push completeness grids to the appendix, cross-referenced.
- Non-Latin script examples need declared fonts and romanization plus gloss; an example the reviewer cannot read is an example that does not exist.
- Short papers: one claim, stated in the first paragraph, with the strongest single table — a short paper that "surveys" its own contribution has already failed.
The revision pass, ordered
Run the passes separately — combined passes miss things: (1) claim-scope pass over every abstract and section-opening sentence; (2) example audit tying each excerpt to a counted category; (3) hedge calibration; (4) Limitations content check against the weaknesses you privately know; (5) format sweep for scripts, table widths, and the uncounted sections. The first pass matters most and is best done by the coauthor who did not run the experiments — attachment to results is what inflates their description.
Output format
[Voice diagnosis] scoped / inflated / over-hedged / anecdotal
[Claim-scope repairs] <sentence -> scoped rewrite>
[Example audit] <decorative examples -> counted category or cut>
[Limitations quality] ritual / content — with the missing admissions
[Format risks] <tables, scripts, page-cap pressure>© 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 EMNLP-Skills/skills/emnlp-writing-style of brycewang-stanford/Awesome-Journal-Skills.
Open the folder on GitHubat commit 932eb23
Compare with similar skills
Emnlp 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 |
|---|---|---|---|---|---|---|
| Emnlp Writing Style this skillbrycewang-stanford/Awesome-Journal-Skills | 1.2k | — | ~1.7k | Automated safety check: Pass | MIT | |
| Avoid AI Writingconorbronsdon/avoid-ai-writing | 4.9k | 3 repos | ~8.1k | Automated safety check: Pass | MIT | |
| BrandOhh-889/skyroc | 795 | 13 repos | ~733 | Automated safety check: Pass | MIT | |
| Khazix WeChat Article WriterKKKKhazix/khazix-skills | 21k | 1 repos | ~2.9k | Automated safety check: Pass | MIT | |
| Writing Guidelinesvercel-labs/agent-skills | 32k | 7 repos | ~309 | Automated safety check: Pass | None | |
| Unslop AI Writing Cleanuptheclaymethod/unslop | 518 | — | ~1.7k | Automated safety check: Pass | MIT |
Similar skills
Brand
Ohh-889/skyroc
Brand voice, visual identity, messaging frameworks, asset management, brand consistency.
Khazix WeChat Article Writer
KKKKhazix/khazix-skills
Writes long-form WeChat official account articles in the personal style of the Khazix account, from briefs, links, PDFs or rough notes, with a topic quality check.
- Official
Writing Guidelines
vercel-labs/agent-skills
Review docs/prose for Writing Guidelines compliance. An agent skill from vercel-labs/agent-skills.
Unslop AI Writing Cleanup
theclaymethod/unslop
Removes AI writing tells from prose through an audit-first flow, routing to a two-pass rewrite, a report-only cleanup, voice teaching or mimicry depending on the sub-command used.
UX Writing
content-designer/ux-writing-skill
Applies UX writing practice to interface copy such as buttons, errors, forms and onboarding, using four quality standards and accessibility guidance.
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 Emnlp Writing Style
What does Emnlp Writing Style do?
A skill your agent uses when revising an EMNLP draft for the venue's empirical voice — phenomenon-first framing, claims scoped to tested languages and domains, examples tied to counted errors, a…. Emnlp Writing Style is an agent skill from brycewang-stanford/Awesome-Journal-Skills. Use when revising an EMNLP draft for the venue's empirical voice — phenomenon-first framing, claims scoped to tested languages and domains, examples tied to counted errors, a Limitations section with content, honest hedging calibrated to evidence strength, and ACL two-column discipline for long and short formats.
When should I use Emnlp Writing Style?
Emnlp Writing Style fits situations like: revising an EMNLP draft for the venues empirical voice — phenomenon-first framing; claims scoped to tested languages and domains; examples tied to counted errors; A Limitations section with content.
How do I install Emnlp Writing Style in Claude Code?
Run `npx skills add brycewang-stanford/Awesome-Journal-Skills --skill emnlp-writing-style -a claude-code`. Or copy the skill folder (EMNLP-Skills/skills/emnlp-writing-style in brycewang-stanford/Awesome-Journal-Skills) into .claude/skills/emnlp-writing-style in your project. Claude Code loads it when a task matches its description.
How do I install Emnlp Writing Style in Codex?
Run `npx skills add brycewang-stanford/Awesome-Journal-Skills --skill emnlp-writing-style -a codex`. Or copy the skill folder (EMNLP-Skills/skills/emnlp-writing-style in brycewang-stanford/Awesome-Journal-Skills) into .agents/skills/emnlp-writing-style in your project. Codex loads it when a task matches its description.
Can I use Emnlp 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 emnlp-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/emnlp-writing-style, .gemini/skills/emnlp-writing-style, .github/skills/emnlp-writing-style and .opencode/skills/emnlp-writing-style in your project.
What does Emnlp Writing Style need to run?
SKILL.md names no scripts, command-line tools or credentials: Emnlp Writing Style is instructions for the agent only.
Does Emnlp 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 Emnlp 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 Emnlp Writing Style use?
Emnlp 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 Emnlp Writing Style use?
About 1.7k tokens (SKILL.md is roughly 6.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 Emnlp Writing Style?
Skills that share tags, products or a category with Emnlp Writing Style: Avoid AI Writing (conorbronsdon/avoid-ai-writing, 4.9k stars), Brand (Ohh-889/skyroc, 795 stars), Khazix WeChat Article Writer (KKKKhazix/khazix-skills, 21k stars) and Writing Guidelines (vercel-labs/agent-skills, 32k stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.
Who maintains Emnlp 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.