book-ideation — independently scanned and version-tracked by SaferSkills.
SaferSkills independently audited book-ideation (Agent Skill) and scored it 100/100 (green). The audit ran 55 deterministic rules across Security, Supply Chain, Maintenance, Transparency, and Community; it found 0 high-severity and 0 lower-severity findings. The full rule-by-rule trace and per-finding evidence are below. Free, methodology-open.
Findings & checks · 0 flagged
Every scanned point with the score it earned and what moved between them.
First recorded scan — no prior version to compare against.
The primary manifest — the file an agent reads to learn what this artifact does.
Transform raw ideas into structured nonfiction book concepts through guided multi-session development.
Every decision serves the reader. The question is never "what do I want to say?" but "what transformation does the reader need, and how can this book deliver it?"
This skill sits between generic brainstorming and book architecture. Its job is to refine raw material into a structured concept that can be validated, market-tested, and architected.
The goal is not a book outline. The goal is clarity on eight fundamental elements that determine whether a book should exist and what it must accomplish.
This skill accepts:
brainstorm skillBegin every session with:
Develop these through conversation, not interrogation. Surface insights; don't extract data.
#### 1. The Reader
_Who specifically is this for?_
Go beyond demographics. Understand:
Probe: "If your ideal reader walked into a bookstore, what section would they be in? What would they be feeling? What search would they have just done on Amazon?"
#### 2. The Transformation
_Where will they be after reading?_
The reader starts at Point A and ends at Point B. Define both clearly:
The gap between A and B is the book's reason for existence.
#### 3. The Core Thesis
_What's the one big idea?_
This is not a topic—it's a claim. A thesis takes a position. Test it:
Template: "Most people believe [conventional wisdom], but actually [your thesis], because [key insight]."
#### 4. The Author Angle
_Why are you the one to write this?_
Credibility comes from:
You don't need all four. You need at least one that's compelling.
#### 5. The Stakes
_Why does this matter? Why now?_
Articulate:
Stakes create urgency. Without stakes, the book is a "nice to have."
#### 6. The Key Concepts
_What are the 3-7 major ideas that support the thesis?_
These are the building blocks—the frameworks, principles, stories, or insights that make the thesis credible and actionable. They'll become chapters or sections.
Don't list 20 ideas. Force prioritization. What's essential vs. nice-to-have?
#### 7. The Enemy
_What is this book arguing against?_
Every great nonfiction book has a villain:
The enemy clarifies the thesis by contrast.
#### 8. The Promise
_In one sentence, what does the reader get?_
This is the book's value proposition. It should:
Template: "This book will help [reader] achieve [transformation] by [method/insight]."
Collaboration behaviors:
Here's why..."
When stuck on an element:
Always conclude with:
For rapid concept capture when time is short:
sentence)
A Book Concept Document is ready for validation when:
| Element | Readiness Test |
|---|---|
| Reader | Can describe them as a specific person, not a category |
| Transformation | Clear before/after with emotional and practical dimensions |
| Thesis | One sentence, contrarian, defensible |
| Author Angle | At least one compelling credibility source |
| Stakes | Urgency is clear—reader feels cost of inaction |
| Key Concepts | 3-7 prioritized, each clearly supporting the thesis |
| Enemy | Named and specific |
| Promise | One sentence that a reader would find compelling |
Use the template at assets/templates/book-concept-template.md for all Book Concept Documents.
The document is versioned (v1, v2, etc.) and includes:
When discussing Key Concepts, it often helps to preview potential book structures. See references/nonfiction-frameworks.md for framework options to share with the user. This is for orientation only—structural decisions belong to book-architect.
When the Book Concept Document is ready:
→ idea-validator: Will stress-test the thesis and key concepts against existing research → market-research: Will assess KDP viability, competition, and positioning → book-architect: Will use reader/transformation/key concepts to design the structure
~30 seconds. Free. No account. Every finding cites a rule and a line of evidence.