Menu
Use when asked for SEO baseline or to make a public page shareable - adds the technical page packaging (title, description, favicon, Open Graph preview, robots, sitemap, page structure) so links and previews look intentional
Install with Codex or Claude Copy this prompt, paste it into Codex, Claude, or another assistant, and let it review the skill page and install it for you.
Based on SOC occupation classification
Use when specs are approved (phase 4 approved in docs/spp/pipeline-state.md) OR when the user directly asks to turn a spec into an implementation plan outside a running pipeline (e.g. "turn this spec into an implementation plan") - writes implementation plans as bite-sized tasks to docs/spp/05-plans/ for subagent-driven execution
Use after completing a task or major feature, before merging, or when the user asks to review a branch, PR, or work-in-progress diff. Run independent Standards and Spec reviews so clean code cannot hide the wrong behavior and correct behavior cannot hide broken standards.
Diagnose bugs, test failures, build failures, unexpected behavior, and performance regressions before proposing fixes. Build a tight reproduction loop, find the root cause, fix it once, and lock it down with a regression test.
Use when implementing any feature or bugfix, before writing implementation code
Use when starting any conversation - routes each request to a single SPP skill by default, running the full idea-to-deploy pipeline only when the user explicitly asks for "pipeline"
Use when a product is ready to ship, OR when the user directly asks how or where to deploy or to write a deploy runbook - chooses a deploy strategy with the owner in cost-and-consequence terms, then executes it into a repeatable runbook. Self-checks on disk for a fixed release version first โ it warns and offers to fix it, it does not block.
| name | seo-baseline |
| description | Use when asked for SEO baseline or to make a public page shareable - adds the technical page packaging (title, description, favicon, Open Graph preview, robots, sitemap, page structure) so links and previews look intentional |
This is a standalone helper skill. It sits outside the SPP pipeline state machine โ it does not read or write docs/spp/pipeline-state.md, and it is not a numbered phase or a phase checkpoint. It runs whenever asked, triggered by its own description, independent of any pipeline in progress.
SEO for a first MVP is not an attempt to rank on Google in a week. It's the basic technical packaging of a page: a link isn't embarrassing to share, a search engine can parse the page, and a preview in a messenger doesn't look like random junk.
This skill covers technical packaging for search engines and messengers only. Making a product legible to AI-assisted search (Generative Engine Optimization) is a separate concern, covered by the sibling geo-optimization skill โ don't duplicate its checklist here and don't reach into it.
Baseline items to check on a public page:
noindex on purpose, not by accident.This is not about ranking magic. It's about the absence of technical sloppiness.
Before touching metadata, decide whether the page should be indexed at all:
noindex via meta tag or robots.txt.Walk the target page and check every item in the Checklist against it:
robots.txt and sitemap.xml presence and content against the indexability decision from step 1.<a> and actions use <button>.Produce findings only in this step. Don't fix anything yet.
For each finding, decide fix now vs. list for later:
Keep fixes minimal. Don't add marketing pages, new routes, or content beyond what's needed to fill the checklist.
Report back:
This is technical packaging, not a ranking campaign:
geo-optimization skill.noindex, not a full SEO pass.