A skill your agent uses when your manuscript is finished and you need the writing that sells it.

MITAuto-check passedWriting & Content

Install Editorial Package

skills CLI
$ npx skills add felipelobomotta-blip/book-genesis-studio --skill editorial-package -a claude-code

Project install by default; add -g for ~/.claude/skills/.

GitHub CLI
$ gh skill install felipelobomotta-blip/book-genesis-studio editorial-package --agent claude-code

Project scope by default; add --scope user for a personal install. Needs GitHub CLI 2.90.0 or later (public preview).

Manual copy
$ git clone --depth 1 https://github.com/felipelobomotta-blip/book-genesis-studio.git skills-src && mkdir -p .claude/skills && cp -r skills-src/skills/editorial-package .claude/skills/editorial-package && rm -rf skills-src

Use ~/.claude/skills/ instead of .claude/skills for a personal install. The folder must contain SKILL.md.

Claude Code skills documentation · loads skills from .claude/skills/

Facts

Skill name
editorial-package
GitHub stars
139
Token cost
~3.7k tokens
SKILL.md length
2,058 words
Files
2 (incl. references)
Skills in repo
4
Repo updated
First seen
Licence
MIT

At a glance

A skill your agent uses when your manuscript is finished and you need the writing that sells it.

  • Works in 9 steps: Logline → Back-cover blurb → Online store description → …
  • Your manuscript is finished and you need the writing that sells it
  • SKILL.md covers Before you write, Package card (top of the output), Route decides the order and 1. Logline, plus 10 more sections
  • Instructions only: no scripts, shell commands, URLs or credentials in SKILL.md

What it does

Editorial Package is an agent skill from felipelobomotta-blip/book-genesis-studio. 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…

Its SKILL.md is about 3.7k tokens, which your agent loads only when the skill is triggered. The skill folder holds 2 other files, including reference files (for example `references/hook-test.md`).

It sits in Writing & Content, covering E-commerce operations. The repository describes itself as: Open-source writing skills for Claude Code, Codex, OpenCode, Antigravity, Gemini, OpenClaw, and Hermes. Your creativity. Your agent. Your book. The licence is MIT.

When your agent uses it

  • Your manuscript is finished and you need the writing that sells it
  • Tasks that involve E-commerce operations

Example prompts

  • “/editorial-package”

Workflow steps

9 steps, taken from the step headings in SKILL.md.

  1. Logline
  2. Back-cover blurb
  3. Online store description
  4. Editorial synopsis
  5. Query letter
  6. Cover brief
  7. Submission checklist
  8. What writing the package revealed
  9. Hook test (optional)

What it can do on your machine

Read from SKILL.md and the folder at commit 46a744f. It shows what the files ask for, not the result of running them.

  • Tool permissions

    Pre-approves nothing: there is no allowed-tools line, so your agent's usual permission prompts apply.

    From allowed-tools in the SKILL.md frontmatter.

  • Runs code

    No scripts in the folder and no shell commands in SKILL.md (its code samples are markdown).

    From the folder's file list and the shell code blocks in SKILL.md.

  • Network

    No URLs in SKILL.md.

    From URLs in SKILL.md, links to its own repository left out.

  • Credentials

    Names no API keys, tokens, secrets or passwords.

    From names ending in _API_KEY, _TOKEN, _SECRET, _KEY or _PASSWORD in SKILL.md.

Context cost

Editorial Package loads about 3.7k tokens when it runs, and up to ~4.9k if it reads all its reference files. Until then it costs about 212 tokens; SKILL.md has 2,058 words of instructions outside code blocks.

Always · name and description, kept in context so the agent knows when to use it
~212
When it runs · the whole SKILL.md, loaded when a task matches
~3.7k
With references · SKILL.md plus every file in references/, read only if the agent opens them
~4.9k

Estimates: characters ÷ 4, the usual rule of thumb; real counts depend on the model's tokenizer. Scripts and assets cost tokens only if the agent reads them.

Safety

Auto-check passed

The automated check found no risky patterns in SKILL.md.

Automated static check — not a guarantee. Review scripts before installing. It scans the text of SKILL.md for risky patterns (piping downloads into a shell, reading credential files, hidden Unicode, destructive commands); files beside SKILL.md are not scanned.

SKILL.md

The full file from felipelobomotta-blip/book-genesis-studio at commit 46a744f, republished under its MIT licence (© felipelobomotta-blip). 2,058 words, ~3,658 tokens.

