digital-guide-builder
Turn one person's expertise into ONE finished, sellable digital guide/ebook, fast. Interviews the user briefly on their niche, angle, and pillars, then writes a full polished guide where every chapter delivers one concrete unlock, formats it as a clean print-ready file, and writes storefront listing copy (title, pitch, price, bullets). Use when the user wants to build a digital guide, ebook, PDF product, or storefront product from their own knowledge, says 'help me make a digital product', 'turn my knowledge into an ebook', 'build a guide I can sell', 'make me a Stan Store / Gumroad product', or /digital-guide-builder. NOT a general-purpose book-writing tool.
duncan-buildroom · Static checks on file
Installation
Read the source and dependencies before running a command. Copying does not install or execute anything.
npx skills add duncan-buildroom/profit-room-skills --skill digital-guide-builderAbout this skill
name: digital-guide-builder description: "Turn one person's expertise into ONE finished, sellable digital guide/ebook, fast. Interviews the user briefly on their niche, angle, and pillars, then writes a full polished guide where every chapter delivers one concrete unlock, formats it as a clean print-ready file, and writes storefront listing copy (title, pitch, price, bullets). Use when the user wants to build a digital guide, ebook, PDF product, or storefront product from their own knowledge, says 'help me make a digital product', 'turn my knowledge into an ebook', 'build a guide I can sell', 'make me a Stan Store / Gumroad product', or /digital-guide-builder. NOT a general-purpose book-writing tool." allowed-tools: Bash, Read, Write, Edit, Glob, Grep metadata: argument-hint: "your niche/expertise, your audience, and the transformation you help people get" user-invocable: true
Digital Guide Builder
Turns one person's real expertise into one finished, sellable digital guide. Think of the well-known case study of a creator with no design background who made tens of thousands of dollars in two weeks from a short, focused first ebook sold through a simple storefront — this skill is what actually builds their version of it.
Scope is deliberately narrow: ONE person, ONE guide, shipped fast. Not a ghostwriting service, not a multi-book series, not a general nonfiction-writing tool. If the user wants something broader (a course, a book series, ongoing content), point them elsewhere — this skill exists to get one sellable asset out the door in a single session.
Personalization
This skill writes in your voice, about your expertise. Before running, load the brand profile at
~/.claude/brand-profile.md.
- If it doesn't exist, run the personalize skill first (or just tell me your niche, audience, and the transformation you help people get — I'll create it).
- Prefer a writing sample the user pastes; fall back to the profile's Tone and Words-to-avoid as the voice baseline. Always use the user's own niche language and story.
- Never invent numbers, results, or claims the user did not give you.
Step 1 — Intake (from the user's first message)
Pull these three things out of whatever the user gives you (or the brand profile):
- Expertise/niche: what they actually know how to do
- Audience: who they help
- Transformation: the result people get from following their method
If the user's opening message is thin (e.g. "help me build a guide to sell") and the profile doesn't cover it, ask for these three directly before anything else. Don't guess at someone's expertise — a wrong guess here means the whole guide is off.
Step 2 — The Interview (2-4 questions, no more)
Once you have the Step 1 basics, ask ONLY what's still missing from this list. Skip anything already answered. Never turn this into a 10-question intake — the whole point of the format is speed.
- The angle/story: What's the one thing that makes THEIR version of this different — a specific moment, result, or mistake they can point to? (This becomes the hook of the guide and the reason someone buys from them instead of googling it for free.)
- The pillars: 3-5 core lessons, steps, or principles they'd teach someone doing this from scratch. These become the chapters. If the user can't articulate them, propose a draft set based on their niche and confirm before writing.
- Length/page count: Rough target (most first digital products run short: 20-40 pages / 4,000-8,000 words total — a tight, high-signal guide, not a textbook). Default to short if the user has no preference; a guide that gets finished and read beats a long one that doesn't.
- Price point: What they want to charge. If they don't know, recommend based on transformation value and comparable digital products: $9-$27 for a focused single-topic guide, $27-$47 if it includes templates/swipe files/worksheets, $47-$97 if it replaces a service they'd otherwise charge hundreds for. State the recommendation with the one-line reason, don't present an open menu.
Also ask, in the same round: do you have any writing samples (a post, an email, a video transcript) I
can match your voice to? If yes, read what they paste and write in that voice. If no, fall back to the
Tone in ~/.claude/brand-profile.md (or a clean default: direct, confident, no fluff, short sentences,
specific over vague) — but always substitute in the user's own niche language and story.
Step 3 — Structure the Guide
Build the chapter list from the pillars gathered in Step 2. Standard shape:
- Title page (title + subtitle + author name)
- Intro chapter: the hook/story (the angle from Step 2), what the reader will walk away able to do,
who this is for
- One chapter per pillar (3-5 chapters) — see the unlock rule below
- Closing chapter: how to actually implement this, the single next action, light CTA to the reader's
own next offer if they have one (optional, ask if unsure)
Every chapter must be built around ONE unlock, not a pile of information. An unlock is a specific, actionable insight the reader didn't have before, paired with exactly how to apply it to their own situation. Hormozi-style: plain words, no padding, no restating the same point three ways, no chapter that could be summarized as "here's some context." If a chapter doesn't end with the reader knowing exactly what to do differently, it's not done. Concrete over clever: never sacrifice clarity to hit a word or page target.
Confirm the chapter list with the user in one short message before writing the full guide — this is the one checkpoint where a wrong structure would waste the whole write. Keep it to a numbered list, not a lengthy pitch.
Step 4 — Write the Guide
Write the full guide once the structure is confirmed. Per chapter:
- Open with the concrete situation or question the reader is in, not a definition
- Teach the ONE unlock plainly, w