Med Tracker

Medication tracker for logging prescriptions, dosages, schedules, and reminders. Use when users want to track what medications they take, set reminders, or c...

Security Scan

The skill's description (logging meds, setting reminders, checking interactions) is plausible, but the instructions assume storage and reminder/delivery capabilities and access to interaction data without declaring how those will be performed or what integrations/permissions are needed.

Purpose & Capability

The skill claims to log medications, set reminders, and flag interactions but is instruction-only and declares no storage, scheduler, calendar, notification, or external data-source integrations. It's unclear how reminders will be delivered or where medication lists are persisted, which is disproportionate to the minimal runtime footprint declared.

Instruction Scope

SKILL.md tells the agent to record medications, set reminder schedules, and answer interaction questions, but it does not specify where to store logs, how reminders are triggered/delivered, or which drug-interaction data source to use. That vagueness grants the agent broad discretion and could lead to unexpected behavior (e.g., using agent memory only, or attempting to call external services).

Install Mechanism

No install spec and no code files — lowest-risk deployment surface. Nothing will be written to disk by the skill itself.

Credentials

The skill requests no environment variables, credentials, or config paths, which is consistent with an instruction-only skill. However, given its functionality (reminders, persistence, drug databases), real implementations usually require additional integrations that are not declared.

Persistence & Privilege

always:false and normal invocation settings. The skill does not request persistent presence or elevated privileges. It also does not claim to modify other skills or system-wide settings.

What to consider before installing

This skill's scope (logging medications, delivering reminders, and checking drug interactions) implies storage, scheduling, and access to interaction data — but none of those capabilities or integrations are declared. Before installing, ask the publisher: (1) Where and how will medication data be stored and for how long? (2) How are reminders delivered (in-app message, calendar event, email, push notification) and what permissions/integrations are required? (3) What medical/reference sources are used for drug interaction information? (4) How is sensitive health data protected and who can access it? If you rely on it for safety-critical reminders or medical decisions, avoid using it until these details (and privacy/security guarantees) are clarified. If you only want conversational, transient logging within a single chat session, verify that no persistent storage will be used for protected health information.

Help users manage their medications by logging drug names, dosages, frequency, and timing. Provide reminders and flag potential concerns about missed doses or interactions.

When to Use

• User wants to log or track medications they're taking
• User asks about medication schedule or dosage
• User wants reminders to take medication
• User asks about drug interactions
• User wants to review their current medication list

How to Use

1. Record medication name, dosage, frequency (daily/twice daily/as needed)
2. Note start date, end date (if applicable), and prescribing condition
3. Set reminder schedule and preferred reminder format
4. Flag if user reports missing doses — advise to consult doctor before doubling up
5. For interaction questions: provide general info and always recommend pharmacist/doctor verification

Examples

• "Add metformin 500mg twice daily to my medication list"
• "Remind me to take my blood pressure pill every morning at 8am"
• "Can I take ibuprofen with my current medications?"