T09 · Insecure Skill Coding Practices
- Location
SKILL.md:31- Finding
Persistent Plaintext Profiling of Real-World Interactions
- Content
View full analysis
Vulnerability Details
File Location:
SKILL.md, lines 31–46
Vulnerability Type: Plaintext storage of potentially identifiable personal and behavioral data
Risk Level: MediumComplete Code Snippet:
markdown **Agent action**: In your head or notes app, run the 3-second checklist: Capable? Tiny ask? Genuine opener ready? If yes, proceed. Use the filesystem to log successful activations in `help-log.md` (date, person type, ask, outcome) to track what works in your area. ### Step 2: Deliver the Micro-Request Script Use this exact 4-part formula out loud (keep it under 15 seconds total): 1. Genuine opener (smile + eye contact): “Hi, I really like how [specific positive thing] you did.” 2. State the tiny need: “I’m trying to [simple action] and could use a quick hand for literally 10 seconds.” 3. Make it easy for them: “Would you mind just [super-specific one-step action]?” 4. Immediate gratitude + exit: “Thank you so much — you just saved me.” **Agent action**: Practice the full script aloud once before approaching (record yourself if possible). After the interaction, immediately note in `help-log.md`: exact script used, their reaction (warm / neutral / hesitant), and what you offered in return. ### Step 3: Close with Reciprocity (The Glue) Within 10 seconds of their help, offer something back — even if tiny: “Next time I see you I’ll grab the door for you” or hand them a spare bottle of water / snack you have, or simply “If you ever need anything like this, I’m around.” **Agent action**: If it’s a repeat person (neighbor, regular cashier), create a new file `relationship-[name-or-type].md` and note the date + small reciprocity offered. Update it each time you see them to keep the ally warm.Technical Analysis
The skill instructs the agent to persist dates, person types or names, requests, reactions, and relationship histories in ordinary Markdown files. These records may identify or make rec ...[truncated 1652 chars]
- Remediation
View remediation
Remediation Suggestions
- Make interaction logging optional and disabled by default.
- Store anonymous aggregate statistics instead of person-level records.
- Explicitly prohibit names, contact information, precise locations, physical descriptions, work schedules, and other identifying details.
- Do not create one file per person; use non-identifying counters or ephemeral session notes.
- Define a short retention period and automatically delete expired records.
- Require informed consent before retaining information about another person.
- Keep any necessary records outside shared repositories and apply restrictive filesystem permissions.
- Warn users not to synchronize, publish, or commit the records to source control.
- Avoid recording audio unless all affected parties have consented and applicable law permits it.
