Symptoms
v1.0.0Build a private symptom tracker for logging health patterns and preparing for doctor visits.
⭐ 2· 1k·1 current·1 all-time
byIván@ivangdavila
MIT-0
Download zip
LicenseMIT-0 · Free to use, modify, and redistribute. No attribution required.
Security Scan
OpenClaw
Benign
medium confidencePurpose & Capability
The name/description (private symptom tracker) match the SKILL.md: it asks the agent to gather symptom details, keep logs, prepare doctor summaries, and store data under ~/symptoms/. There are no unrelated environment variables, binaries, or installs required.
Instruction Scope
Instructions explicitly direct creating and writing files under ~/symptoms/ and taking detailed, sensitive health input. That is appropriate for a local tracker, but the skill also instructs proactive follow-ups (e.g., '2 hours later', 'next day'), which implies scheduling or repeated invocations. The SKILL.md promises 'All data stays local, never synced' but provides no technical enforcement (e.g., encryption or access controls).
Install Mechanism
No install spec or code files are provided (instruction-only), so nothing is downloaded or written by an installer. This keeps the risk surface small.
Credentials
No environment variables, credentials, or external config paths are requested. The only system access implied is writing to the user's home directory (~/symptoms/), which is proportional to the stated purpose.
Persistence & Privilege
always is false and model invocation is allowed (platform default). Because the skill asks for follow-ups over time, it will need the agent/platform to re-invoke it or schedule reminders; users should confirm whether they want autonomous follow-ups and ensure the platform's invocation behavior matches expectations.
Assessment
This skill appears coherent for a local symptom tracker, but it handles sensitive health information and will write files to ~/symptoms/. Before installing: (1) confirm your agent/platform will keep inputs private (the SKILL.md promises local-only storage but the platform may send prompts to remote models), (2) decide whether you want the agent to run autonomous follow-ups or only act when you invoke it, (3) consider storing the folder in an encrypted location or using disk encryption/backups to protect health data, and (4) check that the agent will ask permission before scheduling reminders. If you need stronger guarantees (no network exfiltration), verify platform privacy docs or avoid entering highly sensitive details.Like a lobster shell, security has layers — review code before you run it.
latestvk9771dn8hfafcn93n60sjj0jqs80zffr
License
MIT-0
Free to use, modify, and redistribute. No attribution required.
Runtime requirements
🩺 Clawdis
OSLinux · macOS · Windows