growth-blueprint
Skill0 starsChanged 38 days agoNo licenceView on GitHub
Writes a website build's Growth Blueprint and the internal AM Briefing from the files Week 1 produced. Use when SEO or the AM asks to write or redo the Growth Blueprint, the Blueprint document or strategy write-up for a new build, or the AM Briefing on the Blueprint, for a client whose kickoff folder, Reference Kit, saved keyword research, sitemap report and competitor report exist. A script copies the keyword tiers and sitemap and checks sections, Source lines, figures and the page cap. Missing inputs become NEEDS INPUT lines, never invented figures. Do NOT use for the keyword research itself (use keyword-research), planning the sitemap (use site-structure-optimizer), benchmarking competitors (use competitor-analysis), the Blueprint Input Package from the Kickoff Call (use kickoff-call-processing), the brand and voice files (use client-reference-kit), checking that Week 1 is complete (use week-1-handoff-check), or the branded client deck built from the Blueprint (use blueprint-deck).
In this repository40 other files it gives its agents.
- CLAUDE.mdCLAUDE.md
- blueprint-deckSkill
- case-studySkill
- clickup-progress-syncSkill
- client-context-updateSkill
- client-feedbackSkill
- client-reference-kitSkill
- competitor-analysisSkill
- content-briefSkill
- content-gap-analysisSkill
- content-quality-auditorSkill
- design-qa-dev-prepSkill
- dev-handoff-indexSkill
- google-ads-analysisSkill
- google-ads-auditSkill
- homepage-design-briefSkill
- keyword-researchSkill
- kickoff-call-briefSkill
- kickoff-call-processingSkill
- new-build-kickoffSkill
- offsite-signal-analyzerSkill
- page-type-design-briefsSkill
- project-close-outSkill
- prospect-digital-auditSkill
- retainer-roadmapSkill
- seo-content-writerSkill
- seo-drift-monitorSkill
- serp-analysisSkill
- site-structure-optimizerSkill
- staging-site-qaSkill
- subagent-performance-reviewSkill
- technical-seo-checkerSkill
- week-1-client-emailSkill
- week-1-handoff-checkSkill
- week-2-client-emailSkill
- week-2-handoff-checkSkill
- week-5-client-emailSkill
- week-5-handoff-checkSkill
- week-6-go-live-emailSkill
- welcome-emailSkill
The file
We split this skill into the rules it gives an agent
2 rules. About 0 are common, 1 is distinctive, and 1 is very specific to this project.
≈0
Common · estimate
Many files like this have a rule of this kind.
≈1
Distinctive · estimate
This author's own choices. Worth a look.
1
Very specific
Tied to their project's names, files or tools. Probably skip.
No licence file, so all rights are reserved — read it at the source. We count its rules but don't quote them. Read them on GitHub.
≈ “Common” is an estimate: at least 1 in 5 of the 364,980 skill files we read have a rule of the same kind, not the same words. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.
Does it work?
Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.
No reviews yet
People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.
- It worked
- Partly
- It didn't
Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.
Your trail
Files you open will collect here, so you can find them again.
Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.
Now do this for your own.
Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.

