Blog Flow
FreeStreamline your blogging process with evidence-led prompts.
Free · Opens the source repo
What Blog Flow does
The Blog Flow skill integrates the FLOW framework specifically designed for bloggers, providing a structured approach to content creation through a series of evidence-based prompts. This skill operates on a Find, Optimize, Win loop, allowing users to systematically enhance their blogging workflow. By utilizing this skill, bloggers can transform raw data and source notes into actionable insights, rather than relying on improvised content generation. The framework is grounded in a library of 30 prompts that guide users through each stage of their blogging process, ensuring that their content is both relevant and optimized for audience engagement.
When users activate the skill with commands like /blog flow, they receive an overview of the FLOW framework and can choose which stage of the process they want to focus on. The Find stage assists in identifying keywords and mapping user intent, while the Optimize stage helps refine existing content based on specific prompts tailored to the user's niche. Finally, the Win stage is designed to enhance conversion strategies, making it a comprehensive tool for bloggers aiming to increase their content's effectiveness.
This skill is particularly beneficial for content creators who want to adopt a more analytical approach to blogging. By leveraging structured prompts, users can ensure that their content not only meets audience needs but also stands out in a competitive landscape. The skill is built for those who value data-driven decision-making in their writing, allowing them to focus on quality and relevance in their posts.
Overall, Blog Flow is an essential tool for bloggers who are looking to streamline their content creation process while ensuring that their work is backed by solid evidence and strategic thinking. It is designed to enhance productivity and effectiveness in blogging, making it a valuable addition to any content creator's toolkit.
When to use it
Use this skill when you want to enhance your blogging workflow with systematic, data-driven prompts at various stages of content creation.
When not to use it
This skill may not be suitable for casual bloggers who prefer a more spontaneous approach to writing or those focused exclusively on local SEO, as it excludes local-SEO prompts.
What you can build with it
Keyword Discovery
Use the `/blog flow find [topic|url]` command to uncover relevant keywords and map user intent, helping you create content that meets audience needs.
Content Optimization
Activate the `/blog flow optimize [url]` command to select targeted prompts that refine your existing blog posts based on specific context and niche requirements.
Conversion Strategies
Leverage the `/blog flow win [url]` command to apply prompts focused on enhancing conversion rates and improving the effectiveness of your blog's content.
How to install Blog Flow
View source1. Install with the skills CLI
npx skills add agricidaniel/claude-blog/blog-flow --agent claude-code2. Or install it manually
Download the skill folder and drop it into ~/.claude/skills/ for all projects, or .claude/skills/ to scope it to one repo. Restart Claude Code so it picks up the new skill.
Anthropic's agentic coding CLI, and the reference implementation of Agent Skills. Drop a skill folder into ~/.claude/skills and Claude Code loads it automatically whenever a task matches the skill's description. Claude Code docs
Inside SKILL.md
Written by agricidanielFLOW 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 cannibalizationto 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 analyzeE-E-A-T gap routes to authority prompts;/blog seo-checkfailures route to on-page prompts;/blog geogaps 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 flowactivation.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. |
Frequently asked questions about Blog Flow
Similar skills
Content Creator
Streamline your content creation with SEO and brand voice tools.
Content Production
Transform topics into polished, publish-ready content.
Content Creator
Streamline your content creation with brand voice and SEO tools.
Content Strategy
Plan impactful content that drives traffic and engagement.
Blog Post
Create structured long-form articles effortlessly.
Post to Weibo
Effortlessly publish to Weibo with Markdown support.