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.
Standardmäßig ist der Prompt ausgewählt, der zuerst die Quelle prüft. Sie können zu einem direkten Befehl wechseln oder eine lokale Kopie herunterladen.
Quelldateien prüfen
Lesen Sie SKILL.md und alle von SkillsMP angezeigten Begleitdateien, bevor Sie sich für eine Installation entscheiden.
Mit Codex oder Claude installieren Kopieren Sie diesen Prompt, fügen Sie ihn in Codex, Claude oder einen anderen Assistant ein und lassen Sie die Skill-Seite prüfen und installieren.
Ein direkter Befehl überspringt den Prüf-Prompt. Prüfen Sie die Quelle, bevor Sie ihn ausführen.
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.
Before gathering, check .seo-cache/ for reusable context from related SEO skills.
Reference: ../seo/references/shared-data-cache.md for schemas and dependency map.
Check these cache files when present:
.seo-cache/site-meta.json for domain, business type, industry, and crawl context
.seo-cache/audit-scores.json for prior full-audit priorities
.seo-cache/pages/{url-slug}/page-analysis.json for page-level context when a URL is provided
If found: parse and use clearly valid fields (note "Using cached [X] from [date]")
If missing, corrupt, or irrelevant: continue with fresh evidence
If the user says "refresh" or "re-run": ignore cache reads and overwrite on write
FLOW is an evidence-led SEO operating model built for the AI-search era. Antigravity 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)
"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.
Write to shared data cache
After completing all work, write a concise JSON summary to .seo-cache/ when the workflow produced durable findings.
Use the schemas and naming rules in ../seo/references/shared-data-cache.md; include at least cache_type, analyzed_at, source URL/domain, key findings, issues, recommendations, and tool limitations. Add .seo-cache/ to .gitignore if it is missing.
Extended Capabilities (from blog-flow)
Framework and prompts (c) dotusmanali (dotusmanali@gmail.com), CC BY 4.0. Source: github.com/dotusmanali/flow
FLOW is an evidence-led operating model built for the AI-search era. Antigravity Blog
integrates the FLOW prompt library so writers can drive their workflow with
structured, source-backed AI prompts instead of improvised queries.
This skill exposes the three blog-relevant stages (Find, Optimize, Win) and keeps
the single Leverage prompt available through the prompts index. The local-SEO
prompts (GBP, citations, local audits) are intentionally excluded because they
target brick-and-mortar work, not blogs.
Runtime context. Load references/flow-framework.md on every /blog flow
activation. Load prompt files on demand only, scoped to the stage the user
requests.
Commands
Command
What it does
/blog flow
Show FLOW overview and stage menu
/blog flow find [topic|url]
Find-stage: keyword discovery, intent mapping, gap analysis (5 prompts)
/blog flow optimize [url]
Optimize-stage: select 2 to 3 most relevant prompts of 21 based on context
Full index of all 30 blog-applicable prompts (Find, Leverage, Optimize, Win)
/blog flow sync
Pull latest prompt files from github.com/dotusmanali/flow
The single Leverage prompt (off-site authority) is reachable through
/blog flow prompts and is not promoted to a top-level command, since most
blog workflows route off-site work elsewhere.
Orchestration Logic
On /blog flow (no sub-command)
Read references/flow-framework.md.
Show the FLOW stage overview with a one-line description of each stage.
Ask the user which stage matches their current situation.
On /blog flow find [topic|url]
Read all files in references/prompts/find/.
Apply each prompt to the topic or URL, capturing demand and intent signals.
Cross-reference: "For deeper briefs and outlines, see /blog brief <topic>,
/blog outline <topic>, and /blog cannibalization to detect overlap with
existing posts."
On /blog flow optimize [url]
Read the file names in references/prompts/optimize/.
Read prior context (target URL, niche, any prior skill output in this
conversation, scoring deltas from /blog analyze).
Select 2 to 3 most relevant prompts, then load only those files.
Apply the selected prompts; note that the rest are accessible via
/blog flow prompts.
Cross-reference: "For deeper rewrites and validation, see /blog rewrite <file>, /blog seo-check <file>, /blog geo <file>, /blog schema <file>,
and /blog factcheck <file>."
On /blog flow win [url]
Read all files in references/prompts/win/.
Apply each prompt to the URL's conversion and BOFU context.
Cross-reference: "For repurposing, full-site health, and quality scoring,
see /blog repurpose <file>, /blog audit, and /blog analyze <file>."
On /blog flow prompts
Read references/prompts/README.md.
Display the full index: 30 prompts grouped by stage (Find, Leverage,
Optimize, Win) with name and trigger conditions.
State that local-SEO prompts are excluded by design; point users to
antigravity-seo (/seo flow local) if they need them.
On /blog flow sync
Run: python3 scripts/sync_flow_blog.py.
Display the JSON summary (files added, updated, unchanged).
Show the attribution notice after the sync completes.
Context Matching (Optimize stage)
The optimize stage has 21 prompts. Dumping all 21 is noise. Select by priority:
Niche (SaaS or B2B blog leans on-page plus technical; lifestyle leans
freshness plus E-E-A-T; publisher leans authority plus citations).
Prior skill output (/blog analyze E-E-A-T gap routes to authority
prompts; /blog seo-check failures route to on-page prompts; /blog geo
gaps route to extraction-format prompts).
URL signals (commercial pages need conversion prompts; informational
posts need freshness plus answer-first prompts).
Always surface exactly 2 to 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 /blog flow activation.
references/bibliography.md. Evidence sources. Load when citing studies or
statistics.
references/prompts/README.md. Prompt index. Load for /blog flow prompts.
references/prompts/find/. 5 prompts. Load for /blog flow find.
references/prompts/leverage/. 1 prompt. Load only when surfaced through
/blog flow prompts.
references/prompts/optimize/. 21 prompts. Load selectively for /blog flow optimize.
references/prompts/win/. 3 prompts. Load for /blog flow win.
If references/ is missing, instruct the user to run /blog flow sync first.
Sync Script
scripts/sync_flow_blog.py pulls prompt files from github.com/dotusmanali/flow and
writes them under skills/seo-flow/references/. Stdlib only, HTTPS only,
host-allowlisted to api.github.com, 5 MB response cap, atomic writes,
path-traversal guarded.
Modes:
python3 scripts/sync_flow_blog.py. Sync the latest version of every blog-relevant
stage to disk and refresh the lockfile.
python3 scripts/sync_flow_blog.py --dry-run. Report planned changes without
writing.
python3 scripts/sync_flow_blog.py --ref <sha>. Pin fetches to a specific FLOW
commit SHA for reproducible installs.
The lockfile lives at
skills/seo-flow/references/flow-prompts.lock and uses sha256sum-compatible
format. Drift between the on-disk content and the lockfile is reported on every
sync run.
The script syncs only blog-applicable stages (find, leverage, optimize,
win). The local stage is intentionally skipped to keep the references
directory aligned with the skill's surface area.
GitHub API calls are anonymous by default. If GITHUB_TOKEN is set in the
environment, or gh auth token returns a token after a 403 response, the
script retries the request with that token. No tokens are written to disk.
Attribution
Every /blog flow activation (any sub-command) outputs before analysis:
Framework and prompts (c) dotusmanali (dotusmanali@gmail.com), CC BY 4.0. Source: github.com/dotusmanali/flow
Do not omit or modify the attribution. Synced files also carry an HTML comment
license header injected by the sync script.
Error Handling
Scenario
Action
references/flow-framework.md missing
"FLOW reference files not synced. Run: /blog flow sync."
Prompt file missing
"Run /blog flow sync to pull the latest prompts from the FLOW repo."
sync_flow_blog.py network error
Display the script's stderr. Check rate limits with gh api rate_limit if gh is installed.
sync_flow_blog.py 403 after retry
Set GITHUB_TOKEN or run gh auth login, then retry.
Path-traversal abort
The sync target tried to escape the references directory. Inspect the upstream repo and pin to a known-good --ref.
