sf-review-process
Use to understand how Social Forces (SF) evaluates a manuscript — double-anonymized review via ScholarOne, what expert reviewers weigh (rigor, general significance, theoretical grounding), the typical decision categories, and the journal's reported review timeline. Sets expectations and shapes the paper to survive review; it does not contact editors.
Profile →npx skills add brycewang-stanford/Awesome-Journal-Skills --skill sf-review-process --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.
# Review Process (sf-review-process) Knowing how Social Forces screens and decides lets you pre-empt the failure modes before submitting. SF is **double-anonymized** and managed through **ScholarOne Manuscript Central** for the editorial office at the **UNC Department of Sociology**. Its reviewers prize **methodological rigor**, **general social-science significance**, and a **theoretically grounded** contribution. ## When to trigger - Before submitting, to stress-test the paper against the likely reviewer concerns - Interpreting a decision letter and setting expectations - Understanding what reviewers and editors weigh at SF specifically - Estimating timeline (the journal reports a ~71-day median review-to-decision; 待核实) ## How SF review works 1. **Double-anonymized.** Reviewers do not know the authors and authors do not know reviewers. Anonymize the manuscript accordingly; all identifying material lives on a separate title page (see `sf-submission`). 2. **Editorial screening.** The editorial office assesses fit for a **general social-science audience** and basic soundness before sending out for external review; poorly fit or under-developed papers can be declined without full rev
- When to trigger
- How SF review works
- Shape the paper to pass
- Anti-patterns
- Reading an SF decision letter
- Review-risk pass for Social Forces
- Output format
- Supplementary resources
What does the sf-review-process skill do?
Use to understand how Social Forces (SF) evaluates a manuscript — double-anonymized review via ScholarOne, what expert reviewers weigh (rigor, general significance, theoretical grounding), the typical decision categories, and the journal's reported review timeline. Sets expectations and shapes the paper to survive review; it does not contact editors.
How do I install it?
Run `npx skills add brycewang-stanford/Awesome-Journal-Skills --skill sf-review-process --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.