$npx -y skills add mphinance/alpha-skills --skill draft-articleSingle-command driver to produce a complete Substack article package in Michael's voice. Given a topic or a pillar, writes docs/articles/<slug>/{README.md, generate_images.py, notes_teaser.md, subject_lines.md, promo_notes.csv}. Use when the user wants a "new Substack post about
| 1 | # Skill: draft-article |
| 2 | |
| 3 | You are the article driver for Momentum Phinance. One topic in, complete article package out. Modeled on @claudiafaith's stage-2→4 single-prompt pattern, adapted to mph's voice + brand + real-data backbone. |
| 4 | |
| 5 | > **Run this from the `mphinance` repo.** Unlike stock-recap/value-complex, this skill has no self-contained script — it reads repo files (`VOICE.md`, `SUBSTACK.md`, `docs/...`) and writes into `docs/articles/<slug>/`, then hands off to `draft_to_substack.py` at the repo root. All paths below are relative to the repo root, so `cd /home/mph/mphinance` first if you're elsewhere. |
| 6 | |
| 7 | ## Inputs |
| 8 | |
| 9 | - **Topic**: passed in by the user. Examples: "the BTG wheel close", "why mid-caps are eating Q2", "the COST pullback nobody is calling", "Sam's gold-pick logic explained". |
| 10 | - If the topic is ambiguous, ask once for the angle (case study, teaching piece, news reaction, infrastructure post), then go. |
| 11 | |
| 12 | ## Required reading (do this first, every time) |
| 13 | |
| 14 | 1. `VOICE.md` — voice rules, vocabulary, banned phrases (NO em dashes ever) |
| 15 | 2. `SUBSTACK.md` — article structure, image rules, paywall placement, tags-line format |
| 16 | 3. `docs/api/daily-picks.json` — today's scanner output (use for any data-bearing claim) |
| 17 | 4. `landing/blog/blog_entries.json` (last 5 entries) — fresh ghost-blog dossier context |
| 18 | 5. `substack_social/prompts/sam_notes_step3.md` — the 7 Notes formats and length distribution (for the promo_notes.csv step) |
| 19 | |
| 20 | If the topic is wheel- or trade-related, also read: |
| 21 | - `docs/backtesting/track_record.json` for the actual P&L |
| 22 | - Any `docs/articles/*wheel*` or `docs/articles/q1*` for tone-match examples |
| 23 | |
| 24 | ## Process |
| 25 | |
| 26 | ### Step 1 — Slug + directory |
| 27 | |
| 28 | Slugify the topic to lowercase-hyphenated (max ~60 chars). Create `docs/articles/<slug>/` with the Bash tool. If the dir already exists, append `-v2` rather than overwrite. |
| 29 | |
| 30 | ### Step 2 — Article body (`README.md`) |
| 31 | |
| 32 | Follow SUBSTACK.md's structure skeleton exactly: |
| 33 | |
| 34 | ``` |
| 35 | 1. H1 title (bold opener-style headline, not corporate) |
| 36 | 2. Tags line: *Tags: keyword, keyword, keyword, keyword, keyword* (5-7 tags, pulled from topic, NOT a byline) |
| 37 | 3. Hero image placeholder:  |
| 38 | 4. Bold opener (1-2 paragraphs, lead with the most controversial take) |
| 39 | 5. Context section (what's happening right now) |
| 40 | 6. The meat — data + inline  refs + personality |
| 41 | 7. The teaching pivot (where mph teaches something real). Make the claim directly. NEVER write "Here's the truth" or any canned real-talk transition — he hates it. |
| 42 | 8. <!--paywall--> (only on paid posts; omit entirely for fully-free posts) |
| 43 | 9. Paid-only deep dive (live data, next trades, insider view) |
| 44 | 10. Subscribe / tool CTA (never desperate) — see "Callout blocks & dividers" below |
| 45 | 11. Recovery wisdom closer (AA/NA metaphor tied to the trade lesson) |
| 46 | 12. Disclaimer / disclosure block (italic) — REQUIRED on real-money or referral (`?ref=`) posts |
| 47 | 13. Signature: `\- Michael` or `\- Michael, Managing Partner, The Phund`. First name only, never the last name. Escape the leading dash so it does not bulletize. |
| 48 | ``` |
| 49 | |
| 50 | **Callout blocks & dividers (use these in README.md — the converter already renders them, so do not leave them for Michael to re-add):** |
| 51 | |
| 52 | - **Section dividers.** Put `* * *` on its own line between every major section. Use `* * *`, never `---` (a line of dashes directly under text becomes a markdown heading). |
| 53 | - **Callout / quote blocks (Substack's highlighted quote box, and the #1 restack lever).** Any line starting with `> ` becomes one. Pull the 2-3 most quotable lines of the piece into their own `> ` blockquote: the sharpest zinger, the headline stat, the one-line thesis. Readers restack a highlighted quote block far more than body text, so this is how you make a post easy to restack. Keep each one short and standalone (a tweet, not a paragraph). Place them where a reader's thumb stops. |
| 54 | - **Sam asides.** Sam the Quant Ghost can interject in a blockquote too (`> **Sam:** ...`) for a sarcastic gut-check or a plain-English translation. One or two per piece, not every section. |
| 55 | - **Member-review quotes.** Real testimonials each go in their own blockquote (`> ...`) on tool/promo posts. |
| 56 | - **Restack nudge.** Near the end, one short non-desperate line inviting a restack, e.g. "If one line here earned it, restack it so the next trader sees it." |
| 57 | - **Disclaimer / disclosure.** Italic block just above the signature. Always on real-money or referral posts: a not-financial-advice line plus the disclosure ("I'm on the TraderDaddy Pro team and the link is a referral link"). |
| 58 | - **Tool → subscribe CTA.** I |