lyndonkl/skills/x-thread-rewrite
skills/x-thread-rewrite/SKILL.md
--- name: x-thread-rewrite description: Rewrites a published substacker essay as three X thread variants (short 3-5 tweets, medium 6-8, long 9-12). Each tweet ≤280 chars. Hook tweet works standalone. No numbering by default (2026 convention for tech-first-principles accounts). Final tweet is the link. If essay doesn't translate to X, emits a VERDICT line and halts rather than producing weak variants. Trigger keywords: X thread, Twitter thread, thread, tweet, threaded post, thread variants. ---
$ install --global
skillsauthnpx skillsauth add lyndonkl/claude skills/x-thread-rewriteInstall 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:29 AM161.8s1 file scanned
SKILL.md
- name:
- x-thread-rewrite
- description:
- Rewrites a published substacker essay as three X thread variants (short 3-5 tweets, medium 6-8, long 9-12). Each tweet ≤280 chars. Hook tweet works standalone. No numbering by default (2026 convention for tech-first-principles accounts). Final tweet is the link. If essay doesn't translate to X, emits a VERDICT line and halts rather than producing weak variants. Trigger keywords: X thread, Twitter thread, thread, tweet, threaded post, thread variants.
X Thread Rewrite
Workflow
Rewrite for X:
- [ ] Step 1: Load spine + chosen hook + voice-profile
- [ ] Step 2: Score translatability: if >60% of claims score ≤2, emit VERDICT: skip X, halt
- [ ] Step 3: For each of 3 variants (short 3-5, medium 6-8, long 9-12):
- Pick spine claims by translatability (short = only 5s; medium = 4s and 5s; long = full spine)
- Write each tweet ≤280 chars, one claim per tweet
- Preserve paper attributions verbatim
- End with link tweet: `Full essay: {substack-url}`
- [ ] Step 4: No hashtags, no emoji, no numbering
- [ ] Step 5: Voice-check pass
Output format
ops/distribution/{date}-{slug}/x-thread.md:
---
source_post: {slug}.md
platform: x
variants: [short, medium, long]
numbering: off
section: {section-slug}
---
### VARIANT: short
Tweet 1 (hook) [{N chars}]:
{text}
Tweet 2 [{N chars}]:
{text}
...
Link tweet [{N chars}]:
Full essay: {substack-url}
---
### VARIANT: medium
...
---
### VARIANT: long
...
Worked example
See the Distribution Translator agent's example B in the spec archive. Each tweet has character count in brackets. No 1/n, no emoji, link only in final tweet.
Guardrails
- Hard cap: 12 tweets per variant. Attention cliff beyond that.
- ≤280 characters per tweet. Include character count in brackets for writer's audit.
- One claim per tweet. A tweet with two claims fails the "each stands alone" test.
- Keep paper attributions intact. If
Chen et al., Google, 2024won't fit with the claim, drop the tweet — never collapse the attribution. - Link ONLY in the final tweet. Links mid-thread get algorithmic depression post-March-2026.
- If essay can't translate (>60% low translatability, or hook can't fit in 280 chars), emit
## VERDICT: this essay doesn't translate to X. Skip X for this post.and halt. Do not produce weak variants. - No hashtags, no emoji, no numbering (1/n is dated for tech-first-principles accounts).
- Hedges from essay preserved verbatim. No sharpening.
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