Pregnancy Tracker
PassAudited by VirusTotal on May 12, 2026.
Overview
Type: OpenClaw Skill Name: pregnancy-tracker Version: 1.0.0 The skill bundle, comprising `_meta.json` and `SKILL.md`, is clearly benign. The `SKILL.md` file provides descriptive information about a 'Pregnancy Tracker' skill, outlining its features and usage for the user. Crucially, it explicitly states, 'All data stays local on your machine - Your pregnancy journey is private and never leaves your device,' directly contradicting any potential for data exfiltration. There are no instructions for the AI agent that suggest prompt injection, malicious execution, persistence, or any other harmful behavior; all instructions are user-facing and align with the stated purpose.
Findings (0)
Artifact-based informational review of SKILL.md, metadata, install specs, static scan signals, and capability signals. ClawScan does not execute the skill or run runtime probes.
Sensitive pregnancy, symptom, appointment, and personal health details could be retained or reused in ways the user does not fully understand.
The skill invites users to create a persistent pregnancy and health diary and says it syncs across devices, but the artifact provides no clear storage, retention, deletion, or data-boundary details.
Track weekly development milestones, log how you're feeling, monitor appointments... Everything syncs across devices and stays organized in one place.
Only enter information you are comfortable storing in Clawd, and the skill should clearly document where data is stored, whether it syncs, how long it is retained, and how to delete it.
A user may trust the skill with sensitive reproductive-health information based on a privacy claim that is internally inconsistent.
The privacy statements conflict: cross-device syncing normally implies data leaves a single device, while the skill simultaneously claims all data stays local and never leaves the device.
Everything syncs across devices... Your data follows you everywhere... All data stays local on your machine... never leaves your device.
Clarify the actual data flow before use: either document the sync service and privacy controls, or remove the sync claim if data is truly local-only.