FLOW Framework — Find · Leverage · Optimize · Win
FLOW framework integration — evidence-led SEO using the Find → Leverage → Optimize → Win loop. Surfaces stage-specific AI prompts from the FLOW knowledge base (41 prompts, CC BY 4.0). Use when user says "FLOW", "FLOW framework", "seo flow", "evidence-led SEO", "find leverage optimize win", or wants stage-specific SEO prompts.
MCP get_skill({ skillId: "flow-framework-find-leverage-optimize-win-42f6148b" })Use this skill with your agent
Create a free account and connect via MCP
# FLOW Framework — Find · Leverage · Optimize · Win > Framework and prompts © Daniel Agrici, CC BY 4.0 — github.com/AgriciDaniel/flow 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. **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 | Command | What it does | |---------|-------------| | `/seo flow` | Show 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 prompts` | Full index of all 41 prompts — stage, name, trigger conditions | | `/seo flow sync` | Pull 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: `python scripts/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 | Scenario | Action | |----------|--------| | `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 error | Display the script's stderr. Check rate limits: `gh api rate_limit`. | | `sync_flow.py` auth error | Run `gh auth login` then retry. |
Related Skills
More skills in Business, Marketing & Sales
Ab Testing
When the user wants to plan, design, or implement an A/B test or experiment, or build a growth experimentation program. Also use when the user mentions "A/B test," "split test," "experiment," "test this change," "variant copy," "multivariate test," "hypothesis," "should I test this," "which version is better," "test two versions," "statistical significance," "how long should I run this test," "growth experiments," "experiment velocity," "experiment backlog," "ICE score," "experimentation program," or "experiment playbook." Use this whenever someone is comparing two approaches and wants to measure which performs better, or when they want to build a systematic experimentation practice. For tracking implementation, see analytics. For page-level conversion optimization, see cro.
Ab Test Setup
When the user wants to plan, design, or implement an A/B test or experiment. Also use when the user mentions "A/B test," "split test," "experiment," "test this change," "variant copy," "multivariate test," "hypothesis," "conversion experiment," "statistical significance," or "test this." For tracking implementation, see analytics-tracking.
Ab Test Setup
Ab Test Setup linked from Corey Haines marketing skills, with the upstream skill instructions available on GitHub.
Ab Test Store Listing
When the user wants to A/B test App Store product page elements to improve conversion rate. Also use when the user mentions "A/B test", "product page optimization", "test my screenshots", "test my icon", "conversion rate optimization", "CPP", or "custom product pages". For screenshot design, see screenshot-optimization. For metadata optimization, see metadata-optimization.
Account Research
Research a company or person and get actionable sales intel. Works standalone with web search, supercharged when you connect enrichment tools or your CRM. Trigger with "research [company]", "look up [person]", "intel on [prospect]", "who is [name] at [company]", or "tell me about [company]".
Account Research
Research a company using Common Room data. Triggers on 'research [company]', 'tell me about [domain]', 'pull up signals for [account]', 'what's going on with [company]', or any account-level question.
Explore Other Categories
Skills from other categories with shared topics
/tour — Interactive walkthrough
Interactive walkthrough of the Memory Kit system using the user's actual project files
AgentMail — Agent-Owned Email Inboxes
Give the agent its own dedicated email inbox via AgentMail. Send, receive, and manage email autonomously using agent-owned email addresses (e.g. hermes-agent@agentmail.to).
AI Agent Builder
Build AI agents with tools, memory, and multi-step reasoning - ChatGPT, Claude, Gemini integration patterns