plugins/copywriting/skills/knowledge-book/SKILL.md
Use when writing a non-fiction knowledge book — compact books that package expertise into memorable formats (like Steal Like an Artist, Rework, Zluta kniha). Two modes — setup (creates book blueprint with positioning, archetype, voice, outline) and chapter (writes one chapter per invocation). Trigger phrases — "write a book", "napsat knihu", "knowledge book", "book chapter", "kapitola", "book blueprint", "osnova knihy", "kniha o". Do NOT use for fiction, academic papers, blog posts (use web-copy), or marketing copy (use copywriting-orchestrator).
npx skillsauth add petrogurcak/skills knowledge-bookInstall this skill globally with one command. Works with Claude Code, Cursor, and Windsurf.
3 of 9 scanners reported clean
Some scanners were skipped, did not run, or reported a non-clean status. Review each row below.
Write compact, visually distinctive non-fiction books that package expertise into memorable, actionable formats.
Announce: "Using knowledge-book skill in [setup/chapter] mode."
| Mode | When | Output |
|------|------|--------|
| setup | Starting a new book project | book-blueprint.md |
| chapter | Writing content | chapters/XX-slug.md |
If book-blueprint.md exists in project root, default to chapter mode. Otherwise, start with setup.
Walk the author through 6 steps. Ask one question at a time. Save output as book-blueprint.md.
Three questions (Levin):
Synthesize into North Star: "I will teach [AUDIENCE] about [KNOWLEDGE] so they can [ACTION]."
Present table. Author picks one:
| Archetype | Example | Words | Unit Size | |-----------|---------|-------|-----------| | Minimalist | Steal Like an Artist, Anything You Want | 15-35K | 10 principles or 40 micro-lessons | | Manifesto | Rework | 25-30K | 60-90 micro-essays in sections | | Process | Sprint, Make Time | 50-65K | 5-10 sequential steps or tactics menu | | Maximalist | Zluta kniha budovani znacky | 80-120K | 10-15 principles in 3-4 phases |
Ask where content comes from (can combine):
Descriptive only (for future designer):
Generate chapter structure based on archetype. For each chapter:
Structural options (Barry Fox): Presenting the New Idea / Smashing the Paradigm / "We've Got Trouble!" / Story-Fable / Borrowing from Other Fields / Encyclopedic / Topic 101
Save blueprint as book-blueprint.md in project root.
book-blueprint.mdGenerate section-by-section (1,000-2,000 words per section, assemble into chapter).
Structure — Brooks 4-part arc:
| Phase | % | Content | |-------|---|---------| | Setup | 0-25% | Problem framing, reader's current reality | | Response | 25-50% | Failed approaches, conventional wisdom | | Attack | 50-75% | Your solution, framework, core insight | | Resolution | 75-100% | Proof, application, springboard forward |
SUCCESs checklist (Made to Stick) — apply to every chapter:
Writing craft:
Anti-slop guardrails:
After drafting, check:
Save as chapters/XX-slug.md:
---
chapter: 1
title: "Chapter Title"
words: 2847
status: draft
---
[Chapter content]
[Typographic opener — title as manifesto]
[Personal story — 1-3 paragraphs]
[Supporting examples from practitioners]
[Practical how-to mini-section]
[Visual break — illustration description]
[Closing kicker — short, punchy]
Generate 5-10 micro-essays per session, grouped by section:
[Provocative headline — contrarian claim]
[Illustration concept — one line]
[Opening assertion — thesis first sentence, no warm-up]
[2-4 paragraphs — reasoning + analogy + anecdote]
[Closing imperative — flips expectations or commands]
[Phase context — where in the process]
[Step-by-step instructions — numbered, time-boxed]
[Sidebar — facilitator tips]
[Embedded case study]
[End-of-step checklist]
[Transition to next step]
[Principle statement — memorable declaration]
[Why this matters — reader's reality]
[Framework diagram description + explanation]
[Case study 1 — detailed, specific numbers]
[Case study 2 — contrasting industry]
[Common mistakes]
[Application guide — step by step]
[Section summary for reference]
| Skill | Usage | |-------|-------| | storytelling | Anchor story selection, narrative arc | | writing-clearly-and-concisely | Edit pass on drafts | | brand-voice | Load existing voice doc if available |
project/
book-blueprint.md
voice-sample.md
chapters/
00-introduction.md
01-slug.md
...
Methodology: Barry Fox (7 archetypes), Scribe Media (interview method), Michael Levin (3 questions, bridge structure), Story Grid (5 commandments)
Craft: Zinsser (On Writing Well), Pinker (Sense of Style), McPhee (Draft No. 4), Handley (Everybody Writes), Brooks (Story Engineering)
Sticky ideas: Heath brothers (Made to Stick) — SUCCESs, Commander's Intent, Curse of Knowledge, Sinatra Test
Format references: Kleon (Steal Like an Artist), Fried (Rework), Pastier (Zluta kniha), Knapp (Sprint, Make Time), Sivers (Anything You Want), Pressfield (War of Art)
Visual design: Tufte (data-ink ratio), Roam (Back of the Napkin, 6x6), Rohde (Sketchnote Handbook)
NotebookLM reference notebook: ff785860-29ee-4420-a576-cf449e65704f (8 source books)
development
Builds a pre-launch social proof strategy through structured beta programs using D'Souza Brain Audit interviews. Use when launching new products/services and need compelling testimonials, planning a beta cohort, designing interview questions to harvest objection-busting social proof, improving video testimonials for landing pages, or designing case studies with metrics. Trigger phrases include "beta tester program for testimonials", "pre-launch social proof", "Brain Audit testimonial framework", "case study harvest", "reverse testimonial", "video testimonial mechanics", "social proof landing page", "sběr referencí", "beta tester program", "testimonial pro landing page", "social proof před launchem", "rozhovor s klientem", "case study sběr", "reference před spuštěním". NOT for ongoing case study production (use growth-hacking case-study approach), offer design (use offer-creation), or conversion optimization (use ux-optimization).
development
Use when planning a product launch and the product type is unclear or could be either generic (SaaS/app/physical) or info-product. Routes between marketing:launch-strategy (generic launches) and marketing:info-product-launch (courses, memberships, ebooks, cohorts, communities). Trigger phrases - "launch", "spuštění", "go-to-market", "product launch", "release strategy", "uvedení na trh", "launch plan", "spuštění produktu", "launch sequence", "launch strategy". Do NOT trigger when product type is already clear (use specific skill directly).
testing
Specialized 8-week launch cadence for info-products — online courses, cohort programs, memberships, communities, ebooks, masterminds. Combines Jeff Walker's Product Launch Formula (Seed/Internal/JV variants, PLC sequence, open-cart day-by-day) with Stu McLaren's membership mechanics (closed cart, Success Path) and Hormozi Grand Slam Offer stacking. Use when planning "launch online kurzu", "info-product launch", "PLF launch", "course launch", "membership launch", "cohort launch", "ebook launch", "open cart close cart", "8-week launch of online course", "beta cohort to launch sequence", "spuštění kurzu", "launch členské sekce", "open cart strategie". Differentiates from marketing:launch-strategy (generic SaaS/app launches) — info-product-specific. NOT for SaaS launches, physical products, or services.
development
Use when releasing an Expo/React Native mobile app to App Store and Google Play - covers eas submit, ASC "Submit for Review", Play promote Internal→Production, OTA update, and decoding common silent failures (Apple agreement expiry, missing English locale, Background Location declaration, web bundle failure on react-native-maps).