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

56 stars

Best use case

book-research-assistant is best used when you need a repeatable AI agent workflow instead of a one-off prompt.

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

Teams using book-research-assistant should expect a more consistent output, faster repeated execution, less prompt rewriting.

When to use this skill

  • You want a reusable workflow that can be run more than once with consistent structure.

When not to use this skill

  • You only need a quick one-off answer and do not need a reusable workflow.
  • You cannot install or maintain the underlying files, dependencies, or repository context.

Installation

Claude Code / Cursor / Codex

$curl -o ~/.claude/skills/book-research-assistant/SKILL.md --create-dirs "https://raw.githubusercontent.com/robertguss/claude-code-toolkit/main/skills/non-fiction-book-factory/book-research-assistant/SKILL.md"

Manual Installation

  1. Download SKILL.md from GitHub
  2. Place it in .claude/skills/book-research-assistant/SKILL.md inside your project
  3. Restart your AI agent — it will auto-discover the skill

How book-research-assistant Compares

Feature / Agentbook-research-assistantStandard Approach
Platform SupportNot specifiedLimited / Varies
Context Awareness High Baseline
Installation ComplexityUnknownN/A

Frequently Asked Questions

What does this 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 Blueprints) and book-ideation (Book Concept Document).

Where can I find the source code?

You can find the source code on GitHub using the link provided at the top of the page.

Related Guides

SKILL.md Source

# 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.** 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`:

1. **Book Context** — Thesis, reader, transformation, author angle, enemy
   (condensed)
2. **Chapter Context** — Number, title, position in arc, purpose, entry/exit
   states, key insight
3. **The Research Gap** — Gap ID, priority, clear statement, why it matters
4. **Author's Existing Position** — What's known, what's genuinely unknown
5. **Evidence Type Needed** — Statistics, case studies, quotes, examples,
   counterarguments
6. **Scope & Boundaries** — Depth calibration, recency requirements, geographic
   scope, what NOT to include
7. **Source Requirements** — Full bibliographic info, Chicago format, primary
   vs. secondary distinction, verification confidence flags, source strength
   assessment, accessibility notes, conflicting sources flagged
8. **Quality Criteria** — What "good enough" looks like, minimum threshold,
   source hierarchy
9. **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:**

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

**If criteria met:**

1. Produce Chapter Research Summary (see
   `assets/templates/chapter-research-summary-template.md`)
2. Update Book-Level Tracker to show chapter Complete
3. 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:

1. Gather all Chapter Research Summaries
2. Produce Final Research Synthesis (see
   `assets/templates/final-research-synthesis-template.md`)
3. Extract and consolidate Architecture Feedback across all chapters
4. Render final readiness verdict for handoff to chapter-outline skill

### Session End

Always conclude by:

1. Updating relevant trackers
2. Stating current status clearly
3. Identifying what to bring to next session
4. 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:

