Token导航 LogoToken导航TokenDH.com
研究检索只读github未标认证来源可访问许可证需确认审计通过

book-writing写书

Agent Skill

用于辅助文档、README、Markdown、说明文和内容稿件的整理与改写。它适合让 Agent 提炼结构、补齐章节、统一术语、检查链接或把零散材料整理成可读文档。使用时应保留项目已有事实、命令和路径,不要把未确认的信息写成确定结论;涉及对外文案时,还需要控制语气,避免过度营销或夸大能力。

总安装

321

周安装

13

GitHub Stars

3

下载量

101
CodexClaudeCursorGemini CLI

安装说明

本站只整理中文说明和来源信息,不托管安装包,也不代用户安装。

GitHub

来源数

2

许可证

unknown

最后核验

2026-05-01

来源状态

来源可访问

安装方式

通过对话安装

复制提示词发给支持本地命令或 Skills 的 AI 助手,先确认命令和权限,再让它执行。

请帮我安装这个 Agent Skill:book-writing(写书)
来源仓库:https://github.com/mikefilsaime-groove/clickcampaigns-for-claude-code-in-cursor
仓库路径:skills/book-writing
安装命令:
npx skills add https://github.com/mikefilsaime-groove/clickcampaigns-for-claude-code-in-cursor --skill book-writing
安装前请先检查当前环境是否支持对应 CLI,并向我确认将要执行的命令、安装目录、联网范围和文件读写权限;确认后再执行。

命令行安装

复制命令到本机终端执行。该命令会通过 npx skills 从第三方来源获取 Skill;本站只展示命令,不托管安装包,也不自动执行。

skills.shnpx skills
npx skills add https://github.com/mikefilsaime-groove/clickcampaigns-for-claude-code-in-cursor --skill book-writing

简介

book-writing 用于辅助文档、README、Markdown 和内容稿件的整理与改写。

  • 适合提炼结构、补齐章节、统一术语或检查链接。
  • 通过 npx skills add 命令从指定仓库安装并使用该技能。
  • 使用时应保留项目事实,避免写成确定结论;涉及对外文案时需控制语气。
  • 适用宿主包括 Codex、Claude、Cursor、Gemini CLI,接入前应确认版本、权限和运行环境要求。

SKILL.md

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" language - Address the reader directly
  • Create open loops - Hint at what's coming to maintain engagement

Chapter Opening Formulas:

  1. The Story Open: "It was 3 AM and I was staring at my computer screen, wondering if everything I'd built was about to collapse..."
  2. The Question Open: "What if everything you've been told about [topic] is actually keeping you stuck?"
  3. The Statistic Open: "87% of [audience] will never [achieve outcome]. Here's why you don't have to be one of them..."
  4. The Bold Claim Open: "This chapter contains the single most important concept in this entire book. If you only implement one thing..."

Chapter Closing Formulas:

  1. The Action Bridge: "Before you move on, take 5 minutes to [specific action]. This will set you up for what we're about to cover in Chapter [X], where we'll dive into [preview]..."
  2. The Summary Bridge: "So now you understand [key concept]. But knowing isn't enough. In the next chapter, we'll turn this knowledge into a practical system you can implement today..."

Examples

MVB Chapter Example

Chapter 3: The 3-Step Authority Framework

Most experts make this mistake...

They try to establish authority by listing credentials. Degrees. Certifications. Years of experience.

But here's what I've learned after helping hundreds of coaches and consultants build 6 and 7-figure businesses:

Credentials don't create authority. Transformation does.

Let me explain...

When someone is searching for help with [problem], they're not looking for the most credentialed expert. They're looking for someone who can take them from Point A to Point B.

That's why I developed what I call the Authority Triangle:

1. Story - Your journey that makes you relatable 2. Framework - Your unique system that makes you credible 3. Results - Your proof that makes you trustworthy

Let's break each one down...

[Content continues with each element explained]

Your Action Step:

