skills/abdulsamad94/chapter-outline-generator/SKILL.md
Generates comprehensive chapter outlines for books, including key topics, subtopics, learning objectives, and estimated word counts. Use this when the user needs help structuring a book chapter or creating a table of contents.
npx skillsauth add aiskillstore/marketplace chapter-outline-generatorInstall this skill globally with one command. Works with Claude Code, Cursor, and Windsurf.
3 of 9 scanners reported clean
Some scanners were skipped, did not run, or reported a non-clean status. Review each row below.
This skill helps authors create detailed, structured chapter outlines for their books. It ensures logical flow, comprehensive coverage, and balanced chapter lengths.
Ask the user for:
For each chapter, create:
Present the outline in a clean, hierarchical format:
# Book Title: [Title]
## Chapter 1: [Chapter Title]
**Summary**: [2-3 sentence overview]
**Learning Objectives**:
- Objective 1
- Objective 2
- Objective 3
**Sections**:
1. [Section Title]
- Subsection A
- Subsection B
2. [Section Title]
- Subsection A
- Subsection B
**Estimated Word Count**: [X,XXX words]
---
## Chapter 2: [Chapter Title]
...
User: "I'm writing a mystery novel about a detective solving art thefts. Can you outline the first 3 chapters?"
Output:
# Book Title: The Vanishing Canvas
## Chapter 1: The Empty Gallery
**Summary**: Detective Sarah Chen receives a mysterious call about a high-profile art theft at the Metropolitan Museum. She arrives to find not just one, but three priceless paintings missing without a trace.
**Learning Objectives**:
- Introduce the protagonist and her detective skills
- Establish the central mystery and stakes
- Set up the museum setting and key supporting characters
**Sections**:
1. The Midnight Call
- Sarah's routine disrupted
- Initial crime scene details
2. The Crime Scene Investigation
- Missing paintings identified
- Security footage review
- First clues discovered
3. Meeting the Museum Director
- Background on the stolen artworks
- List of potential suspects
- Political pressure mounting
**Estimated Word Count**: 3,500 words
User: "Help me outline a book about remote team management."
Output:
# Book Title: Leading from Anywhere: The Remote Manager's Playbook
## Chapter 1: The Remote Work Revolution
**Summary**: Explores the shift to remote work, examining why traditional management approaches fail in virtual environments and what successful remote leaders do differently.
**Learning Objectives**:
- Understand the fundamental differences between in-office and remote management
- Identify common pitfalls of traditional management in remote contexts
- Learn the core principles of effective remote leadership
**Sections**:
1. The Great Remote Transition
- Statistics and trends in remote work adoption
- Case studies of companies that succeeded (and failed)
2. Why Old Management Models Don't Work
- The visibility bias problem
- Time zone challenges
- Communication breakdowns
3. The Remote Leadership Mindset
- Trust over surveillance
- Output versus activity
- Asynchronous-first thinking
**Estimated Word Count**: 4,000 words
Before finalizing the outline, verify:
development
Apple Human Interface Guidelines for content display components. Use this skill when the user asks about charts component, collection view, image view, web view, color well, image well, activity view, lockup, data visualization, content display, displaying images, rendering web content, color pickers, or presenting collections of items in Apple apps. Also use when the user says how should I display charts, what's the best way to show images, should I use a web view, how do I build a grid of items, what component shows media, or how do I present a share sheet. Cross-references: hig-foundations for color/typography/accessibility, hig-patterns for data visualization patterns, hig-components-layout for structural containers, hig-platforms for platform-specific component behavior.
tools
Automate HelpDesk tasks via Rube MCP (Composio): list tickets, manage views, use canned responses, and configure custom fields. Always search tools first for current schemas.
testing
Expert Haskell engineer specializing in advanced type systems, pure functional design, and high-reliability software. Use PROACTIVELY for type-level programming, concurrency, and architecture guidance.
tools
GraphQL gives clients exactly the data they need - no more, no less. One endpoint, typed schema, introspection. But the flexibility that makes it powerful also makes it dangerous. Without proper controls, clients can craft queries that bring down your server. This skill covers schema design, resolvers, DataLoader for N+1 prevention, federation for microservices, and client integration with Apollo/urql. Key insight: GraphQL is a contract. The schema is the API documentation. Design it carefully.