agentleFS
link7373link7373/agentic-sales-marketing/.claude/skills/grow-seo/SKILL.md

grow-seo

Skill1 starsChanged 3 months agoMITView on GitHub

Build organic search as a channel — technical audit, keyword-to-funnel mapping, competitive read, prioritized fixes, and content briefs handed to /create-content. Run once to establish the plan, then quarterly to refresh; rank tracking rolls into /measure.

The file

We split this skill into the rules it gives an agent

3 rules. About 0 are common, 1 is distinctive, and 2 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.

  • 2

    Very specific

    Tied to their project's names, files or tools. Probably skip.

  • Common
  • Distinctive
  • Very specific
  1. Very specific:

    Build the question list: Start from knowledge/research/customer-language.md, expand with the Ahrefs MCP (or Bright Data search), and record …

    line 16
  2. Very specific:

    No site to optimize (marketplace-only or no web presence) → run the whole method against the marketplace listings.

    line 32
  3. Distinctive:

    Every candidate term reads as closed → that's a real finding, not a failure.

    line 33

≈ “Common” is an estimate: at least 1 in 5 of the 372,429 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.

Keep what fits and drop the rest. Your version, ready for your agents.
Files
SKILL.md

/grow-seo — The Channel That Compounds

Inputs: knowledge/positioning.md, knowledge/audience-profiles.md, knowledge/research/customer-language.md, knowledge/competitors.md, knowledge/strategy.md, the site or listings themselves. Agents: seo-specialist leads; tools-operator runs Ahrefs / Bright Data seo-audit; content-marketer receives the briefs; funnel-builder fixes technical and on-page issues. Method: knowledge/methods/seo.md.

Steps

  1. Set expectations first. State the timeline honestly: 4–8 months to meaningful movement. If the business needs sales sooner, say so and position SEO as the compounding investment running alongside the faster channel — never as the answer to an urgent revenue gap.
  2. Audit what exists. Technical health (indexation, speed, mobile, canonicals, broken links, sitemap) plus current rankings and any pages already earning impressions. Marketplace businesses: audit the listings instead — titles, tags, images, review volume.
  3. Build the question list. Start from knowledge/research/customer-language.md, expand with the Ahrefs MCP (or Bright Data search), and record volume and difficulty for each — weighting difficulty more heavily.
  4. Read the results pages. For every serious candidate, examine what actually ranks: page type, thoroughness, freshness, site authority. Mark each term open or closed, and say why. Closed doors get abandoned here, not discovered six months later.
  5. Map topics to funnel stages. Group related questions into clusters; assign each to AWARE / TRUSTING / BUYING per playbook.md §1. Prioritize commercial intent — it converts far better and is less contested.
  6. Prioritize the work. Rank every opportunity by effort vs. likely return. In practice the order is nearly always: (a) refresh pages already on page two, (b) fix anything technically broken, (c) improve titles and descriptions where impressions exist but clicks don't, (d) internal linking, (e) new content — last, because it's slowest.
  7. Write the briefs. For each prioritized topic, fill templates/content-brief.md — target question, intent, what ranks and what it misses, the angle, must-cover points, structure, internal links, conversion path. Hand to /create-content; the calendar picks them up ahead of invented topics.
  8. Instrument and set the review date. Confirm Search Console access and organic tracking so /measure can report impressions and average position monthly. Judge content at 3 months, again at 6 — record those dates now.

Before you start

  1. Required inputs: knowledge/positioning.md and knowledge/audience-profiles.md at seeded+; knowledge/research/customer-language.md present (without it, keyword research becomes guessing at phrasing).
  2. Scan knowledge/decision-log.md for tags channel, content — if a prior decision deprioritized SEO, this run either honors it or supersedes it explicitly.
  3. Gate check: none for research and briefing. Site changes are public → publishing gate via /build-funnel or /create-content.

If things go wrong

  • Ahrefs unauthorized → use Bright Data seo-audit/search plus Search Console; note that difficulty scores are estimates rather than measured, and say which numbers came from where.
  • No site to optimize (marketplace-only or no web presence) → run the whole method against the marketplace listings; the discipline transfers unchanged. If there's no surface at all, recommend /build-funnel first.
  • Every candidate term reads as closed → that's a real finding, not a failure. Report it, and recommend the channel where this audience is actually reachable.
  • Site is technically broken beyond quick fixes (platform limitations, no access) → prioritize what's fixable, park the rest in knowledge/pending.md with exact instructions.

Outputs

An SEO audit with prioritized fixes, a keyword-to-funnel topic map, and a set of content briefs queued into the calendar. Close with the report per templates/skill-report.md.

Writeback

knowledge/research/seo-<YYYY-MM>.md (audit + topic map); briefs into knowledge/content-calendar.md; technical fixes to knowledge/decision-log.md (tag: content); tracking setup to knowledge/tool-registry.md; a learning line to knowledge/methods/seo.md once results arrive.

Download now (ZIP)

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
What did you use it for? e.g. Reviewing pull requests in a Rails app

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.