Take out a piece of paper right now. Write down:

  • One story from your journey that shows you understand your audience's pain
  • The 3-5 steps of YOUR framework (even if it's rough)
  • Three results you or your clients have achieved

Don't overthink it. We'll refine this in Chapter 4...


Full Book Part Opening Example

PART II: THE SYSTEM

*"Give me a lever long enough and a fulcrum on which to place it, and I shall move the world."* — Archimedes

In Part I, you learned why most [audience] struggle with [problem].

You discovered the three hidden beliefs that keep people stuck...

And you saw why the traditional approach—[old way]—simply doesn't work anymore.

Now it's time to give you the lever.

Over the next four chapters, I'm going to walk you through my complete [Framework Name]—the exact system I've used to [result] and helped [number] of clients achieve [outcome].

This isn't theory. Every principle you're about to learn has been tested, refined, and proven in the real world.

Here's what we'll cover:

  • Chapter 5: [First component] - The foundation everything else builds on
  • Chapter 6: [Second component] - The acceleration strategy most people miss
  • Chapter 7: [Third component] - How to [specific outcome]
  • Chapter 8: [Fourth component] - Putting it all together

By the time you finish Part II, you'll have a complete roadmap for [transformation].

Let's begin...


Guidelines

Avoid Book Writing Pitfalls:

  • Never: Write academic, dry prose that reads like a textbook
  • Never: Use long paragraphs (5+ lines) that lose readers
  • Never: Skip stories—every chapter needs at least one
  • Avoid: Generic advice that could apply to anyone
  • Avoid: Chapters without clear action items
  • Skip: Jargon and industry terms without explanation

Maintain Reader Engagement:

  • Open loops at chapter ends to pull readers forward
  • Vary chapter lengths (some short punchy chapters, some deeper)
  • Include "quick win" chapters early to build momentum
  • Use cliffhangers before major revelations
  • Break up teaching with stories every 500-800 words

Book Quality Standards:

  • Every chapter must deliver standalone value
  • The book should be quotable—include memorable one-liners
  • Frameworks should be visual and easy to remember
  • Content should be implementable, not just informational
  • Readers should feel transformed, not just informed

Voice Consistency:

  • Maintain conversational, confident tone throughout
  • Use consistent terminology for key concepts
  • Reference earlier chapters when building on concepts
  • Keep the same energy from Chapter 1 to Conclusion

Output Format

When generating book content, output in Markdown format with clear structure:

# Chapter [Number]: [Title]

[Opening hook - 1-2 paragraphs]

## [First Subheading]

[Content with 3-5 line paragraphs]

[Story or example]

## [Second Subheading]

[Content continues...]

---

**Key Takeaway:** [One sentence summary]

**Action Step:** [Specific action reader should take]

---

*Next up in Chapter [X]: [Preview of next chapter]*

Quality Checklist

  • Does the book deliver on its core promise?
  • Is every chapter engaging from first line to last?
  • Are there enough stories to maintain interest?
  • Would a reader feel transformed after finishing?
  • Is the unique framework clear and memorable?
  • Does the book naturally bridge to the author's offer?
  • Would readers recommend this to others?

Additional Resources

Reference Files

  • references/book-frameworks.md - MVB, Short, and Full book structures

适合场景

01

用户想查找某类 Agent Skill 时

02

需要根据任务场景推荐可安装能力包时

03

需要对比不同来源的安装命令和来源信息时

能力概览

能力 1

按任务关键词查找相关 Skills

能力 2

展示可复制的安装命令

能力 3

保留来源站点、仓库和原始说明,方便继续核验

能力 4

展示第三方安全扫描或审计结果

安装后应在对应宿主中按原始 README 的触发条件使用;具体调用方式请以来源页面和 README 为准。

平台分布

Codex

36.89%
按下载量换算37

Claude

30.03%
按下载量换算30

Cursor

18.35%
按下载量换算19

Gemini CLI

11.24%
按下载量换算11

安全审计

Gen Agent Trust Hub

通过

Socket

通过

Snyk

通过

权限和风险

只读

该 Skill 主要提供规则、说明或参考内容,本身偏只读;真正读写文件、联网或执行命令仍取决于宿主 Agent 的任务。

安装前确认

本站仅展示第三方公开信息,不托管安装包,不提供自动安装或运行环境。安装前应自行审查源码、依赖和命令行为。当前只有一个来源,正式发布前建议补源仓库或其他目录站核验。

来源信息

继续浏览同类 Skills