elder-scam-briefing
GitHub专为保护老年人免受诈骗设计的沟通与防护技能。提供尊严优先的对话脚本、家庭暗号机制、常见诈骗模式清单及无责备应急响应协议，帮助家庭成员在不冒犯长辈的前提下建立有效防御体系。
Trigger Scenarios
Install
npx skills add mohitagw15856/pm-claude-skills --skill elder-scam-briefing -g -y
SKILL.md
Frontmatter
{
"name": "elder-scam-briefing",
"description": "Protect aging parents from the scams that target them — the conversation that doesn't condescend, the family code word, the top patterns aimed at seniors, and the guardrails that help without taking over. Use when asked how do I talk to my parents about scams, my mom almost sent money to someone, set up scam protection for my dad, or what scams target the elderly. Produces the briefing conversation script (dignity-first), the household defenses, the pattern one-pager to leave behind, and the if-it-already-happened response."
}
Elder Scam Briefing Skill
Scammers target seniors with the most personal attacks in the catalog — the grandchild in fake trouble, the "Medicare representative," the romance that asks for nothing for months — and the standard family response ("Mom, never answer the phone") fails because it trades safety for dignity, so it gets quietly ignored. This skill builds the version that works: a conversation between adults ("these are professional operations targeting everyone — here's what they're running this year"), one family code word, a few structural guardrails that don't require surveillance, and a no-blame protocol for the day something slips through — because shame is the scammer's best retention tool.
What This Skill Produces
- The conversation script — dignity-first framing, the ask-their-advice open, and the code-word agreement
- The pattern one-pager — the current senior-targeted families in plain language, printable, fridge-worthy
- The household guardrails — call handling, payment tripwires, and the pause-rule — protective without infantilizing
- The response protocol — if it already happened: the no-blame script + the damage-control ladder
Required Inputs
Ask for these if not provided:
- The people and the dynamics — who's being briefed, their tech comfort, and the honest relationship texture (a parent who resents "being managed" needs the advice-asking version, which happens to be the better version anyway)
- The exposure surface — landline heavy? Active on social media? Online banking? Recently widowed (a targeting trigger the pattern list adjusts for)? Managing their own money entirely?
- Any incidents so far — near-misses or losses reroute the output: response protocol first, briefing second
Framework: The Dignity-First Rules
- Open by recruiting, not warning: "I read that these phone scams stole billions last year — has anything weird come through your phone? What do you think about how they work?" — asking their read makes them the analyst, not the mark. The worst possible open is "you need to be careful," which files the whole topic under being-managed.
- The code word is the single highest-value minute: a family password for any call claiming emergency-money-needed ("what's the word?"), agreed once, works forever — and covers the voice-cloning era honestly: a voice that sounds exactly like the grandkid no longer proves anything; the word does. Say that plainly; it's the update most families haven't made.
- The pattern one-pager stays current and concrete: the grandparent emergency (urgency + secrecy — "don't tell Mom" is itself the tell) · government/Medicare impersonation (agencies don't call asking for numbers or payment) · tech-support pop-ups (the number on the screen is the scam) · romance grooming (months of warmth, then the investment platform or the emergency) · prize/lottery ("pay fees to collect" — collecting costs nothing, ever) · the fake-fraud-alert "safe account" call (banks never ask you to move money). Each with its one-line counter, in large type, on the fridge.
- Guardrails beat vigilance: unknown-caller screening (voicemail is a fine scam filter), the 24-hour pause rule for any unplanned payment over a threshold they set ("big decisions deserve a day" — a dignity frame, not a leash), bank alerts on large transfers configured with them, not on them, and — where the family relationship supports it — a trusted-contact designation at the bank (a standard, limited mechanism; not account access). Every guardrail is opt-in and explained by its logic.
- Pre-load the no-blame protocol: the reason losses go unreported for months is shame — so the briefing ends by installing the antidote in advance: "these people are professionals; if anything ever gets through, telling us fast is the win, and nobody will be upset." If something already happened: that script first, then the data-breach-response/fraud-line ladder, then reporting — with the note that reporting is also how they protect the next person, which restores agency.
Output Format
Scam Briefing Plan: [family]
The Conversation
[The recruiting open, verbatim · the code-word agreement + the voice-cloning sentence · the advice-asking posture throughout]
The One-Pager (print this)
[The 6 patterns in large plain type, each: the setup → the tell → the counter-line]
The Guardrails (opt-in, with their logic)
[Call screening · the pause rule at their threshold · alerts configured together · trusted-contact option (flag: mechanisms vary by bank/jurisdiction)]
If Something Gets Through
[The no-blame script, verbatim · the speed ladder: fraud line → passwords → report · the agency-restoring reporting frame]
Scam patterns evolve and protective mechanisms (trusted contacts, alert options) vary by institution and jurisdiction — refresh the one-pager yearly and verify the mechanisms with their bank. Protection that costs dignity gets ignored; everything here is designed to be accepted.
Quality Checks
- The conversation opens by asking their read, never by warning
- The code word appears with the voice-cloning update stated plainly
- Every guardrail is opt-in and carries its dignity-preserving logic
- The one-pager is concrete: setup → tell → counter, no lectures
- The no-blame protocol is installed before it's needed
Anti-Patterns
- Do not script condescension — "let me handle your money" loses the war to win a battle
- Do not rely on vigilance — tired, lonely, or rushed defeats vigilance; structure doesn't care
- Do not skip the voice-cloning sentence — the family that trusts voices is running last decade's defense
- Do not respond to a loss with anger or I-told-you-so — shame is why the second loss goes unreported
- Do not build surveillance and call it protection — alerts configured with them, or the whole system gets opted out of
Version History
- 54fad50 Current 2026-07-19 13:25
