Renewal Alert

v1.0.0

Track insurance policy renewal dates and send timely reminders before policies expire. Use when users want to register insurance renewal dates, get expiry al...

0· 113·0 current·0 all-time
byWenbing Ji@jiwenbing
MIT-0
Download zip
LicenseMIT-0 · Free to use, modify, and redistribute. No attribution required.
Security Scan
VirusTotalVirusTotal
Benign
View report →
OpenClawOpenClaw
Benign
high confidence
Purpose & Capability
Name/description (renewal reminders) align with the SKILL.md steps (record policy data, set reminders, alert before renewals). There are no unexpected required binaries or credentials.
Instruction Scope
Instructions stay within the renewal-reminder scope (record policy details, schedule reminders, prompt review). However the SKILL.md is vague about where/how data is stored or how reminders are delivered (local memory, calendar, email, external service). That lack of storage/transport detail could lead to unintended exposure of sensitive policy data if the implementing agent persists or transmits it without protections.
Install Mechanism
No install spec and no code files — instruction-only skill. This is low-risk from an installation perspective because nothing is written to disk or downloaded by the skill itself.
Credentials
The skill requests no environment variables, credentials, or config paths. The data it asks the user to record (policy numbers, insurer, premium) is expected for its purpose, but any requester should still consider data-handling practices.
Persistence & Privilege
always is false and the skill does not request elevated presence. There is no instruction to modify other skills or system-wide settings. The main open question is how/where the agent will persist reminders — the skill does not specify retention, encryption, or deletion behavior.
Assessment
This skill appears to do what it says (track renewal dates and remind you). Before installing, consider: 1) You will likely be asked to record sensitive policy details (policy numbers, insurer, premium). Ask or confirm where that data will be stored (agent memory, cloud, calendar) and how it will be protected (encryption, retention, deletion). 2) Confirm how reminders are delivered (local notification, email, third-party service) to avoid unintended data transmission. 3) If you prefer, limit the stored information to non-sensitive fields (e.g., policy type and renewal date) and avoid entering full policy numbers. 4) If you need stronger privacy guarantees, request a storage policy or choose a skill/agent integration that stores data locally or on a service you control. Overall the skill is internally coherent but lacks explicit data-handling details you should verify before use.

Like a lobster shell, security has layers — review code before you run it.

latestvk97ahnnt767dbwmskxwv4b3bfn8339g4

License

MIT-0
Free to use, modify, and redistribute. No attribution required.

Comments