{"id":17534,"plugin_id":"plugins_6a78f4659d108191877f1a968a4ae987","kind":"skill","collection_source":null,"comparison_source":null,"observed_at":"2026-09-30T23:14:15.150Z","digest":"07cfe14a2e57b28bc52fa066132c7afbed503a75345a586870b8435e606f4b3f","against":null,"payload":{"description":"Use when the user needs SEO strategy, keyword research, content gaps, on-page SEO, technical SEO diagnosis, internal linking, site architecture, local SEO, programmatic SEO, schema planning, or organic-search prioritization.","included_files":[{"relative_path":"agents/openai.yaml","size_in_bytes":199}],"name":"seo","skill_md_contents":"---\nname: seo\ndescription: Use when the user needs SEO strategy, keyword research, content gaps, on-page SEO, technical SEO diagnosis, internal linking, site architecture, local SEO, programmatic SEO, schema planning, or organic-search prioritization.\n---\n\n# SEO\n\n## Use it for\n\n- SEO audits\n- Keyword and intent research\n- Content clusters and site architecture\n- On-page or technical diagnosis\n- Local and programmatic SEO planning\n\n## Operating rules\n\n- Use context already present in the conversation before asking for more input.\n- Separate known facts, reasonable assumptions, and unknowns. Do not present assumptions as evidence.\n- When the answer depends on current platform rules, market conditions, pricing, benchmarks, or competitors, verify them with current sources when tools are available.\n- Prefer concrete decisions, examples, and next actions over generic marketing advice.\n- Do not invent campaign performance, customer quotes, research findings, testimonials, rankings, or competitor claims.\n- Keep the requested market, language, funnel stage, audience awareness, budget, and channel constraints visible throughout the work.\n- Verify current search guidance and product behavior when the answer depends on recent changes.\n- Separate technical blockers, relevance, quality, authority, and SERP competition.\n- Do not promise rankings.\n- Do not create thin pages simply to scale keyword coverage.\n\n## Workflow\n\n1. Define business goal, target market, site type, conversion path, and current organic baseline if available.\n2. Map search demand by intent and business relevance.\n3. Assess current pages, gaps, cannibalization, internal linking, and technical constraints.\n4. Prioritize work by impact, confidence, effort, and dependency.\n5. Specify page-level changes and technical requirements.\n6. Define measurement using impressions, clicks, qualified traffic, conversions, and business outcomes.\n\n## Output contract\n\n- SEO diagnosis\n- Priority roadmap\n- Keyword/intent or page map when relevant\n- Technical and on-page actions\n- Measurement plan\n\n## Quality gate\n\n- Recommendations tie to search intent and business value\n- No bulk-content recommendation without quality safeguards\n- Technical issues include verification method\n- Priority order is explicit\n\n## Handoff\n\nIf the task is part of a larger marketing request, return the completed deliverable plus the evidence or decisions the next PrePilot skill needs. Do not repeat upstream analysis unless it changes the result.\n"},"changes":[],"summary":"First saved snapshot. No earlier version is available for comparison.","summary_kind":"deterministic","summary_metadata":{}}