Pregnancy Care

ReviewAudited by ClawScan on May 10, 2026.

Overview

The skill’s pregnancy tracking purpose is coherent, but it persistently stores sensitive pregnancy and birth information, including in Core Memory, without clear consent, retention, or deletion controls.

Before installing, consider whether you are comfortable with pregnancy-related details being saved in a local workspace file and possibly in the agent’s long-term memory. Use it only if you can review or delete stored data, and avoid entering unnecessary medical details.

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

A user who says the baby was born or asks to stop tracking may have that sensitive event remembered across future interactions.

Why it was flagged

The skill directs the agent to store a birth or stop-tracking event in persistent agent memory. That is sensitive personal and health-related information, and the instruction does not require explicit user consent, limit future reuse, or describe deletion.

Skill content
Call `pregnancy_helper.py archive [user_id]`. ... Create a Core Memory of the event.
Recommendation

Require explicit opt-in before creating Core Memory, store only the minimum information needed, and provide a clear way to view and delete the memory.

What this means

Sensitive pregnancy-related details may remain on disk and be available to future agent sessions or anyone with access to the workspace files.

Why it was flagged

The helper stores pregnancy tracking data persistently in a local JSON file. The same script saves LMP, role, relationship, completed tasks, custom milestones, and archive status, but the artifacts do not define retention, encryption, access boundaries, or deletion.

Skill content
DATA_DIR = os.path.join(WORKSPACE_ROOT, "data", "pregnancy-care") ... DATA_FILE = os.path.join(DATA_DIR, 'user_data.json')
Recommendation

Clearly disclose the storage path and retained fields, ask before saving sensitive data, support deletion instead of archive-only retention, and avoid storing unnecessary health details.