Skip to content
Agentmart
Submit a tool

book-title-creator

Creates, audits, compares, improves, and validates marketable book titles and subtitles.

Skill by MichaelZelbel

IndexedMIT
Write a review

Install

Works with Claude Code, Claude apps, Codex, Cursor, Gemini CLI, GitHub Copilot, VS Code, OpenCode, Goose, Windsurf. Read the repository before you give any tool access to your data.

npx agentmarket install skill/michaelzelbel-book-title-creator

Asks which of your tools to add it to (Claude Code, Codex, Cursor, VS Code, Windsurf, Gemini CLI, Claude Desktop) and shows the change first. See https://agentmart.dev/cli.

Get the weekly diff

The weekly diff: one email a week with new agent tools, notable updates and grade changes, plus security alerts for tools you follow. Double opt-in, one-click unsubscribe.

We use your email only for this newsletter. Privacy

About

Creates, audits, compares, improves, and validates marketable book titles and subtitles. Use for nonfiction book naming, title strategy, subtitle rescue, candidate ranking, market positioning, or reader testing. Especially useful for business, self-help, how-to, technical, professional, and thought-leadership books.

Use cases: testing

No reviews yet. Installed it? Reviews come from verified installers only. How reviews work

Permissions

What this skill can do and what it asks for, from its SKILL.md. Checked Oct 25, 2026.

Tools
No tools found
Secrets
None asked for
Install scripts
None found

Network hosts it talks to 1

  • codeload.github.com · found in install command

Files it touches

  • ~/.claude/skills/book-title-creator

What's inside

Skill name
book-title-creator
Description
Creates, audits, compares, improves, and validates marketable book titles and subtitles. Use for nonfiction book naming, title strategy, subtitle rescue, candidate ranking, market positioning, or reader testing. Especially useful for business, self-help, how-to, technical, professional, and thought-leadership books.
License
MIT
Instructions
534 lines in SKILL.md · view on GitHub

Agent Skills spec issues

  • body: 534 lines (spec recommends under 500)

Files (1)

  • SKILL.md

SKILL.md (first lines)

# Book Title Creator

## Purpose

Turn a book's market promise into titles and subtitles that the right reader can understand, want, remember, repeat, and trust.

A title is not decoration. It is a compact positioning decision. Optimize for the reader's response, not the author's attachment to a clever phrase.

Strong commercial nonfiction titles usually trigger at least one useful reaction:

- "I want that result."
- "That is exactly my problem."
- "This was written for someone like me."
- "I need to understand that idea."

Never claim that a title guarantees commercial success. Treat every candidate as a marketing hypothesis that still needs conflict checks and real-reader validation.

## Scope

This skill is optimized for commercial nonfiction, including business, self-help, how-to, professional, technical, practical, memoir-with-a-promise, and thought-leadership books.

For fiction, poetry, or highly literary work, adapt the method toward genre signal, emotional promise, atmosphere, intrigue, and memorability. State that the nonfiction scoring weights do not transfer perfectly.

## Choose the working mode

Infer the mode from the request rather than making the user choose.

### Full strategy

Use when the user wants a serious naming process or a publishable shortlist. Build the positioning brief, inspect the current competitive landscape when tools are available, generate broadly, score, red-team, and propose validation.

### Fast sprint

Use when the user wants ideas quickly and has supplied enough context. State only the assumptions that materially affect the answer, then produce strategically diverse candidates. Do not bury the user in process.

### Audit and compare

Use when the user supplies one or more existing titles. Diagnose each candidate before rewriting it. Preserve what works. Explain trade-offs rather than replacing everything merely to appear creative.

### Subtitle rescue

Use when the main title is fixed. Create subtitle directions that add missing audience, outcome, mechanism, scope, or credibility without repeating the title.

### Validation

Use when the user wants to test titles or interpret reader-test results. Measure comprehension, audience recognition, credibility, recall, and behavior, not preference alone.

## Interaction rules

- Reuse all relevant information already supplied.
- Ask only for information that could materially change the naming strategy.
- When clarification is essential, ask the single highest-leverage question and stop.
- When the user requests immediate output, state reasonable assumptions and proceed.
- When the user requests step-by-step work, provide only the current stage and stop.
- Do not fabricate market research, title availability, trademarks, sales data, or legal clearance.
- When browsing is available and the decision matters, research current comparable titles, reader language, exact-title conflicts, and marketplace rules.
- Distinguish verified findings from inference.
- Treat model scores as structured judgment, not proof of demand.
- Avoid em dashes unless the user explicitly requests them.

## Core principles

### 1. Start with the reader's desired movement

A nonfiction book is usually purchased because the reader wants movement:

- toward a result
- away from pain, cost, risk, or confusion
- into a valued identity
- toward mastery, agency, or control
- toward a new explanation of something important

A useful diagnostic question is:

> Does this title express something the reader wants, fears, recognizes, or urgently wants to understand?

A title that merely labels the subject usually forces the subtitle and description to do too much work.

### 2. Do not confuse the subject with the promise

"A book about AI context management" is a subject.

"Build an AI that remembers how you work" is a promise.

The **destination** is what the reader wants. The **vehicle** is the author's framework, technology, method, or process. Lead with the destination or tension unless the vehicle is already desirable, genuinely distinctive, or inherently intriguing.

### 3. Use the reader's language

Prefer words the intended reader already uses for the pain, desired result, failed alternatives, and emotional meaning of success. Avoid author-centric jargon unless it is a useful category signal for the target audience.

When research is possible, mine patterns from reviews, communities, interviews, search suggestions, sales calls, and support conversations. Do not copy a competitor's distinctive wording.

### 4. Give title and subtitle different jobs

The title usually earns **attention and recall**. It may lead with an outcome, problem, identity, big idea, mechanism, or curiosity.

The subtitle usually earns **comprehension and trust**. It can add audience, outcome, mechanism, scope, proof, or a credible boundary.

A subtitle that merely restates the title wastes valuable cover space.

### 5. Prefer memorable clarity

Clarity over cleverness is a guardrail, not a command to be dull. Add memory through rhythm, alliteration, contrast, balanced structure, concrete imagery, or a compact unexpected phrase.

Read every serious candidate aloud. A title must work when spoken, recommended, searched, and remembered.

### 6. Make specificity earn its keep

Numbers, timeframes, absolutes, superlatives, and "without" promises increase attention and proof burden. Never invent precision merely because it strengthens the headline.

Ask:

- Can the manuscript support the claim?
- Is the qualifier visible enough?
- Does the specificity simplify the promise or clutter it?
- Would a reasonable reader feel misled?

### 7. Balance category signal and distinction

From MichaelZelbel/godspeed-mission-control, MIT.

More from MichaelZelbel/godspeed-mission-control

Signals

Stars
0
Forks
0
Open issues
10
Last commit (this folder)
Oct 18, 2026 (11 days ago)
Last release
Oct 24, 2026 (5 days ago)

From GitHub (fetched Oct 24, 2026).

Details

License
MIT
First seen
Oct 24, 2026
Last checked
Oct 24, 2026

More from MichaelZelbel

Cite this page

book-title-creator skill. Agent Mart. https://agentmart.dev/skills/michaelzelbel-book-title-creator (last updated 2026-10-24)