skills/cross-poster-blurb/SKILL.md
--- name: cross-poster-blurb description: Writes a 60-140 word third-person blurb for the Substack cross-post feature, positioned so another newsletter writer can paste it into their cross-post popup without editing. Third-person throughout ("In this piece, Kushal argues…"). No subscriber CTAs. Use as the cross-post arm of the Distribution Translator. Trigger keywords: cross-post, cross-poster, blurb, Substack cross-post, third person, positioning. --- # Cross-Poster Blurb ## Workflow ``` Wri
npx skillsauth add lyndonkl/claude skills/cross-poster-blurbInstall this skill globally with one command. Works with Claude Code, Cursor, and Windsurf.
3 of 9 scanners reported clean
Some scanners were skipped, did not run, or reported a non-clean status. Review each row below.
Write blurb for cross-post:
- [ ] Step 1: Load spine + voice-profile + audience-notes
- [ ] Step 2: One-line positioning: "In this piece, Kushal argues…"
- [ ] Step 3: 2-3 sentences summarizing argument + one concrete anchor
- [ ] Step 4: One sentence on why a tech-adjacent audience should care
- [ ] Step 5: Sign-off minimal: "Read the full piece." or a period — no subscribe CTA
- [ ] Step 6: Enforce 60-140 words
---
source_post: {slug}.md
platform: substack-crosspost
target_length: 60-140 words
actual_length: {N}
section: {section-slug}
---
In this piece, Kushal argues {thesis}. {2-3 sentences of argument + concrete anchor}. For anyone building with {domain}, the {specific-claim} is the move that reframes the problem. Read the full piece.
---
source_post: architecture-not-prompting.md
platform: substack-crosspost
target_length: 60-140 words
actual_length: 98
section: agent-workshop
---
In this piece, Kushal argues that most prompt-engineering advice mistakes the unit of analysis — the lever that moves behaviour in long-running AI systems is organisational, not linguistic. Drawing on Wang et al., Anthropic (2024), which found multi-agent decompositions outperformed long-prompted single agents by roughly 40% on sustained tasks, he lays out four recurring patterns: supervisor-worker, pipeline, jury, and debate. For anyone building with agents — or watching teams ship agents that don't quite work — the reframing from "better prompt" to "better architecture" is worth the ten-minute read.
development
--- name: zettel-note description: The note-writing discipline for this vault's evergreen knowledge graph, modeled on a Zettelkasten reading companion and governed by the vault conventions. Enforces declarative-claim titles, one claim per note (atomicity), own-words prose with no block quotes, the piped [[slug|Title]] link form, the labeled link-relationship vocabulary (Confirms/Contradicts/Extends/Context/Prerequisite/Builds-on/Applies/Example-of/Contrasts-with), 3-6 links per note, and search-
development
Plans between-round FIFA World Cup Fantasy transfers — budgets the round's free transfer(s), forces out players whose nation has been eliminated, chases fixture-swing drops, upgrades on value, and decides when a rebuild is large enough to fire the Wildcard instead of spending free transfers one at a time. Ranks candidate in/out pairs by EV gain over each player's remaining survival horizon (delta xEV weighted by progression_carry) MINUS transfer cost (a free transfer is cheap, a points hit is real, churning the squad for marginal swings is a critic flag), and tags forced/fixture/upgrade priority. Emits a `transfer-plan` signal. Use when called by wc-squad-architect (whose transfer work this skill is the engine for) and by the strategists in the populate stage when their candidate is transfer-adjacent rather than a full rebuild.
testing
Reads and updates the FIFA World Cup Fantasy tournament state machine (footballfantasy/context/tournament-state.md) — the temporal backbone tracking phase (pre-tournament → group MD1-3 → R32 → R16 → QF → SF → final), budget ($100m group / $105m knockouts), nation cap (3 group, loosening in knockouts), chips remaining, surviving nations, each owned player's elimination-risk horizon, and deadlines. Validates state on load (count/feasibility checks), applies phase transitions, and appends to the append-only state log (never silent overwrite). Use to load state at the start of a run and to commit state changes after the manager makes a move.
development
Validates and persists FIFA World Cup Fantasy signal files to signals/YYYY-MM-DD-<type>.md. Checks the required frontmatter (type, round, date, emitted_by, confidence, source_urls), range-checks declared numeric signals, confirms every factual claim carries a source URL or "manager-provided", rejects unknown signal types, and refuses to persist a signal that fails validation (logging the failure instead). Keeps the inter-agent signal layer auditable so downstream agents can trust what they read and never re-derive it. Use whenever an agent or skill writes a signal.