lyndonkl/skills/cross-poster-blurb
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
$ install --global
skillsauthnpx skillsauth add lyndonkl/claude skills/cross-poster-blurbInstall this skill globally with one command. Works with Claude Code, Cursor, and Windsurf.
Security Scan Results
3 of 9 scanners reported clean
Some scanners were skipped, did not run, or reported a non-clean status. Review each row below.
3
Scanners Passed
9
Scanners in report
Clean
TrivyContainer and dependency vulnerability scanner
95%
Clean
SemgrepStatic code analysis for vulnerabilities
95%
Clean
mcp-scan (Snyk)Model Context Protocol security validation
95%
Skipped
Snyk (dep)Open source security scanning
50%
Skipped
Socket.devSupply chain security analysis
50%
Skipped
VirusTotalMulti-engine malware detection
50%
Skipped
CrowdStrikeAdvanced threat intelligence
50%
Skipped
OSV-ScannerOpen Source Vulnerability database check
50%
Skipped
OWASP Dep-Check
50%
Last scanned: Apr 25, 2026, 10:10 AM133.0s1 file scanned
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
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
Output format
---
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.
Worked example (Architecture, Not Prompting)
---
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.
Guardrails
- Third person throughout. Never "I argue…" — the blurb will be pasted by another writer.
- 60-140 words. Substack's cross-post popup is small; shorter reads.
- Never say "amazing," "brilliant," "must-read" — the other writer sounds like a fan, not a curator.
- No subscriber CTA ("subscribe to From First Principles"). Just positioning.
- Preserve paper attributions.
- If the essay is in a specific section, the blurb can reference the section's promise subtly — not as "Filed under."
- Voice register: neutral-analytical. Not the writer's confessional register; the blurb represents the piece to strangers.
Related Skills
lyndonkl/conf-theme-clustering
testing
VerifiedTrustedCommunity
Cluster a conference's event records into a small set of coarse themes with finer sub-clusters, an explicit outlier bucket, and soft (multi-membership) affinities — using the hybrid embed-then-label pipeline (embed abstracts, reduce, density-cluster, then LLM-label the clusters) when embedding libraries are available, and an LLM-reasoned hierarchical fallback when they are not. Embeddings do the grouping; the LLM only names the groups. Conference-agnostic. Use when turning structured event records into a navigable theme map for preference elicitation and scheduling, when you need 6-8 reasonable themes rather than 20 muddy ones, or when overlapping talks must belong to more than one theme. Trigger keywords - theme clustering, cluster talks, embed then label, soft membership, outlier talks, conference themes, topic map.
127SKILL.mdUpdated Jun 28, 2026
lyndonkl/conf-schedule-optimization
development
VerifiedTrustedCommunity
Build a personal conference schedule as a constraint-optimization problem — hard constraints (no time overlap, room-to-room travel time, capacity/registration, the attendee's own must-attends and blackouts) plus a user-owned weighted objective trading interest against breadth, pacing (maximize contiguous free time), and serendipity. Surfaces unbreakable conflicts (two high-value overlapping talks the model cannot rank) as decisions for the human rather than silently picking, and reports what each choice traded away. Conference-agnostic. Use to turn a preference profile plus a theme map into a day-by-day plan, to resolve overlapping sessions, or to balance a packed vs paced schedule. Trigger keywords - schedule optimization, conference schedule, constraint optimization, overlapping talks, contiguous free time, conflict surfacing, packed vs paced.
127SKILL.mdUpdated Jun 28, 2026
lyndonkl/conf-program-extraction
development
VerifiedTrustedCommunity
Parse a heterogeneous conference program (markdown, HTML, PDF-derived text, or JSON) into normalized event records with per-field confidence scores and independent classification axes (topic, depth, format, prerequisites, recorded, capacity). Detects the program's format before extracting, treats every inferred field as uncertain (present vs inferred vs missing), and flags thin or missing abstracts so downstream enrichment can target them. Conference-agnostic. Use when ingesting a conference or event schedule into a structured store, normalizing a talk/session list, or extracting per-session metadata with calibrated confidence. Trigger keywords - program ingestion, parse schedule, session extraction, event records, conference program, talk metadata, per-field confidence.
127SKILL.mdUpdated Jun 28, 2026
lyndonkl/conf-preference-elicitation
development
VerifiedTrustedCommunity
Build a personalized preference profile from a small number of well-chosen, cluster-grounded questions instead of a long survey. Represents the person's interests as an uncertainty region over the theme map, picks the single highest-information-gain choice-based question (contrasting real talks from different clusters), balances exploiting known interests against exploring uncertain ones, deliberately injects outlier probes to fight selection bias, and stops as soon as the schedule would be stable. Also elicits the user-owned objective weights and hard constraints. Interactive — runs where it can actually ask the person. Conference-agnostic. Use to turn a theme map into a preference profile, to decide what to ask a conference attendee, or to elicit scheduling priorities. Trigger keywords - preference elicitation, ask few questions, information gain, choice-based questions, selection bias probe, objective weights, attendee preferences.
127SKILL.mdUpdated Jun 28, 2026