New: Earn 20% as an AgentAlley affiliate. Share your link and earn on every sale you refer. Join now New: Earn 20% as an affiliate. Join now

Help someone write a eulogy

Eulogy writer

by mohitagw15856 · MIT license · ★ 1,395 on GitHub · updated Sep 23

Eulogy writer cover

Help someone write a eulogy — the hardest writing most people ever do, at the worst possible time. Use when someone must speak at a funeral or memorial and doesn't know where to start, or has fragments and no shape.

---
name: eulogy-writer
description: "Help someone write a eulogy — the hardest writing most people ever do, at the worst possible time. Use when someone must speak at a funeral or memorial and doesn't know where to start, or has fragments and no shape. Produces a 3-5 minute eulogy built from their memories in their voice, plus a delivery copy formatted for shaking hands — gentle process, no interrogation, nothing invented."
deprecated: 2026-08-25
supersededBy: eulogy-and-obituary-writer
---

# Eulogy Writer

A eulogy is not a biography and not a performance. It is one person saying: *this is who they were to us, and it mattered.* The writing help here is quiet: draw out three true stories, find the thread, and shape it so it can be read aloud by someone whose voice may break.

## Required Inputs

Gathered gently — a few at a time, never as a form:

- **Who they were to the speaker** (parent, friend of forty years, colleague) and roughly who's in the room.
- **Two or three specific memories** — small beats grand: how they answered the phone, what they always said, the thing everyone will smile at. Fragments and half-sentences are enough; that's what the skill is for.
- **One true sentence** the speaker wants said, if they have it. Many do; it becomes the spine.

Overview

A eulogy is not a biography and not a performance. It is one person saying: this is who they were to us, and it mattered. The writing help here is quiet: draw out three true stories, find the thread, and shape it so it can be read aloud by someone whose voice may break.

What you get

  • The eulogy400-650 words (3-5 minutes spoken), in the speaker's register (their words from the conversation reused deliberately), reading-aloud rhythm: short sentences, breathing room.
  • The delivery copythe same text formatted for the podium: large paragraphs broken into breath-length lines, pause marks, and a note at the top: "If you break, stop, breathe. No one is timing you."
  • Two alternate closingsbecause the ending is the hardest choice, offer a warm one and a plain one.
Manual install (npx, ZIP)
Claude Codenpx skills add mohitagw15856/pm-claude-skills --skill eulogy-writer -g -a claude-code
Claude Code (manual)mkdir -p ~/.claude/skills && curl -sL https://codeload.github.com/mohitagw15856/pm-claude-skills/tar.gz/f6ca79348c55 \ | tar -xz -C ~/.claude/skills --strip-components=2 pm-claude-skills-f6ca79348c55/skills/eulogy-writer
Windows (PowerShell)New-Item -ItemType Directory -Force "$HOME\.claude\skills" | Out-Null; Invoke-WebRequest "https://m.agentalley.io/zip/edaf623546e88f98fb31/eulogy-writer.zip" -OutFile "$env:TEMP\eulogy-writer.zip"; Expand-Archive "$env:TEMP\eulogy-writer.zip" -DestinationPath "$HOME\.claude\skills" -Force
Claude.ai / desktopDownload the ZIP and upload it under Settings → Capabilities → Skills.
Codex, Cursor, other agentsPoint them at SKILL.md. The other files are plain text.

Connects with Agent Alley MCP · agentalley.io/mcp

Files included

  • SKILL.md3.6 KB
Read the files here
mohitagw15856/f6ca7931 file
SKILL.md
Show the full text49 lines

Eulogy Writer

A eulogy is not a biography and not a performance. It is one person saying: this is who they were to us, and it mattered. The writing help here is quiet: draw out three true stories, find the thread, and shape it so it can be read aloud by someone whose voice may break.

Required Inputs

Gathered gently — a few at a time, never as a form:

  • Who they were to the speaker (parent, friend of forty years, colleague) and roughly who's in the room.
  • Two or three specific memories — small beats grand: how they answered the phone, what they always said, the thing everyone will smile at. Fragments and half-sentences are enough; that's what the skill is for.
  • One true sentence the speaker wants said, if they have it. Many do; it becomes the spine.
  • Tone check: is laughter welcome in this room? (Usually yes; always ask.)

The Shape That Works

  1. Arrive small — one concrete image of them, mid-life, mid-gesture. Never "we are gathered" and never a dictionary definition of loss.
  2. The stories (2-3) — each one specific, each landing on what it showed about them. Specific beats comprehensive: the best eulogies leave out most of a life.
  3. The turn — what they gave the people in the room; the sentence the speaker wanted said lives here.
  4. The goodbye — direct address ("you would have hated this fuss") or a returned image from the opening. Short. The last line should survive being spoken through tears.

