T09 · Insecure Skill Coding Practices
- Location
SKILL.md:23- Finding
Unnecessary Sensitive Profiling and Unsupported Privacy Guarantees
- Content
View full analysis
Vulnerability Details
File Location:
SKILL.md:23-27,SKILL.md:75-77,user-profile.md:36-44,user-profile.md:75-84,user-profile.md:90-107
Vulnerability Type: Excessive personal-data collection and unverifiable privacy claims
Risk Level: MediumRelevant excerpts translated into English from the source:
markdown ### First use Learn about the user's workplace background to provide precise advice: - Organization type - Position level - Financial situation, including mortgage obligations, living paycheck to paycheck, or inherited wealthmarkdown - Responses are adjusted according to workplace background, position, and financial pressure. - When the background changes, tell the Agent to update the profile. - Conversations are confidential and used only for personalized advice.markdown ## History ### Previously discussed scenarios - Automatically records the types of scenarios discussed by the user. ### Preferred response style - Automatically learns from the responses selected by the user. ### Feedback history - Records user feedback to optimize future advice.markdown The profile is updated automatically, and subsequent advice is adapted to the new situation. ### Data privacy - Profile information is used only to provide personalized advice. - All information is stored locally. - Conversation content is not shared or uploaded.Technical Analysis
The Skill solicits financial circumstances and employment information even though these details are not necessary to produce general workplace communication templates. It also describes automatic maintenance of consultation history, preferences, and feedback.
The project contains only Markdown instructions. It provides no implementation of consent controls, data minimization, encryption, access restrictions, retention periods, secure deletion, or storage isolation. It also contai ...[truncated 1888 chars]
- Remediation
View remediation
Remediation Suggestions
- Remove financial-status questions unless a concrete and proportionate need is documented.
- Make all profiling optional and provide useful generic advice when users decline.
- Obtain explicit, informed consent before retaining profile fields, consultation history, preferences, or feedback.
- Default to session-only processing rather than persistent storage.
- Clearly identify every collected field, its purpose, storage location, retention period, access boundary, and deletion procedure.
- Replace absolute claims such as “all information is stored locally” and “conversation content is not uploaded” with statements verified against the actual Agent runtime and model provider.
- Provide commands or documented procedures that allow users to inspect, correct, export, and permanently delete their profile.
- If persistence is implemented, apply restrictive file permissions, encryption where appropriate, retention limits, and safeguards preventing profile data from entering unrelated prompts or sessions.
- Collect only the minimum context needed for each response and avoid retaining raw workplace-conflict narratives.
