SkillAgentSearch skills...

amann-writing-style

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.

Install / Use

npx skills add brycewang-stanford/Awesome-Journal-Skills --skill amann-writing-style

Installs into whichever agent you are using.

About this skill
📄

SKILL.md

Installable skill definition

Quality Score

85/100

Supported Platforms

Universal

Our assessment of amann-writing-style

amann-writing-style scores 85/100 on our quality scale, 814th of 1,156 Content & Media skills we index.

Its SKILL.md is 5.6 KB long, well organised into 9 sections with 1 code example: a solid amount of guidance for an agent.

With 1,158 GitHub stars, it is one of the more widely adopted skills in the catalogue.

Substance
26/30
Structure
17/20
Description
15/15
Adoption
13/20
Freshness
15/15

Maintenance, license and trust

  • The repository was last updated about 2 months ago, so amann-writing-style is actively maintained.
  • Our last check on 2026-11-05 found the source still online.
  • It is released under the MIT license, a permissive license that allows use, modification and commercial use with attribution.
  • Its trust signals score 100/100, with no cautions. These come from repository metadata, not a code audit — read the skill file before letting an agent act on it.

Safety scan

No issues found

Our scan of the whole file found no instruction hijacking, hidden characters, credential access, data exfiltration or destructive commands. An AI review of the same text found nothing harmful.

AI review by kimi-k2.7-code on 2026-10-04. Automated pattern scan on 2026-10-04. It catches known dangerous patterns, not every risk — read a skill before letting an agent act on it.

amann-writing-style compared with similar skills

All 4 of these similar skills score higher than amann-writing-style; compare them before choosing.

SkillScoreStarsUpdatedFormat
amann-writing-style (this skill)by brycewang-stanford851.2k2mo agoSKILL.md
taste-skillby Leonxlnx100117.6k9d agoCLAUDE.md
Claude-Code-Game-Studiosby Donchitos10039.9k8d agoCLAUDE.md
LocalAIby mudler10050.4ktodayMCP Server
siyuanby siyuan-note10047.3ktodayMCP Server

Frequently asked questions

How do I install amann-writing-style?
Run npx skills add brycewang-stanford/Awesome-Journal-Skills --skill amann-writing-style. The install tabs above show the steps for each supported agent.
Which AI agents does amann-writing-style work with?
It is written for Universal, as a SKILL.md file. Other agents that read the same format can often use it too.
Is amann-writing-style safe to use?
Our scan of the whole file found no instruction hijacking, hidden characters, credential access, data exfiltration or destructive commands. An AI review of the same text found nothing harmful. It is MIT-licensed and scores 100/100 on trust signals. Skills are instructions an agent will follow, so read the file before installing it and do not approve commands you do not understand.
Is amann-writing-style still maintained?
The repository was last updated about 2 months ago, so amann-writing-style is actively maintained.

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:

  1. 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.
  2. 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.
  3. 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.
  4. 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; 待核实.)

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

Related Skills

View on GitHub
GitHub Stars1.2k
CategoryContent
Updated2mo ago
Forks153

Languages

Stata

Trust signals

100/100

From repository metadata: license, adoption, age and documentation. Not a code audit — see the Safety scan above for what the skill file itself contains.

No cautions