Viral Short Form Ideas
vyralcontent/content-skills
Generate short-form video ideas at volume and stop the blank-page problem for good.
Develop ebook ideas into structured concepts ready for architecture.
Install Ebook Concept Development
$ npx skills add robertguss/claude-code-toolkit --skill ebook-concept-development -a claude-codeProject install by default; add -g for ~/.claude/skills/.
$ gh skill install robertguss/claude-code-toolkit ebook-concept-development --agent claude-codeProject scope by default; add --scope user for a personal install. Needs GitHub CLI 2.90.0 or later (public preview).
$ git clone --depth 1 https://github.com/robertguss/claude-code-toolkit.git skills-src && mkdir -p .claude/skills && cp -r skills-src/skills/ebook-factory/ebook-concept-development .claude/skills/ebook-concept-development && rm -rf skills-srcUse ~/.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/
Install the "ebook-concept-development" agent skill from https://github.com/robertguss/claude-code-toolkit/tree/main/skills/ebook-factory/ebook-concept-development into .claude/skills/ebook-concept-development/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "ebook-concept-development", then confirm the skill loads.Claude Code copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$skill-installer install https://github.com/robertguss/claude-code-toolkit/tree/main/skills/ebook-factory/ebook-concept-developmentType this inside Codex. $skill-installer <name> installs a curated skill from openai/skills. The installer writes to $CODEX_HOME/skills (default ~/.codex/skills). Restart Codex if the skill does not show up.
$ npx skills add robertguss/claude-code-toolkit --skill ebook-concept-development -a codexProject install goes to .agents/skills/; add -g for ~/.codex/skills/.
$ gh skill install robertguss/claude-code-toolkit ebook-concept-development --agent codexProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/robertguss/claude-code-toolkit.git skills-src && mkdir -p .agents/skills && cp -r skills-src/skills/ebook-factory/ebook-concept-development .agents/skills/ebook-concept-development && rm -rf skills-srcUse ~/.agents/skills/ instead of .agents/skills for a personal install.
Codex skills documentation · loads skills from .agents/skills/
Install the "ebook-concept-development" agent skill from https://github.com/robertguss/claude-code-toolkit/tree/main/skills/ebook-factory/ebook-concept-development into .agents/skills/ebook-concept-development/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "ebook-concept-development", then confirm the skill loads.Codex copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ npx skills add robertguss/claude-code-toolkit --skill ebook-concept-development -a cursorProject install goes to .agents/skills/; add -g for ~/.cursor/skills/.
$ gh skill install robertguss/claude-code-toolkit ebook-concept-development --agent cursorProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/robertguss/claude-code-toolkit.git skills-src && mkdir -p .cursor/skills && cp -r skills-src/skills/ebook-factory/ebook-concept-development .cursor/skills/ebook-concept-development && rm -rf skills-srcUse ~/.cursor/skills/ instead of .cursor/skills for a personal install.
Cursor skills documentation · loads skills from .cursor/skills/, .agents/skills/, .claude/skills/, .codex/skills/
Install the "ebook-concept-development" agent skill from https://github.com/robertguss/claude-code-toolkit/tree/main/skills/ebook-factory/ebook-concept-development into .cursor/skills/ebook-concept-development/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "ebook-concept-development", then confirm the skill loads.Cursor copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ gemini skills install https://github.com/robertguss/claude-code-toolkit.git --path skills/ebook-factory/ebook-concept-development--scope user (default) or --scope workspace; --path is the subfolder of the repo that holds the skill; --consent skips the security confirmation prompt.
$ npx skills add robertguss/claude-code-toolkit --skill ebook-concept-development -a gemini-cliProject install goes to .agents/skills/; add -g for ~/.gemini/skills/.
$ gh skill install robertguss/claude-code-toolkit ebook-concept-development --agent gemini-cliProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/robertguss/claude-code-toolkit.git skills-src && mkdir -p .gemini/skills && cp -r skills-src/skills/ebook-factory/ebook-concept-development .gemini/skills/ebook-concept-development && rm -rf skills-srcUse ~/.gemini/skills/ instead of .gemini/skills for a personal install, then run /skills reload.
Gemini CLI skills documentation · loads skills from .gemini/skills/, .agents/skills/
Install the "ebook-concept-development" agent skill from https://github.com/robertguss/claude-code-toolkit/tree/main/skills/ebook-factory/ebook-concept-development into .gemini/skills/ebook-concept-development/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "ebook-concept-development", then confirm the skill loads.Gemini CLI copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ gh skill install robertguss/claude-code-toolkit ebook-concept-developmentInstalls for Copilot at project scope by default; add --scope user for a personal install. Preview a skill first with gh skill preview. Needs GitHub CLI 2.90.0 or later (public preview).
$ npx skills add robertguss/claude-code-toolkit --skill ebook-concept-development -a github-copilotProject install goes to .agents/skills/; add -g for ~/.copilot/skills/.
$ git clone --depth 1 https://github.com/robertguss/claude-code-toolkit.git skills-src && mkdir -p .github/skills && cp -r skills-src/skills/ebook-factory/ebook-concept-development .github/skills/ebook-concept-development && rm -rf skills-srcUse ~/.copilot/skills/ instead of .github/skills for a personal install. Commit .github/skills so cloud agent and code review can use it.
GitHub Copilot skills documentation · loads skills from .github/skills/, .claude/skills/, .agents/skills/
Install the "ebook-concept-development" agent skill from https://github.com/robertguss/claude-code-toolkit/tree/main/skills/ebook-factory/ebook-concept-development into .github/skills/ebook-concept-development/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "ebook-concept-development", then confirm the skill loads.GitHub Copilot copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ npx skills add robertguss/claude-code-toolkit --skill ebook-concept-development -a opencodeOpenCode documents no install command of its own. Project install goes to .agents/skills/; add -g for ~/.config/opencode/skills/.
$ gh skill install robertguss/claude-code-toolkit ebook-concept-development --agent opencodeProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/robertguss/claude-code-toolkit.git skills-src && mkdir -p .opencode/skills && cp -r skills-src/skills/ebook-factory/ebook-concept-development .opencode/skills/ebook-concept-development && rm -rf skills-srcUse ~/.config/opencode/skills/ instead of .opencode/skills for a personal install.
OpenCode skills documentation · loads skills from .opencode/skills/, .claude/skills/, .agents/skills/
Install the "ebook-concept-development" agent skill from https://github.com/robertguss/claude-code-toolkit/tree/main/skills/ebook-factory/ebook-concept-development into .opencode/skills/ebook-concept-development/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "ebook-concept-development", then confirm the skill loads.OpenCode copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
Facts
- Skill name
ebook-concept-development- GitHub stars
- 123
- Token cost
- ~2.1k tokens
- SKILL.md length
- 973 words
- Files
- 5 (incl. references, assets)
- Skills in repo
- 14
- Repo updated
- First seen
- Licence
- MIT
At a glance
Develop ebook ideas into structured concepts ready for architecture.
- Works in 5 steps: Summary of what you understand the core… → What seems strongest or clearest → What seems fuzzy or underdeveloped → …
- The user has an ebook idea (from a brainstorm document
- SKILL.md covers Core Philosophy, What Makes This Ebook-Specific, The Five Core Elements and Situational Elements, plus 5 more sections
- Instructions only: no scripts, shell commands, URLs or credentials in SKILL.md
What it does
Ebook Concept Development is an agent skill from robertguss/claude-code-toolkit. Develop ebook ideas into structured concepts ready for architecture. Use when the user has an ebook idea (from a brainstorm document, existing content to repurpose, a book section to extract, or a fresh concept) and wants to develop it into a clear, validated concept. Produces an Ebook Concept Document with reader, transformation, promise, content source, scope/format, and key topics. Handles multi-session development with living documents.
Its SKILL.md is about 2.1k tokens, which your agent loads only when the skill is triggered. The skill folder holds 7 other files, including reference files and assets (for example `assets/templates/concept-document-template.md`, `references/element-examples.md` and `references/failure-patterns.md`).
It sits in Documents & Office, covering Brainstorming and Content repurposing. The repository describes itself as: A collection of custom skills that extend Claude's capabilities with specialized workflows, methods, and domain knowledge. The licence is MIT.
When your agent uses it
- The user has an ebook idea (from a brainstorm document
- Existing content to repurpose
- A book section to extract
- A fresh concept) and wants to develop it into a clear
Example prompts
- “/ebook-concept-development”
Workflow steps
5 steps, taken from the first numbered list in SKILL.md.
- Summary of what you understand the core idea to be
- What seems strongest or clearest
- What seems fuzzy or underdeveloped
- Your initial observations or concerns (with reasoning)
- One focused question to start developing
What it can do on your machine
Read from SKILL.md and the folder at commit f7fd35e. 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.
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
Ebook Concept Development loads about 2.1k tokens when it runs, and up to ~8.3k if it reads all its reference files. Until then it costs about 118 tokens; SKILL.md has 973 words of instructions outside code blocks.
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 robertguss/claude-code-toolkit at commit f7fd35e, republished under its MIT licence (© robertguss). 973 words, ~2,102 tokens.
Download SKILL.mdSave it as
.claude/skills/ebook-concept-development/SKILL.md (or your agent's skills folder). This skill also uses 4 other files; get the full folder from GitHub.- name
- ebook-concept-development
- description
- Develop ebook ideas into structured concepts ready for architecture. Use when the user has an ebook idea (from a brainstorm document, existing content to repurpose, a book section to extract, or a fresh concept) and wants to develop it into a clear, validated concept. Produces an Ebook Concept Document with reader, transformation, promise, content source, scope/format, and key topics. Handles multi-session development with living documents.
Ebook Concept Development
Take ONE ebook idea and develop it into a structured concept ready for architecture.
Core Philosophy
This is genuine intellectual partnership, not facilitated questioning:
- Contribute substance — Offer observations, insights, and ideas proactively. Don't just ask questions; bring thinking to the table.
- Push back with reasoning — Challenge weak ideas, but always explain WHY. "This scope feels too big because..." not just "This scope feels too big."
- One question at a time — Never overwhelm with multiple questions. One focused question per response.
- Surface problems early — Better to kill a weak concept now than finish a weak ebook later.
- Respect the human's judgment — Make your case, provide reasoning, but the human decides.
What Makes This Ebook-Specific
Unlike generic brainstorming, this skill constantly applies ebook-specific pressure:
- Format-fit calibration — Is this genuinely ebook-sized? Too thin = blog post. Too thick = full book.
- Value density thinking — Ebooks are concentrated solutions. Every element must earn its place.
- Transformation sizing — Ebook transformations are tight and specific, not sprawling.
The Five Core Elements
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. |
Situational Elements
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" |
Also Capture
- Author's intent — Income, authority, audience service, lead generation, passion project
- Key topics/themes/concepts — Raw ingredients that need a home in the ebook
- Decisions made — With reasoning, not just conclusions
- Out of scope — What's explicitly NOT this ebook
Session Flow
Arriving with Material
The human may bring:
- A single sentence idea
- A rough paragraph
- A brainstorm document from Ebook Discovery
- Existing content to repurpose
- A section from a larger book to extract
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?"
First Response Pattern
After receiving material, provide:
- Summary of what you understand the core idea to be
- What seems strongest or clearest
- What seems fuzzy or underdeveloped
- Your initial observations or concerns (with reasoning)
- One focused question to start developing
During the Session
Collaboration behaviors:
- Proactively offer observations: "I notice the transformation you're describing actually has two stages — is this one ebook or two?"
- Challenge with reasoning: "The scope feels ambitious for ebook format because you're describing three distinct skill-building stages. Am I reading this right?"
- Surface element connections: "Your reader and your promise seem misaligned — the reader is beginners but the promise assumes they already understand X."
- Ask the hard questions the human might avoid
Working the elements:
- Don't march through elements like a checklist
- Follow the natural flow of conversation
- Notice when an element gets developed and acknowledge it
- Circle back to fuzzy elements naturally
Update the document at milestones:
- When an element moves from fuzzy to developed
- When a significant decision is made
- When the scope shifts meaningfully
- At session end
Show full SKILL.md (349 more words)Show less
Returning to Continue
When the human returns with a working document:
- Read the document to orient yourself
- Provide status summary: current state of each element, what's developed vs. fuzzy, where you left off
- Ask where they'd like to focus
Don't assume the human remembers where things stand — days may have passed.
Readiness and Stress Test
When elements feel developed, offer to run a stress test. Evaluate:
Element quality:
- Reader specific enough to make real decisions?
- Transformation concrete with clear before/after?
- Promise compelling enough that someone would pay?
- Scope genuinely ebook-sized?
- Key topics sufficient to deliver the transformation?
Internal coherence:
- Does everything align? (Reader → Transformation → Promise → Topics)
- Any contradictions?
- Does format serve the content and reader?
Viability concerns:
- Red flags noticed during development?
- Anything forced or uncertain?
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:
- Reader can be described as a specific person
- Transformation has clear before/after states
- Promise is one compelling sentence
- Scope is defined and genuinely ebook-sized
- Key topics/concepts identified
- Value Gap articulated (if creator-led)
Session End
When pausing (concept not yet ready):
- Update the document with current state
- Note what's still fuzzy and what to tackle next
- Provide the updated document for next session
When ready for architecture:
- Run final stress test
- Confirm readiness with the human
- Produce final concept document
- Note: "This concept is ready for the Ebook Architecture skill"
Working Document
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.
Reference Files
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 signs
Load these as needed during development.
Key Reminders
- One question at a time — always
- Reasoning with every pushback — always
- The human decides — always
- Update document at milestones, not constantly
- Surface ebook-specific concerns throughout (scope, density, transformation size)
- Don't force situational elements — let them emerge
- Be direct about problems — ego protection creates weak ebooks
© robertguss, 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 4 other files (references, assets) in skills/ebook-factory/ebook-concept-development of robertguss/claude-code-toolkit.
- SKILL.md
- assets/templates/concept-document-template.md
- references/element-examples.md
- references/failure-patterns.md
- references/format-options.md
Open the folder on GitHubat commit f7fd35e
Compare with similar skills
Ebook Concept Development 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.
| Skill | Stars | Used in | Tokens | Auto-check | Licence | Repo updated |
|---|---|---|---|---|---|---|
| Ebook Concept Development this skillrobertguss/claude-code-toolkit | 123 | — | ~2.1k | Automated safety check: Pass | MIT | |
| Viral Short Form Ideasvyralcontent/content-skills | 132 | 1 repos | ~2.9k | Automated safety check: Pass | MIT | |
| Memstack Automation Content Pipelinecwinvestments/memstack | 423 | — | ~2.5k | Automated safety check: Pass | Proprietary | |
| Beautiful ArticleConardLi/garden-skills | 13k | — | ~4.7k | Automated safety check: Pass | MIT | |
| Quant Paper ExtractorCamusGIT/EvoQuant | 151 | — | ~2.4k | Automated safety check: Pass | Apache-2.0 | |
| Yao Crux Skillyaojingang/yao-open-skills | 1.3k | — | ~2.5k | Automated safety check: Pass | MIT |
Similar skills
Memstack Automation Content Pipeline
cwinvestments/memstack
A skill your agent uses when the user says 'content pipeline', 'content automation', 'auto-publish', 'repurpose content', 'multi-platform publishing', or needs end-to-end content workflow from…
Beautiful Article
ConardLi/garden-skills
Turns a URL, PDF, DOCX, Markdown file, text or screenshots into a designed, shareable single-file HTML article through a staged review workflow.
Quant Paper Extractor
CamusGIT/EvoQuant
Convert quantitative research report PDFs to markdown, then extract structured knowledge (paperId, title, year, source, keywords, tldr, abstract, strategy, method, experiment, result) into JSONL…
Yao Crux Skill
yaojingang/yao-open-skills
A skill your agent uses when a user is stuck in a complex real-world situation with many conflicts, limited resources, unclear priorities, or asks to identify the principal contradiction, secondary…
Yao Gametheory Skill
yaojingang/yao-open-skills
Route CEO-facing competition, negotiation, channel, pricing, platform, M&A, financing, competitor-response, alliance, and regulator problems through an applied game-theory framework router when…
More from robertguss/claude-code-toolkit
All 14 skills in this repoBrainstorm
robertguss/claude-code-toolkit
Collaborative brainstorming partner for multi-session ideation projects.
Voice Capture
robertguss/claude-code-toolkit
This skill should be used when extracting voice profiles from sample text, creating voice documentation, or matching a specific writing style.
Dhh Writing
robertguss/claude-code-toolkit
This skill should be used when writing in the distinctive style of David Heinemeier Hansson (DHH).
Pragmatic Writing
robertguss/claude-code-toolkit
This skill should be used when writing technical content in the style of Hunt/Thomas (The Pragmatic Programmer) and Joel Spolsky (Joel on Software).
Writing Orchestration
robertguss/claude-code-toolkit
This skill should be used when orchestrating complex writing workflows with multiple phases.
App Store Opportunity Research
robertguss/claude-code-toolkit
Full-pipeline iOS App Store opportunity research. An agent skill from robertguss/claude-code-toolkit.
Related
Categories
Questions about Ebook Concept Development
What does Ebook Concept Development do?
Develop ebook ideas into structured concepts ready for architecture. Ebook Concept Development is an agent skill from robertguss/claude-code-toolkit. Develop ebook ideas into structured concepts ready for architecture.
When should I use Ebook Concept Development?
Ebook Concept Development fits situations like: the user has an ebook idea (from a brainstorm document; existing content to repurpose; A book section to extract; A fresh concept) and wants to develop it into a clear.
How do I install Ebook Concept Development in Claude Code?
Run `npx skills add robertguss/claude-code-toolkit --skill ebook-concept-development -a claude-code`. Or copy the skill folder (skills/ebook-factory/ebook-concept-development in robertguss/claude-code-toolkit) into .claude/skills/ebook-concept-development in your project. Claude Code loads it when a task matches its description.
How do I install Ebook Concept Development in Codex?
Run `npx skills add robertguss/claude-code-toolkit --skill ebook-concept-development -a codex`. Or copy the skill folder (skills/ebook-factory/ebook-concept-development in robertguss/claude-code-toolkit) into .agents/skills/ebook-concept-development in your project. Codex loads it when a task matches its description.
Can I use Ebook Concept Development 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 robertguss/claude-code-toolkit --skill ebook-concept-development -a cursor` (or -a gemini-cli, github-copilot or opencode for the others). To copy it by hand, put the folder in .cursor/skills/ebook-concept-development, .gemini/skills/ebook-concept-development, .github/skills/ebook-concept-development and .opencode/skills/ebook-concept-development in your project.
What does Ebook Concept Development need to run?
SKILL.md names no scripts, command-line tools or credentials: Ebook Concept Development is instructions for the agent only.
Does Ebook Concept Development 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 Ebook Concept Development 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 Ebook Concept Development use?
Ebook Concept Development 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 Ebook Concept Development use?
About 2.1k tokens (SKILL.md is roughly 8.4k 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 6.2k tokens, read only when the agent opens those files.
What are the alternatives to Ebook Concept Development?
Skills that share tags, products or a category with Ebook Concept Development: Viral Short Form Ideas (vyralcontent/content-skills, 132 stars), Memstack Automation Content Pipeline (cwinvestments/memstack, 423 stars), Beautiful Article (ConardLi/garden-skills, 13k stars) and Quant Paper Extractor (CamusGIT/EvoQuant, 151 stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.
Who maintains Ebook Concept Development?
robertguss (a GitHub user) maintains it in robertguss/claude-code-toolkit, which has 123 GitHub stars. The repository holds 14 skills in this directory. The repository was last updated on September 16, 2026.
Source: robertguss/claude-code-toolkit on GitHub. Facts on this page come from the repository at the commit we read; the author's words are quoted as theirs.