Skills DirectorySkills Directory
SkillsLearnSecurityCategoriesDocsBlogPro
Sign InSubmit Skill
Skills Directory

Security-tested agent skills for Claude, coding agents, and AI workflows.

Directory

  • Browse Skills
  • All Skills A–Z
  • Claude Skills
  • Claude Code Skills
  • Agent Skills
  • Categories
  • Authors
  • Submit a Skill

Learn

  • Learn Hub
  • Install Claude Skills
  • Write SKILL.md
  • Skills vs MCP
  • Directories Compared

Security

  • Security
  • Methodology
  • Secure Claude Skills
  • Security Badges
  • Chrome Extension
  • Skill Manager

Company

  • About
  • Community
  • Blog
  • API Docs
  • Advertise

2026 Skills Directory. All rights reserved.

ProTermsPrivacyRefunds
Back to skills

Funeral Pricing Decoder

ASecurity

Decode a funeral home price list while grieving — the package maths versus the itemised list, the non-declinable basic fee, the upsells that arrive as care, and the direct-cremation benchmark that anchors every other number. Use when asked to compare funeral quotes, is this funeral price fair, what can we decline, or help me read this price list. Produces a line-by-line decode, the decline-safely list, package-versus-itemised maths, questions for the director, and a comparison across homes. C...

1,378 stars
0 votes
0 copies
0 views
Added 9/20/2026
ai-agentsgit

Works with

cli

Security Analysis

A100/100

Scanned 9/20/2026

$npx -y skills add mohitagw15856/pm-claude-skills --skill funeral-pricing-decoder --agent claude-code

Installs into .claude/skills of the current project.

Are you the author of Funeral Pricing Decoder?

Add the live security badge to your README — it updates automatically with every re-scan.

