skills/linkedin-post-rewrite/SKILL.md
--- name: linkedin-post-rewrite description: Rewrites a published substacker essay as a LinkedIn post with a hook fitting the 210-char fold, practitioner framing (less confessional than Substack), short 2-3 line paragraphs, and 0-2 niche hashtags. 900-2500 characters. Emits linkedin-post.md. Use as the LinkedIn-native arm of the Distribution Translator. Trigger keywords: LinkedIn post, LinkedIn rewrite, practitioner, professional network, niche hashtags. --- # LinkedIn Post Rewrite ## Workflow
npx skillsauth add lyndonkl/claude skills/linkedin-post-rewriteInstall 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.
Rewrite for LinkedIn:
- [ ] Step 1: Load spine + chosen hook + voice-profile + audience-notes
- [ ] Step 2: Hook ≤210 chars (first 1-2 lines; must survive the "...see more" fold)
- [ ] Step 3: Line break, then one-sentence pivot paragraph
- [ ] Step 4: Body — 4-7 short paragraphs of 2-3 lines each (white space is structural)
- [ ] Step 5: Optional list block only if essay's spine is genuinely enumerable
- [ ] Step 6: Practitioner-takeaway closer (NOT bolded maxim — bold doesn't render well on LinkedIn)
- [ ] Step 7: Link line: `Full essay: {substack-url}`
- [ ] Step 8: 0-2 niche hashtags on final line (prefer 0-1)
- [ ] Step 9: Cap at 2500 chars total
LinkedIn reads "practitioner sharing learnings," not "writer thinking aloud." Slight voice shift allowed:
---
source_post: {slug}.md
platform: linkedin
target_length: 900-2500 chars
actual_length: {N}
length_mode: short | long
hook_chars: {N}
hashtags: 0-2
section: {section-slug}
---
{hook — first 1-2 lines, ≤210 chars total}
{one-sentence pivot paragraph}
{body — 4-7 short paragraphs, 2-3 lines each}
{optional list block only if genuinely enumerable}
{practitioner takeaway — not bolded}
Full essay: {substack-url}
{#NicheHashtag1 #NicheHashtag2} ← 0-2 only
#MultiAgentSystems, #LLMEngineering). Never generic (#AI, #tech, #innovation, #thoughts, #leadership).testing
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.
development
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.
development
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.
development
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.