arsoc-editor-strategy
Use when working with the Annual Review of Sociology (ARSoc) Editorial Committee and Annual Reviews production team — negotiating the commissioned scope, anticipating what review referees evaluate, and the annual-volume timeline. Plans the interaction; it does not run the delivery preflight (arsoc-submission) or draft the response letter (arsoc-revision).
Profile →npx skills add brycewang-stanford/Awesome-Journal-Skills --skill arsoc-editor-strategy --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.
# Editor & Committee Strategy (arsoc-editor-strategy) ## When to trigger - The Editorial Committee invited the topic and you are negotiating the review's scope - You want to anticipate what ARSoc reviewers of a *review* will push on (different from a paper) - The editor has asked you to expand, cut, or rebalance coverage - You are calibrating how the Committee review cycle and the Annual Reviews production timeline work ## Who you are working with at ARSoc ARSoc is run by an **Editorial Committee** — an editor (检索于 2026-06：co-editors Douglas Massey & Mary C. Waters；以官网为准), associate editors, regular members serving multi-year terms, and occasional one-year guest members — plus the journal's **production team** at Annual Reviews. Your primary partners differ by phase: the **commissioning editor / Committee** owns scope and acceptance; the **production editor** owns format, figures, copyediting, and the volume schedule. Because the article is **commissioned**, the relationship is more collaborative than adversarial — the Committee wants the review to succeed — but acceptance is **not** automatic: an invited manuscript is still assessed for **accuracy, rigor, and balance** (检索于 2026-0
- When to trigger
- Who you are working with at ARSoc
- How review differs for a review article
- Sociology-specific editorial posture
- Scope negotiation with the Committee
- Checklist
- Anti-patterns
- Output format
What does the arsoc-editor-strategy skill do?
Use when working with the Annual Review of Sociology (ARSoc) Editorial Committee and Annual Reviews production team — negotiating the commissioned scope, anticipating what review referees evaluate, and the annual-volume timeline. Plans the interaction; it does not run the delivery preflight (arsoc-submission) or draft the response letter (arsoc-revision).
How do I install it?
Run `npx skills add brycewang-stanford/Awesome-Journal-Skills --skill arsoc-editor-strategy --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.