AGENT SKILL

seo-flow

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.

License 许可
MIT
最近更新
2026-10-22
Stars
★ 1
Forks
0

01 前言 Front Matter

name
seo-flow
license
MIT
metadata
{ "author": "AgriciDaniel", "version": "2.2.5", "category": "seo" }
description
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.
argument-hint
[stage] [url|topic]
user-invocable
true

02 资源文件 45

03 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

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: 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

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.

04 同仓库更多 Skills

Hazek-dc
Hazek-dc/PresensiGuru_FaceNet_EMAR

testing-best-practices

Laravel test design and review. Use when selecting coverage, naming or structuring tests, choosing assertions or test data, isolating dependencies, testing HTTP or security boundaries, improving suite performance, or reviewing test value. Use framework guidance or search-docs for Pest and PHPUnit syntax.

★ 1
Hazek-dc
Hazek-dc/PresensiGuru_FaceNet_EMAR

tailwindcss-development

Always invoke when the user's message includes 'tailwind' in any form. Also invoke for: building responsive grid layouts (multi-column card grids, product grids), flex/grid page structures (dashboards with sidebars, fixed topbars, mobile-toggle navs), styling UI components (cards, tables, navbars, pricing sections, forms, inputs, badges), adding dark mode variants, fixing spacing or typography, and Tailwind v3/v4 work. The core use case: writing or fixing Tailwind utility classes in HTML templates (Blade, JSX, Vue). Skip for backend PHP logic, database queries, API routes, JavaScript with no HTML/CSS component, CSS file audits, build tool configuration, and vanilla CSS.

★ 1
Hazek-dc
Hazek-dc/PresensiGuru_FaceNet_EMAR

laravel-best-practices

Apply this skill whenever writing, reviewing, or refactoring Laravel PHP code. This includes creating or modifying controllers, models, migrations, form requests, policies, jobs, scheduled commands, service classes, and Eloquent queries. Triggers for N+1 and query performance issues, caching strategies, authorization and security patterns, validation, error handling, queue and job configuration, route definitions, and architectural decisions. Also use for Laravel code reviews and refactoring existing Laravel code to follow best practices. Covers any task involving Laravel backend PHP code patterns.

★ 1
Hazek-dc
Hazek-dc/PresensiGuru_FaceNet_EMAR

infer-conventions

Use this skill to analyze how a Laravel application is actually written and record its conventions as shared rules. Trigger when the user wants to detect, infer, document, or standardize project conventions or coding style, set up or grow `.ai/rules`, resolve mixed or conflicting patterns (e.g. "are we using Form Requests or inline validation?"), or onboard agents and teammates to "how we do things here". Covers: a systematic sweep of ~49 Laravel convention dimensions (validation, models, architecture, testing, frontend, database, console), open-ended house-pattern discovery, conflict reporting, and recording rules scoped to the right paths via the Boost `record-rule` MCP tool. Only run this skill when the user explicitly asks for it; never start a sweep as part of another task. Do not use for one-off code review, enforcing formatting a linter already handles, or editing `.ai/rules` files by hand.

★ 1
Hazek-dc
Hazek-dc/PresensiGuru_FaceNet_EMAR

inertia-react-development

Develops Inertia.js v2 React client-side applications. Activates when creating React pages, forms, or navigation; using <Link>, <Form>, useForm, or router; working with deferred props, prefetching, or polling; or when user mentions React with Inertia, React pages, React forms, or React navigation.

★ 1
Hazek-dc
Hazek-dc/PresensiGuru_FaceNet_EMAR

deploying-to-cloud

Deploys and manages Laravel applications on Laravel Cloud using the `cloud` CLI. Use when the user wants to deploy an app, ship to Cloud, create or manage applications, environments, databases, caches, object storage, queues, domains, instances, background processes, secrets, compute, scheduled tasks, or Laravel Cloud infrastructure; or check billing, usage, or spend. Triggers on deployment, shipping, Cloud management, environment setup, database provisioning, billing or usage queries, the `cloud` CLI, and Laravel Cloud deployment troubleshooting.

★ 1