Download SKILL.mdSave it as .claude/skills/editorial-package/SKILL.md (or your agent's skills folder). This skill also uses 1 other file; get the full folder from GitHub.
name
editorial-package
description
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.

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)

markdown
**Title:** [title and subtitle]
**Author:** [name as it will appear on the cover]
**Category:** [genre and shelf in one line, for example "adult psychological thriller"]
**Length:** [the author's word count; if you estimated it, "about N words (estimate, confirm before sending)"]
**Reader:** [one sentence: who reads this, and what else they read]
**Comparable titles:** [2 or 3 titles with year, each marked "checked" or "verify before sending"]
**Promise:** [one sentence: the experience the book delivers]
**Route:** [querying agents or publishers / self-publishing / both]
**Language and market:** [for example "Portuguese, Brazil"]

Route decides the order

  • Querying agents or publishers: logline, query letter, and synopsis first; blurb and cover brief after.
  • Self-publishing: blurb, store description, and cover brief first; skip the query letter and synopsis unless asked.
  • Both: everything.

Always say what you skipped and why.

1. Logline

About 25 words, one sentence. It sells the book in one breath: in a pitch, an email, a bio.

It holds four things:

  • Who: the protagonist, defined by their situation, not their name.
  • What: the action or challenge at the center.
  • Stakes: what happens if they fail.
  • Hook: what makes this story different from every other book with the same premise.

Scaffold (the final logline should not read like a template): "When [inciting incident], [protagonist] must [action] or [stakes], but [the complication that makes it unique]."

Examples:

  • Weak: "A story about finding yourself in a world that doesn't understand you."
  • Strong: "A burned-out programmer discovers that the AI he built to automate his job has started automating his relationships, and doing it better."
  • Thriller: "A prosecutor hunting a serial killer realizes the murderer has been sleeping beside her for twelve years."
  • Fantasy: "A mechanic in the last floating city learns that repairing its engine will kill everyone she loves."
  • Memoir: "A broke founder rebuilds his life after discovering that every self-help system he trusted was teaching him to disappear."
  • Nonfiction: lead with the surprising claim, who the book is for, and what changes for the reader.

Test: would a stranger say "tell me more"? If they would say "interesting" and change the subject, rewrite. Draft three, keep the best, and say why.

2. Back-cover blurb

100 to 180 words. It sells the reading experience, not a plot summary.

Four movements:

  1. Hook: the situation that creates immediate interest. It goes in the first line, before any setting or context.
  2. Context: what kind of book this is.
  3. Distinction: why this book and not a generic version of the premise.
  4. Promise: who it is for and why it matters now.

Rules:

  • End before the climax. Never reveal the ending or spoil a major reversal.
  • Use the target reader's language, and match the book's voice: a thriller sounds urgent, a literary novel contemplative, a comedy funny.
  • Make the last sentence create urgency, dread, desire, recognition, or curiosity.
  • No empty praise ("gripping", "powerful", "unforgettable") unless something specific backs it up.
  • "For fans of X and Y" only if the comparison is accurate.

By genre:

  • Memoir: lead with vulnerability, voice, and the cost of transformation.
  • Thriller: lead with impossible pressure and a clock.
  • Fantasy and science fiction: lead with the world's rule, the dilemma, and the scale.
  • Nonfiction: lead with a surprising claim and its practical consequence.
  • Literary fiction: lead with voice, situation, and the moral or emotional contradiction.

3. Online store description

The product page on a site such as Amazon, Kobo, or Apple Books. It is a sales page, not the back cover.

  • The first 150 characters carry the hook; that is often all a browser sees before "Read more".
  • Short paragraphs of two or three sentences, for phone screens.
  • Work in two or three phrases readers actually type when searching this shelf ("small-town mystery", "enemies to lovers"), naturally, never as a list.
  • End with the reader promise, not "buy now": "If you have ever [experience], this book will [payoff]."
  • If self-publishing, suggest up to seven search phrases for the store's keyword fields. Leave out other authors' names and other books' titles: they mislead readers, and Amazon's keyword rules, for one, forbid naming authors not associated with the book.

4. Editorial synopsis

For agents and editors. One page, about 500 words (300 to 700 if the guidelines ask for it). It reveals the ending; professionals reject coy synopses.

Structure, in proportion:

  1. Setup (about 15%): the world, the protagonist, what they want.
  2. Inciting incident (about 10%): what breaks the normal.
  3. Escalation (about 30%): the key turns, and how the protagonist changes.
  4. Climax (about 15%): the decisive moment, told plainly.
  5. Resolution (about 15%): how it ends and what changed.
  6. What it is really about (about 15%): the core transformation or the final open question, and why it matters now.

Rules: present tense; a plain, professional tone, neither academic nor jacket copy; no more than five named characters; mention stylistic devices (two timelines, an unreliable narrator) only if they shape how the book is positioned.

For nonfiction, write an overview plus a chapter-by-chapter summary of two to four sentences per chapter instead.

5. Query letter

250 to 400 words, one page. Its only job is to make an agent or editor ask for pages.

  1. Hook (one or two sentences): the logline, sharpened. If the author names a specific agent or editor, add one line on why them: a book they represented or edited, or an interest they have stated publicly. If you can browse, check their current guidelines; if you can't, leave [PERSONALIZE: agent's recent book or stated interest] and tell the author what to look up. Personalization proves fit; it does not flatter.
  2. Pitch (about 150 words): protagonist, conflict, stakes, in the book's voice. It stops before the climax.
  3. Comparable titles (one or two sentences): two titles from roughly the last five years, in the same category, successful but not runaway phenomena, with the comparison explained: "the institutional paranoia of X with the voice-driven grief of Y."
  4. Bio (two or three sentences): only what is relevant (awards, publications, expertise, platform). If nothing is relevant, one plain line or nothing. Never apologize for being a debut author.
  5. Details (one sentence): title, category, word count rounded to the nearest thousand, complete, standalone or series.
  6. Close: a brief thank-you.

