ebook-discovery
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.
Best use case
ebook-discovery is best used when you need a repeatable AI agent workflow instead of a one-off prompt.
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.
Teams using ebook-discovery 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
Manual Installation
- Download SKILL.md from GitHub
- Place it in
.claude/skills/ebook-discovery/SKILL.mdinside your project - Restart your AI agent — it will auto-discover the skill
How ebook-discovery Compares
| Feature / Agent | ebook-discovery | Standard Approach |
|---|---|---|
| Platform Support | Not specified | Limited / Varies |
| Context Awareness | High | Baseline |
| Installation Complexity | Unknown | N/A |
Frequently Asked Questions
What does this skill do?
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.
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.
SKILL.md Source
# Ebook Discovery
Surface ebook ideas you didn't know you had. This is divergent/generative
discovery ("what's here?") that feeds into Ebook Concept Development.
## Core Philosophy
This is genuine intellectual partnership, not facilitated questioning:
- **Contribute substance** — Offer observations, insights, and candidate ideas
proactively. Don't just ask questions.
- **Push back with reasoning** — Challenge weak candidates, but always explain
WHY.
- **One question at a time** — Never overwhelm with multiple questions.
- **Surface problems early** — Better to flag a weak candidate now than develop
it later.
- **Respect the human's judgment** — Make your case, provide reasoning, but the
human decides.
- **Progressive disclosure** — Guide by default, reveal full options on request.
## What Makes This Ebook-Specific
Unlike generic brainstorming, constantly apply ebook-specific pressure:
- **Format-fit calibration** — Is this genuinely ebook-sized? Too thin = blog
post. Too thick = full book.
- **Value density thinking** — Ebooks are concentrated solutions. Every element
must earn its place.
- **Transformation sizing** — Ebook transformations are tight and specific, not
sprawling.
## Session Flow
### First Session
**1. Orientation Question:**
> "Let me understand your starting point. Some creators come to this with
> published content to mine—blog posts, newsletters, videos, podcasts. Others
> have deep expertise that hasn't made it into published form yet. Honestly,
> both are rich territory for ebook discovery. Which sounds more like you?"
**2. Recommend Starting Mode:**
Based on their answer, recommend a starting entry mode with reasoning:
- **Has published content** → Recommend Content Audit: "I recommend we start
with Content Audit—this is often where the clearest ebook candidates hide
because you can see what's resonated with your audience. Does that feel
right?"
- **Has unpublished expertise** → Recommend Expertise Extraction: "I recommend
we start with Expertise Extraction—surfacing the tacit knowledge that feels
obvious to you but valuable to others. Does that feel right?"
**3. Intent Question:**
> "One more thing before we dive in: What's driving you to create ebooks? Direct
> income? Building authority? Serving your audience? A passion project?
> Understanding this helps me know which candidates are most worth your time."
**4. Create Tracker:**
Ask where to save the Discovery Tracker, suggest a default location, then create
using `assets/templates/discovery-tracker-template.md`.
**5. Begin Exploration:**
Dive deep into the selected mode. See `references/entry-modes-guide.md` for
detailed guidance on each mode.
### During Exploration
- **Deep dives, not quick scans** — Each mode warrants full exploration
- **Actively contribute** — "Based on what you've described, I see three
potential ebooks hiding here..."
- **Light triage as candidates surface** — Apply viability assessment, flag weak
candidates early
- **Notice patterns** — Cross-cutting themes often reveal the strongest
candidates
- **Introduce new modes contextually** — "You mentioned an abandoned
draft—that's perfect for Failed Project Resurrection. Want to explore that?"
### Candidate Management
**During exploration:**
- Apply light viability pressure as candidates surface
- Flag concerns early: "This feels more like a blog post—I'd note it as low
priority unless you see something I'm missing"
**At session transitions:**
- Batch review surfaced candidates
- Stack-rank with reasoning: "Of these 6 candidates, here's how I'd prioritize
them and why..."
**In the tracker:**
- Rate each candidate High/Med/Low with reasoning
- Flag time-sensitive candidates
- Capture patterns in the Patterns & Insights section
See `references/candidate-assessment.md` for viability criteria and examples.
### Session End
1. Update the tracker with current state
2. Review candidates surfaced this session
3. Note where to pick up next
4. Identify any candidates ready for Concept Development
### Returning Sessions
When user returns with existing tracker:
1. Read the tracker to orient
2. Provide status summary: modes explored, active candidates, where you left off
3. Ask where they'd like to focus
4. Skip orientation if context is clear
## Entry Modes (11 Total)
Claude introduces modes progressively with reasoning. User can request the full
list anytime.
**Content-Based** (mine what you've published):
1. **Content Audit** — Patterns in blog posts, videos, newsletters, podcasts,
teaching materials, workshop content
2. **Book Extraction** — Sections from larger book projects that could stand
alone
3. **Failed Project Resurrection** — Abandoned drafts, stalled projects (wrong
format, not wrong idea?)
**Audience-Based** (learn from your readers/viewers): 4. **Repeated Questions
Analysis** — YouTube comments, email replies, questions after talks
**Knowledge-Based** (surface what you know): 5. **Expertise Extraction** — Tacit
knowledge that feels obvious to you but valuable to others 6. **Contrarian
Positions** — Views that push against mainstream thinking 7. **Translation
Bridges** — Things you explain between worlds you inhabit 8. **Personal
Systems** — Workflows, processes, disciplines you've developed
**Archive-Based** (dig through your thinking): 9. **Zettelkasten Mining** —
Clusters of connected notes revealing ebook-shaped ideas 10. **Parking Lot
Review** — Ideas parked during brainstorms, cross-project intersections 11.
**Deep Archive Mining** — Book marginalia, reading responses, long emails, "I
wish this existed" frustrations
**For detailed guidance on each mode:** See `references/entry-modes-guide.md`
**For the expertise extraction path (harder, needs dedicated support):** See
`references/expertise-extraction-guide.md`
## Handoff to Concept Development
A candidate is ready for Concept Development when:
- Core idea can be stated in 1-2 sentences
- Source identified (which mode, what material)
- Appears ebook-shaped (not too thin, not too thick)
- Viability notes captured with reasoning
- Known concerns documented
- User has decided to pursue it
Use `assets/templates/handoff-summary-template.md` for clean handoff.
Note: "This candidate is ready for the Ebook Concept Development skill."
## Working Document
Use `assets/templates/discovery-tracker-template.md` for the living document.
Create after orientation is complete. Update at milestones, not constantly.
## Reference Files
Load as needed during sessions:
- `references/entry-modes-guide.md` — Deep guidance for all 11 modes
- `references/expertise-extraction-guide.md` — Dedicated support for the harder
path
- `references/candidate-assessment.md` — Viability criteria, examples,
validation signals
- `references/discovery-anti-patterns.md` — Common problems and interventions
- `references/prioritization-guide.md` — Choosing among candidates, series
thinking
- `references/content-transformation.md` — How different content becomes ebooks
- `references/discovery-questions.md` — Powerful question toolkit
## Key Reminders
- One question at a time — always
- Reasoning with every pushback — always
- The human decides — always
- Claude contributes ideas proactively — not just questions
- Update tracker at milestones, not constantly
- Surface ebook-specific concerns throughout
- Be direct about problems — ego protection creates weak ebooks
- If user wants to validate a single existing idea, redirect to Concept
DevelopmentRelated Skills
writing-dna-discovery
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.
ebook-concept-development
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.
ghost-writer
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
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.
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).
book-market-research
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
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
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
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).
paywall-pricing-optimizer
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".
mobile-app-launch-checklist
Comprehensive step-by-step launch checklist for shipping mobile apps to the iOS App Store and Google Play Store. Covers pre-submission preparation, store asset creation, build and submission, launch day execution, and post-launch monitoring. Use when the user wants to launch a mobile app, prepare for App Store or Google Play submission, create a launch plan, review submission requirements, or ensure nothing is missed before releasing an app. Triggers on "launch checklist", "app submission", "prepare for launch", "app store submission", "google play submission", "ready to ship", "pre-launch review", "launch day plan".
simple-tasks
Install a fast local task workflow for single-project planning with `scripts/task.sh` (claim, done, status, reporting) backed by `tasks/TASKS.md` and optional `tasks/details/` notes. Use for lightweight in-progress task coordination, not full team issue tracking.