Agent skill · Code Review & Quality

book-research-assistant

Plan, orchestrate, and validate deep research for nonfiction books. Use when an author has completed book architecture and needs to fill research gaps before outlining chapters. Triggers include requests to plan research, generate research prompts, validate research quality, or prepare for drafting. This skill does everything around deep research—planning, prompting, validating, synthesizing—but the actual research execution happens externally via Claude and Gemini deep research. Requires upstream documents from book-architect (Research Gaps Document, Master Architecture Document, Section Blue

majiayu000github.com/majiayu000GitHub ↗
claude-codeMIT
Install
npx skills add majiayu000/claude-skill-registry --skill book-research-assistant --agent claude-code

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

Facts
Files in the skill folder: 2
SKILL.md size: 14 KB
Bundled scripts: none
Path: skills/analysis/book-research-assistant/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 Assistant Plan, orchestrate, and validate deep research for nonfiction books. This skill is the research quality gate—it does everything around the research (planning, prompting, validating, organizing, certifying readiness) while you execute the actual deep research using Claude and Gemini. ## Core Philosophy 1. **Reader-first research.** Every gap filled, every source vetted, every question asked serves the reader's transformation. Research isn't academic exercise—it's ammunition for changing someone's mind. 2. **Expert directness.** Be honest about weak evidence, thesis tensions, and gaps that aren't filled. No coddling, no hedging, no ego protection. Adults serving readers. 3. **Precision over speed.** Research is foundation. A book built on shaky evidence fails readers. Take the time to get it right, one gap at a time. 4. **Truth over thesis.** If research contradicts the book's argument, surface it immediately. Better to know now than publish a book that falls apart under scrutiny. 5. **Systematic rigor.** Follow the process. Every gap validated against all dimensions. Every chapter completed before moving on. Discipline protects quality. 6. **Verify everything.**

What's inside
Steps it walks through
  1. Core Philosophy
  2. Two Phases
  3. Session Flow
  4. Session Start: Smart Triage
  5. Phase 1: Research Planning
  6. Phase 2: Research Validation
  7. Chapter Completion
  8. Book Completion
  9. Session End
  10. Inputs
  11. Outputs
  12. Readiness Criteria
  13. Handoff
  14. References
Ships with 1 file
  • metadata.json
More from claude-skill-registry
All skills →
About this skill
What does the book-research-assistant skill do?

Plan, orchestrate, and validate deep research for nonfiction books. Use when an author has completed book architecture and needs to fill research gaps before outlining chapters. Triggers include requests to plan research, generate research prompts, validate research quality, or prepare for drafting. This skill does everything around deep research—planning, prompting, validating, synthesizing—but the actual research execution happens externally via Claude and Gemini deep research. Requires upstream documents from book-architect (Research Gaps Document, Master Architecture Document, Section Blue

How do I install it?

Run `npx skills add majiayu000/claude-skill-registry --skill book-research-assistant --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