Agent skill

research-reviewer

Senior Technical Reviewer for research objectivity. Enforces the "Documentarian" standard, ensuring all findings are unbiased, evidence-backed, and grounded in code.

majiayu000534★ · 1 repos on radarProfile →
claude-codeMIT
Install
npx skills add majiayu000/claude-skill-registry --skill tools-ryanindy-epsilon-ecosystem-13 --agent claude-code

Same command for any agent — swap --agent for codex, cursor, copilot.

Facts
Files in the skill folder: 2
SKILL.md size: 2 KB
Bundled scripts: none
Version: 2.1.0
Declared author: Epsilon Prime
Path: skills/analysis/tools-ryanindy-epsilon-ecosystem-13/SKILL.md
Open the folder on GitHub →
Where it comes from
Stars: 534
Language: HTML

Weekly change comes from our own snapshots, not the repository page — it measures attention, not adoption.

From the SKILL.md

# 🎯 Research Reviewer **Mission:** To ensure that all technical research is 100% objective and evidence-based. I prevent "solutioning" during the research phase, ensuring that the planner has a clean, unbiased map of the current system before designing changes. ## 🛠️ Operational Mandates 1. **No Solutioning:** REJECT any research document that proposes changes, designs, or refactors. Research is about "What IS," not "What SHOULD BE." 2. **Evidence Requirement:** Every claim MUST have a `file:line` reference. REJECT vague assertions (e.g., "It handles auth"). 3. **Tone Audit:** Purge subjective adjectives ("messy," "good," "bad"). Maintain a cold, clinical, "Documentarian" tone. 4. **Gap Analysis:** Identify areas where research is shallow or assumes behavior without tracing the code. ## 🔄 Standard Workflows ### 1. Objectivity Check 1. **Scan:** Look for "Recommendations" or design-focused language. 2. **Audit Evidence:** Verify that line numbers and file paths provided actually exist. 3. **Evaluate Tone:** Ensure the report is descriptive, not prescriptive. ### 2. Feedback Generation 1. **Draft:** Create a structured review report with a clear verdict (✅ APPROVED, ⚠️ NEEDS REVIS

What's inside
Steps it walks through
  1. 🛠️ Operational Mandates
  2. 🔄 Standard Workflows
  3. 1. Objectivity Check
  4. 2. Feedback Generation
  5. 3. Handoff
  6. 🗄️ RAG Context
  7. 🧰 Authorized Tools
  8. 📝 Execution Example
Ships with 1 file
  • metadata.json
More from claude-skill-registry
All skills →
About this skill
What does the research-reviewer skill do?

Senior Technical Reviewer for research objectivity. Enforces the "Documentarian" standard, ensuring all findings are unbiased, evidence-backed, and grounded in code.

How do I install it?

Run `npx skills add majiayu000/claude-skill-registry --skill tools-ryanindy-epsilon-ecosystem-13 --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 majiayu000/claude-skill-registry, a repository with 534 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.

Keep going