Toc Generator
Add or fix jump-linked tables of contents on long blog posts and guides so readers and search engines navigate in-page sections cleanly.
Overview
toc-generator is an agent skill most often used in Launch SEO (also Grow content) that plans and optimizes table-of-contents placement and jump links for long-form pages.
Install
npx skills add https://github.com/kostja94/marketing-skills --skill toc-generatorWhat is this skill?
- Trigger phrases: TOC, jump links, in-page navigation, long-form audit
- Placement strategy matrix: after intro, floating sidebar, collapsible top—pros and cons per pattern
- Recommends TOCs for 1000+ word articles, guides, whitepapers, and docs
- Reads .claude/.cursor project-context.md when present for site structure
- Pairs with article-page-generator for full article SEO templates (per metadata)
- TOC most valuable for 1000+ word content
- Placement strategies comparison table with multiple rows
- metadata version 1.0.1
Adoption & trust: 732 installs on skills.sh; 586 GitHub stars; 3/3 security scanners passed (skills.sh audits).
What problem does it solve?
Your long article has no skimmable section map, so readers bounce and you miss SEO value from clear in-page structure.
Who is it for?
Indie bloggers, docs-heavy SaaS founders, and SEO-minded builders polishing 1000+ word URLs before or after publish.
Skip if: Short landing pages under roughly a thousand words where a TOC adds clutter without navigation benefit.
When should I use this skill?
When the user wants to add, optimize, or audit a table of contents—or says TOC, jump links, content outline, in-page navigation, or TOC for long content.
What do I get? / Deliverables
You get a placement-aware TOC plan with anchors and navigation patterns suited to your content length and platform—then can hand off to article-page-generator for full templates if needed.
- TOC placement recommendation
- Section anchor/outline plan
- UX/SEO notes for web vs mobile
Recommended Skills
Journey fit
Spans multiple journey phases - primary shelf plus alternate fits below.
TOC structure is a launch-time SEO and UX artifact for pages you want ranked and skimmed—canonical shelf is Launch SEO even when you draft in Build. The skill explicitly ties TOCs to SEO outcomes (bounce, jump links, crawl-friendly outlines), not lifecycle email or support macros.
Where it fits
Add anchor-linked TOC after the intro on a pillar post before indexing push.
Refresh an old guide with collapsible TOC to reduce bounce on mobile readers.
Structure API reference pages with consistent H2 jump links for developer onboarding docs.
How it compares
TOC-focused editorial skill—use article-page-generator when you need the entire article SEO skeleton, not just navigation blocks.
Common Questions / FAQ
Who is toc-generator for?
Solo builders and marketers optimizing long blog posts, guides, or docs where jump links and section outlines improve readability and search performance.
When should I use toc-generator?
At Launch when polishing SEO for a long URL, during Grow content refreshes, or anytime you hear TOC, jump links, or in-page navigation requests.
Is toc-generator safe to install?
It is editorial guidance without shell requirements—review the Security Audits panel on this page like any third-party skill before enabling in production repos.
Workflow Chain
Then invoke: article page generator
SKILL.md
READMESKILL.md - Toc Generator
# Components: Table of Contents (TOC) Guides TOC implementation for long-form articles, guides, and whitepapers. TOCs improve UX and SEO by enabling quick navigation and reducing bounce rates. **When invoking**: On **first use**, if helpful, open with 1-2 sentences on what this skill covers and why it matters, then provide the main output. On **subsequent use** or when the user asks to skip, go directly to the main output. ## Initial Assessment **Check for project context first:** If `.claude/project-context.md` or `.cursor/project-context.md` exists, read it for content structure. Identify: 1. **Content type**: Blog article, guide, whitepaper, documentation 2. **Length**: TOC most valuable for 1000+ word content 3. **Platform**: Web, mobile, both ## Placement Strategies | Placement | Best For | Pros | Cons | |-----------|----------|------|------| | **After intro** | Most articles | Natural flow; visible early | Can scroll out of view | | **Floating sidebar** | Very long content | Always visible | More complex; mobile challenges | | **Collapsible** | Long articles | Less intrusive | May be overlooked | | **Top of article** | Mobile-first | Accessible on all devices | Takes space | ## Technical Implementation ### Heading Structure - One `<h1>` per page - `<h2>` for major sections - `<h3>` for subsections; avoid skipping levels - Headings >=15 characters for SEO ### Jump Links - Assign unique IDs to headings (e.g., `id="keyword-optimization"`) - Use kebab-case for IDs - Link TOC entries via anchor tags (`#section-id`) - Descriptive anchor text; include target keywords naturally ### Semantic HTML ```html <nav aria-label="Table of contents"> <ol> <li><a href="#section-1">Section Title</a></li> </ol> </nav> ``` ## SEO Best Practices | Practice | Purpose | |----------|---------| | **Schema.org TableOfContents** | Help search engines understand structure | | **Keywords in headings** | Natural integration; avoid stuffing | | **Jump links in SERP** | Google may feature TOC links; increases CTR; see **serp-features** | ## UX Guidelines ### Visibility & Interaction - Clear visual hierarchy; indent nested items - Highlight current section when scrolling (optional) - Smooth scroll behavior for jump links ### Mobile - Minimum 16px font size - Touch targets >=44x44px - Responsive layout; consider collapsible on small screens ### Accessibility | Requirement | Practice | |-------------|----------| | **ARIA** | `aria-label="Table of contents"` on nav | | **Keyboard** | All links keyboard-accessible | | **Screen readers** | Proper heading structure; TOC aids skimming | ## Output Format - **TOC structure** (sections, nesting) - **Heading/ID mapping** suggestions - **HTML/ARIA** notes - **SEO** checklist ## Related Skills - **tab-accordion**: Collapsible TOC uses same disclosure pattern; details/summary implementation - **heading-structure**: TOC built from heading structure - **content-optimization**: H2 structure, lists, tables for Featured Snippets - **featured-snippet**: Featured Snippet optimization; TOC supports snippet structure - **serp-features**: SERP features; jump links in results - **article-page-generator**: TOC common in long-form article pages