mcpbeat

Book Research Assistant

robertguss/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 Blueprints) and book-ideation (Book Concept Document).

40k tokens
context cost
the whole folder, loaded on every use
19
files
instructions only
0
copies elsewhere
how many repositories repackaged it
102
stars on the repo
on the repository, not the skill itself

Install

one command, takes just this skill from the repository
npx skills add https://github.com/robertguss/claude-code-toolkit --skill book-research-assistant

What comes with it

144 470 bytes besides the instruction
assets/templates/book-level-tracker-template.md
assets/templates/chapter-research-summary-template.md
assets/templates/chapter-research-tracker-template.md
assets/templates/final-research-synthesis-template.md
assets/templates/follow-up-prompt-template.md
assets/templates/research-output-format-example.md
assets/templates/research-prompt-template.md
assets/templates/validation-checklist-template.md
references/citation-standards.md
references/contradiction-reconciliation.md
references/contrarian-research-strategies.md
references/deep-research-prompting.md
references/evidence-types-catalog.md
references/proof-burden-matching.md
references/research-output-format.md
references/research-question-formulation.md
references/source-evaluation-guide.md
references/synthesis-best-practices.md

The instruction itself

16 sections, as written by the author

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

  • 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.

  • 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.

  • 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.

  • 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.

  • Systematic rigor. Follow the process. Every gap validated against all

dimensions. Every chapter completed before moving on. Discipline protects

quality.

  • Verify everything. LLM research can hallucinate. Sources need checking.

Confidence flags matter. Skepticism serves accuracy.

Two Phases

This skill operates in two distinct phases:

Phase 1: Research Planning

  • Review and expand gaps from book-architect
  • Generate self-contained research prompts
  • Initialize tracking documents

Phase 2: Research Validation

  • Review research outputs gap by gap
  • Render verdicts (Complete, Needs More, Problematic)
  • Produce chapter summaries
  • Certify readiness for next phase

Session Flow

Session Start: Smart Triage

Guide the user to the right entry point through conversational triage.

Question 1: "Are you starting fresh on a new book's research, or continuing

work already in progress?"

If starting fresh:

  • Request required documents:
  • Research Gaps Document (from book-architect) — required
  • Book Concept Document (from book-ideation) — required
  • Master Architecture Document (from book-architect) — required
  • Section Blueprint Documents (from book-architect) — required
  • Initialize Book-Level Research Tracker
  • Begin with first chapter

If continuing:

  • Request Book-Level Research Tracker
  • Read status and determine where things stand
  • Ask: "Do you have research to review, or are you picking up where we left

off?"

Smart routing based on context:

| Scenario | What to Request | Next Action |

| ------------------------------ | ----------------------------------------------------- | --------------------------------------------- |

| New book, first chapter | All upstream docs | Initialize trackers, start Chapter 1 planning |

| Continuing, new chapter | Book-Level Tracker | Initialize Chapter Tracker, begin planning |

| Continuing, validation | Book-Level Tracker + Chapter Tracker + research files | Begin gap-by-gap validation |

| Continuing, follow-up round | Trackers + additional research | Continue validation |

| Jumping chapters | Book-Level Tracker | Confirm intent, start new chapter |

| Revisiting complete chapter | Both trackers | Understand why, reopen if needed |

| Architecture changed | All trackers + revised architecture docs | Reconcile and update |

| Thesis pivot | All docs | Assess impact, regenerate affected prompts |

| Prompt refinement | Chapter Tracker + prompts to refine | Revise before execution |

| Partial validation | Trackers + partial research | Validate what's available |

| External research integration | Trackers + external material | Validate against gaps |

| Research audit/status briefing | Book-Level Tracker | Provide status overview |

| Final synthesis | All Chapter Summaries + Book-Level Tracker | Produce Final Research Synthesis |

Always tell the user what documents to upload based on their situation. If they

don't have something, help them understand what's needed and how to proceed.

Phase 1: Research Planning

Step 1: Review Architect's Gaps

Load references/research-question-formulation.md as needed.

  • Read the Research Gaps Document from book-architect
  • Assess each gap: Is it well-formed? Specific enough? Missing anything?
  • Identify gaps architect may have missed (cross-reference thesis, proof

burdens, key claims)

  • Note where gaps need splitting into multiple questions

