T09 · Insecure Skill Coding Practices
- Location
SKILL.md:40- Finding
Silent and Indefinite Persistence of Personal Information
- Content
View full analysis
Vulnerability Details
File Location:
SKILL.md, lines 40–50 and 62–80
Vulnerability Type: Silent storage of personal information without retention or deletion controls
Risk Level: MediumEvidence
markdown ## First-Time Setup When `plan.md` has `status: template`: 1. Detect the user's language from their messages. Ask in that language. 2. Ask these questions (can ask all at once): - What's your name? - What do you do? (Developer / Designer / Creator / Student / Other) - What's your most important focus right now? - What hours do you usually work? (Morning / Daytime / Evening / Night owl / Irregular) - Preferred language? (English / 中文 / Mix) 3. Generate initial files from answers: - `me/identity.md` — name, role, current season - `plan.md` — mission + focus as first goal (set `status: active`) - `tasks/active.md` — first task from their focusmarkdown ### Distillation — what to save where | Signal | Destination | |--------|-------------| | New task | `tasks/active.md` | | Decision | `decisions/YYYY-MM-DD-slug.md` | | Personal fact | `me/identity.md` | | Insight / lesson | `me/learned.md` | | Goal change | `plan.md` | | Vague thought | `inbox.md` | **Factual** → save silently in background, DO NOT make it the focus of your reply **Subjective** (values, strategy) → ask user first ### Behavior 1. **Be a normal AI first, memory system second.** When the user says something, RESPOND to it naturally (react, comment, ask follow-up, help). Saving to brain happens silently in background — never reply with just "记住了" or "已记录". The user should feel like talking to a smart friend who happens to have perfect memory, not a filing cabinet. 2. Read brain files before answering questions about the user 3. Distill conclusions, not raw conversations 4. Archive, never deleteTechnical Analysis
The Skill instructs the agent to collect identity, occupation, work schedule, goals, tasks, decisions, and other perso ...[truncated 2121 chars]
- Remediation
View remediation
Remediation Suggestions
- Require explicit user consent before enabling persistent memory and separately disclose that later factual statements may be stored.
- Notify the user whenever new information is persisted, or provide a clear session summary of saved items.
- Implement commands or documented procedures to inspect, edit, export, selectively forget, and fully delete stored information.
- Apply configurable retention periods instead of using an unconditional “archive, never delete” policy.
- Exclude credentials, authentication tokens, payment information, medical data, and similarly sensitive information from automatic capture.
- Minimize collected data and store only information necessary for an explicitly selected memory feature.
- Create the memory directory and files with restrictive permissions, such as owner-only access where supported.
- Warn users when the selected directory is managed by cloud synchronization, shared storage, or automated backup software.
- Document the storage location and threat model without exposing implementation details unnecessarily during ordinary interactions.
