Agent skill

long-term-care-options

Understand the long-term care options for an older or ill loved one — from in-home care to assisted living to nursing care — so you can compare them for your situation. Use when asked what are the care options for my parent, in-home care vs assisted living vs nursing home, help me choose a care option, or explain long-term care. Produces a plain-English explainer of the main care levels and what each is for, a match to the person's needs (care level, budget, preferences), the key questions and red flags when evaluating providers, cost and funding considerations to research, and how to involve

mohitagw158561,255★ · 1 repos on radarProfile →
claude-codecursorMIT
Install
npx skills add mohitagw15856/pm-claude-skills --skill long-term-care-options --agent claude-code

Same command for any agent — swap --agent for codex, cursor, copilot.

Facts
Files in the skill folder: 1
SKILL.md size: 5 KB
Bundled scripts: none
Path: skills/long-term-care-options/SKILL.md
Open the folder on GitHub →
Where it comes from
Stars: 1,277
Language: HTML

Weekly change comes from our own snapshots, not the repository page — it measures attention, not adoption.

From the SKILL.md

# Long-Term Care Options Choosing care for an aging or ill loved one is one of the hardest decisions a family faces — emotionally fraught, expensive, and full of confusing options. This maps the landscape: what the main levels of care actually are and who each suits, how to match them to your person's real needs and budget, what to look for (and the red flags) when evaluating providers, and how to involve the person with dignity. It's a decision map, not medical or financial advice. ## What This Skill Produces - **The options explained** — the main levels in plain language: in-home care (from occasional help to live-in), adult day programs, assisted living, memory care, and nursing/skilled care — and who each is for - **A needs match** — which options fit the person's actual care level (daily-living help vs. medical vs. dementia care), budget, and preferences - **Evaluation questions & red flags** — what to ask and observe when touring/vetting providers (staffing, safety, cleanliness, culture, turnover, reviews, inspection records) - **Cost & funding to research** — the (jurisdiction-specific) cost ranges and funding routes to look into, flagged to verify - **Involving the person**

What's inside
Steps it walks through
  1. What This Skill Produces
  2. Required Inputs
  3. Framework: Match Need To Level, Vet Carefully
  4. Output Format
  5. Long-term care: [person's needs] · budget [x] · [region]
  6. Quality Checks
  7. Anti-Patterns
  8. Example Trigger Phrases
More from pm-claude-skills
All skills →
About this skill
What does the long-term-care-options skill do?

Understand the long-term care options for an older or ill loved one — from in-home care to assisted living to nursing care — so you can compare them for your situation. Use when asked what are the care options for my parent, in-home care vs assisted living vs nursing home, help me choose a care option, or explain long-term care. Produces a plain-English explainer of the main care levels and what each is for, a match to the person's needs (care level, budget, preferences), the key questions and red flags when evaluating providers, cost and funding considerations to research, and how to involve

How do I install it?

Run `npx skills add mohitagw15856/pm-claude-skills --skill long-term-care-options --agent claude-code` — it drops the skill into your project so the agent can pick it up. Swap the --agent value for codex, cursor or copilot if you use one of those.

Where does this skill come from?

From mohitagw15856/pm-claude-skills, a repository with 1,277 stars. We read it straight from the repository tree rather than a submitted listing, so what you see here is what is actually published.

Is a popular skill a good skill?

Not necessarily. Stars measure attention, not adoption — a repository can trend for a week and be abandoned. That is why we show the weekly change from our own snapshots next to the total, instead of a single flattering number.

Keep going