T09 · Insecure Skill Coding Practices
- Location
SKILL.md:323- Finding
Persistent User Profiling Is Required Without Defined Privacy or Storage Controls
- Content
View full analysis
Vulnerability Details
File Location:
SKILL.md:323-335
Additional Locations:SKILL.md:99,SKILL.md:259,SKILL.md:416,SKILL.md:431-457,README.md:50
Vulnerability Type: Uncontrolled storage of conversation-derived personal data
Risk Level: MediumRelevant Source Segment — English Translation:
markdown ### Feature 3: Growth Records (User Profile) **Recorded content**: - The user's core problems (confusion, blockers, and goals) - The user's areas of interest (fields where the user actually spends the most time) - The user's action records (what the user said they would do and what they actually did) - The user's key insights ("aha moments" from conversations) **Use cases**: - Review previous progress during the next conversation - Identify user patterns, such as repeatedly selecting a plan but not executing it - Adjust strategies, such as determining that the user needs stronger external supervisionThe archival instructions are reinforced later in the same file:
markdown ## Conversation Completion and Archiving 1. Confirm what the user gained 2. Archive key information: the user's problem, insight, and action plan 3. End the conversation **Archived content for review during subsequent conversations**: - The user's core problem - The user's key insight - The user's action plan - The user's execution resultTechnical Analysis
The Skill directs the agent to create a cross-session user profile containing personal concerns, interests, behavioral history, plans, and outcomes. Such information may include sensitive emotional, career, educational, or mental-health-adjacent disclosures.
No corresponding instructions define:
- An affirmative consent requirement before persistence
- The storage backend or exact destination
- Access-control boundaries
- Data minimization requirements
- Encryption requirements
- A retention or automatic- ...[truncated 1966 chars]
- Remediation
View remediation
Remediation Suggestions
- Make persistent recording opt-in and request explicit user consent before the first write.
- Explain which fields will be retained, why they are needed, where they are stored, and how long they will remain.
- Store concise summaries rather than raw conversations, and exclude sensitive details unless strictly necessary.
- Define a retention period with automatic expiration.
- Provide commands or documented procedures to review, correct, export, and permanently delete profile data.
- Require per-user and per-tenant isolation with least-privilege access controls.
- Require encryption in transit and at rest when the host supports persistent storage.
- Do not claim that information has been saved unless the host exposes an approved storage mechanism and confirms a successful write.
- Add an explicit no-storage mode and make it the default for sensitive or mental-health-adjacent discussions.
- Document that persistence is host-dependent and prohibit fallback storage in logs, temporary files, or shared workspace files.