Security grade badge for Funeral Pricing Decoder
[![Security: A — Skills Directory](https://www.skillsdirectory.com/api/skills/mohitagw15856-funeral-pricing-decoder/badge)](https://www.skillsdirectory.com/skills/mohitagw15856-funeral-pricing-decoder)

More formats (shields.io, HTML) on the badges page. Keep it an A: scan every change in CI with Pro.

Download with Pro
Files
SKILL.md
---
name: funeral-pricing-decoder
description: "Decode a funeral home price list while grieving — the package maths versus the itemised list, the non-declinable basic fee, the upsells that arrive as care, and the direct-cremation benchmark that anchors every other number. Use when asked to compare funeral quotes, is this funeral price fair, what can we decline, or help me read this price list. Produces a line-by-line decode, the decline-safely list, package-versus-itemised maths, questions for the director, and a comparison across homes. Consumer information, not legal advice; disclosure rules are strongest in the US (FTC Funeral Rule)."
homepage: https://mohitagw15856.github.io/pm-claude-skills/skill/funeral-pricing-decoder.html
metadata:
  {
    "openclaw": { "emoji": "🧠" }
  }
---

# Funeral Pricing Decoder

Funeral pricing is the only major purchase routinely made inside seventy-two hours, by someone in grief, from a seller who is also a comforter — and the price list reflects that. Packages bundle the declinable with the mandatory; the casket room is arranged around the middle-priced model; and phrases like *protective* and *what most families choose* do work that would be illegal in most other retail. This decodes the list line by line: what the law (where it applies) says must be itemised, what can be declined, what the direct-cremation figure reveals about every other number on the page — so the decision can be made with love *and* arithmetic, which are not opposites.

## What This Skill Produces

- **A line-by-line decode** — every item on the price list classified: mandatory fee, required-if-chosen, freely declinable, or third-party pass-through
- **The decline-safely list** — what can be refused without disrespect: embalming in many circumstances, the package's bundled extras, the home's own casket
- **Package vs itemised maths** — the package unbundled and re-priced from the itemised list, with the difference shown
- **The benchmark anchor** — the home's direct-cremation and immediate-burial figures, which price the *service minimum* and expose the margin on everything above
- **Questions for the director** — phrased for a conversation that stays warm while the numbers get answered
- **A comparison table** — the same funeral specified across multiple homes, like-for-like

## Required Inputs

Ask for these if not provided:
- **The price list(s)** — pasted or summarised; if the home has not provided one in writing, that fact is itself a finding
- **What is wanted** — burial or cremation, service type and size, any religious or cultural requirements that fix certain choices
- **The budget reality** — stated plainly; the skill's whole job is making the money conversation possible
- **The country** — disclosure rights differ sharply: the US FTC Funeral Rule mandates itemised general price lists and third-party casket acceptance; elsewhere protections vary and the skill flags what to verify locally

## Framework: Read the List Like a Buyer, Not a Mourner

1. **Find the non-declinable fee first.** Most lists carry a basic-services fee that applies regardless of choices — it is the real price of engaging that home, and comparing *it* across homes is the fastest meaningful comparison.
2. **Unbundle every package.** Re-price the package from the home's own itemised list. Packages that cost more than their parts are common; packages that hide declinable items inside "everything taken care of" are the norm.
3. **Anchor on direct cremation / immediate burial.** These minimum-service figures reveal each home's floor. A home whose floor is double another's prices everything from a different baseline — grief does not change that arithmetic.
4. **Decode the casket room.** Markup concentrates here. *Protective* caskets (gaskets, sealers) do not preserve remains — where the US Rule applies, homes may not claim otherwise — and third-party caskets generally must be accepted without a handling fee there. Elsewhere: ask, in writing.
5. **Question embalming as a default.** It is frequently presented as required; in many jurisdictions it is not, outside specific circumstances (some public viewings, some transport). The decode marks it required-if-chosen at most, pending local verification.
6. **Separate the home from the cash advances.** Flowers, obituaries, clergy, cemetery fees are often pass-throughs — ask whether they are marked up, and take any the family would rather handle directly.
7. **Keep the warmth.** Every question here can be asked kindly. Directors who welcome them are common and worth choosing; a home that resists itemised discussion has answered a different question.

## Output Format

### Funeral price decode: [home(s)] · [burial/cremation] · [date]

**The non-declinable floor:** basic-services fee [amount] · direct-cremation benchmark [amount] · immediate-burial benchmark [amount]

**Line-by-line**
| Item | Price | Class | Note |
|---|---|---|---|
| [item] | [amount] | mandatory / required-if-chosen / declinable / pass-through | [what the phrasing is doing] |

**Package check:** [package name] at [price] vs unbundled [sum] → **difference [amount]** · bundled declinables: [list]

**Decline-safely list:** [items, each with the one-line reason and any verify-locally flag]

**Questions for the director** — [warm phrasings that get numbers]

**Across homes** (like-for-like: [specification])
| Home | Basic fee | This funeral, itemised | Notes |
|---|---|---|---|

> Consumer information, not legal advice. Itemisation rights, embalming rules, and casket-acceptance duties vary by country; the strongest stated protections referenced here are US (FTC Funeral Rule) — verify locally elsewhere. None of this arithmetic is a comment on how much anyone loved anyone.

## Quality Checks
- [ ] Every line is classified, and no item is left as ambiguous prose
- [ ] The package is re-priced from the home's own itemised numbers
- [ ] The benchmark figures appear and are used as the anchor
- [ ] Protective-casket and embalming claims are decoded with the verify-locally flag where the US Rule does not apply
- [ ] Questions are phrased to keep the conversation warm
- [ ] The tone never implies spending less means grieving less

## Anti-Patterns
- **Decoding with contempt.** Most funeral directors are decent; the decode targets pricing structure, not the profession.
- **Letting the package stand unexamined** because "it's easier right now" — easier is what the bundle is priced on.
- **Treating embalming or the protective casket as fact** rather than claims with jurisdictions attached.
- **Comparing homes on the package price** instead of the like-for-like itemised build.
- **Rushing the reader.** Nothing here expires in an afternoon; a family that takes a day to compare loses nothing.
- **Ever equating cost with love.** The skill exists to break that equation, not reinforce it.

Attribution

mohitagw15856mohitagw15856
View sourceSee grades on GitHubMore from mohitagw15856 →
SSkills DirectorySkills Directory

Ship a skill? Prove it's safe.

Free 120-pattern security scan, letter grade, and an embeddable README badge.

Submit a skill

Is this your skill, or is something wrong with this listing? Request removal or report an issue. Author removals are honored within 72 hours.

Comments (0)

No comments yet. Be the first to comment!

SSkills DirectorySkills Directory

Ship a skill? Prove it's safe.

Free 120-pattern security scan, letter grade, and an embeddable README badge.

Submit a skill

Related Skills

Caveman

Terse caveman voice: answer first, fluff gone, every technical fact kept. Use for /caveman, "caveman mode", "talk like caveman", "be brief", "less tokens". Stays on until "stop caveman" or "normal mode".

1100021 votes

Hyperplan

Adversarial multi-agent planning skill. Self-orchestrates 5 hostile category members (unspecified-low, unspecified-high, deep, ultrabrain, artistry) via team-mode for ruthless cross-critique debate, distills only the defensible insights, then MANDATORILY hands the distilled insight bundle to the `plan` agent for executable plan formalization. Use when planning needs maximum rigor and surfacing of weak assumptions, blind spots, and over-engineering. Triggers: 'hyperplan', 'hpp', '/hyperplan', ...

698431 votes

Writing Skills

Create and manage Claude Code skills in HASH repository following Anthropic best practices. Use when creating new skills, modifying skill-rules.json, understanding trigger patterns, working with hooks, debugging skill activation, or implementing progressive disclosure. Covers skill structure, YAML frontmatter, trigger types (keywords, intent patterns), UserPromptSubmit hook, and the 500-line rule. Includes validation and debugging with SKILL_DEBUG. Examples include rust-error-stack, cargo-dep...

3931 votes

Mcp Code Execution

Routes multi-tool workflows through MCP servers for large datasets and pipelines. Use when Bash tool overhead is limiting throughput on data-heavy tasks.

3421 votes

catchup

Recovers the conversation and failed tool calls of a previous Codex, Amp, Claude Code, Antigravity, Cline, Copilot CLI, Cursor, DeepSeek Harness, Grok Build, Kimi, OpenCode, Pi Agent, or ZCode session. Use when the user says "catch up", "what did the last session do", "get me up to speed", "I switched agents", asks to recover/summarize a previous session before continuing, or asks to diagnose or report a catchup failure. Do NOT use for the current conversation, git history, or any non-agent log.

741 votes
View all in ai-agents →