Step 2: Expand and Enhance Gaps

For each gap, determine:

  • What TYPE of evidence is needed? (Load references/evidence-types-catalog.md)
  • What's the proof burden? (Load references/proof-burden-matching.md)
  • How much is enough for this chapter's use?
  • What sources should be prioritized? (Load

references/source-evaluation-guide.md)

Step 3: Initialize Chapter Research Tracker

Create tracker with all gaps:

  • Gap ID (e.g., CH03-GAP-01)
  • Origin (Architect / RA-Expanded / RA-Added)
  • Priority (P1 / P2 / P3)
  • Description
  • Evidence type needed
  • Status: Prompt Ready
  • Model coverage: Not Started
  • Quality verdict: Pending
  • Notes

Step 4: Generate Research Prompts

Load references/deep-research-prompting.md and

references/research-output-format.md.

For each gap, create a self-contained prompt file following

assets/templates/research-prompt-template.md:

  • Book Context — Thesis, reader, transformation, author angle, enemy

(condensed)

  • Chapter Context — Number, title, position in arc, purpose, entry/exit

states, key insight

  • The Research Gap — Gap ID, priority, clear statement, why it matters
  • Author's Existing Position — What's known, what's genuinely unknown
  • Evidence Type Needed — Statistics, case studies, quotes, examples,

counterarguments

  • Scope & Boundaries — Depth calibration, recency requirements, geographic

scope, what NOT to include

  • Source Requirements — Full bibliographic info, Chicago format, primary

vs. secondary distinction, verification confidence flags, source strength

assessment, accessibility notes, conflicting sources flagged

  • Quality Criteria — What "good enough" looks like, minimum threshold,

source hierarchy

  • Search Guidance — Angles, terms, source types, experts to find

10. Special Requests — Quotability, steelman, expert identification, visual

opportunities, connection flags

11. Output Format — Required structure per

references/research-output-format.md

Save each prompt as individual file: chapter-XX-gap-XX-[short-description].md

Step 5: Update Trackers

  • Mark all gaps as "Prompt Ready" in Chapter Tracker
  • Update Book-Level Tracker to show chapter "In Progress"

Phase 2: Research Validation

Execution Model: One gap at a time. Precision over speed.

Step 1: Confirm Gap

State which gap is being validated (by ID and description).

Step 2: Request Research

Ask user to attach:

  • Claude's deep research output for this gap
  • Gemini's deep research output for this gap

Step 3: Thorough Review

Load references/source-evaluation-guide.md and

references/contradiction-reconciliation.md as needed.

Assess against seven dimensions (use

assets/templates/validation-checklist-template.md):

| Dimension | Question |

| ------------------- | ------------------------------------------------------------------- |

| Coverage | Did the research actually answer the question, or drift? |

| Depth | Is there enough evidence for how the chapter will use it? |

| Source Quality | Are sources verifiable, authoritative, properly cited? |

| Contradiction Check | Did Claude and Gemini agree? Conflicts needing reconciliation? |

| Thesis Tension | Did anything challenge or complicate the book's thesis? |

| Usability | Is this actually usable for drafting? Specific, quotable, concrete? |

| Gap Spawning | Did answering this reveal NEW gaps? |

Step 4: Render Verdict

Complete: Research satisfies all dimensions. Gap is filled.

Needs More: Research fell short. Specify what's missing. Generate follow-up

prompt using assets/templates/follow-up-prompt-template.md.

Problematic: Thesis tension or serious issue requiring author decision.

Surface clearly. Do not proceed until resolved.

Step 5: Update Chapter Tracker

  • Update status
  • Record model coverage (Claude / Gemini / Both)
  • Record quality verdict
  • Add notes
  • If gap spawned new gaps, add them with Origin: RA-Added

Step 6: Proceed to Next Gap

Repeat until all gaps for chapter are validated.

Chapter Completion

When all gaps for a chapter are validated, check readiness criteria:

