Pregnancy Tracker
v1.0.0Track pregnancy journey with weekly updates, symptom logging, and milestone countdowns
⭐ 1· 1.8k·2 current·2 all-time
MIT-0
Download zip
LicenseMIT-0 · Free to use, modify, and redistribute. No attribution required.
Security Scan
OpenClaw
Suspicious
medium confidencePurpose & Capability
The skill promises week-by-week tracking, cross-device sync, reminders, and appointment management, but the package is instruction-only with no code, no storage mechanism, no cloud integration, and no required credentials. Claims like "sync across devices" and "All data stays local" are contradictory or unsupported by any implementation details.
Instruction Scope
SKILL.md describes what the agent should do (log symptoms, send reminders, share summaries) but gives no concrete runtime instructions, file paths, or APIs. That vagueness grants the agent broad discretion about where/how to store or transmit sensitive health data — the instructions neither specify local-only storage mechanics nor explicitly forbid network transmission.
Install Mechanism
There is no install spec and no code files. This minimizes direct supply-chain risk because nothing will be downloaded or written during install. However, it also means promised features would need to be implemented by the agent or host environment.
Credentials
The skill requests no environment variables, credentials, or config paths — which is proportionate. But because it handles sensitive personal health data, the absence of declared storage or sharing mechanisms is notable: you should confirm how and where the data will actually be stored, backed up, or shared.
Persistence & Privilege
always is false (good). The skill is user-invocable and can be invoked autonomously by the agent (platform default). That autonomy combined with the skill's vague storage/sharing semantics could allow the agent to persist or transmit data unless platform policies or the user explicitly constrain it.
What to consider before installing
This skill reads like a feature spec, not an implemented component. Before installing or using it, ask the developer or publisher: (1) Where exactly is journal data stored? (full path, file format, and whether it is encrypted at rest). (2) What mechanism provides "sync across devices" and "reminders" (local OS notifications, cloud service, third‑party API)? If a cloud service is used, which one and what credentials are required? (3) How does sharing (partner summaries) work and can you opt out? (4) Request an implementation or install spec (code or clear platform integration) and a privacy/security statement. If you need guaranteed local-only behavior, do not use the skill until it documents local storage and proves it does not transmit data off your device. Treat any handling of health data as sensitive.Like a lobster shell, security has layers — review code before you run it.
latestvk974kpy5td9b7nct9xd79cwjt97zx6d8
License
MIT-0
Free to use, modify, and redistribute. No attribution required.