T09 · Insecure Skill Coding Practices
- Location
SKILL.md:323- Finding
Persistent User Profiling Is Requested Without Consent or Data-Handling Safeguards
- Content
View full analysis
Vulnerability Details
File Location:
SKILL.md:323-334, with related persistence instructions atSKILL.md:431-458
Vulnerability Type:T09: Insecure Skill Coding Practices
Risk Level: MediumVulnerable Skill Text
The following is an English rendering of the complete relevant directives in
SKILL.md:323-334: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 the conversation **Usage scenarios**: - Review previous progress in the next conversation - Identify user patterns - Adjust the coaching strategyRelated end-of-conversation instructions at
SKILL.md:431-458direct the Agent to archive the user's problem, insights, action plan, and later execution results for recall in subsequent conversations. The same behavior is advertised inREADME.md:50as automatically saving conversations and actions.Technical Analysis
The Skill handles potentially sensitive coaching information, including emotional condition, relationships, career concerns, behavioral patterns, goals, and execution history. It instructs the Agent to persist this information in a user profile but does not define:
- An explicit opt-in or informed-consent step
- The storage system or permitted storage scope
- Data minimization requirements
- A retention or automatic-expiration period
- A user-accessible review, correction, or deletion process
- Encryption or access-control requirements
- A rule preventing raw user instructions from being stored as reusable memory
- Separation between factual profile data and untrusted conversational content
This creates both a privacy concern and a memory-integrity risk. If the hosting Agent supports persistent memory, user-controlled content co ...[truncated 1926 chars]
- Remediation
View remediation
Remediation Suggestions
- Require explicit opt-in before creating or updating a persistent profile.
- Show the exact proposed memory entry and require user confirmation before saving it.
- Store only a concise, structured summary approved by the user; do not store raw conversation transcripts by default.
- Prohibit persistence of commands, role instructions, tool requests, URLs, executable content, or text that attempts to control future sessions.
- Define a retention period and automatically delete expired records.
- Provide commands or documented procedures for users to inspect, correct, export, and delete all saved information.
- Bind records to the correct authenticated user and prevent access from unrelated sessions or users.
- Require encryption at rest and in transit when the runtime supports external storage.
- Distinguish verified user facts, tentative inferences, action plans, and untrusted quoted content using separate structured fields.
- Replace the unconditional archival instruction with language such as: “Offer to save a minimal summary only after obtaining explicit user consent.”
