For SEO agencies and hands-on in-house teams
SEO and search
v1.1.0One explicit choice between opportunity mapping and evidence-led content briefing, with the selected function Skill loaded before execution.
Route a broad SEO request to the smallest verified function Skill that owns either opportunity prioritisation or a cited content brief.
Choose the deliverable you need
Decide what to target next, then turn the selected opportunity into an evidence-led content brief.
- Organic Opportunity MapA cited, prioritised opportunity map with target evidence, competitor evidence, demand and difficulty signals, recommended next actions and explicit uncertainty labels.View Skill →
- Evidence-led Content BriefA writer-ready brief with one primary topic, audience and intent, a supported angle, source-backed claims, outline, exclusions and measurable acceptance criteria.View Skill →
What this Skill does—and does not do
The router does not run catalog tools, combine workflows without a new checkpoint, provide continuous tracking, publish content or promise rankings.
Inputs
- The SEO outcome or deliverable the user wants
- Any supplied target domain, market, audience or selected topic
Outputs
- One selected verified function Skill and a concise reason
- A clear boundary when no verified function Skill owns the request
How this Skill works
- 1
Describe the outcome
Tell your agent which business result or artifact you need.
- 2
Select one function Skill
The router chooses the smallest verified Skill that owns that deliverable and stops when none does.
- 3
Review the paid plan
The selected function Skill shows its exact inputs, tools and maximum cost before paid work begins.
- 4
Review the finished result
After approval, your agent returns the promised output and reports the tools used, final cost and any limitations.
Full instructions your agent receives
Choose one outcome before selecting tools or spending credit. This router does not perform SEO research itself; it loads the smallest verified function Skill that owns the requested deliverable.
Before routing, use any supplied positioning, audience or client brief. If the project contains .agents/product-marketing.md, read it as context; it is not evidence and does not replace the task-specific domain, market or objective.
Route the request
- Use SEO Opportunity Map when the user needs to compare a domain with search competitors, identify evidence-backed organic opportunities, decide which topics deserve further work, or when the user gives a broad request such as “improve our SEO.”
- Use SEO Content Brief when the user already has a business topic or selected opportunity and needs a cited, writer-ready brief.
- For a broad request such as “improve our SEO,” start with SEO Opportunity Map unless the user already supplied a prioritised topic and explicitly wants a brief.
Do not execute both function Skills merely because both are installed. If the user wants the sequence, complete and review the opportunity map first; treat any selected topic and second paid plan as a new checkpoint before loading the content-brief workflow.
Return the selected Skill, the artifact it will produce and why the other route does not own the current job. Do not make the user choose between tool names.
Boundaries
The available function Skills do not provide continuous rank tracking, a full technical site audit, content publication, backlink outreach or ranking guarantees. State that boundary when the requested outcome falls outside the package; do not improvise a new paid workflow under the router.
After choosing a function, read its complete SKILL.md and follow its inputs, cost ceiling, approvals, state and acceptance criteria. If the selected Skill is not present in the current installation, ask before installing it from this repository and pin the source revision.
Cost and approvals
How pricing works
Routing is agent-side and makes no paid call.
Trial-safe limits
The selected function Skill presents and obtains approval for its own paid plan.
Your approval points
- Ask before installing or updating a missing function Skill; paid approvals belong to the selected function Skill
Related Resources
What are agentic workflows? Examples, architecture and when to use them
Learn how agentic workflows combine model decisions, external tools and human controls, with practical examples and a framework for choosing when they fit.
SEO agents: tools, workflows and controls
Learn how AI SEO agents use live search data to automate keyword research, SERP analysis and page decisions without automating away human judgment.
How an SEO agent turns noisy keyword data into a defensible content decision
See how an SEO agent used Scrollport to research keyword demand, test a content idea and produce an evidence-backed article under editorial supervision.