T09 · Insecure Skill Coding Practices
- Location
SKILL.md:323- Finding
Persistent Retention of Sensitive Coaching Data Without Defined Safeguards
- Content
View full analysis
Vulnerability Details
File Location:
SKILL.md, lines 323-335
Vulnerability Type: Uncontrolled retention of potentially sensitive user information
Risk Level: MediumVulnerable Code Snippet
The following is an English translation of the complete relevant source segment:
markdown ### Feature 3: Growth Records (User Profile) **Recorded content**: - User's core problems (confusion, blockers, goals) - User's areas of interest (areas where the user actually spends the most time) - User's action records (what the user said they would do and what they actually did) - User's key insights ("aha moments" from conversations) **Usage scenarios**: - Review previous progress during the next conversation - Discover user patterns, such as "the user always selects option 1 but does not execute it" - Adjust strategies, such as "the user needs stronger external supervision"Related retention instructions also appear at
SKILL.md:431-458, including archiving the user's problem, insights, action plan, and execution results.README.md:50describes saving conversations and actions as an automatically executed feature.Technical Analysis
The Skill directs the Agent to create and reuse a persistent user profile containing behavioral, career, relationship, emotional, and potentially mental-health-related information. It does not specify:
- Whether explicit user consent is required before storage
- Which storage or memory system receives the information
- How access to the retained information is controlled
- How long records are retained
- How users can inspect, correct, export, or delete records
- Which sensitive fields must be excluded or minimized
- Whether the data may be reused outside the original coaching context
This is an insecure data-lifecycle design. Although the Skill does not contain code that directly writes files or sends records externally, a capable Agent may interpret th ...[truncated 1376 chars]
- Remediation
View remediation
Remediation Suggestions
- Make persistent recording strictly opt-in and ask for explicit consent before storing any information.
- Clearly identify the storage system, intended purpose, retention period, and parties or components that can access the data.
- Store only the minimum information required. Prefer short, user-approved summaries over full conversations or detailed personal profiles.
- Exclude sensitive health, relationship, identity, financial, credential, and other high-risk data by default.
- Provide commands or documented procedures to inspect, correct, and permanently delete stored records.
- Apply encryption at rest, access controls, tenant isolation, and audit logging in any supporting memory implementation.
- Require renewed consent before reusing stored information for a materially different purpose.
- Replace statements that imply automatic storage with language such as: “With your permission, I can save a brief summary for future coaching sessions.”
