peer-review-ops

Audit academic peer review operations -- reviewer matching algorithms, conflict of interest detection, turnaround time optimization, review quality scoring, and editorial workflow management. Covers COPE guidelines compliance, COI screening (co-authorship, affiliation, funding), blinding enforcement, reviewer pool health metrics, ORCID/CrossRef integration, and plagiarism detection workflows. Supports ScholarOne, Editorial Manager, OJS, and custom editorial platforms. Use when optimizing reviewer assignment, reducing manuscript turnaround, auditing COI detection, or evaluating COPE compliance. It's a reusable SKILL.md instruction set that loads into your AI coding assistant on demand, no prompt engineering, no copy-pasting every session.

Run `npx @skills-hub-ai/cli install peer-review-ops` from your terminal. The CLI writes the SKILL.md to the correct location for your AI tool (e.g. ~/.claude/skills/peer-review-ops/ for Claude Code or ~/.cursor/skills/ for Cursor with --target cursor) and adds it to your project's .skills.json lockfile.

peer-review-ops runs in Claude Code. It follows the open Agent Skills standard (SKILL.md), so the same skill works in every supported tool without modification.

Yes. Every skill on skills-hub.ai is free and open-source. There are no premium tiers, paywalls, or usage limits. You only pay for whatever AI assistant you're already using.

In Claude Code, type `/peer-review-ops` (or whatever slash command the skill registers) and the AI follows the skill's instructions immediately. You can also reference it by name in natural language, your AI loads the skill into context when relevant.

Yes. Commit your project's .skills.json lockfile and teammates run `npx @skills-hub-ai/cli install` (no args) to install every skill at the exact version you pinned. Organization-scoped installs work via skills-hub.ai organizations.