Weak opening: "I am writing to submit my manuscript..."

Strong opening: "In my novel, an archivist discovers that deleted manuscripts are still being edited by someone who knows how every author dies."

For nonfiction, the bio and platform paragraph carry more weight: say why this author is the one to write this book. In markets where writers submit directly to publishers, adapt the letter to each publisher's guidelines.

Show full SKILL.md (749 more words)Show less

6. Cover brief

For a designer, not a writer: visual language (color, shape, feeling), not plot.

  • Positioning: category, target shelf, what that shelf's readers expect a cover to look like, and whether the ebook thumbnail or the print edition matters more.
  • Emotional concept: one paragraph on the single feeling the cover must create before anyone knows the plot.
  • Visual direction: primary element, secondary element, composition, lighting, texture, how realistic or abstract, and what must still read at phone-thumbnail size.
  • Color: dominant, secondary, and accent, with hex codes; the overall mood; colors to avoid.
  • Typography: title treatment, how prominent the author name is, subtitle or series line, and the genre signal the lettering sends.
  • Must include / must avoid: the elements that carry the book's essence; the genre cliches and misleading imagery to stay away from.
  • References: three to five real covers (one for color, one for type, one for composition, one from the same shelf, one anti-reference), each with what to take from it. If you can't look covers up, describe the shelf's look and ask the author to collect the references. Don't describe a cover from memory.
  • Image-model prompt (optional): [style], [primary subject], [setting], [mood], [lighting], [composition], [palette], negative space for the title, book cover art, 2:3 aspect ratio, no text. Never ask for a living artist's style by name. Add all text in layout software afterward; image models are not reliable for final typography.

