agentsclimarketplace

Book research assistant

Skill bg-szy/TOP-SKILLS/skills/claude-code-toolkit/book-research-assistant

全球最大的 Claude Code 技能聚合库 · 收录 3900+ 来自 12+ 来源的技能,提供在线搜索与趋势分析看板 / The world's largest Claude Code skill aggregation hub — 3900+ skills from 12+ sources with online search and trend dashboardFrom the repository description

Install
npx -y skills add bg-szy/TOP-SKILLS --skill book-research-assistant

Assembled from the repository path, not quoted from the project. Check it against their README if it does not work.

2 things to look at

  • no licenseNo license file was found in the repository. Code published without one is not open source by default, so using it at work is a question for whoever answers licensing questions where you are.
  • 4 stars4 stars. Stars are a popularity signal and not a quality one, but at this level it is likely that nobody has read this closely except its author, and you would be relying on your own review.

What its file declares

Copied from the file, not written here

The file declares its own license as Proprietary. That is the author’s claim about this one file, and it is not the same thing as the license GitHub reports for the repository, which is listed with the other numbers below.

SKILL.md

14.4 KB, ~2.9k tokens by cl100k_base, as published. Nobody here has run it

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:

ScenarioWhat to RequestNext Action
New book, first chapterAll upstream docsInitialize trackers, start Chapter 1 planning
Continuing, new chapterBook-Level TrackerInitialize Chapter Tracker, begin planning
Continuing, validationBook-Level Tracker + Chapter Tracker + research filesBegin gap-by-gap validation
Continuing, follow-up roundTrackers + additional researchContinue validation
Jumping chaptersBook-Level TrackerConfirm intent, start new chapter
Revisiting complete chapterBoth trackersUnderstand why, reopen if needed
Architecture changedAll trackers + revised architecture docsReconcile and update
Thesis pivotAll docsAssess impact, regenerate affected prompts
Prompt refinementChapter Tracker + prompts to refineRevise before execution
Partial validationTrackers + partial researchValidate what's available
External research integrationTrackers + external materialValidate against gaps
Research audit/status briefingBook-Level TrackerProvide status overview
Final synthesisAll Chapter Summaries + Book-Level TrackerProduce 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):

DimensionQuestion
CoverageDid the research actually answer the question, or drift?
DepthIs there enough evidence for how the chapter will use it?
Source QualityAre sources verifiable, authoritative, properly cited?
Contradiction CheckDid Claude and Gemini agree? Conflicts needing reconciliation?
Thesis TensionDid anything challenge or complicate the book's thesis?
UsabilityIs this actually usable for drafting? Specific, quotable, concrete?
Gap SpawningDid 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

What ships with it

Read from the repository

Just SKILL.md. No reference files, no scripts.

Gives 0 of the 12 instructions most research analysis skills give in ~2.9k tokens

Counted across 1,063 of the 1,754 authors here whose files we hold, read 2026-08-07

  • Generate a markdown reportin 32 of 1063, across 23 files
  • Cite each claim's sourcein 30 of 1063, across 15 files
  • Define the ideal customer profilein 20 of 1063, across 2 files
  • Search for companies matching the criteriain 20 of 1063, across 2 files
  • Assign a fit score from one to tenin 20 of 1063, across 2 files
  • Analyze the codebase to understand the productin 19 of 1063, across 1 file
  • Ask clarifying questions about the value propositionin 19 of 1063, across 1 file
  • Look for signals of immediate needin 19 of 1063, across 1 file
  • Identify the target decision maker rolein 19 of 1063, across 1 file
  • Suggest a personalized contact strategyin 19 of 1063, across 1 file
  • Provide conversation starters for outreachin 19 of 1063, across 1 file
  • Format results in a scannable markdown templatein 19 of 1063, across 1 file

Grouped from the skills themselves: near-identical wordings counted once, and counted by distinct author, so one author publishing three of these counts once. Length counted with cl100k_base; the agent that loads this file may tokenize it differently.

Keep looking

Skills are one crate of 326,790. Ordering is by how many stacks a row turns up in, so the top of any crate is what has actually been picked rather than what has the most stars.