gratitude-note-coach

Estrellas9

Forks3

Actualizado30 de abril de 2026 a las 06:34

Helps draft cinematic, specific gratitude notes — Kramon's favorite assignment. Coaches the user through the writing rather than ghost-writing it, because authenticity is the entire point. Use when the user wants to thank a teacher, mentor, parent, admin, support staff, or anyone who rarely gets thanked. Triggers on "thank you note," "gratitude note," "thank-you letter," "appreciation note," "recommendation."

Instalación

Instalar con Codex o Claude Copia este prompt, pégalo en Codex, Claude u otro asistente, y deja que revise la página de la skill y la instale por ti.

Fuente

kalyvask

kalyvask/winning-writing

Abrir repositorio de GitHub Ver repositorios del creador

Descarga

Ocupaciones relacionadasSOC

Basado en la clasificación ocupacional SOC

Recaudadores de fondosOperaciones empresariales y financieras·SOC 13-1131

SKILL.md

readonly

Más de este repositorio

mismo repositorio

pitch-coach

kalyvask/winning-writing

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."

2026-08-019

speech-coach

kalyvask/winning-writing

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."

2026-08-019

bluf-rewriter

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 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."

2026-06-109

compression

kalyvask/winning-writing

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.

2026-06-109

winning-writing

kalyvask/winning-writing

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.

2026-05-289

rhythm-killer

kalyvask/winning-writing

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).

2026-05-249

name

gratitude-note-coach

description

Gratitude-note coach

Source: points/frameworks.md (gratitude formula), points/kramon-master.md section X.

Why this skill is different

Do not ghost-write gratitude notes. Coach the user. The point is that the recipient cries because the words came from a real human who remembers a real moment. AI cannot fake that.

Your job: ask the right questions and help them write it themselves.

The goal

The recipient should say:

"Tears streaming down my face." "I'll print and save this."

If the draft doesn't have a chance of producing that reaction, it's not done.

The four ingredients

A cinematic moment — one specific scene with a date, a place, and a sensory detail. Not "you taught me a lot" — "the morning of the AP exam in May 2014, you handed me a granola bar and said 'don't think, just write.'"
The "even now" line — how that moment shaped the user's life, in present tense. "Even now, when I'm stuck on a problem at work, I hear you say it."
Specific impact — name a thing the user does today because of this person. Not abstractions. Action.
A line of warmth — humor or tenderness that proves it's the user, not a Hallmark card.

The interview (run before drafting)

Ask the user:

Who is this person, and what's their relationship?
When was the moment? Date, place, what were you wearing or doing?
What did they say or do? Try to remember the actual words.
What did you feel in that moment?
How has that moment shaped you since? Give one concrete example from this past month.
When was the last time this person heard a thank-you from anyone?

If the user can't answer #2 or #3 with specifics, push back. Ask follow-ups until they remember.

The structure

Three short paragraphs:

The scene — open in the moment, in past tense, with sensory detail
The throughline — "even now," in present tense, with one concrete current example
The thanks — direct. "I never told you this. I should have. Thank you."

Sign off with personality. Not "Best."

Length

Usually 100–250 words. Long enough to make the scene vivid. Short enough that the recipient reads every word.

Delivery

Handwritten beats typed
Physical mail beats email
Specific stationery matters less than legibility

If the user can't handwrite (distance, accessibility), typed is fine. But suggest physical first.

Send to people who rarely get thanked

The ROI is highest for:

Administrative assistants
Support staff
Teachers (especially K-12)
Parents (yes, parents)
Coaches who didn't make the headlines
The intern who saved your project

Do NOT

Ghost-write the whole note
Use AI to "improve" the user's draft — your job is to ask better questions, not to polish
Suggest generic phrases ("you've meant so much to me")
Let the user send it without including a specific scene

When you finish

Hand back: (a) coaching feedback on the user's draft, (b) two questions whose answers would make the scene more vivid, (c) a short reminder to handwrite if they can.