Goals
v1.0.0Build a personal goal-setting system with milestones, tracking, and regular reviews.
⭐ 3· 1k·7 current·7 all-time
byIván@ivangdavila
MIT-0
Download zip
LicenseMIT-0 · Free to use, modify, and redistribute. No attribution required.
Security Scan
OpenClaw
Benign
high confidencePurpose & Capability
The name/description (personal goal-setting, milestones, reviews) match the SKILL.md: it specifies file-based goals, folder layout, review cadence, and tracking behavior. No unrelated binaries, env vars, or installs are requested.
Instruction Scope
The instructions explicitly direct creation/use of ~/goals/ and one-file-per-goal under that workspace; this is coherent for goal tracking. Note: the SKILL.md implies ongoing surfacing of progress ('surface when relevant') — which gives the agent discretion to notify or read these files. There are no instructions to access unrelated system paths or external endpoints.
Install Mechanism
No install spec and no code files — instruction-only skill. This minimizes disk-write/install risk.
Credentials
No environment variables, credentials, or config paths are requested. The data model (local files in ~/goals/) is proportional to the stated purpose.
Persistence & Privilege
always: false (normal). The skill implies periodic monitoring/reminders but does not request persistent system-wide privileges. Be aware autonomous invocation is enabled by default for skills (allowing the agent to act without explicit single-step prompts) — combined with file reads/writes this could lead to ongoing notifications unless you control invocation settings.
Assessment
This skill is coherent and appears safe from a permissions/credential perspective, but consider the following before installing: (1) it will create and read/write a ~/goals/ workspace in your home directory — if you keep sensitive information in home folders, review or move it first; (2) the instructions allow the agent discretion to “surface” progress/reminders — disable autonomous invocation or limit the agent's notification permissions if you don't want ongoing monitoring; (3) there are no declared integrations (calendar/journal), but if you later grant calendar or cloud access to enable integrations, those are separate permissions to evaluate; (4) back up or encrypt any goal files you consider sensitive. If you want stricter limits, request the skill be modified to require explicit user prompts before creating files or sending reminders.Like a lobster shell, security has layers — review code before you run it.
latestvk97eh49xaay42ce4yhj4mtzzdh80ze88
License
MIT-0
Free to use, modify, and redistribute. No attribution required.
Runtime requirements
🎯 Clawdis
OSLinux · macOS · Windows