T09 · Insecure Skill Coding Practices
- Location
SKILL.md:323- Finding
Automatic Retention of Potentially Sensitive Coaching Data Without Privacy Controls
- Content
View full analysis
Vulnerability Details
File Location:
SKILL.md:323-334, with related instructions atSKILL.md:99,SKILL.md:259,SKILL.md:416, andSKILL.md:431-459; also advertised atREADME.md:50
Vulnerability Type: Uncontrolled retention of potentially sensitive user data
Risk Level: MediumRelevant instruction excerpt translated into English:
markdown ### Feature 3: Growth Records (User Profile) **Recorded content:** - The user's core problems, such as confusion, obstacles, and goals - The user's areas of interest - The user's action records, including intended and completed actions - The user's key insights from conversations **Usage scenarios:** - Review previous progress during the next conversation - Identify patterns in the user's behavior - Adjust coaching strategiesRelated instructions require the Agent to save conversations and actions for later sessions, record insights in a user profile, and archive the user's problems, insights, action plans, and execution results.
README.md:50describes this behavior as automatic.Technical Analysis
The Skill instructs the Agent to create a persistent behavioral profile containing personal problems, interests, plans, insights, and execution history. In a coaching context, these records may include mental-health concerns, relationship information, career circumstances, and other sensitive personal details.
No consent mechanism, storage boundary, retention period, deletion procedure, data-minimization rule, access-control requirement, or user-isolation requirement is defined. The instructions also do not distinguish temporary conversational context from persistent memory.
The package contains no storage implementation, so the audit cannot establish where the information would be written. The vulnerability arises when a host Agent follows these instructions using an available memory or profile facility. This is an insecure data-handling desi ...[truncated 1262 chars]
- Remediation
View remediation
Remediation Suggestions
- Make all cross-session storage explicitly opt-in rather than automatic.
- Before saving anything, disclose what fields will be stored, why they are needed, where they are stored, and how long they will be retained.
- Default to ephemeral conversational context when the user has not consented to persistence.
- Store concise summaries instead of complete conversations, and exclude mental-health, relationship, identity, financial, and other sensitive details unless strictly necessary.
- Require per-user isolation and prohibit reading or writing another user's profile.
- Add commands or documented procedures to inspect, correct, export, and delete stored information.
- Define a short retention period and automatic expiration policy.
- Require encryption and access controls from any host memory implementation.
- Update
README.mdso that it does not describe storage as automatic. - Clearly state that the Skill itself does not provide storage and that persistence must not occur unless the host supports the required privacy controls.
