T09 · Insecure Skill Coding Practices
- Location
SKILL.md:125- Finding
Persistent Storage of Sensitive Health and Behavioral Information
- Content
View full analysis
Vulnerability Details
File Location:
SKILL.md, lines 125-145 and 363-378
Vulnerability Type: Sensitive data persisted without defined privacy safeguards
Risk Level: MediumVulnerable Code Snippet
markdown ## User Preferences to Learn Over time, remember these preferences (via SkillBoss API Hub memory): **Schedule & Energy:** - Peak focus hours (morning person vs. night owl) - Typical energy patterns throughout the day - Best times for deep work vs. shallow tasks **Task Management:** - Preferred number of daily priorities (1-3 recommended) - Task/note storage location (files, apps, directories) - Preferred reminder frequency and channels **ADHD Profile:** - Diagnosed or suspected ADHD - Current treatments (medication, therapy) - for context only - Common pitfalls (social media, hyperfocus traps) - Strategies that have worked in the past **Communication Style:** - Prefers gentle prompts vs. direct reminders - Response to body doubling (helpful/neutral/unhelpful) - Sensitivities around accountability languageThe related persistence instructions state:
markdown ### Memory Usage: - Store user preferences and patterns - Remember what strategies have worked - Track routine adherence over time - Note energy patterns and triggersTechnical Analysis
The skill instructs the agent to retain diagnosis status, medication or therapy information, behavioral triggers, routines, energy patterns, and communication sensitivities in persistent SkillBoss API Hub memory. These data can constitute sensitive health and behavioral information.
The instructions do not require explicit user consent before persistence, limit collection to strictly necessary fields, define a retention period, provide a deletion mechanism, or prohibit storing detailed treatment and crisis-related information. The skill also supports coordination with task-tracking, calendar, and note-tak ...[truncated 1815 chars]
- Remediation
View remediation
Remediation Suggestions
- Require explicit, informed opt-in before saving any information across sessions.
- Do not persist diagnosis, medication, therapy, crisis, or other clinical details by default.
- Store only minimal task-relevant preferences, such as preferred reminder frequency or focus-block length.
- Tell users what will be stored, where it will be stored, why it is needed, and which integrations may access it.
- Establish short retention periods and allow users to inspect, correct, export, and delete stored information.
- Separate ordinary productivity preferences from health-related data and apply stricter access controls to the latter.
- Prohibit sharing sensitive memory with calendar, task-tracking, note-taking, or other skills unless the user separately authorizes the specific disclosure.
- Avoid writing sensitive details to plaintext task files or notes; use protected storage with encryption and least-privilege access where persistence is necessary.
- Add an instruction such as: “Never store diagnosis, medication, therapy, crisis disclosures, or other health information unless the user explicitly asks you to remember that specific item.”
- Log and surface memory writes so users can verify what was retained.