Growth — suite dispatcher

This skill routes work; it does not do analysis itself. Given any growth, SEO, AEO, or analytics request, identify the job, open the right member skill(s), and follow them in the right order. Never answer a growth question from memory when a member skill covers it — the skills carry the state and the honesty rules that make an answer trustworthy.

Every output renders through growth-report-format. Open it alongside whichever member skill is doing the work.

The data layer: agentman-google-search MCP

Every number in this suite comes from one of these calls. Use full tool names.

Default Agentman targets: GSC sc-domain:agentman.ai, GA4 property 471838641. For any other property, resolve the target before calling — never assume.

What this suite cannot answer

State the limit rather than reasoning past it. These eight tools do not return:

• SERP composition. Whether a click was lost to a competitor, an AI Overview, or a featured snippet. Position moved or it didn't; why is outside the data. This is the most common question after a traffic drop, and the honest answer is that answering it needs a look at the live SERP or a rank tracker.
• Demand we don't already rank for. GSC impressions only reveal queries Google already shows us for. "Which topic should we write about next" cannot be answered from first-party data alone — seo-keyword-competitor-research grounds choices between candidates, but net-new topic selection needs a volume source outside this suite.
• Backlinks. So "is this page stuck at position 12 because of content or because of authority" is not decidable here.
• Revenue. Key events are clicks, not dollars. Nothing joins to billing.

When a finding needs one of these, say so plainly instead of substituting a plausible cause.

Provenance rules — inherited by every member skill

1. Every number names the call that produced it. A figure without a traceable call does not go in the output.
2. Never mix tool outputs. audit_page returns no CTR, impressions, or position; gsc_search_analytics returns no page structure. Do not attach a performance claim to a structural finding unless you pulled it in the same run.
3. A failed or empty call is a finding. Report "the call returned no rows" and stop. Never substitute a remembered or estimated number.
4. Never cite a prior report, baseline, or document that is not in context.
5. Never invoke a skill you have not confirmed exists.

These exist because the failure has already happened here: a page audit reported correct structural facts, then attached invented impression and CTR figures off by roughly 6× against real Search Console data, and cited a prior report that did not exist. The tool was right; the narrative around it was fabricated.

The ordering rule

Trust → Diagnose → Act → Prove. Verify the measurement layer before treating a number as true; name a cause before shipping a fix; register anything you ship.

Trust is a caveat, not a blocker. Report the number with an (UNVERIFIED) tag when the audit chain hasn't run recently — do not withhold it. A workflow that demands three audits before answering "how was last week" sends people to the GA4 UI, and the discipline is lost entirely.

Target resolution (shared by every member skill)

1. A named target wins.
2. Otherwise the default registered in the skill's data/ binds — example-* files are fictional and never bind.
3. Otherwise ask — never guess a property.

The six jobs

Plus the AEO loop: aeo-visibility measures AI-surface presence → aeo-blog-generator produces for the prompts being lost → shipped work is registered → aeo-visibility re-measures.

Symptom router

Multi-skill playbooks

Onboard a new property:

1. growth-measurement-audit — inventory the measurement layer, write the registry
2. growth-tracking-verify — fire the key flows, confirm arrival
3. seo-opportunity-matrix — first ranked opportunity list
4. growth-report --cadence monthly — start the heartbeat; first run sets baselines

Traffic-drop triage:

1. Measurement check — instrumentation death is the first suspect
2. growth-report diagnose: segment by brand/non-brand, device, page, source
3. Act, and register the fix

Content sprint:

1. seo-opportunity-matrix + aeo-visibility — pick targets
2. seo-keyword-competitor-research — ground the choices
3. aeo-blog-generator / seo-title-rewrite — produce
4. Register what ships; growth-report picks up the movement

What this skill does not do

• It does not compute, estimate, or recall metrics itself.
• It does not cover paid acquisition, social, email, or lifecycle.
• Deprecated members (seo-weekly-report, traffic-acquisition-analysis) are never routed to.