seo-offer-architect
Skill7 starsChanged 5 months agoMITView on GitHub
Turn SEO findings into a paid agency package or retainer. Use when Codex needs to structure findings, recommendations, and estimated impact into a sellable service offering.
In this repository22 other files it gives its agents.
- authority-mark-keyword-difficultySkill
- cannibalization-checkSkill
- client-report-writerSkill
- competitor-serp-monitorSkill
- content-decay-monitor-setupSkill
- content-moat-plannerSkill
- content-refresh-briefSkill
- exceed-quality-thresholdSkill
- internal-link-builderSkill
- keyword-opportunity-finderSkill
- keyword-plannerSkill
- live-search-console-dataSkill
- proposal-builderSkill
- refresh-vs-new-contentSkill
- schema-fix-writerSkill
- seo-content-briefSkill
- seo-growth-loopSkill
- seo-priority-scoreSkill
- seo-strategySkill
- technical-seo-triageSkill
- title-meta-rewriterSkill
- traffic-decay-detectorSkill
The file
We split this skill into the rules it gives an agent
1 rule. About 0 are common, 1 is distinctive, and 0 are 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.
0
Very specific
Tied to their project's names, files or tools. Probably skip.
- Common
- Distinctive
- Very specific
- Distinctive: line 30
Write the offer narrative: problem → solution → outcome.
≈ “Common” is an estimate: at least 1 in 5 of the 350,495 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.
Files
SEO Offer Architect
Overview
Given a prospect or client's SEO diagnosis (from Diagnose skills) and strategic context, structure the findings into a priced agency package or retainer proposal. This bridges diagnosis output to revenue.
Inputs
- SEO diagnosis output (issues found, opportunities sized)
- Client business context and goals
- Optional: competitor analysis, market positioning
Workflow
- Review diagnosis findings and categorize by service type:
- Technical fixes (one-time / recurring)
- Content work (refresh, new content, strategy)
- Authority building (linkable assets, outreach)
- Reporting and monitoring
- Structure packages:
- Scope: what's included, what's excluded
- Deliverables per package
- Timeline and milestones
- Price each package based on effort, specialization, and client size.
- Write the offer narrative: problem → solution → outcome.
- Include success metrics and expected impact ranges.
Output
Priced agency package or retainer structure with scope, deliverables, timeline, and pricing.
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.