agentleFS
joaoguirunasjoaoguirunas/team-os/.claude/skills/seo-flow/SKILL.md

seo-flow

Skill6 starsChanged 2 days agoMITView on GitHub

Integração do framework FLOW — SEO guiado por evidência no ciclo Find → Leverage → Optimize → Win, com prompts por estágio da base FLOW (41 prompts, CC BY 4.0). Use ao pedir 'FLOW', 'seo flow', 'evidence-led SEO' ou prompts de SEO por estágio.

17 other projects use a version of this, 16 of them edited.

Adopted by

Most recently taken up by

Used with

Projects with it also use seo-agentic.

Other files people use alongside this one.

Files found in the same public projects as a version of this one, more often than they turn up anywhere else. Each project counts once, large collections count for less, and this file's own repository is left out.
  • AgriciDanielSkill

    seo-agentic

    Audit and fix agent readiness: the Lighthouse Agentic Browsing fraction, accessibility tree for agents, robots.txt and Content-Signal for AI agents, WAF treatment of agent traffic, llms.txt, Markdown delivery, ai-catalog.json, /.well-known discovery files, and WebMCP tools. Use when the user asks whether AI agents can use or browse the site, or about llms.txt or WebMCP. Exclude AI citability and brand signals (seo-geo) and commerce protocol depth (seo-ecommerce).

    Also in 3 projects that use this

The file

We split this skill into the rules it gives an agent

8 rules. 4 are common, 0 are distinctive, and 4 are very specific to this project.

  • 4

    Common

    Most of the 16 edited versions we read keep these.

  • 0

    Distinctive

    This author's own choices. Worth a look.

  • 4

    Very specific

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

  • Common
  • Distinctive
  • Very specific
  1. Common:

    Ask: which stage matches the user's current situation?

    line 48
  2. Very specific:

    Read all files in references/prompts/find/

    line 51
  3. Very specific:

    Read the file in references/prompts/leverage/

    line 56
  4. Very specific:

    Read all file names in references/prompts/optimize/

    line 61
  5. Common:

    Read prior analysis context (URL, industry vertical, any prior skill output in conversation)

    line 62
  6. Common:

    Always surface exactly 2-3 prompts.

    line 96
  7. Very specific:

    Every /seo flow activation (any sub-command) outputs before analysis:

    line 116
  8. Common:

    Do not omit or modify the attribution.

    line 122

“Common” is measured: kept by at least 6 in 10 of the 16 edited versions of this file we could read. “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

FLOW Framework: Find · Leverage · Optimize · Win

FLOW is an evidence-led SEO operating model built for the AI-search era. Claude SEO integrates the FLOW prompt library (41 prompts across 5 stages) so every analysis can be driven by structured, evidence-backed AI prompts rather than improvised queries.

Framework and prompts © Daniel Agrici, CC BY 4.0: github.com/AgriciDaniel/flow

Runtime context: Load references/flow-framework.md on every /seo flow activation. Load prompt files on demand, only for the stage the user requests.


Commands

CommandWhat it does
/seo flowShow FLOW overview + stage menu
/seo flow find [url|topic]Find-stage: keyword research, gap analysis, SERP intent mapping (5 prompts)
/seo flow leverage [url]Leverage-stage: backlink strategy, off-site authority (1 prompt)
/seo flow optimize [url]Optimize-stage: select 2-3 most relevant of 21 prompts based on context
/seo flow win [url]Win-stage: BOFU, conversion rate, dual-surface scorecard (3 prompts)
/seo flow local [url]Local-stage: GBP optimization, meta, title tags, local audits (11 prompts)
/seo flow promptsFull index of all 41 prompts (stage, name, trigger conditions)
/seo flow syncPull latest prompt files from github.com/AgriciDaniel/flow

Orchestration Logic

On /seo flow (no sub-command)

  1. Read references/flow-framework.md
  2. Show the FLOW stage overview with a one-line description of each stage
  3. Ask: which stage matches the user's current situation?

On /seo flow find [url|topic]

  1. Read all files in references/prompts/find/
  2. Apply each prompt to the URL or topic
  3. Cross-reference: "For deeper SERP clustering, see /seo cluster <seed-keyword>"

On /seo flow leverage [url]

  1. Read the file in references/prompts/leverage/
  2. Apply to the URL's current backlink context
  3. Cross-reference: "For raw backlink data, see /seo backlinks <url>"

On /seo flow optimize [url]

  1. Read all file names in references/prompts/optimize/
  2. Read prior analysis context (URL, industry vertical, any prior skill output in conversation)
  3. Select 2-3 most relevant prompts; load only those files
  4. Apply selected prompts; note the others are accessible via /seo flow prompts
  5. Cross-reference: "For full content quality analysis, see /seo content <url> and /seo geo <url>"

On /seo flow win [url]

  1. Read all files in references/prompts/win/
  2. Apply each prompt to the URL's conversion and BOFU context
  3. Cross-reference: "For SXO persona scoring, see /seo sxo <url>"

On /seo flow local [url]

  1. Read all files in references/prompts/local/
  2. Apply to the URL's local SEO context
  3. Cross-reference: "For full local SEO analysis, see /seo local <url> and /seo maps [command]"

On /seo flow prompts

  1. Read references/prompts/README.md
  2. Display the full index: all 41 prompts with stage, name, trigger conditions

On /seo flow sync

  1. Run: "${CLAUDE_PROJECT_DIR:-$(git rev-parse --show-toplevel 2>/dev/null || pwd)}/.claude/skills/seo/scripts/claude-seo" run sync_flow.py
  2. Display the JSON summary (files added, updated, unchanged)
  3. Show attribution notice after sync completes

Context Matching (Optimize stage)

The optimize stage has 21 prompts. Dumping all 21 is noise. Select by priority:

  1. Industry vertical (SaaS → on-page + technical; local → citations + GBP; publisher → E-E-A-T + freshness)
  2. Prior skill output (seo-technical flagged crawl issues → technical optimize prompts; seo-content flagged E-E-A-T gaps → content optimize prompts)
  3. URL signals (product pages → conversion; blog → freshness + authority)

Always surface exactly 2-3 prompts. State which prompts you chose and why.


Reference Files

Load on-demand, do NOT load all at startup:

  • references/flow-framework.md: FLOW operating model (load on every /seo flow activation)
  • references/bibliography.md: Evidence sources; load when citing studies or statistics
  • references/prompts/README.md: Prompt index; load for /seo flow prompts
  • references/prompts/find/: 5 prompts; load for /seo flow find
  • references/prompts/leverage/: 1 prompt; load for /seo flow leverage
  • references/prompts/optimize/: 21 prompts; load selectively for /seo flow optimize
  • references/prompts/win/: 3 prompts; load for /seo flow win
  • references/prompts/local/: 11 prompts; load for /seo flow local

Attribution

Every /seo flow activation (any sub-command) outputs before analysis:

Framework and prompts © Daniel Agrici, CC BY 4.0: github.com/AgriciDaniel/flow

Do not omit or modify the attribution.


Error Handling

ScenarioAction
references/flow-framework.md missing"FLOW reference files not synced. Run: /seo flow sync"
Prompt file missing"Run /seo flow sync to pull the latest prompts from the FLOW repo."
sync_flow.py network errorDisplay the script's stderr. Check rate limits: gh api rate_limit.
sync_flow.py auth errorRun gh auth login then retry.

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.