minutes-seo-wave
Plan, build, and review one evidence-backed SEO content wave for the Minutes site, including SERP research, page inventory, design-system compliance, internal linking, generated LLM text, and a shipped-wave retro. Use when the user asks for an SEO wave, a group of comparison or use-case pages, a docs or resource hub expansion, or a coordinated batch of search landing pages.
npx skills add silverstein/minutes --skill minutes-seo-wave --agent claude-code
Same command for any agent — swap --agent for codex, cursor, copilot.
Weekly change comes from our own snapshots, not the repository page — it measures attention, not adoption.
# /minutes-seo-wave Produce one coherent SEO content wave, not a pile of disconnected pages. Keep the method reusable across comparison pages, use-case or resource pages, and docs hubs. Competitive research and keyword specifics are time-sensitive. Research them fresh for each wave. Internal competitive plans may exist in gitignored documentation; never invent, reconstruct, or embed those private specifics in this skill or in repository documentation. ## Inputs Collect: - the wave theme, such as comparison pages, use-case pages, a resource cluster, or a docs hub - target keywords and search intents - the intended audience and conversion action - the requested number of pages or the time box - existing pages and drafts that must not be duplicated - any supplied first-party research, approved claims, and source requirements If theme or keywords are missing, inspect the repository and ask only for the choice that materially changes the wave. Do not invent search volume, keyword difficulty, competitor capabilities, pricing, compliance status, or product claims. ## Steps ### 1. Inventory the existing site Map the current routes before proposing slugs or outlines: ```bash rg --files site
- Inputs
- Steps
- 1. Inventory the existing site
- 2. Perform SERP recon
- 3. Outline the wave page by page
- 4. Implement within DESIGN.md
- 5. Run an evidence and honesty pass
- 6. Complete the internal-linking pass
- 7. Regenerate and validate generated surfaces
- Output format
- Checklist
rg --files site/app | rg '/page\.tsx$' rg --files site/public | rg '\.md$' sed -n '1,240p' site/app/sitemap.ts node scripts/generate_llms_txt.mjs node scripts/generate_llms_txt.mjs --check node scripts/check_design_tokens.mjs
What does the minutes-seo-wave skill do?
Plan, build, and review one evidence-backed SEO content wave for the Minutes site, including SERP research, page inventory, design-system compliance, internal linking, generated LLM text, and a shipped-wave retro. Use when the user asks for an SEO wave, a group of comparison or use-case pages, a docs or resource hub expansion, or a coordinated batch of search landing pages.
How do I install it?
Run `npx skills add silverstein/minutes --skill minutes-seo-wave --agent claude-code` — it drops the skill into your project so the agent can pick it up. Swap the --agent value for codex, cursor or copilot if you use one of those.
Where does this skill come from?
From silverstein/minutes, a repository with 1,410 stars. We read it straight from the repository tree rather than a submitted listing, so what you see here is what is actually published.
Is a popular skill a good skill?
Not necessarily. Stars measure attention, not adoption — a repository can trend for a week and be abandoned. That is why we show the weekly change from our own snapshots next to the total, instead of a single flattering number.