blog-flow
Skill0 starsChanged 3 months agoMITView on GitHub
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.
- Reads credentials
3 other projects use a version of this, 2 of them edited.
Adopted by
Most recently taken up by
- gaznilmuzammil12-prog/seo-skills-by-gaznilword for word, first seen Nov 16, 2026
- alpit-patel/seo-aeo-geo-kitedited, first seen Nov 8, 2026
- AgriciDaniel/claude-blogedited, first seen Oct 25, 2026
Other versions3 projects use a version of this.
Word for word · 1
- gaznilmuzammil12-prog/seo-skills-by-gaznil★ 0100% same
Edited · 2
- AgriciDaniel/claude-blog★ 2.7k43% same
- alpit-patel/seo-aeo-geo-kit★ 293% same
Wrote their own version · 0
None found.
How matches are found. Word for word: the exact same text. Edited: shares passages with this file (“99% same” means 99% of its five-word phrases also appear here; 10% or more counts). Their own version: similar meaning, or, weakest, the same name. We can’t tell which project had it first. Projects are counted among the 200 most-starred candidates, and mentions are links to the repository we found, up to 50 per site, so both counts are a floor.
In this repository85 other files it gives its agents.
- AGENTS.mdAGENTS.md
- docs/llms-full.txtllms.txt
- docs/llms.txtllms.txt
- llms-full.txtllms.txt
- llms.txtllms.txt
- ab-testingSkill
- accessibilitySkill
- ai-seoSkill
- analyticsSkill
- attributionSkill
- blog-analyzeSkill
- blog-audioSkill
- blog-auditSkill
- blog-brandSkill
- blog-briefSkill
- blog-calendarSkill
- blog-cannibalizationSkill
- blog-chartSkill
- blog-clusterSkill
- blog-discourseSkill
- blog-factcheckSkill
- blog-geoSkill
- blog-googleSkill
- blog-imageSkill
- blog-locale-auditSkill
- blog-localizeSkill
- blog-multilingualSkill
- blog-notebooklmSkill
- blog-outlineSkill
- blog-personaSkill
- blog-repurposeSkill
- blog-rewriteSkill
- blog-schemaSkill
- blog-seo-checkSkill
- blogSkill
- blog-strategySkill
- blog-taxonomySkill
- blog-translateSkill
- blog-writeSkill
- canonical-tagSkill
- competitorsSkill
- content-optimizationSkill
- content-strategySkill
- copywritingSkill
- core-web-vitalsSkill
- croSkill
- directory-submissionsSkill
- eeat-signalsSkill
- entity-seoSkill
- featured-snippetSkill
- google-search-consoleSkill
- heading-structureSkill
- indexingSkill
- indexnowSkill
- internal-linksSkill
- keyword-researchSkill
- local-seoSkill
- meta-descriptionSkill
- mobile-friendlySkill
- open-graphSkill
- The first 60 shown.
The file
We split this skill into the rules it gives an agent
8 rules. About 0 are common, 3 are distinctive, and 5 are very specific to this project.
≈0
Common · estimate
Many files like this have a rule of this kind.
≈3
Distinctive · estimate
This author's own choices. Worth a look.
5
Very specific
Tied to their project's names, files or tools. Probably skip.
- Common
- Distinctive
- Very specific
- Distinctive: line 60
Ask the user which stage matches their current situation.
- Very specific: line 63
Read all files in references/prompts/find/.
- Very specific: line 70
Read the file names in references/prompts/optimize/.
- Very specific: line 71
Read prior context (target URL, niche, any prior skill output in this conversation, scoring deltas from /blog analyze).
- Distinctive: line 112
Always surface exactly 2 to 3 prompts.
- Very specific: line 132
If references/ is missing, instruct the user to run /blog flow sync first.
- Very specific: line 169
Every /blog flow activation (any sub-command) outputs before analysis:
- Distinctive: line 175
Do not omit or modify the attribution.
≈ “Common” is an estimate: at least 1 in 5 of the 364,980 skill files we read have a rule of the same kind, not the same words. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.
Files
FLOW Framework for Bloggers (Find, Optimize, Win)
Framework and prompts (c) Daniel Agrici, CC BY 4.0. Source: github.com/AgriciDaniel/flow
FLOW is an evidence-led operating model built for the AI-search era. Claude 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 |
/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/flowDo 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. |
Does it work?
Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.
No reviews yet
People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.
- It worked
- Partly
- It didn't
Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.
Your trail
Files you open will collect here, so you can find them again.
Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.
Now do this for your own.
Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.

