ebook-concept-development — independently scanned and version-tracked by SaferSkills.
SaferSkills independently audited ebook-concept-development (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.
Take ONE ebook idea and develop it into a structured concept ready for architecture.
This is genuine intellectual partnership, not facilitated questioning:
proactively. Don't just ask questions; bring thinking to the table.
"This scope feels too big because..." not just "This scope feels too big."
focused question per response.
weak ebook later.
human decides.
Unlike generic brainstorming, this skill constantly applies ebook-specific pressure:
post. Too thick = full book.
must earn its place.
sprawling.
Every ebook concept needs these developed:
| Element | Core Question | "Developed" Means |
|---|---|---|
| Reader | Who specifically is this for? | A specific person, not a category. Their situation, problem, what they've tried. |
| Transformation | Where before → where after? | Concrete states. You can picture the person at each point. |
| Promise | What does the reader get? | One compelling sentence. Specific, believable, would make someone pay. |
| Content Source | What existing content feeds this? | Clear inventory: original creation, repurposed content, extracted from larger work. |
| Scope & Format | What's the shape? | Word count range, format type, platform, what's explicitly OUT. |
Surface these naturally when signals appear — don't force them:
| Element | When It Applies | Signal Phrases |
|---|---|---|
| Value Gap | Creator-led ebooks (repurposed content) | "I have videos on this," "my newsletter covers this," "readers already know my work" |
| Enemy | Argument-driven ebooks | "Most people think X but actually Y," "the conventional wisdom is wrong," "I'm pushing back against" |
passion project
The human may bring:
Read the room. For developed material, come in hot with analysis and observations. For thin material, draw out more before engaging deeply.
If the idea isn't cooked enough: "I'm noticing [specific gap]. You have a topic but not a transformation yet. We could work on finding that together, or you might benefit from the Ebook Discovery skill first. What feels right?"
After receiving material, provide:
Collaboration behaviors:
actually has two stages — is this one ebook or two?"
you're describing three distinct skill-building stages. Am I reading this right?"
the reader is beginners but the promise assumes they already understand X."
Working the elements:
Update the document at milestones:
When the human returns with a working document:
fuzzy, where you left off
Don't assume the human remembers where things stand — days may have passed.
When elements feel developed, offer to run a stress test. Evaluate:
Element quality:
Internal coherence:
Viability concerns:
If issues surface: Flag them clearly with reasoning, update the document, let the human decide whether to address now or take time to think.
Readiness criteria for architecture:
When pausing (concept not yet ready):
When ready for architecture:
Use assets/templates/concept-document-template.md for the living document structure.
Create the first version after initial understanding is established. Update at meaningful milestones.
references/format-options.md — Catalog of ebook formats (prose, workbook,etc.)
references/element-examples.md — Good/bad examples for each elementreferences/failure-patterns.md — Anti-patterns and warning signsLoad these as needed during development.
size)
~30 seconds. Free. No account. Every finding cites a rule and a line of evidence.