7. Submission checklist

  • Title and author name identical in every piece
  • Word count confirmed by the author, and inside the usual range for the category (if you don't know the range for this market, say so)
  • Category stated the same way everywhere
  • Rights status and completion stated
  • Query under 400 words, unless the market expects otherwise
  • Synopsis reveals the ending
  • Comparable titles recent, real, and checked
  • Cover brief matches the target shelf
  • No placeholders left ([AUTHOR NAME], [PERSONALIZE: ...])
  • Sensitivity, legal, or fact-check needs listed (real people, quoted song lyrics or poems, medical or legal claims)
  • Next recipient and next action listed

8. What writing the package revealed

Writing the package tests the book. End with honest signals:

  • Premise clarity: was the logline hard to write? If so, the core hook may be buried or weak.
  • Structural suspense: could the query pitch stop at a moment of real suspense? If you struggled to find one, the plot may lack a clear escalation point.
  • Distinction: did the blurb need empty praise words to work? If so, what sets the book apart is not yet visible on the page.
  • Shelf: could you name the category in one line? If not, the genre is unclear.
  • Risks: comparable titles that are old, wrong, or unverified; claims you could not back up; sensitivity or legal exposure; a cover that doesn't match its shelf; a word count outside the category's usual range; a manuscript that is not actually ready.

Do not hide blockers. A useful package is an honest one.

9. Hook test (optional)

Run it only when the author asks. Otherwise, offer it in one line at the end of the package, and say why if the title or pitch looks unsettled. The full procedure is in references/hook-test.md: three to five pitch options (title, logline, blurb), three simulated readers from the target audience, three questions (would you click, would you buy, would you keep reading after the first 250 words), and a ranking with the reasons. The result is always labeled a simulated signal, not a market measurement.

Output

One document, in this order: the package card, the pieces for the chosen route, the submission checklist, what writing the package revealed, and the hook test if it ran. If you can write files, save it beside the manuscript as editorial-package-YYYY-MM-DD.md (or as separate files, if the author asks), and never overwrite an earlier version. Otherwise, reply in the conversation.

Rules

  1. The real book. Read the entire manuscript before writing anything.
  2. Voice match. Every piece sounds like the book it sells.
  3. One story. The same title, author name, genre, and promise everywhere.
  4. Nothing invented. Never make up a comparable title, a sales figure, an award, a review, a quote, or an agent's wishes. If you are not sure a book exists or when it came out, mark it "verify before sending".
  5. No promises. Never promise or imply sales, bestseller status, or virality. Never write "bestselling" or "award-winning" unless the author supplies the fact.

This skill stands alone. The full idea-to-book workflow is the Book Genesis skill.

© felipelobomotta-blip, MIT. Rendered from Markdown: HTML in the file is shown as text, images as links, and headings moved down two levels. Raw file

Files

SKILL.md and 1 other file (references) in skills/editorial-package of felipelobomotta-blip/book-genesis-studio.

  • SKILL.md
  • references/hook-test.md

Open the folder on GitHubat commit 46a744f

Compare with similar skills

Editorial Package next to the 5 skills that share the most tags, products or categories with it. Stars are the repository's; “used in” counts other GitHub owners with a copy.

Editorial Package compared with similar skills
SkillStarsUsed inTokensAuto-checkLicenceRepo updated
Editorial Package this skillfelipelobomotta-blip/book-genesis-studio139—~3.7kAutomated safety check: PassMIT
Ecommerce Copywriteranbeime/skill7.7k—~1.3kAutomated safety check: PassNone
Memstack Content Product Descriptioncwinvestments/memstack423—~2.6kAutomated safety check: PassProprietary
Product Description Generatornexscope-ai/eCommerce-Skills1.1k—~3.3kAutomated safety check: PassMIT
Tiktok Shop Seller Guidenexscope-ai/eCommerce-Skills1.1k—~1.9kAutomated safety check: PassMIT
Ecommerce Copywriterinfometa/workbuddyskills346—~488Automated safety check: PassNone

Similar skills

  • 电商运营与内容创作者在需要为多品类商品创作或优化营销图片文案时使用。自动提炼核心卖点,生成带emoji的吸睛标题与直击痛点的场景化正文,一键产出高转化率电商文案,省时省力大幅提升商品点击与购买转化!

    7.7k GitHub stars~1.3k tokensUpdated yesterday
    Writing & ContentAuto-check passed
  • A skill your agent uses when the user says 'product description', 'product listing', 'product copy', 'Amazon listing', 'Shopify listing', 'e-commerce copy', or needs conversion-optimized product…

    423 GitHub stars~2.6k tokensUpdated 13 days ago
    Writing & ContentAuto-check passed
  • Product Description Generator

    nexscope-ai/eCommerce-Skills

    E-commerce product description generator for any platform. An agent skill from nexscope-ai/eCommerce-Skills.

    1.1k GitHub stars~3.3k tokensUpdated 1 mo ago
    Writing & ContentAuto-check passed
  • Tiktok Shop Seller Guide

    nexscope-ai/eCommerce-Skills

    Complete TikTok Shop selling guide. An agent skill from nexscope-ai/eCommerce-Skills.

    1.1k GitHub stars~1.9k tokensUpdated 1 mo ago
    Writing & ContentAuto-check passed
  • Ecommerce Copywriter

    infometa/workbuddyskills

    电商爆款文案生成技能。为淘宝/拼多多/抖音/京东卖家生成高转化率的商品标题、详情页文案、卖点提炼和促销文案。使用场景:(1) 商品标题优化,(2) 详情页文案生成,(3) 卖点提炼,(4) 促销活动文案,(5) 竞品文案分析。

    346 GitHub stars~488 tokensUpdated yesterday
    Writing & ContentAuto-check passed
  • E-commerce Visual Copywriting

    feichanggege/ecommerce-visual-copywriting-skill

    Turns product details, packaging, target platform and audience into an executable e-commerce image plan with copy, storyboards, image prompts and a compliance review.

    858 GitHub stars~1.3k tokensUpdated 23 days ago
    Writing & ContentAuto-check passed

More from felipelobomotta-blip/book-genesis-studio

  • Beta Reader

    felipelobomotta-blip/book-genesis-studio

    A skill your agent uses when you want beta reader feedback on your draft from three sharply different test readers, one who reads for pace, one who reads for depth, and one who hunts for plot holes…

    139 GitHub stars~2.4k tokensUpdated yesterday
    Auto-check passed
  • Book Genesis

    felipelobomotta-blip/book-genesis-studio

    A skill your agent uses when someone wants to write a complete book from an idea, even a one-line one, or to continue, audit, revise or package a book in progress.

    139 GitHub stars~1.2k tokensUpdated yesterday
    Auto-check passed
  • Literary Agent Panel

    felipelobomotta-blip/book-genesis-studio

    A skill your agent uses when you want to know how a literary agent, an acquiring editor, a bookseller, and a reader from your target audience might react to your book before you submit it.

    139 GitHub stars~1.9k tokensUpdated yesterday
    Auto-check passed

Questions about Editorial Package

What does Editorial Package do?

A skill your agent uses when your manuscript is finished and you need the writing that sells it. Editorial Package is an agent skill from felipelobomotta-blip/book-genesis-studio. Use when your manuscript is finished and you need the writing that sells it.

When should I use Editorial Package?

Editorial Package fits situations like: your manuscript is finished and you need the writing that sells it; tasks that involve E-commerce operations.

How do I install Editorial Package in Claude Code?

Run `npx skills add felipelobomotta-blip/book-genesis-studio --skill editorial-package -a claude-code`. Or copy the skill folder (skills/editorial-package in felipelobomotta-blip/book-genesis-studio) into .claude/skills/editorial-package in your project. Claude Code loads it when a task matches its description.

How do I install Editorial Package in Codex?

Run `npx skills add felipelobomotta-blip/book-genesis-studio --skill editorial-package -a codex`. Or copy the skill folder (skills/editorial-package in felipelobomotta-blip/book-genesis-studio) into .agents/skills/editorial-package in your project. Codex loads it when a task matches its description.

Can I use Editorial Package in Cursor, Gemini CLI or GitHub Copilot?

Cursor, Gemini CLI, GitHub Copilot and OpenCode also load SKILL.md folders. With the skills CLI, run `npx skills add felipelobomotta-blip/book-genesis-studio --skill editorial-package -a cursor` (or -a gemini-cli, github-copilot or opencode for the others). To copy it by hand, put the folder in .cursor/skills/editorial-package, .gemini/skills/editorial-package, .github/skills/editorial-package and .opencode/skills/editorial-package in your project.

What does Editorial Package need to run?

SKILL.md names no scripts, command-line tools or credentials: Editorial Package is instructions for the agent only.

Does Editorial Package access the network?

SKILL.md contains no URLs. Any network use would come from the scripts or tools the agent runs. This is read from the text; nothing was executed.

Is Editorial Package safe to install?

Our automated static check of SKILL.md found no risky patterns, such as piping downloads into a shell, reading credential files or hidden Unicode. It is not a guarantee. Review the folder before installing.

What licence does Editorial Package use?

Editorial Package is published under the MIT licence (the repository's licence). It allows redistribution, so the full SKILL.md is shown on this page.

How many tokens does Editorial Package use?

About 3.7k tokens (SKILL.md is roughly 15k characters). Agents keep only the skill's name and description in context until a task matches; then they load SKILL.md in full. Its references folder adds about 1.2k tokens, read only when the agent opens those files.

What are the alternatives to Editorial Package?

Skills that share tags, products or a category with Editorial Package: Ecommerce Copywriter (anbeime/skill, 7.7k stars), Memstack Content Product Description (cwinvestments/memstack, 423 stars), Product Description Generator (nexscope-ai/eCommerce-Skills, 1.1k stars) and Tiktok Shop Seller Guide (nexscope-ai/eCommerce-Skills, 1.1k stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.

Who maintains Editorial Package?

felipelobomotta-blip (a GitHub user) maintains it in felipelobomotta-blip/book-genesis-studio, which has 139 GitHub stars. The repository holds 4 skills in this directory. The repository was last updated on October 9, 2026.

Source: felipelobomotta-blip/book-genesis-studio on GitHub. Facts on this page come from the repository at the commit we read; the author's words are quoted as theirs.