Pregnancy Tracker

ReviewAudited by ClawScan on May 10, 2026.

Overview

This instruction-only pregnancy tracker is purpose-aligned, but it asks for sensitive health information while making conflicting claims about local-only privacy and cross-device syncing.

Use caution before entering pregnancy symptoms, appointment details, or other health information. The skill has no code or install-time risk in the provided artifacts, but its privacy claims are inconsistent; confirm whether data is local-only, synced, retained, or deletable before relying on it.

Findings (2)

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.

What this means

Sensitive pregnancy, symptom, appointment, and personal health details could be retained or reused in ways the user does not fully understand.

Why it was flagged

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.

Skill content
Track weekly development milestones, log how you're feeling, monitor appointments... Everything syncs across devices and stays organized in one place.
Recommendation

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.

What this means

A user may trust the skill with sensitive reproductive-health information based on a privacy claim that is internally inconsistent.

Why it was flagged

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.

Skill content
Everything syncs across devices... Your data follows you everywhere... All data stays local on your machine... never leaves your device.
Recommendation

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.