Output Format

  • The eulogy — 400-650 words (3-5 minutes spoken), in the speaker's register (their words from the conversation reused deliberately), reading-aloud rhythm: short sentences, breathing room.
  • The delivery copy — the same text formatted for the podium: large paragraphs broken into breath-length lines, pause marks, and a note at the top: "If you break, stop, breathe. No one is timing you."
  • Two alternate closings — because the ending is the hardest choice, offer a warm one and a plain one.

Quality Checks

  • Every fact and story came from the speaker — nothing biographical was invented or embellished, not even connective details
  • The deceased's name appears in the first two sentences and the last two
  • At least one line is verbatim from how the speaker talked about them — their phrase, kept
  • Read-aloud test: no sentence over ~22 words; no clause a shaking voice can't restart
  • The tone matches the room the speaker described — humour only where it was welcomed

Anti-Patterns

  • Do not interrogate a grieving person with a question list — ask for one memory, work with what comes, ask softly for one more
  • Do not write poetry unless they brought poetry — borrowed grandeur ("a candle in the wind of our hearts") embarrasses the speaker later
  • Do not summarise the whole life — a eulogy is a portrait, not a résumé; the gaps are allowed
  • Do not sand off the person's edges — "he was difficult and we loved him" is a better sentence than any halo
  • Do not produce only a polished artifact — the delivery copy with pause marks is the part they'll actually clutch at the podium
1---
2name: eulogy-writer
3description: "Help someone write a eulogy — the hardest writing most people ever do, at the worst possible time. Use when someone must speak at a funeral or memorial and doesn't know where to start, or has fragments and no shape. Produces a 3-5 minute eulogy built from their memories in their voice, plus a delivery copy formatted for shaking hands — gentle process, no interrogation, nothing invented."
4deprecated: 2026-08-25
5supersededBy: eulogy-and-obituary-writer
6---
7 
8# Eulogy Writer
9 
10A eulogy is not a biography and not a performance. It is one person saying: *this is who they were to us, and it mattered.* The writing help here is quiet: draw out three true stories, find the thread, and shape it so it can be read aloud by someone whose voice may break.
11 
12## Required Inputs
13 
14Gathered gently — a few at a time, never as a form:
15 
16- **Who they were to the speaker** (parent, friend of forty years, colleague) and roughly who's in the room.
17- **Two or three specific memories** — small beats grand: how they answered the phone, what they always said, the thing everyone will smile at. Fragments and half-sentences are enough; that's what the skill is for.
18- **One true sentence** the speaker wants said, if they have it. Many do; it becomes the spine.
19- Tone check: is laughter welcome in this room? (Usually yes; always ask.)
20 
21## The Shape That Works
22 
231. **Arrive small** — one concrete image of them, mid-life, mid-gesture. Never "we are gathered" and never a dictionary definition of loss.
242. **The stories** (2-3) — each one specific, each landing on what it *showed* about them. Specific beats comprehensive: the best eulogies leave out most of a life.
253. **The turn** — what they gave the people in the room; the sentence the speaker wanted said lives here.
264. **The goodbye** — direct address ("you would have hated this fuss") or a returned image from the opening. Short. The last line should survive being spoken through tears.
27 
28## Output Format
29 
30- **The eulogy** — 400-650 words (3-5 minutes spoken), in the speaker's register (their words from the conversation reused deliberately), reading-aloud rhythm: short sentences, breathing room.
31- **The delivery copy** — the same text formatted for the podium: large paragraphs broken into breath-length lines, **pause marks**, and a note at the top: "If you break, stop, breathe. No one is timing you."
32- **Two alternate closings** — because the ending is the hardest choice, offer a warm one and a plain one.
33 
34## Quality Checks
35 
36- [ ] Every fact and story came from the speaker — nothing biographical was invented or embellished, not even connective details
37- [ ] The deceased's name appears in the first two sentences and the last two
38- [ ] At least one line is verbatim from how the speaker talked about them — their phrase, kept
39- [ ] Read-aloud test: no sentence over ~22 words; no clause a shaking voice can't restart
40- [ ] The tone matches the room the speaker described — humour only where it was welcomed
41 
42## Anti-Patterns
43 
44- [ ] Do not interrogate a grieving person with a question list — ask for one memory, work with what comes, ask softly for one more
45- [ ] Do not write poetry unless they brought poetry — borrowed grandeur ("a candle in the wind of our hearts") embarrasses the speaker later
46- [ ] Do not summarise the whole life — a eulogy is a portrait, not a résumé; the gaps are allowed
47- [ ] Do not sand off the person's edges — "he was difficult and we loved him" is a better sentence than any halo
48- [ ] Do not produce only a polished artifact — the delivery copy with pause marks is the part they'll actually clutch at the podium
49 
View all files on GitHub →

Details

Updated
Sep 23, 2026
License
MIT
Stars on the repo
★ 1,395
Checked
Source
mohitagw15856/pm-claude-skills ↗
Creator
mohitagw15856 · 193 listings
View creator

Made with eulogy-writer

Eulogy writer — Galaxy 3D — fly through all 1170 skills as a glowing constellation you orbit and click into (from the mohitagw15856/pm-claude-skills README)
Eulogy writer — Galaxy 3D — fly through all 1170 skills as a glowing constellation you orbit and click into (from the mohitagw15856/pm-claude-skills README)

