Skill

Pass

Audit score 90

blog-flow

agricidaniel/claude-blog

FLOW framework integration for evidence-led blog workflows: Find, Optimize, Win stages with 30 CC BY 4.0 prompts.

What is blog-flow?

Implements the FLOW (Find, Optimize, Win) framework for bloggers to turn query data, source notes, and page evidence into structured decisions. Use when you need stage-specific prompts for keyword discovery, content optimization, or conversion strategy instead of improvised prompts.

Run Find-stage prompts for keyword discovery, intent mapping, and gap analysis (5 prompts)
Select 2–3 most relevant Optimize-stage prompts from 21 based on niche, prior skill output, and URL signals
Apply Win-stage prompts for BOFU, conversion, and dual-surface scoring (3 prompts)
Access the full index of 30 blog-applicable prompts grouped by stage (Find, Leverage, Optimize, Win)
Sync latest prompt files from the upstream FLOW repository with atomic writes and lockfile tracking

How to install blog-flow

npx skills add https://github.com/agricidaniel/claude-blog --skill blog-flow

Prerequisites

Claude Code or Cursor with Python 3.11+
Run `/blog flow sync` once to pull prompt files from github.com/AgriciDaniel/flow

Claude Code

Cursor

Windsurf

Cline

How to use blog-flow

1.Run `/blog flow` to see the FLOW stage overview and choose your current workflow stage
2.For keyword discovery, run `/blog flow find [topic|url]` to apply 5 Find-stage prompts
3.For content optimization, run `/blog flow optimize [url]` to select and apply 2–3 most relevant prompts from 21 based on context
4.For conversion strategy, run `/blog flow win [url]` to apply BOFU and conversion prompts
5.Run `/blog flow prompts` to view the full index of 30 prompts and their trigger conditions
6.Run `/blog flow sync` periodically to pull the latest prompt files and refresh the lockfile

Use cases

Good for

Discover keyword gaps and content opportunities for a new blog topic
Select the most impactful optimization prompts for a commercial or informational post based on E-E-A-T gaps or SEO failures
Develop conversion and bottom-of-funnel strategies for high-value pages
Audit your blog's prompt library against the latest FLOW framework updates
Cross-reference FLOW analysis with other blog skills (brief, outline, rewrite, seo-check, schema, factcheck)

Who it's for

Blog writers and content strategists using evidence-led workflows
SaaS and B2B marketers optimizing on-page and technical content
Lifestyle and publisher bloggers building authority and freshness
Teams standardizing prompt selection across multiple blog projects

blog-flow FAQ

Why does Optimize stage only show 2–3 prompts instead of all 21?

Dumping all 21 prompts is noise. The skill selects by priority: niche (SaaS vs. lifestyle vs. publisher), prior skill output (E-E-A-T gaps, SEO failures, geo gaps), and URL signals (commercial vs. informational). You can always view all 21 via `/blog flow prompts`.

What if my references directory is missing or out of date?

Run `/blog flow sync` to pull the latest prompt files from github.com/AgriciDaniel/flow. The sync script uses atomic writes, path-traversal guards, and a lockfile to track drift.

Are local-SEO prompts (GBP, citations, local audits) included?

No, they are intentionally excluded because they target brick-and-mortar work, not blogs. If you need local-SEO prompts, use `/seo flow local` in the claude-seo skill.

How do I use FLOW output with other blog skills?

FLOW Find routes to `/blog brief`, `/blog outline`, and `/blog cannibalization`. FLOW Optimize routes to `/blog rewrite`, `/blog seo-check`, `/blog geo`, `/blog schema`, and `/blog factcheck`. FLOW Win routes to `/blog repurpose`, `/blog audit`, and `/blog analyze`.

Can I pin the sync to a specific FLOW commit?

Yes. Run `python3 scripts/sync_flow.py --ref <sha>` to pin fetches to a known-good commit SHA for reproducible installs.

Full instructions (SKILL.md)

Source of truth, from agricidaniel/claude-blog.

name: blog-flow description: > FLOW framework integration for bloggers. Evidence-led content workflow using the Find, Optimize, Win loop with stage-specific AI prompts from the FLOW knowledge base (30 blog-applicable prompts, CC BY 4.0). Use when user says "FLOW", "FLOW framework", "blog flow", "evidence-led blogging", "find optimize win", or wants stage-specific blog prompts. user-invokable: true argument-hint: "[stage] [url|topic]" license: MIT compatibility: Requires Claude Code and Python 3.11+ for the sync script metadata: author: AgriciDaniel version: "2.2.0" category: blog

FLOW Framework for Bloggers (Find, Optimize, Win)

Runs FLOW Find/Optimize/Win prompts for a blog topic or URL, turning query data, source notes, and page evidence into structured decisions instead of improvised prompts.

Framework and prompts (c) Daniel Agrici, CC BY 4.0. Source: github.com/AgriciDaniel/flow

FLOW is an evidence-led operating model for retrieval, citation, and conversion workflows. Claude Blog integrates the FLOW prompt library so writers can turn query data, source notes, and page evidence into structured decisions instead of improvised prompts.

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
`/blog flow win [url]`	Win-stage: BOFU, conversion, dual-surface scorecard (3 prompts)
`/blog flow prompts`	Full index of all 30 blog-applicable prompts (Find, Leverage, Optimize, Win)
`/blog flow sync`	Pull latest prompt files from github.com/AgriciDaniel/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 claude-seo (/seo flow local) if they need them.

On `/blog flow sync`

Run: python3 scripts/sync_flow.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.py pulls prompt files from github.com/AgriciDaniel/flow and writes them under skills/blog-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.py. Sync the latest version of every blog-relevant stage to disk and refresh the lockfile.
python3 scripts/sync_flow.py --dry-run. Report planned changes without writing.
python3 scripts/sync_flow.py --ref <sha>. Pin fetches to a specific FLOW commit SHA for reproducible installs.

The lockfile lives at skills/blog-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) Daniel Agrici, CC BY 4.0. Source: github.com/AgriciDaniel/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.py` network error	Display the script's stderr. Check rate limits with `gh api rate_limit` if `gh` is installed.
`sync_flow.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`.