T09 · Insecure Skill Coding Practices
- Location
references/onboarding-flow.md:56- Finding
Plaintext Persistence of Sensitive Household Profiles
- Content
View full analysis
- Remediation
View remediation
Security audit
Security checks for vulnerabilities and agentic risk
This instruction-only skill is coherent with its family-reminder purpose, but users should understand it stores sensitive household notes locally.
Install only if you are comfortable letting the agent keep local notes about family, friends, children, dates, preferences, and reminders. Keep the memory directory out of Git, shared folders, and cloud sync unless you understand the exposure; avoid storing school names, detailed health history, financial details, addresses, or full birth dates, and delete memory/people/ if you stop using it.
references/onboarding-flow.md:56Plaintext Persistence of Sensitive Household Profiles
Skill enables autonomous high-impact decisions without human-in-the-loop verification. Critical operations (destructive commands, financial transactions, data deletion) should require explicit user confirmation.
### Immediate: Holidays & Leave Calendar
Before or during onboarding, populate the user's memory with local public holidays, school term dates (if they have kids), and annual leave optimisation strategies. This is public information — no approval needed. See [references/holidays-and-leave.md](references/holidays-and-leave.md) for the full approach.
### First Use: Onboarding
The file describes ongoing monitoring and proactive assistance across highly sensitive personal domains including relationships, health, finances, parenting, and social history, but provides no privacy guardrails, consent requirements, data minimization rules, or restrictions on retention/sharing. In this skill context, the absence of explicit handling guidance is risky because the assistant is intended to accumulate intimate household knowledge over time, increasing the chance of over-collection, inappropriate inference, or unsafe prompting around sensitive data.
The onboarding flow explicitly instructs collecting and storing sensitive personal and household data about the user and third parties, including names, ages, relationships, health considerations, life context, financial renewal timing, and interaction history, but it provides no explicit privacy warning, consent guidance, retention limits, or access controls. In this skill context, the danger is elevated because the assistant is designed to accumulate longitudinal dossiers on family and social contacts over time, increasing the risk of privacy harm, unauthorized profiling, and exposure of people who may never have consented to being recorded.
No suspicious patterns detected.