Skip to content
Content
Skill

/book-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

From plugin
robertguss-claude-code-toolkit
11629 skills7 agents4 commands
Install
$ npx -y skills add robertguss/claude-code-toolkit --skill book-research-assistant --agent claude-code

How it fires

How this skill gets triggered: by you, by Claude, or both.

  • Fires itselfAuto-invocation. Claude auto-loads it when your prompt matches the work.Auto-invocation is when the right skill fires by itself at the right moment, driven by a FLOW.md router and a hook, instead of you invoking it by name. It is the difference between a skill being installed and a skill actually getting used.Read the full definition →
  • You can call itInvoke it directly when you want it.
  • Slash command/book-research-assistant

Context preview

The summary Claude sees to decide when to auto-load this skill.

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

SKILL.md

book-research-assistant.SKILL.md
name: book-research-assistant
license: Proprietary
metadata:
  author: robertguss
  version: "1.0"
description:
  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).

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 in
Read more
Ships withrobertguss-claude-code-toolkit

Extend Claude Code with specialized workflows, automatic formatting, and better defaults. Skills give Claude domain expertise—brainstorming methods, documentation generation, book writing pipelines.

Get the whole plugin