Individual skill
editorial-package
Use when your manuscript is finished and you need the writing that sells it. You get a logline, a back-cover blurb, an online store description, a one-page synopsis that reveals the ending, a query letter for agents or publishers, and a cover brief a designer can work from, all consistent with each other and written in the language of your book. An optional hook test drafts three to five alternative titles, loglines, and blurbs, asks three simulated readers from your target audience whether they would click, buy, and keep reading after your first 250 words, and ranks the options with their reasons. That test is a simulated signal to help you choose, not a market measurement. The package also tells you honestly what writing it revealed, such as a premise that is hard to pitch or comparable titles that are out of date.
skills/editorial-package/SKILL.md
Source commit 475b71f30dfd1c838b1409e8780ab6d6c8067f21
What was checked
- Matches the observed repository HEAD
- Yes
- Scanner rules are current
- No
- Repository scan complete
- No
- Skill scan complete
- Yes
- Observed behavior
- Not checked yet
- Last checked
- Nov 6, 2026
These are observations at the recorded commit, not a guarantee of safety. Review the source before running it.
Install this skill
Choose an agent in your Stack or copy a command below. Commands fetch the pinned commit and copy only this skill directory. Existing destinations are refused. Copying a command does not install anything.
An install command is unavailable: current rules, complete repository and skill scans, an eligible behavior level and a permitted license are required.
Repository context
- Repository stars (not skill ratings)
- 159
- Repository last updated
- Nov 6, 2026
- License
- MIT
Observed agent integration: No specific integration evidence. Standard SKILL.md installation does not imply verified compatibility.
- claude-code Repository topic
- open-source Repository topic
- writing-tools Repository topic
- ai-writing Repository topic
- openai-codex Repository topic
- book-writing Repository topic
- cli Repository topic
- creative-writing Repository topic
- epub Repository topic
- fiction-writing Repository topic
- writing Derived category
- testing Derived category
Files and excerpt
File metadata and permitted, redacted excerpts come from the recorded scan. Source links are pinned to that commit.
Browse files
SKILL.mdcore · 14,630 bytesreferences/hook-test.mddoc · 4,940 bytes
Read excerpt
# Editorial Package
You write the materials that carry a finished manuscript to agents, publishers, bookstores, and readers: logline, blurb, store description, synopsis, query letter, and cover brief. Everything describes the book that exists on the page, not the one that was planned, and every piece tells the same story about it: same title, same author name, same genre, same promise to the reader.
This skill does not edit, proofread, or format the manuscript.
## Before you write
1. **Read the whole manuscript first.** The logline must capture the real book. For a long manuscript, read it in order, in parts, keeping notes on premise, protagonist, turning points, ending, and voice. If you only have a synopsis, say at the top of the package that it was written from a synopsis, not from the pages.
2. **Read what the author already has.** If the author has an outline, a synopsis, comparable titles, an author bio, or earlier pitch copy, read them. Where they disagree with the manuscript, the manuscript wins; note the disagreement.
3. **Fill in the package card** (below). Infer what you can. Ask only for what only the author knows: author name or pen name, route (querying, self-publishing, or both), rights status, and standalone or series. If there is no answer, use visible placeholders such as `[AUTHOR NAME]` and list them in the checklist.
4. **Set the language and market.** Write the package in the manuscript's language, for its home market, unless the author asks otherwise (for example, an English query for a book they plan to translate). Comparable titles, word counts, and submission customs differ by market. Where you don't know a market's conventions, say so instead of quietly applying US norms.
## Package card (top of the output)