Renewal Alert

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

Security Scan

The skill's declared purpose (tracking insurance renewals and sending reminders) matches its instructions, and it requests no installs, binaries, or credentials — nothing appears disproportionate or covert.

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.

Track all insurance policies and their renewal dates. Alert users before policies expire so they never face a coverage gap due to a forgotten renewal.

When to Use

• User wants to register an insurance policy renewal date
• User asks when their insurance expires
• User wants a reminder before their policy renews or expires
• User wants to review all upcoming insurance renewals
• User got a renewal notice and wants help deciding whether to renew

How to Use

1. Record policy details: type, insurer, policy number, renewal date, premium amount
2. Set reminder schedule (e.g., 60 days, 30 days, 7 days before renewal)
3. At renewal time: remind user and prompt them to review coverage before auto-renewing
4. Suggest reviewing coverage needs annually at renewal
5. Flag if premium has increased significantly from previous year

Examples

• "My car insurance renews on July 15th, remind me 30 days before"
• "When does my health insurance expire?"
• "List all my insurance renewal dates coming up in the next 90 days"