Feelings

v1.0.0

Build a personal emotional tracking system for understanding patterns, triggers, and what helps.

2· 1k·2 current·2 all-time
byIván@ivangdavila
MIT-0
Download zip
LicenseMIT-0 · Free to use, modify, and redistribute. No attribution required.
Security Scan
VirusTotalVirusTotal
Benign
View report →
OpenClawOpenClaw
Benign
high confidence
Purpose & Capability
Name/description (emotional tracking) match the instructions: create a ~/feelings/ workspace, log entries, surface patterns, and suggest interventions. There are no unrelated env vars, binaries, or install steps requested.
Instruction Scope
SKILL.md stays within the purpose: it prescribes file layout, what to capture (emotion, intensity, context), and proactive check-ins. The one open-ended area is 'Proactively check in during difficult periods' — this gives the agent discretion to initiate interactions (timing/triggers are not precisely defined). The instructions do not direct reading of unrelated system files or sending data to external endpoints.
Install Mechanism
No install spec and no code files — instruction-only. This is low-risk because nothing is written to disk by an installer and no external packages are fetched.
Credentials
The skill requests no environment variables, credentials, or config paths. The data it uses and creates is local and directly relevant to personal emotional tracking.
Persistence & Privilege
always:false (default) and the skill is user-invocable. Model invocation is allowed by default, so the skill could autonomously perform proactive check-ins if the platform permits — this is expected but worth confirming with the user: how often and under what triggers should the agent initiate check-ins?
Assessment
This skill appears coherent and uses only local files, but it will store sensitive personal/emotional data in ~/feelings/. Before installing or using it, consider: (1) whether you want that data written in plaintext — if not, avoid or use encryption (e.g., store in an encrypted folder or use OS-level FileVault/BitLocker); (2) check and tighten file permissions so others on the device can't read the logs; (3) confirm the agent's proactive check-in behavior (how often, what triggers) so it doesn't prompt you at undesirable times; (4) avoid enabling cloud sync for the ~/feelings/ folder unless you trust and encrypt the data; (5) if you plan to share insights externally, verify the skill (or agent) asks for explicit permission before transmitting any entries; and (6) if you want stronger privacy guarantees, prefer a manual, user-invoked mode rather than autonomous check-ins. Overall the skill is consistent with its purpose but handle the sensitive local data with care.

Like a lobster shell, security has layers — review code before you run it.

latestvk970jye56mb26qyse43zmqvda580zgy6

License

MIT-0
Free to use, modify, and redistribute. No attribution required.

Runtime requirements

💭 Clawdis
OSLinux · macOS · Windows

Comments