菜单
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 buries the lede, opens with context instead of conclusion, or builds up to the point with "organ music." Triggers on "BLUF," "lede," "buried," "memo," "status update," "exec summary," "TL;DR."
用 Codex 或 Claude 帮你安装 复制这段 Prompt，粘贴到 Codex、Claude 或其他助手里，让它检查 Skill 页面并帮你完成安装。
基于 SOC 职业分类
Drafts and critiques business pitches, investor decks, mission statements, and personal pitches using the 7-part pitch framework, S.H.I.T., and the six-word test. Use when the user is writing a VC pitch, a deck narrative, a "tell me about yourself," a LinkedIn bio, a one-pager, a founding story, or any pitch about themselves or their company. Triggers on "pitch," "deck," "investor," "mission statement," "tell me about yourself," "founding story," "LinkedIn bio," "elevator pitch."
Drafts and critiques speeches, talks, keynotes, lightning talks, demo-day pitches, all-hands updates, conference presentations, wedding toasts, and any spoken-delivery piece using Glenn Kramon's 12 wowing-the-crowd rules from Stanford GSB's Winning Writing. Use when the user is preparing a talk, presentation, keynote, panel opener, board presentation, all-hands, town hall, demo-day pitch, toast, eulogy, commencement address, or any piece that will be delivered aloud. Triggers on phrases like "I'm giving a talk," "preparing a speech," "keynote," "all-hands," "demo day pitch," "wedding toast," "panel opener," "TED-style," "deliver this aloud," "speaking at," "presentation script."
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 op-ed, 6 for a product summary). redundancy catches the specific failure where a phrase says what the verb or context already implied — "going forward" after a future-tense verb, "as I mentioned earlier," "reduce so they are smaller." Implements Kramon's "rewrite this in less than 100 words" exercise, the six-word summary drill, and the in-class redundancy exercise. Use when the user says "shorten this," "cut this," "tighten," "make it concise," "too many words," "going forward," "say it twice," "redundant." Pass --mode target-count|redundancy|both (default both) and --target-words N for target-count.
Mode-aware writing critic. Distilled from Rachel Konrad's Stanford GSB "Winning Writing" course (spring 2026), the 10 rules of cold outreach, Heidi Roizen's mailing rules, and live class critiques. Loads a rule catalog (rules/catalog.json) and a mode definition (rules/modes.json) at invocation. Use whenever drafting or critiquing a cold email, outreach message, LinkedIn intro, exec memo, personal essay, bio, README, or LinkedIn post. Pass a mode argument to filter which rules apply.
Fixes two sentence-rhythm tells that mark prose as AI-generated. Two targets behind one skill, picked via the --target arg. fragment-chain (three or more short sentences back-to-back) and uniform-length (two or more consecutive sentences within ~2 words of each other, especially with parallel structure). Use when the user says "reads like AI," "too choppy," "same length sentences back to back," "staccato," "fragments piled up," "rhythm is off," "uniform pacing." Pass --target fragment-chain|uniform-length|all (default all).
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. Use whenever the user is drafting a performance review, a Slack message to a report, a 1:1 talking point, an HR conversation script, a peer-review comment, or any line where they're tempted to criticize a colleague directly. Triggers on "give feedback to," "tell my report," "perf review line," "stop doing X," "you don't / you're not / you should stop," "smile more," "speak up more," "interrupt less," "less blunt," "burning out," "running late."
| name | bluf-rewriter |
| description | 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 buries the lede, opens with context instead of conclusion, or builds up to the point with "organ music." Triggers on "BLUF," "lede," "buried," "memo," "status update," "exec summary," "TL;DR." |
Source: points/frameworks.md (BLUF section), points/core-rules.md (rule 3).
Bottom line up front. The conclusion goes in the first sentence. Context, evidence, and qualification come after.
This is a military principle. It applies to every form of business writing: emails, memos, status updates, board reports, performance reviews, investor updates, even op-ed openings.
"Over the past quarter, we evaluated several scenarios with input from sales, finance, and ops, and after extensive analysis with the team, we have come to believe that…"
40 words of throat-clearing before the actual point. The reader has already started skimming.
"We need to lower Q3 sales forecast by 50%. Three reasons:"
1. Enterprise pipeline collapsed in August (down 60% MoM) 2. Top customer renewed for 1 year instead of 3 3. Competitor launched at 40% lower price point
The conclusion is the first sentence. Evidence follows. Reader knows in 5 seconds whether to keep reading.
Read the draft. What is the one sentence the reader needs to walk away with? Often it's buried in paragraph 3 or in the conclusion.
Cut, paste, done. If it doesn't work as the first sentence, the sentence isn't sharp enough — rewrite it until it does.
Choose one of three structures:
A. The "three reasons" memo
B. The exec update
C. The decision memo
Delete every sentence that:
The bottom line should be bold. Bullets should be bullets. White space between sections.
Hand back:
Subject line should also be the BLUF. Not "Q3 update" — "Q3 forecast: cutting by 50%, recommend you call the board."
The first line of the email body repeats the conclusion in case the subject got truncated.
BLUF still applies. Bury bad news under "context" and you make it worse — readers feel manipulated when they realize the lede was buried.
❌ "As you know, the macro environment has been challenging this quarter, and we've seen some headwinds in our enterprise segment, leading us to reassess…"
✅ "We're cutting Q3 forecast by 50%. Here's what happened and what I'm doing about it."
The second version takes ownership. The first one feels like spin.
Common: "but I need to give context first."
Response: "Context goes in sentence 2. Sentence 1 is the conclusion. If the reader stops after sentence 1, they should still know what you want them to do."
