Skill 详情
book-writing
Directly creates book concepts, outlines, chapters, and complete manuscripts.
使用前先检查
自动化审核只检查相关性,不代表安全审查或推荐。使用前请阅读来源中的说明。
SKILL.md
这段内容是审核时保存的快照。外部来源才是完整且最新的版本。
--- name: book-writing description: This skill should be used when the user asks to "write a book", "create book content", "book chapters", "book manuscript", "MVB", "authority book", or mentions writing a book from scratch. Creates complete book manuscripts from concept to final chapters. --- # Book Writing Write complete books that establish authority, deliver transformational value, and position the author as the go-to expert in their field. Apply direct response principles from **Russell Brunson**, **Mike Filsaime**, **Dan Kennedy**, and **Brendon Burchard** to create books that not only inform but persuade and convert. ## Core Objectives - Create a compelling book concept and unique framework - Develop a chapter-by-chapter structure that builds momentum - Write engaging, transformation-focused content - Maintain conversational, direct response style throughout - Deliver actionable value that makes readers into believers ## Book Size Options ### MVB (Minimum Viable Book) - **Length:** 30-50 pages (~15,000-20,000 words) - **Chapters:** 5-7 chapters - **Purpose:** Quick authority builder, lead magnet, "free + shipping" offer - **Timeline:** Can be consumed in 1-2 hours - **Structure:** Introduction + 5 core chapters + conclusion ### Short Book - **Length:** 50-100 pages (~25,000-40,000 words) - **Chapters:** 8-12 chapters - **Purpose:** Positioning book, thought leadership, course companion - **Timeline:** Can be consumed in 3-5 hours - **Structure:** Introduction + 3 parts (3-4 chapters each) + conclusion ### Full Book - **Length:** 100-200+ pages (~50,000-80,000 words) - **Chapters:** 15-20 chapters - **Purpose:** Traditional publishing, comprehensive guide, flagship authority piece - **Timeline:** Multi-day read - **Structure:** Introduction + 4-5 parts (3-4 chapters each) + conclusion + appendices ## Book Writing Process ### Phase 1: Concept & Outline **Book Concept Development:** - **Core Promise:** What transformation will readers achieve? - **Unique Mechanism:** What's your proprietary framework or method? - **Target Reader:** Who is this book for? What's their current pain? - **Author Positioning:** Why are YOU the one to write this book? **Outline Structure:** ``` TITLE: [Transformation-focused title] SUBTITLE: [Mechanism or promise expansion] INTRODUCTION - Hook: Story or statistic that creates urgency - Problem: The pain readers are experiencing - Promise: What they'll achieve by reading - Credibility: Why you're qualified to teach this - Roadmap: What's coming in each section PART 1: [Foundation/Problem] - Chapter 1: [Current reality / false beliefs] - Chapter 2: [Why traditional approaches fail] - Chapter 3: [The new opportunity] PART 2: [Framework/Solution] - Chapter 4: [Core concept introduction] - Chapter 5: [Step 1 of framework] - Chapter 6: [Step 2 of framework] - Chapter 7: [Step 3 of framework] PART 3: [Implementation/Results] - Chapter 8: [Putting it together] - Chapter 9: [Case studies / proof] - Chapter 10: [Common obstacles] CONCLUSION - Summary of key principles - Call to action / next steps - Bridge to offer (if applicable) ``` ### Phase 2: Chapter Writing **Chapter Structure (Per Mike Filsaime):** Every chapter follows this flow: 1. **Hook** (1-2 paragraphs) - Story, question, or bold claim 2. **Context** (2-3 paragraphs) - Why this matters 3. **Core Teaching** (60% of chapter) - The actual content 4. **Story/Example** (15% of chapter) - Proof and relatability 5. **Action Item** (1-2 paragraphs) - What to do next 6. **Bridge** (1 paragraph) - Transition to next chapter **Writing Style Guidelines:** - **3-5 lines maximum per paragraph** (mandatory) - **Conversational tone** - Write like you're talking to a friend - **Use ellipses (...)** occasionally for pacing and transitions - **Bold key concepts** for scannability - **Break up walls of text** with subheadings every 300-500 words - **Include stories** - Personal stories, client stories, historical examples - **Use "you" langu在 GitHub 阅读完整来源 (打开外部页面)