Agent Skills
› brycewang-stanford/Awesome-Journal-Skills
› orgstud-writing-style
orgstud-writing-style
GitHub专用于优化组织研究（OS）期刊的手稿写作风格。在理论分析已确定的前提下，将平淡或描述性文本转化为具有欧洲学术特色的论述性、理论丰富且逻辑严密的散文风格，提升论证弧光与概念深度，不改变原有理论与分析内容。
Trigger Scenarios
手稿理论分析已定，但文风平淡或缺乏理论深度
过程研究使用僵化的方差语言而非动态表述
审稿人认为写作‘理论发展不足’或过于‘描述性’
Install
npx skills add brycewang-stanford/Awesome-Journal-Skills --skill orgstud-writing-style -g -y
SKILL.md
Frontmatter
{
"name": "orgstud-writing-style",
"description": "Use for full-manuscript prose and the discursive European register of an Organization Studies (OS) manuscript — voice, theoretical texture, the argument's arc, and qualitative craft. Polishes the writing; it does not change the theory or analysis."
}
Writing Style & Craft (orgstud-writing-style)
When to trigger
- The theory and analysis are settled; the prose must reach OS's register
- The manuscript is technically correct but flat, atheoretical in tone, or hard to follow
- A process study is written in dead "variance-speak" (factor A raised outcome B)
- Reviewers/editors praise the idea but call the writing "underdeveloped theoretically" or "descriptive"
OS's register: theoretically-rich, discursive, European
OS prose differs from the lean US empirical style. It is discursive and conceptually textured: the theoretical thread is foregrounded throughout, social theory is woven into the argument rather than quarantined in a lit review, and the writing carries an argumentative, sometimes essayistic confidence. This is not licence for vagueness — the best OS papers are precise about their concepts and generous in developing them. The voice should read as someone in deep conversation with organization theory, building an argument, not reporting a study.
The argument's arc
- Open with the puzzle, theorized. The first pages make a smart reader curious and signal the theoretical stakes — the anomaly and why existing theory cannot hold it, not a literature catalogue.
- Foreground theory throughout. The theoretical thread is visible in every section, including methods and findings — a hallmark of OS, distinct from journals where theory lives only in intro and discussion.
- Develop, don't just report. Findings sections in OS theorize as they present — interpreting evidence through the conceptual lens, not deferring all interpretation to a discussion.
- Earn the surprise / reframing. Set up the prior carefully so the reader feels the reconceptualization land.
- Close on generativity. End by opening new questions and implications for the conversation, not by restating findings.
Prose discipline (precision under richness)
- Define concepts once, precisely, then use them consistently. OS tolerates conceptual density but punishes sloppy or shifting use of borrowed theory.
- Concrete subjects and verbs; cut nominalization stacks ("the operationalization of the conceptualization of...").
- One idea per paragraph, with a topic sentence that advances the argument.
- Signpost the argument so the reader always knows where they are in the theoretical journey.
- Engage theory actively — make Weick, Bourdieu, institutional logics do work in the sentence, not appear as citations.
Process vs. variance voice
- For process theory, write in process language: events, sequences, becoming, unfolding, enactment, feedback. Never flatten a process into a static relationship.
- For variance/quantitative work at OS, be precise about relationships and magnitudes — but still narrate the organizational why and keep the theoretical thread visible.
Qualitative-specific craft
- Weave informant voice into the analysis so quotes advance the argument.
- Show enough of the field — thick description — to make the setting vivid and the inference credible, without drowning the theory.
- Maintain analytic distance: vivid but not journalistic; interpretive but disciplined.
- Make reflexivity audible where it matters, as the European tradition expects.
Checklist
- Opens with a theorized puzzle, not a literature dump
- A single, traceable theoretical thread runs through every section, including findings
- Findings theorize as they present, not just report
- Borrowed theory used precisely and consistently; concepts defined once
- Process papers written in process voice (not variance-speak)
- One idea per paragraph; topic sentences carry the argument; signposting present
- Qualitative: informant voice advances the argument; setting vivid but disciplined
- Ends on generativity (new questions), not a findings recap
Anti-patterns
- "Lab-report" prose: mechanical, voiceless, theory only in intro and discussion
- Conceptual density that is actually vagueness — borrowed theory used loosely
- Front-loading the literature so the puzzle never lands
- Variance-speak imposed on a process phenomenon
- Quote-dumping in qualitative papers with no analytic threading
- A discussion that restates results instead of opening questions
Output format
【Register】theory foregrounded throughout? findings theorize as they present? (Y/N)
【Argument arc】theorized puzzle → development → reframing → generativity (status)
【Theoretical thread】visible in every section? (Y/N)
【Voice】process / variance — matches phenomenon?
【Prose fixes】concept precision / nominalizations / paragraphing / signposting
【Qual craft】informant voice + setting + reflexivity balanced?
【Next skill】orgstud-submission
Version History
- 1839142 Current 2026-07-05 14:09
