skills/legal/advance-health-care-directive/SKILL.md
Drafts jurisdiction-specific Advance Health Care Directive packages with agent appointment, living will instructions, HIPAA authorization bridge, organ donation preferences, and execution compliance checklists. Trigger when the user mentions advance directive, healthcare proxy, living will, health care agent, HIPAA authorization, medical power of attorney, end-of-life planning, capacity trigger planning, state-specific directive forms, witness/notary requirements for healthcare documents, or cross-state directive portability.
npx skillsauth add casemark/skills advance-health-care-directiveInstall this skill globally with one command. Works with Claude Code, Cursor, and Windsurf.
3 of 9 scanners reported clean
Some scanners were skipped, did not run, or reported a non-clean status. Review each row below.
Produces a jurisdiction-aware, clinically actionable directive package — agent appointment, treatment instructions, HIPAA bridge, execution checklist — that an ER team can parse in under 60 seconds and that survives legal challenge. Grounded in state probate/health codes with HIPAA (45 C.F.R. § 164.508) overlay.
Directives fail when they lack state-specific execution formalities (legally void) or use vague language like "no heroic measures" (clinically useless). This skill eliminates both failure modes.
Gather every time unless user says "use defaults" or "just draft":
Request: prior directives, POLST/MOLST, POAs, guardianship orders, organ donation registrations, relevant medical records. If missing, flag explicitly and proceed with labeled assumptions listing "Open Items / Needed Inputs."
Defaults (if no response): immediate-authority directive; primary agent + one alternate; comfort-focused treatment; forum-neutral template with state execution formalities marked [VERIFY JURISDICTION]; standard HIPAA authorization bridge.
Build the jurisdictional scaffold before drafting.
| Data Block | Required Fields | Verification |
|---|---|---|
| Client profile | Name, DOB, aliases, residence, contact | Spelling consistency across blocks |
| Jurisdiction | Primary state, secondary care states, portability | [VERIFY] execution/effectiveness rules per statute |
| Capacity posture | Red flags, physician assessment needs | Flag for contemporaneous memo if risk present |
| Agent chain | Primary + up to 2 alternates, relationships, contact, disqualifications | No disqualified classes under local statute |
| Treatment values | Scenario-based preferences, values hierarchy, palliative directives | No contradictory instructions |
| Legal/medical interfaces | POLST/MOLST, donor registry, prior directives | Reconcile conflicts; harmonized set |
| Execution logistics | Witness sources, notary method, facility constraints | Jurisdiction-specific affidavit/attestation language |
| Delivery plan | Copy recipients (agent, PCP, facilities, portal) | Distribution checklist |
| Topic | Confirm | |---|---| | Governing statute | Controlling statute + official form/guidance URL | | Formalities | Witness vs. notary options, count, disqualifications, facility add-ons | | Trigger mechanics | Springing vs. immediate; incapacity standard; certifying clinician count | | Substantive scope | Definitions: terminal, incurable, persistent unconsciousness | | Limitations | Pregnancy restrictions, mental health authority, substance/HIV record limits | | Revocation | Permitted methods and effective timing | | Provider protection | Reliance rights for copies/electronic versions; good-faith immunity |
Use this fixed section order with clinically interpretable language throughout:
Agent appointment: identify client, appointed agent with relationship and full contact, trigger condition per state law, scope of authority (consent/denial, admission/discharge, transfer, record access). Written instructions control over discretionary choices; unspecified matters use stated values and substituted-judgment standard.
Successor agents: each assumes authority only when all prior agents are unavailable/unwilling/disqualified per state rules.
HIPAA bridge: authorize agent and alternates to access all PHI immediately upon execution for incapacity determination and care coordination. Scope covers all providers, facilities, labs, insurers. Mark [VERIFY: 45 C.F.R. § 164.508 and state/Part 2 overlays].
Treatment preferences: state goals (comfort/pain control, loved-one contact, avoid futile prolonged treatment), then specific positions on CPR, ventilation, artificial nutrition/hydration, hospitalization, comfort care with explicit palliative direction.
Revocation: revocable while capable by state-authorized methods; latest version governs; severability clause; copies/electronic versions per state law.
| Item | Required Output |
|---|---|
| Witnessing | Correct count, disqualification screening completed |
| Notary | Form matches state-prescribed language |
| Facility patients | Facility-specific add-ons satisfied (ombudsman/patient advocate) |
| Agent acceptance | Optional acceptance statement included |
| Usability | Key instructions identifiable in <60 seconds (ER context) |
| Internal consistency | No contradiction between agent powers and treatment instructions |
| Review tags | Every statutory claim marked [VERIFY] unless confirmed by statute URL |
Every output begins with mandatory front matter:
[VERIFY] items for attorney reviewAsk after delivering the initial package:
If no response, recommend next best refinement and proceed if authorized.
[VERIFY][VERIFY]; never finalize as final legal languagedevelopment
name: automated-contract-summary language: en description: Generates structured executive summaries of contracts using ML — captures key terms, party obligations, risk allocations, and compliance requirements in a standardized format. Optimized for high-volume review where speed and consistency matter. tags: - summarization - agreement - corporate --- # Automated Contract Summarization Produces standardized executive summaries of contracts using machine learning, capturing essential term
tools
Extracts regulatory obligations from dense regulations across jurisdictions. Breaks down multi-level regulations into clear article-level obligations, classifies applicability to a business, and prioritizes by risk level. Use when translating regulations into actionable compliance requirements.
development
Continuously monitors regulatory landscapes for changes relevant to a specific business. Ingests global regulatory updates, filters by relevance, summarizes impact, and produces an actionable change advisory. Use when tracking regulatory developments affecting a particular product or market.
testing
Compares an organization's existing compliance controls, policies, and procedures against extracted regulatory obligations to identify coverage gaps. Produces a remediation plan with prioritized actions. Use when assessing compliance maturity or preparing for regulatory audits.