T09 · Insecure Skill Coding Practices
- Location
SKILL.md:126- Finding
Persistent Storage of Sensitive Health and Behavioral Information Without Explicit Privacy Controls
- Content
View full analysis
Vulnerability Details
File Location:
SKILL.md:126-145andSKILL.md:363-368
Vulnerability Type: Persistent storage of sensitive user information without explicit consent, minimization, retention, or deletion requirements
Risk Level: MediumVulnerable Instructions
SKILL.md:126-145: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 languageSKILL.md:363-368: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 explicitly directs the agent to place user information into persistent SkillBoss API Hub memory. The specified information includes diagnosed or suspected ADHD, medication or therapy details, behavioral triggers, routine adherence, energy patterns, and communication sensitivities.
These data points can constitute sensitive health and behavioral information. The instructions do not require:
- Explicit, informed consent before persistence.
- Separate confirmation before storing diagnosis or treatment information.
- Coll ...[truncated 2440 chars]
- Remediation
View remediation
Remediation Suggestions
- Make persistent memory opt-in rather than automatic. Ask for explicit permission before saving any user information.
- Require separate, specific confirmation before storing diagnosis, medication, therapy, or other health-related information.
- Do not persist treatment details by default. Prefer non-sensitive operational preferences such as desired reminder timing.
- Explain what will be stored, why it is needed, where it will be stored, and how long it will remain.
- Apply data minimization. Store generalized preferences instead of raw disclosures, such as “prefers afternoon reminders” rather than detailed health context.
- Define retention limits and automatically expire behavioral and health-related records unless the user renews consent.
- Provide commands or workflows that let users inspect, correct, export, and delete all saved information.
- Restrict memory access to the minimum set of skills and integrations required for the requested workflow.
- Prohibit storing credentials, full medical histories, clinician details, or unnecessary medication information.
- Add an instruction such as:
markdown Never store diagnosis, medication, therapy, crisis disclosures, or other sensitive health information unless the user explicitly asks for that specific information to be remembered. Before saving it, state what will be stored and obtain confirmation. Provide a way to review and delete it. Prefer temporary session context and minimally sensitive summaries.