$npx -y skills add AgriciDaniel/claude-blog --skill blog-flowFLOW 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 b
| 1 | # FLOW Framework for Bloggers (Find, Optimize, Win) |
| 2 | |
| 3 | > Framework and prompts (c) Daniel Agrici, CC BY 4.0. Source: github.com/AgriciDaniel/flow |
| 4 | |
| 5 | FLOW is an evidence-led operating model built for the AI-search era. Claude Blog |
| 6 | integrates the FLOW prompt library so writers can drive their workflow with |
| 7 | structured, source-backed AI prompts instead of improvised queries. |
| 8 | |
| 9 | This skill exposes the three blog-relevant stages (Find, Optimize, Win) and keeps |
| 10 | the single Leverage prompt available through the prompts index. The local-SEO |
| 11 | prompts (GBP, citations, local audits) are intentionally excluded because they |
| 12 | target brick-and-mortar work, not blogs. |
| 13 | |
| 14 | **Runtime context.** Load `references/flow-framework.md` on every `/blog flow` |
| 15 | activation. Load prompt files on demand only, scoped to the stage the user |
| 16 | requests. |
| 17 | |
| 18 | --- |
| 19 | |
| 20 | ## Commands |
| 21 | |
| 22 | | Command | What it does | |
| 23 | |---------|-------------| |
| 24 | | `/blog flow` | Show FLOW overview and stage menu | |
| 25 | | `/blog flow find [topic\|url]` | Find-stage: keyword discovery, intent mapping, gap analysis (5 prompts) | |
| 26 | | `/blog flow optimize [url]` | Optimize-stage: select 2 to 3 most relevant prompts of 21 based on context | |
| 27 | | `/blog flow win [url]` | Win-stage: BOFU, conversion, dual-surface scorecard (3 prompts) | |
| 28 | | `/blog flow prompts` | Full index of all 30 blog-applicable prompts (Find, Leverage, Optimize, Win) | |
| 29 | | `/blog flow sync` | Pull latest prompt files from github.com/AgriciDaniel/flow | |
| 30 | |
| 31 | The single Leverage prompt (off-site authority) is reachable through |
| 32 | `/blog flow prompts` and is not promoted to a top-level command, since most |
| 33 | blog workflows route off-site work elsewhere. |
| 34 | |
| 35 | --- |
| 36 | |
| 37 | ## Orchestration Logic |
| 38 | |
| 39 | ### On `/blog flow` (no sub-command) |
| 40 | 1. Read `references/flow-framework.md`. |
| 41 | 2. Show the FLOW stage overview with a one-line description of each stage. |
| 42 | 3. Ask the user which stage matches their current situation. |
| 43 | |
| 44 | ### On `/blog flow find [topic|url]` |
| 45 | 1. Read all files in `references/prompts/find/`. |
| 46 | 2. Apply each prompt to the topic or URL, capturing demand and intent signals. |
| 47 | 3. Cross-reference: "For deeper briefs and outlines, see `/blog brief <topic>`, |
| 48 | `/blog outline <topic>`, and `/blog cannibalization` to detect overlap with |
| 49 | existing posts." |
| 50 | |
| 51 | ### On `/blog flow optimize [url]` |
| 52 | 1. Read the file names in `references/prompts/optimize/`. |
| 53 | 2. Read prior context (target URL, niche, any prior skill output in this |
| 54 | conversation, scoring deltas from `/blog analyze`). |
| 55 | 3. Select 2 to 3 most relevant prompts, then load only those files. |
| 56 | 4. Apply the selected prompts; note that the rest are accessible via |
| 57 | `/blog flow prompts`. |
| 58 | 5. Cross-reference: "For deeper rewrites and validation, see `/blog rewrite |
| 59 | <file>`, `/blog seo-check <file>`, `/blog geo <file>`, `/blog schema <file>`, |
| 60 | and `/blog factcheck <file>`." |
| 61 | |
| 62 | ### On `/blog flow win [url]` |
| 63 | 1. Read all files in `references/prompts/win/`. |
| 64 | 2. Apply each prompt to the URL's conversion and BOFU context. |
| 65 | 3. Cross-reference: "For repurposing, full-site health, and quality scoring, |
| 66 | see `/blog repurpose <file>`, `/blog audit`, and `/blog analyze <file>`." |
| 67 | |
| 68 | ### On `/blog flow prompts` |
| 69 | 1. Read `references/prompts/README.md`. |
| 70 | 2. Display the full index: 30 prompts grouped by stage (Find, Leverage, |
| 71 | Optimize, Win) with name and trigger conditions. |
| 72 | 3. State that local-SEO prompts are excluded by design; point users to |
| 73 | `claude-seo` (`/seo flow local`) if they need them. |
| 74 | |
| 75 | ### On `/blog flow sync` |
| 76 | 1. Run: `python3 scripts/sync_flow.py`. |
| 77 | 2. Display the JSON summary (files added, updated, unchanged). |
| 78 | 3. Show the attribution notice after the sync completes. |
| 79 | |
| 80 | --- |
| 81 | |
| 82 | ## Context Matching (Optimize stage) |
| 83 | |
| 84 | The optimize stage has 21 prompts. Dumping all 21 is noise. Select by priority: |
| 85 | |
| 86 | 1. **Niche** (SaaS or B2B blog leans on-page plus technical; lifestyle leans |
| 87 | freshness plus E-E-A-T; publisher leans authority plus citations). |
| 88 | 2. **Prior skill output** (`/blog analyze` E-E-A-T gap routes to authority |
| 89 | prompts; `/blog seo-check` failures route to on-page prompts; `/blog geo` |
| 90 | gaps route to extraction-format prompts). |
| 91 | 3. **URL signals** (commercial pages need conversion prompts; informational |
| 92 | posts need freshness plus answer-first prompts). |
| 93 | |
| 94 | Always surface exactly 2 to 3 prompts. State which prompts you chose and why. |
| 95 | |
| 96 | --- |
| 97 | |
| 98 | ## Reference Files |
| 99 | |
| 100 | Load on demand. Do NOT load all at startup. |
| 101 | |
| 102 | - `references/flow-framework.md`. FLOW operati |