Chapter Research Readiness Checklist:

  • All P1 gaps marked Complete
  • All P2 gaps marked Complete or explicitly deferred with rationale
  • P3 gaps addressed or consciously skipped
  • No unresolved "Problematic" verdicts
  • Both models (Claude + Gemini) run for P1 gaps
  • Source quality sufficient for downstream fact-checking
  • No critical gap-spawned items remain unaddressed

If criteria met:

  • Produce Chapter Research Summary (see

assets/templates/chapter-research-summary-template.md)

  • Update Book-Level Tracker to show chapter Complete
  • Announce readiness for next chapter

If criteria not met: Identify what's missing and guide user to resolution.

Book Completion

When all chapters show Complete on Book-Level Tracker:

  • Gather all Chapter Research Summaries
  • Produce Final Research Synthesis (see

assets/templates/final-research-synthesis-template.md)

  • Extract and consolidate Architecture Feedback across all chapters
  • Render final readiness verdict for handoff to chapter-outline skill

Session End

Always conclude by:

  • Updating relevant trackers
  • Stating current status clearly
  • Identifying what to bring to next session
  • Providing clear next steps

Inputs

Required:

  • Research Gaps Document (from book-architect)
  • Book Concept Document (from book-ideation)
  • Master Architecture Document (from book-architect)
  • Section Blueprint Documents (from book-architect)

During Validation:

  • Research outputs from Claude and Gemini (attached per gap)

For Continuing Sessions:

  • Book-Level Research Tracker
  • Chapter Research Tracker (if mid-chapter)

Outputs

Tracking Documents:

  • Book-Level Research Tracker — Status of all chapters
  • Chapter Research Tracker — Gaps, statuses, verdicts for each chapter

Planning Phase:

  • Research Prompt Files — One per gap, fully self-contained
  • Follow-up Prompt Files — Lighter format for "Needs More" scenarios

Validation Phase:

  • Chapter Research Summary — Distillation of findings, includes Architecture

Feedback section

Final Outputs:

  • Final Research Synthesis — Book-wide synthesis, consolidated architecture

feedback, readiness certification

Readiness Criteria

Research phase is complete when:

  • All chapters show Complete on Book-Level Tracker
  • All Chapter Research Summaries produced
  • Final Research Synthesis completed
  • All P1 and P2 gaps across the book are filled
  • No unresolved Problematic verdicts
  • Architecture feedback consolidated and ready for upstream review
  • Author confirms readiness to proceed

Handoff

Downstream:

  • chapter-outline skill receives:
  • Final Research Synthesis
  • All Chapter Research Summaries
  • Book-Level Research Tracker (all green)

Upstream (if needed):

  • book-architect receives:
  • Architecture Feedback (consolidated from Chapter Research Summaries)
  • For structural revisions if research revealed problems

References

Load as needed based on the work at hand:

  • references/source-evaluation-guide.md — Assessing source quality, hierarchy,

red flags

  • references/evidence-types-catalog.md — Types of evidence and when each is

appropriate

  • references/research-question-formulation.md — Turning gaps into sharp,

researchable questions

  • references/citation-standards.md — Chicago format, complete bibliographic

requirements

  • references/deep-research-prompting.md — Best practices for Claude and Gemini

deep research

  • references/contradiction-reconciliation.md — Handling conflicts between

sources and models

  • references/proof-burden-matching.md — What evidence level different claims

require

  • references/synthesis-best-practices.md — Distilling research into useful

summaries

  • references/contrarian-research-strategies.md — Researching claims against

conventional wisdom

  • references/research-output-format.md — Standard format for research outputs

Templates

Output document templates in assets/templates/:

  • book-level-tracker-template.md
  • chapter-research-tracker-template.md
  • research-prompt-template.md
  • follow-up-prompt-template.md
  • chapter-research-summary-template.md
  • final-research-synthesis-template.md
  • research-output-format-example.md
  • validation-checklist-template.md

How to use it

Copy the folder

Take robertguss/book-research-assistant from the repository into ~/.claude/skills for personal use, or into .claude/skills inside a project.

Check the name does not clash

The agent identifies a skill by the name field in its header. Two skills with the same name cannot sit side by side — one of them will be ignored.