by mohitagw15856

Eulogy writer — PM Skills Wrapped — your practice turned into a shareable, Spotify-Wrapped-style story (from the mohitagw15856/pm-claude-skills README)
Eulogy writer — PM Skills Wrapped — your practice turned into a shareable, Spotify-Wrapped-style story (from the mohitagw15856/pm-claude-skills README)

by mohitagw15856

Similar skills

See all →
SkillReverse engineer native, managed, Electron/JavaScriptREAmorluto/rea · by morlutoReverse engineer native, managed, Electron/JavaScript, packaged, firmware, and browser targets with REA. Use shipped-artifact or requested runtime evidence to explain features, compare versions, decompile code, or guide a reconstruction. Skip REA for ordinary source-repository architecture analysis.★ 316k GitHub starsSkillBrainstorms ideas into designs before any creative workBrainstorming Ideas Into Designsobra/superpowers · by obraYou MUST use this before any creative work - creating features, building components, adding functionality, or modifying behavior. Explores user intent, requirements and design before implementation.★ 290k GitHub starsSkillRequires technical rigor and verificationCode Review Receptionobra/superpowers · by obraUse when receiving code review feedback, before implementing suggestions, especially if feedback seems unclear or technically questionable - requires technical rigor and verification, not performative agreement or blind implementation★ 290k GitHub starsSkillDiagnosis loop for hard bugs and performance regressionsDiagnosing bugsmattpocock/skills · by mattpocockDiagnosis loop for hard bugs and performance regressions. Use when the user says "diagnose"/"debug this", or reports something broken/throwing/failing/slow.★ 267k GitHub starsSkillImplement the result of /to-spec and /to-tickets in codeImplement specmattpocock/skills · by mattpocockImplement the result of /to-spec and /to-tickets in code.★ 267k GitHub starsSkillWriting a PR bodymattpocock/skills · by mattpocockUse when writing a PR body.★ 267k GitHub stars

More from mohitagw15856

SkillDesign a 360-degree feedback survey or write a structured360-Degree Feedback Template Skillmohitagw15856/pm-claude-skills · by mohitagw15856Design a 360-degree feedback survey or write a structured 360 feedback report. Use when asked to build a 360 feedback process, write 360 feedback for a colleague, design a feedback survey, or produce a feedback report. Produces either a complete survey instrument with rating scales and open-ended questions, or a structured narrative feedback report with themes, strengths, and development areas.★ 1.4k GitHub starsSkillDesign statistically rigorous A/B tests for product featuresA/B Test Planner Skillmohitagw15856/pm-claude-skills · by mohitagw15856Design statistically rigorous A/B tests for product features, UI changes, onboarding flows, and pricing experiments. Use when asked to set up an experiment, design an A/B test, calculate sample size, or interpret test results. Produces a complete test plan with hypothesis, variant definitions, sample size, duration estimate, guardrail metrics, and a results interpretation guide.★ 1.4k GitHub starsSkillGenerate a WCAG 2.2 accessibility audit checklistAccessibility Audit Skillmohitagw15856/pm-claude-skills · by mohitagw15856Generate a WCAG 2.2 accessibility audit checklist and remediation suggestions for any UI or design. Use when asked to audit for accessibility, check WCAG compliance, review a design for a11y issues, or create an accessibility remediation plan. Produces a prioritised checklist with pass/fail assessments and specific fixes.★ 1.4k GitHub starsSkillBuild a structured account plan for any key customerAccount Plan Skillmohitagw15856/pm-claude-skills · by mohitagw15856Build a structured account plan for any key customer or target account. Use when asked to create an account plan, key account strategy, strategic account review, or territory plan. Produces a complete account plan with relationship map, growth opportunities, risks, and 90-day action plan.★ 1.4k GitHub starsSkillOptimize an article for Answer Engine Optimization so AIAEO Optimizer Skillmohitagw15856/pm-claude-skills · by mohitagw15856Optimize an article for Answer Engine Optimization (AEO) so AI engines like ChatGPT, Perplexity, and Claude can extract, quote, and cite it. Use when asked to AEO-optimize, make content AI-readable, improve AI citation chances, or adapt an article for answer engines. Produces an AEO-optimised rewrite with question headings, 50–80 word answer capsules, a paragraph-length audit, and flagged trust signals.★ 1.4k GitHub starsSkillConduct a structured ethical review of an AI or ML featureAI Ethics Review Skillmohitagw15856/pm-claude-skills · by mohitagw15856Conduct a structured ethical review of an AI or ML feature, model, or product. Use when preparing to deploy an AI system, assessing algorithmic risk, auditing a model for bias, or producing a responsible AI impact assessment. Produces a structured ethics review covering fairness, transparency, privacy, safety, accountability, and societal impact with a risk tier score, pre-deployment checklist, and prioritised mitigations.★ 1.4k GitHub stars