1. All chapters show Complete on Book-Level Tracker
2. All Chapter Research Summaries produced
3. Final Research Synthesis completed
4. All P1 and P2 gaps across the book are filled
5. No unresolved Problematic verdicts
6. Architecture feedback consolidated and ready for upstream review
7. 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`

Related Skills

book-market-research

56
from robertguss/claude-code-toolkit

Assess commercial viability of book concepts for Amazon KDP self-publishing. Use when the user has a Book Concept Document and wants to understand market demand, competition, pricing, and positioning before committing to write. Produces a Market Research Report with viability scorecard and Go/No-Go recommendation. Works standalone (commercial analysis only) or after idea-validator (integrated assessment). Nonfiction only.

book-ideation

56
from robertguss/claude-code-toolkit

Develop raw book ideas into structured nonfiction book concepts. Use when the user wants to develop a book idea, has brainstorm documents to refine into a book concept, wants to articulate a book's thesis/promise/reader/transformation, or needs to prepare a book concept for validation and market research. Nonfiction only. Produces a Book Concept Document with all elements needed for downstream skills (idea-validator, market-research, book-architect).

book-idea-validator

56
from robertguss/claude-code-toolkit

Stress-test book concepts against existing research before committing to architecture. Use when the user has a Book Concept Document ready for validation, wants to verify their thesis is defensible, needs to understand the competitive intellectual landscape, or wants honest assessment of their idea's strengths and weaknesses. Produces a Validation Report that informs the Go/No-Go decision. Nonfiction only.

book-architect

56
from robertguss/claude-code-toolkit

Design the structural and emotional architecture for nonfiction books. Use when an author has a validated book concept and needs to create the blueprint before drafting. Triggers include requests to structure a book, create a chapter outline, design a table of contents, map the reader's journey, or plan book organization. Requires upstream documents from book-ideation (Book Concept Document) and optionally from idea-validator (Validation Report) and market-research (Market Research Report).

app-store-opportunity-research

56
from robertguss/claude-code-toolkit

Full-pipeline iOS App Store opportunity research. Discovers underserved niches, analyzes competitor gaps, estimates revenue, produces scored top-3 opportunity reports, and writes MVP PRDs — all through browser and web research. Use when the user wants to find profitable iOS app ideas, research App Store charts, analyze competitor apps (ratings, reviews, revenue, gaps), generate opportunity reports, or write MVP PRDs. Triggers on "find app opportunities", "app store research", "what app should I build", "research this app category", "find a gap in the app store", "ios app ideas".

app-growth-playbook

56
from robertguss/claude-code-toolkit

Generate platform-specific, actionable growth playbooks for mobile apps. Use when planning a Product Hunt launch, creating TikTok/Reels content strategies, setting up Apple Search Ads campaigns, preparing App Store featuring submissions, building referral loops, designing email/push re-engagement campaigns, writing Reddit launch posts, or creating content marketing plans for app growth. Provides templates, scripts, timing guides, and step-by-step processes — not generic advice.

ebook-discovery

56
from robertguss/claude-code-toolkit

Surface ebook ideas you didn't know you had. Use when ready to discover what ebooks might be hiding in your content, expertise, or thinking. Supports both content-rich creators (blog posts, videos, newsletters) and those with unpublished expertise. Produces a curated list of ebook candidates ready for Concept Development. Handles multi-session discovery with living documents.

ebook-concept-development

56
from robertguss/claude-code-toolkit

Develop ebook ideas into structured concepts ready for architecture. Use when the user has an ebook idea (from a brainstorm document, existing content to repurpose, a book section to extract, or a fresh concept) and wants to develop it into a clear, validated concept. Produces an Ebook Concept Document with reader, transformation, promise, content source, scope/format, and key topics. Handles multi-session development with living documents.

writing-dna-discovery

56
from robertguss/claude-code-toolkit

Capture a writer's voice DNA through collaborative interview and sample analysis. Use when someone wants to document their writing voice for use with a ghost writer skill. Produces a Voice DNA Document with patterns, anti-patterns, and actionable guidance. Handles one register/mode per session, supports refinement over time.

ghost-writer

56
from robertguss/claude-code-toolkit

Produce first drafts that match a writer's authentic voice using their Voice DNA Document. Consumes DNA documents from writing-dna-discovery skill. Generates 2 meaningfully different drafts with headlines, confidence assessment, decision notes, and DNA refinement suggestions. Collaborative partner that evaluates, pushes back, and advocates for quality. Handles blog posts, essays, newsletters, and more.

chapter-architect

56
from robertguss/claude-code-toolkit

Plan and architect a single chapter at beat-level granularity. Use when you have a chapter from the Architecture Document and need to create a detailed outline before drafting. Produces a Chapter Outline Document for use by draft-coach or ghostwriter.

paywall-pricing-optimizer

56
from robertguss/claude-code-toolkit

Design effective paywalls, structure subscription tiers, and optimize pricing for mobile apps. Covers monetization model selection, paywall screen design, pricing psychology, A/B testing strategy, and RevenueCat/StoreKit/Google Billing integration. Use when the user wants to monetize an app, design a paywall, choose between subscription vs one-time purchase, set pricing tiers, improve conversion rates, plan pricing experiments, or integrate in-app purchases. Triggers on "design my paywall", "how should I price my app", "subscription tiers", "monetization strategy", "paywall copy", "free trial length", "RevenueCat setup", "improve paywall conversion".