suggesting-reviewers

Suggesting reviewers or associate editors

Given a manuscript abstract, propose either peer reviewers or an associate editor (AE) to handle the paper, and explain each candidate's fit. Default journal: Organizational Research Methods (ORM).

Mode — reviewer vs. AE

Detect the mode from the request and announce which one you are running.

• Reviewer mode (default — "suggest reviewers", "find referees", …). Two pools: editorial-board members (filtered by eligibility, matched against pre-built profiles) and external experts (found live from the abstract's topics).
• AE mode ("suggest an AE", "assign an associate editor", "who should handle this paper", …). One pool: the journal's current associate editors. No external search — an AE must be a sitting board officer.

The two modes share everything below except the two steps that explicitly branch (Step 2 eligibility, Step 4 candidate lists). If the request is ambiguous, ask which is wanted before proceeding.

Core principle — combine knowledge with retrieval

Training knowledge is a useful starting point: it maps the field and knows established scholars. But it has two blind spots — lesser-known / junior researchers and very recent work — and those are exactly where this skill adds value. So every run must augment training recall with retrieval: the pre-built board profiles plus live OpenAlex / Semantic Scholar searches that deliberately reach for recent and less-visible names.

Ground each final suggestion in a retrieved publication record wherever one exists — and especially for the less-famous names, where training recall is least reliable. Never put a junior or unfamiliar person in the output on memory alone.

Step 1 — Load the roster and check staleness

The bundled ORM data lives under the plugin root:

${CLAUDE_PLUGIN_ROOT}/skills/suggesting-reviewers/rosters/orm/
  index.md            # membership + role + eligible: yes/no, with snapshot_date
  profiles/<surname>.md