| name | site-growth |
| description | Code-generation orchestrator skill for multi-area Career Hub growth work that spans SEO, IA, tools, and expansion opportunities. Use only when the task is broader than one narrower skill. |
| metadata | {"family":"orchestrators","owner":"engineering + content","last_reviewed":"2026-04-30T00:00:00.000Z","version":"1.0.0"} |
Site Growth
This is a code-generation skill. Use it as an orchestrator for broad growth work that should lead to multiple repo-backed recommendations or phased implementation.
Use When
- quarterly or monthly growth reviews
- post-launch audits across several page families
- prioritizing growth opportunities across SEO, internal linking, tool surfaces, and programmatic expansion
- deciding what to build next when several growth levers are on the table
Do Not Use When
- the task is a single SEO diagnosis
Use
seo-audit.
- the task is a single metadata/schema/canonical implementation
Use
seo-page-rules or schema-markup.
- the task is a single IA/navigation/internal-linking review
Use
site-architecture.
- the task is a single page conversion review
Use
page-cro.
Role
This skill should coordinate narrower skills, not duplicate all of them.
Priority Order
- crawlability and rendering health
- internal linking and site architecture gaps
- tool and interactive surface opportunities
- programmatic coverage gaps
- CRO and download-path improvements
Required Output
Return a Growth Priority Brief with:
top_opportunities
why_now
recommended_primary_skill_per_opportunity
expected_repo_areas
verification_or_monitoring_plan
semrush_research_runs — list of recipes from semrush-research that informed this brief, each with recipe, units_paid, and cache_hit. Use keyword-gap.md or pillar-deep-dive.md to source the data; do not hand-wave growth opportunities without it.
Example Routing
- metadata/canonical/schema issues ->
seo-page-rules
- technical diagnosis ->
seo-audit
- AI citation visibility ->
ai-seo
- navigation/internal-link systems ->
site-architecture
- template conversion issues ->
page-cro
- CTA psychology rationale ->
marketing-psychology
- UI implementation ->
frontend-design
Rule
Do not turn this skill into a giant catch-all audit with no clear implementation handoff.