T09 · Insecure Skill Coding Practices
- Location
SKILL.md:129- Finding
Persistent Storage of Sensitive Health Information Without Adequate Privacy Controls
- Content
View full analysis
Vulnerability Details
File Location:
SKILL.md, lines 129-143; related storage instructions at lines 367-371
Vulnerability Type: Sensitive data persistence without explicit consent, minimization, retention, or deletion controls
Risk Level: MediumVulnerable Skill Instructions
markdown 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 onlyThe related memory integration 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 explicitly directs the Agent to retain whether a user has diagnosed or suspected ADHD and details about current medication or therapy in the SkillBoss API Hub memory system. These fields constitute sensitive health information.
The instructions do not require informed opt-in consent before persistence, identify a retention period, provide a deletion mechanism, limit which integrations may retrieve the information, or require data minimization. Treatment information is also not necessary for most of the Skill's stated planning and productivity functions. Although the Skill says the information is for context only, that qualification does not establish a technical access or retention control.
This is classified as
T09: Insecure Skill Coding Practicesbecause the Skill configuration promotes unsafe handling of ...[truncated 1984 chars]- Remediation
View remediation
Remediation Suggestions
- Remove diagnosis status, medication, and therapy details from the default list of information to remember.
- Keep health disclosures session-local unless persistent storage is strictly necessary for a user-requested feature.
- Require explicit, informed, field-specific opt-in before storing any health information. The prompt should identify what will be stored, why it is needed, where it will be stored, and how long it will remain.
- Apply data minimization. Prefer non-medical operational preferences such as desired reminder frequency or preferred focus-block duration.
- Define a short retention period and automatically expire sensitive records.
- Provide commands or documented procedures that allow users to inspect, correct, and delete all stored information.
- Restrict sensitive records from being retrieved by unrelated skills, channels, or integrations.
- Avoid placing health information in plaintext logs, task files, reminder messages, or broadly accessible memory namespaces.
- Add an instruction requiring the Agent to ask before recalling sensitive information in a new conversation or communication channel.
- Document the external memory provider's access controls, encryption expectations, retention behavior, and deletion guarantees.