Health Insurance
PassAudited by ClawScan on May 1, 2026.
Overview
This instruction-only health insurance skill is coherent and locally scoped, with notable but disclosed use of user-approved local memory and setup commands.
This skill appears safe to install as an instruction-only planner. Before using memory, decide what health, prescription, provider, and financial information you are comfortable storing locally, and personally verify any enrollment action before submission.
Findings (3)
Artifact-based informational review of SKILL.md, metadata, install specs, static scan signals, and capability signals. ClawScan does not execute the skill or run runtime probes.
If the user approves memory, private health and financial context may remain on the device and be reused in later conversations.
The persistent memory template can store sensitive health, prescription, provider, and financial risk information for future insurance decisions.
- Recurring prescriptions: - Expected major procedures: ... - Comfortable monthly premium range: - Comfortable deductible exposure: - Maximum annual out-of-pocket tolerance:
Only approve storing information that is useful for future decisions, avoid IDs or payment details, and periodically review or delete `~/health-insurance/memory.md`.
Approving setup will create local files and directories for health insurance memory.
The setup guide includes local shell commands to create and permission a private directory, but it explicitly says to ask for approval before writing files.
Propose local structure and ask for explicit approval before writing files:
```bash
mkdir -p ~/health-insurance/{comparisons,renewals,notes}
touch ~/health-insurance/memory.md
chmod 700 ~/health-insurance
chmod 600 ~/health-insurance/memory.md
```Confirm the path and contents before allowing setup commands, and keep the restrictive file permissions shown in the instructions.
Mistakes during enrollment could affect insurance coverage, costs, or deadlines.
The playbook addresses high-impact enrollment actions that can affect coverage and costs, but the artifacts present this as an approved-channel, evidence-based workflow rather than automatic submission.
- Submit enrollment through approved channel. - Capture confirmation ID and timestamp. - Save screenshots or confirmation artifacts. - Verify the submitted plan matches the recommended plan exactly.
Treat final enrollment as a user-controlled action; independently verify plan names, IDs, dates, networks, and premiums before submitting anything.