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 Academy of Management Annals (Annals) review for the house voice — authoritative, integrative, agenda-setting "reviews with an attitude," with a strong…
Install Amann Writing Style
$ npx skills add brycewang-stanford/Awesome-Journal-Skills --skill amann-writing-style -a claude-codeProject install by default; add -g for ~/.claude/skills/.
$ gh skill install brycewang-stanford/Awesome-Journal-Skills amann-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/Academy-of-Management-Annals-Skills/skills/amann-writing-style .claude/skills/amann-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 "amann-writing-style" agent skill from https://github.com/brycewang-stanford/Awesome-Journal-Skills/tree/main/Academy-of-Management-Annals-Skills/skills/amann-writing-style into .claude/skills/amann-writing-style/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "amann-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/Academy-of-Management-Annals-Skills/skills/amann-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 amann-writing-style -a codexProject install goes to .agents/skills/; add -g for ~/.codex/skills/.
$ gh skill install brycewang-stanford/Awesome-Journal-Skills amann-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/Academy-of-Management-Annals-Skills/skills/amann-writing-style .agents/skills/amann-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 "amann-writing-style" agent skill from https://github.com/brycewang-stanford/Awesome-Journal-Skills/tree/main/Academy-of-Management-Annals-Skills/skills/amann-writing-style into .agents/skills/amann-writing-style/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "amann-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 amann-writing-style -a cursorProject install goes to .agents/skills/; add -g for ~/.cursor/skills/.
$ gh skill install brycewang-stanford/Awesome-Journal-Skills amann-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/Academy-of-Management-Annals-Skills/skills/amann-writing-style .cursor/skills/amann-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 "amann-writing-style" agent skill from https://github.com/brycewang-stanford/Awesome-Journal-Skills/tree/main/Academy-of-Management-Annals-Skills/skills/amann-writing-style into .cursor/skills/amann-writing-style/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "amann-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 Academy-of-Management-Annals-Skills/skills/amann-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 amann-writing-style -a gemini-cliProject install goes to .agents/skills/; add -g for ~/.gemini/skills/.
$ gh skill install brycewang-stanford/Awesome-Journal-Skills amann-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/Academy-of-Management-Annals-Skills/skills/amann-writing-style .gemini/skills/amann-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 "amann-writing-style" agent skill from https://github.com/brycewang-stanford/Awesome-Journal-Skills/tree/main/Academy-of-Management-Annals-Skills/skills/amann-writing-style into .gemini/skills/amann-writing-style/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "amann-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 amann-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 amann-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/Academy-of-Management-Annals-Skills/skills/amann-writing-style .github/skills/amann-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 "amann-writing-style" agent skill from https://github.com/brycewang-stanford/Awesome-Journal-Skills/tree/main/Academy-of-Management-Annals-Skills/skills/amann-writing-style into .github/skills/amann-writing-style/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "amann-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 amann-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 amann-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/Academy-of-Management-Annals-Skills/skills/amann-writing-style .opencode/skills/amann-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 "amann-writing-style" agent skill from https://github.com/brycewang-stanford/Awesome-Journal-Skills/tree/main/Academy-of-Management-Annals-Skills/skills/amann-writing-style into .opencode/skills/amann-writing-style/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "amann-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
amann-writing-style- GitHub stars
- 1.2k
- Token cost
- ~1.4k tokens
- SKILL.md length
- 670 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 Academy of Management Annals (Annals) review for the house voice — authoritative, integrative, agenda-setting "reviews with an attitude," with a strong…
- Works in 4 steps: Authoritative. Confident judgments about… → Has attitude. This is the Annals… → Integrative, not descriptive. Sentences… → …
- Revising an Academy of Management Annals (Annals) review for the house voice — authoritative
- SKILL.md covers When to trigger, The Annals voice:…, The Annals opening arc and The abstract, plus 4 more sections
- Instructions only: no scripts, shell commands, URLs or credentials in SKILL.md
What it does
Amann Writing Style is an agent skill from brycewang-stanford/Awesome-Journal-Skills. Use when revising an Academy of Management Annals (Annals) review for the house voice — authoritative, integrative, agenda-setting "reviews with an attitude," with a strong problem-first opening and a contribution-stating abstract. Polishes prose and structure; it does not design the framework (amann-organizing-framework) or run the submission preflight (amann-submission).
Its SKILL.md is about 1.4k 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 Academy of Management Annals (Annals) review for the house voice — authoritative
- Agenda-setting reviews with an attitude
- With a strong problem-first opening and a contribution-stating abstract
Example prompts
- “reviews with an attitude,”
- “/amann-writing-style”
Workflow steps
4 steps, taken from the first numbered list in SKILL.md.
- Authoritative. Confident judgments about what is known, contested, and how good the evidence is. The reader wants the author's appraisal…
- Has attitude. This is the Annals signature. The review takes a critical, potentially provocative position grounded in the evidence: it…
- Integrative, not descriptive. Sentences make streams talk to each other ("Whereas the X tradition treats … as …, the Y stream implies …")…
- Agenda-setting. The review points forward. The payoff is what becomes researchable after it — propositions, open questions, a…
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
Amann Writing Style loads about 1.4k tokens when it runs. Until then it costs about 99 tokens; SKILL.md has 670 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). 670 words, ~1,434 tokens.
Download SKILL.mdSave it as
.claude/skills/amann-writing-style/SKILL.md (or your agent's skills folder).- name
- amann-writing-style
- description
- Use when revising an Academy of Management Annals (Annals) review for the house voice — authoritative, integrative, agenda-setting "reviews with an attitude," with a strong problem-first opening and a contribution-stating abstract. Polishes prose and structure; it does not design the framework (amann-organizing-framework) or run the submission preflight (amann-submission).
Annals Writing Style — "Reviews with an Attitude" (amann-writing-style)
When to trigger
- The framework and evidence appraisal are settled and it is time to make the review read well
- The draft is descriptive and balanced but has no voice, no position, no agenda
- The opening buries the field's problem under throat-clearing or method machinery
- The abstract reads like a paper abstract ("we find…") rather than a review abstract
The Annals voice: authoritative + integrative + has attitude
Annals is read by management and organization scholars across subfields, plus allied audiences (organizational psychology, sociology of organizations). The voice is that of a trusted, fair expert who has read the whole field and is willing to say what it got right, what it got wrong, and what to do next. Four qualities define it:
- Authoritative. Confident judgments about what is known, contested, and how good the evidence is. The reader wants the author's appraisal, not neutrality-as-evasion — but authority is earned by comprehensiveness and balance, never asserted.
- Has attitude. This is the Annals signature. The review takes a critical, potentially provocative position grounded in the evidence: it names the field's blind spots, over-studied questions, and conceptual confusions. A balanced, accurate, positionless review is the most common stylistic miss.
- Integrative, not descriptive. Sentences make streams talk to each other ("Whereas the X tradition treats … as …, the Y stream implies …"), reorganizing the field rather than touring it stream by stream.
- Agenda-setting. The review points forward. The payoff is what becomes researchable after it — propositions, open questions, a future-research roadmap tied to the framework's empty cells.
The Annals opening arc
An Annals introduction differs from a research-paper intro and even from a generic review:
frame the field and its problem (what it studies, and the specific way it is fragmented/contradictory/confused) → why a review is needed now (a wave of work, a method shift, a hardened debate) → the organizing framework (the new way of seeing the field — the map the reader is given) → the position and the agenda (the "attitude" and what the review will conclude the field should do) → roadmap (brief).
State the framework and the position early. A review that withholds its organizing idea to a final section wastes the reader's time and reads as indecisive — the opposite of "attitude."
The abstract
A review abstract describes what the review does for the field: the literature, why a review now, the integrative framework, the critical position, and the agenda. Avoid "we hypothesize / we find a coefficient…"; that is a primary-paper abstract. (Confirm any length/format limits at submission via amann-submission; 待核实.)
Show full SKILL.md (245 more words)Show less
Length and the reader's stamina
Annals reviews are long (~50 pages of text; 检索于 2026-06；以官网为准), and length is a privilege, not a license. Every section must earn its pages by advancing the argument about the field; confirmatory coverage (the lower tiers of amann-evidence-standards) belongs in compact citation clusters, not paragraph-length summaries. Use strong section architecture that mirrors the framework, periodic "where we are / where we go next" cues, and subsection summaries so a reader who puts the review down can re-enter without rereading.
Checklist
- Opening follows the arc: field+problem → why now → framework → position+agenda → roadmap
- The framework and the critical position are stated early, not withheld to the end
- The review has attitude: it names blind spots / over-studied questions / confusions, grounded in evidence
- Prose integrates (streams in dialogue), not describes (stream-by-stream tour)
- A forward-looking agenda is explicit and tied to the framework's gaps
- Technical material introduced intuition-first; jargon defined or avoided for cross-subfield readers
- Section architecture mirrors the framework; periodic signposting present
- Abstract describes the review's contribution to the field, not a single finding
Anti-patterns
- The annotated-bibliography drone: "Smith (2010) found… Jones (2012) found…" with no connective argument
- A balanced, accurate, positionless review — coverage without the Annals "attitude"
- Opening with method/notation before the field's problem and stakes
- Withholding the framework or the conclusions until the final section
- Closing with a generic "more research is needed" instead of a structured, framework-tied agenda
- A primary-paper abstract ("we find…") on a review; neutrality-as-evasion in place of appraisal
Output format
【Opening arc】field+problem → why-now → framework → position+agenda → roadmap? Y/N
【Framework early】organizing idea stated up front? Y/N
【Attitude】names blind spots / over-studied / confusions, evidence-grounded? Y/N
【Integrative prose】streams in dialogue, not toured? Y/N
【Agenda】forward-looking, tied to framework gaps? Y/N
【Accessibility】intuition-first; jargon controlled for cross-subfield readers? Y/N
【Abstract】review-style (contribution to the field), not a single finding? Y/N
【Next skill】→ amann-editor-strategy / amann-submission© 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 Academy-of-Management-Annals-Skills/skills/amann-writing-style of brycewang-stanford/Awesome-Journal-Skills.
Open the folder on GitHubat commit 932eb23
Compare with similar skills
Amann 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 |
|---|---|---|---|---|---|---|
| Amann Writing Style this skillbrycewang-stanford/Awesome-Journal-Skills | 1.2k | — | ~1.4k | 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 Amann Writing Style
What does Amann Writing Style do?
A skill your agent uses when revising an Academy of Management Annals (Annals) review for the house voice — authoritative, integrative, agenda-setting "reviews with an attitude," with a strong…. Amann Writing Style is an agent skill from brycewang-stanford/Awesome-Journal-Skills. Use when revising an Academy of Management Annals (Annals) review for the house voice — authoritative, integrative, agenda-setting "reviews with an attitude," with a strong problem-first opening and a contribution-stating abstract.
When should I use Amann Writing Style?
Amann Writing Style fits situations like: revising an Academy of Management Annals (Annals) review for the house voice — authoritative; agenda-setting reviews with an attitude; with a strong problem-first opening and a contribution-stating abstract.
How do I install Amann Writing Style in Claude Code?
Run `npx skills add brycewang-stanford/Awesome-Journal-Skills --skill amann-writing-style -a claude-code`. Or copy the skill folder (Academy-of-Management-Annals-Skills/skills/amann-writing-style in brycewang-stanford/Awesome-Journal-Skills) into .claude/skills/amann-writing-style in your project. Claude Code loads it when a task matches its description.
How do I install Amann Writing Style in Codex?
Run `npx skills add brycewang-stanford/Awesome-Journal-Skills --skill amann-writing-style -a codex`. Or copy the skill folder (Academy-of-Management-Annals-Skills/skills/amann-writing-style in brycewang-stanford/Awesome-Journal-Skills) into .agents/skills/amann-writing-style in your project. Codex loads it when a task matches its description.
Can I use Amann 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 amann-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/amann-writing-style, .gemini/skills/amann-writing-style, .github/skills/amann-writing-style and .opencode/skills/amann-writing-style in your project.
What does Amann Writing Style need to run?
SKILL.md names no scripts, command-line tools or credentials: Amann Writing Style is instructions for the agent only.
Does Amann 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 Amann 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 Amann Writing Style use?
Amann 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 Amann Writing Style use?
About 1.4k tokens (SKILL.md is roughly 5.7k 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 Amann Writing Style?
Skills that share tags, products or a category with Amann 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 Amann 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.