T09 · Insecure Skill Coding Practices
- Location
SKILL.md:998- Finding
Plaintext Storage and Unredacted Disclosure of Vehicle and Insurance Identifiers
- Content
View full analysis
- Remediation
View remediation
Security audit
Security checks for vulnerabilities and agentic risk
The skill is a legitimate vehicle-maintenance tracker, but it stores and reuses sensitive vehicle and insurance details, sends VINs to NHTSA, and creates a recurring check-in job without enough privacy and lifecycle controls.
Install only if you are comfortable with a local agent keeping vehicle history, VINs, insurance policy details, provider history, warranty data, fuel logs, and business-use expense information in workspace files. Before using VIN decode or recall checks, understand that the VIN may be sent to NHTSA. Review or disable the weekly cron job if you do not want background check-ins, avoid storing full insurance policy numbers unless you need emergency-card access, and keep the workspace private.
SKILL.md:998Plaintext Storage and Unredacted Disclosure of Vehicle and Insurance Identifiers
The skill is designed to store highly sensitive information including VINs, insurance provider and policy number, roadside assistance numbers, location-linked service history, and warranty records, and to transmit some of that data to external NHTSA endpoints. Without a clear upfront privacy notice and consent flow, users may disclose regulated or sensitive data without understanding retention, sharing, or exposure risks.
Skill enumerates or reads other installed skills. Access to other skills' SKILL.md files or the skills directory reveals prompt instructions, capabilities, and secrets that should be invisible to peer skills.
Copy SKILL.md into your Clawdbot skills directory:
<workspace>/skills/mechanic/SKILL.md
The README states that first use will set up a recurring cron job, but it does not prominently warn users before installation or explain what will run, how often, and how to disable it. Silent or under-disclosed persistence is security-relevant because background scheduled tasks expand the attack surface, surprise users, and can continue operating with access to user data after the initial interaction.
The README explicitly says the skill stores vehicle records in local data files and advertises emergency info cards containing VIN and insurance details, but it does not warn users that sensitive personal and vehicle-identifying information will be persisted on disk. This creates privacy and security risk because users may provide insurance, VIN, provider history, and location-related data without understanding retention, local exposure, backup syncing, or shared-workspace access implications.
The description explicitly says to use the skill for 'anything mechanic-related,' which is broad enough to trigger on generic automotive conversations rather than clear user intent to access a data-storing maintenance tracker. That can cause unnecessary activation, collection of sensitive vehicle/insurance/VIN data, and unintended external API lookups.
The skill instructs sending vehicle identifiers to an external NHTSA recall API, and elsewhere prefers VIN-based lookups. VINs are unique identifiers that can be sensitive when linked with service history, insurance, and location data, so transmitting them off-platform creates privacy and correlation risk even if the destination is legitimate.
Monitor for open recalls on all tracked vehicles using the free NHTSA API (no API key required).
### API Endpoints
- **By make/model/year:** `https://api.nhtsa.dot.gov/recalls/recallsByVehicle?make=Ford&model=F-350&modelYear=2021`
- **By VIN (more precise):** `https://api.nhtsa.dot.gov/recalls/recallsByVin?vin=XXXXX`
If a VIN is stored, prefer the VIN-based lookup. Otherwise fall back to make/model/year.
The VIN-specific recall endpoint explicitly directs the skill to transmit a full VIN to a third-party service. Because the same skill also stores insurance details, policy numbers, emergency contacts, and maintenance history, a mistaken or silent VIN transmission materially increases privacy exposure and linkage risk.
### API Endpoints
- **By make/model/year:** `https://api.nhtsa.dot.gov/recalls/recallsByVehicle?make=Ford&model=F-350&modelYear=2021`
- **By VIN (more precise):** `https://api.nhtsa.dot.gov/recalls/recallsByVin?vin=XXXXX`
If a VIN is stored, prefer the VIN-based lookup. Otherwise fall back to make/model/year.
Skill enumerates or reads other installed skills. Access to other skills' SKILL.md files or the skills directory reveals prompt instructions, capabilities, and secrets that should be invisible to peer skills.
### Integration with Tax-Professional Skill
If the user confirms, reference `skills/tax-professional/SKILL.md` and log to `data/tax-professional/YYYY-expenses.json`:
```json
{
"date": "2026-01-15",
No suspicious patterns detected.