bluf-rewriter
Reorganizes a memo, email, status update, or report so the bottom line is up front. Implements Kramon's BLUF (Bottom Line Up Front) rule. Use when a draft…
Finds specific, genuine "like you" hooks between the writer and a cold-outreach target — the bridges that turn a generic email into one that feels hand-written. Takes the recipient dossier and the writer's profile (about-me.md) and surfaces ranked angles. Use after
$ npx -y skills add kalyvask/winning-writing --skill connection-finder --agent claude-codeHow it fires
How this skill gets triggered: by you, by Claude, or both.
/connection-finderContext preview
The summary Claude sees to decide when to auto-load this skill.
Finds specific, genuine "like you" hooks between the writer and a cold-outreach target — the bridges that turn a generic email into one that feels hand-written. Takes the recipient dossier and the writer's profile (about-me.md) and surfaces ranked angles. Use after
name: connection-finder description: Finds specific, genuine "like you" hooks between the writer and a cold-outreach target — the bridges that turn a generic email into one that feels hand-written. Takes the recipient dossier and the writer's profile (about-me.md) and surfaces ranked angles. Use after recipient-research is done, before drafting. Triggers on "like you," "find a connection," "what do we have in common," "common ground."
Source: `points/cold-email-rules.md` rule 5 — *"Compare yourself to the recipient — the 'like you' move."*
Rachel Konrad's rule 5 is the most-failed rule in the playbook. Most "like you" lines are either:
What works: **specific, genuine, slightly unexpected.** A "like you" line should reference a sensory detail from your shared origin that *cannot be sent to anyone else* — a specific cuisine you both grew up with, a specific city you both lived in for a specific year, a specific job you both did before the one you're emailing about. That's the whole point.
This skill takes two inputs:
1. **Recipient dossier** (from `recipient-research`) 2. **Writer's profile** (`context/about-me.md` or equivalent)
If either is missing, run `recipient-research` first or ask the user to point you at their about-me file.
Cross-reference the two profiles for overlap in these eight categories. The further down the list, the higher the leverage.
Worked at the same company, in the same industry, in similar roles. Use only if there's a *specific* overlap — same product, same team, same era.
Same school. Useful only with a specific shared experience (same professor, same class, same dorm). "Stanford MBA" alone is too generic.
Same hometown. Same immigration story. Lived in the same unusual place. Visited the same specific spot.
Both military veterans. Both first-generation immigrants. Both built something from zero. Both worked a manual-labor job before a desk job. Specific date or place beats abstract category.
Both Ironman triathletes. Both jazz pianists. Both run ultras. Both bake bread. Specificity matters: *"like you, I'm 6 marathons in"* beats *"like you, I'm a runner."*
You both believe an unfashionable thing about the same topic. *"Like you, I think the LLM-evals space is wildly under-priced. A recent paper from a frontier lab made the case better than I could."* This signals you've read them carefully and you have your own brain. (In a real email, you'd name the specific paper and the specific lab — the placeholder above keeps the shape generic for the documentation.)
Both wear the same obscure watch brand. Both reference the same indie film. Both quote the same Greek philosopher. The more unusual, the better — these are the lines people screenshot.
Both have wrestled with the same hard problem. *"Like you, I tried to ship X with Y constraint. I lost three months on it. I'd love your scar tissue."* Vulnerability + specificity.
If your candidate hook fits any of these patterns, throw it out and look harder.
## Top 5 connection angles, ranked ### 1. <One-line hook> [category, leverage score 1–10] **The line as it could appear in the email:** > "Like you, <specific genuine connection>." **Why it works:** <one sentence> **Source for the recipient detail:** <link> **Source for the writer's detail:** <about-me.md line or equivalent> ### 2. <…> ### 3. <…> ### 4. <…> ### 5. <…> ## Notes - <If two of the angles are close to each other, flag it — pick one> - <If the writer's profile is thin in an area where the recipient is rich, name it as a gap> - <If you can't find five strong angles, say so. Better one great hook than five weak ones.>
1. User says: *"Find connections between me and [target]"* or invokes after `recipient-research`. 2. Read `context/about-me.md` (or equivalent). 3. Read the dossier. 4. Cross-reference for the eight categories above. 5. Rank by leverage — contrarian opinions and unusual coincidences at the top. 6. Hand off to `cold-email-coach` or `fun-angle`.
If the only overlap you can find is generic ("we both went to Stanford"), tell the user honestly. That's a signal they should:
A weak connection forced into the email is worse than no connection.
31 Claude skills for cold outreach, op-eds, pitches, press inquiries, bios, exec memos, performance reviews, spoken-delivery talks, fact-checking, and reply-rate tracking.
Repo: kalyvask/winning-writing
Reorganizes a memo, email, status update, or report so the bottom line is up front. Implements Kramon's BLUF (Bottom Line Up Front) rule. Use when a draft…
Cuts a draft to a target word count without losing substance. Two modes behind one skill. target-count hits a specific number (200 for a cold email, 500 for an…
Rewrites blunt downward or peer feedback as "what I like plus what I would like," focused on the work rather than the person, ideally phrased as a question.…
Finds the unexpected, dry, or self-deprecating angle that makes an email memorable. Turns "professional and polite" into "this person sounds like a real…
Rewrites section titles, slide titles, op-ed headlines, email subject lines, and chapter headings from category labels into bold arguable claims. Implements…
Cuts cinematic details that don't serve the main point. The opposite move from vividness. Vividness adds sensory detail; this skill removes detail that's vivid…