other
- Location
SKILL.md:30- Finding
Persistent Collection of Third-Party Personal and Location Data
- Content
View full analysis
Vulnerability Details
File Location:
SKILL.md, lines 30–67
Vulnerability Type: Privacy data overcollection and insecure retention
Risk Level: MediumVulnerable Snippet
markdown **Agent action**: Create a file `local-humans.md` and list 8–12 potential people or roles with how to reach them (general store, church, bar, local Facebook group, county office). Prioritize those within 30 km of your site. **Agent action**: Use this opener script: “I’m spending a lot of time in the [forest name] area and I’m amazed by the old timber buildings around here. Have you seen any good examples of log construction nearby?” Listen 80% of the time. Log every conversation in `mentor-[name].md`. Take detailed notes including seasonal advice, tool recommendations, and safety warnings. **Agent action**: When ready for hands-on help, propose mutual benefit: “I’d love to help you with [their project] for a day if you’d be willing to show me how to properly saddle-notch these logs.” Document all exchanges. **Agent action**: Review and update your human map file monthly. Note what worked and what didn’t in each relationship. - Document everything visually (photos + notes) and show progress to your mentors — they love seeing their advice put into practice.Technical Analysis
The skill instructs the agent to create persistent files containing information about nearby people, including how to reach them, their approximate geographic proximity, named conversation records, exchange histories, and photographs. Combining these fields can create identifiable profiles of third parties.
The instructions do not require informed consent, data minimization, access restrictions, secure storage, retention limits, or deletion. The command to log “every conversation,” document “all exchanges,” and update records monthly encourages collection beyond what is strictly necessary to obtain construction advice. File names such as `mentor-[n ...[truncated 1268 chars]
- Remediation
View remediation
Remediation Suggestions
- Require informed consent before recording an identifiable person, private conversation, contact method, or photograph.
- Default to role-based and anonymized notes rather than names, such as
mentor-01.md. - Record only information strictly necessary for the construction task; do not log every conversation or exchange.
- Do not store precise addresses, habitual locations, sensitive personal details, or photographs unless explicitly required and authorized.
- Define a short retention period and automatically review or delete stale records after the relevant construction stage.
- Store records in a user-approved directory with restrictive permissions and exclude them from public repositories and unintended cloud synchronization.
- Give users an opportunity to review and approve the intended fields before files are created.
- Add instructions for correcting or deleting records when a person withdraws consent.
