seo-context
SEO context
Create and maintain .seo-context.md in the project root so SEO skills can reuse durable project facts instead of repeating discovery.
Article-specific writing preferences belong in .agents/article-writing-context.md, which is created and maintained by the article-writing skill. Do not force voice, image, source, or publishing preferences into this SEO context unless they are also durable business or content constraints.
Other SEO skills should read this file first and ask only for missing task-specific details.
Preflight
Read and follow the shared project, connected-tool, property-resolution, missing-input, and secret-handling rules in ../docs/credentials-and-tooling.md.
For this skill, confirm high-impact business facts rather than silently inferring them. If money-page status, conversions, target markets, or strategic priorities remain unknown, record them as unknown or as candidates awaiting confirmation.
Use .seo-context.md as the reusable record for project tooling. On the first run, inspect callable tools and connectors, save the relevant inventory with its check date and status source, and ask the user whether other tools are available but not visible to the agent. On later runs, reuse that inventory instead of repeating broad discovery. Re-check a specific tool when the task needs live access, the inventory is missing or unknown, the user reports a setup change, or the check is more than 30 days old.