Plan My Day
v1.0.0Generate an energy-optimized, time-blocked daily plan
⭐ 26· 4.4k·24 current·24 all-time
by@itsflow
MIT-0
Download zip
LicenseMIT-0 · Free to use, modify, and redistribute. No attribution required.
Security Scan
OpenClaw
Benign
high confidencePurpose & Capability
Name and description (energy-optimized, time-blocked daily plans) match the SKILL.md instructions. The skill requests no binaries, env vars, or installs that would be unrelated to planning.
Instruction Scope
Instructions are high-level and ask the agent to 'check existing daily notes', 'review current priorities', and 'identify fixed commitments' — these are reasonable for a planner, but they implicitly allow the agent to access user data (notes, calendars, task lists). The SKILL.md does not specify exactly which data sources or how to access them, leaving broad discretion to the agent.
Install Mechanism
No install specification and no code files — instruction-only skills do not write files or fetch external code, which minimizes install risk.
Credentials
The skill declares no environment variables, credentials, or config paths. That is proportionate for a planner that does not embed direct API calls or integrations.
Persistence & Privilege
always is false and there is no request to persist or modify agent/system configuration. The skill does not request elevated or persistent presence.
Assessment
This is an instruction-only planner and appears coherent and low-risk by itself. However, it asks the agent to gather context (daily notes, priorities, fixed commitments), which implies the agent may read your calendars, notes, or task lists if given access. Before enabling or using it: (1) check what connectors/permissions your agent or platform will grant (calendar, drive, file system, task apps) and limit them to the minimum (prefer read-only, narrow scopes); (2) do an initial test with non-sensitive/example data to see what the agent reads; (3) if you do not want the agent to access personal files, remove or restrict those connectors; and (4) if you allow calendar access, prefer OAuth scopes that only expose free/busy or read-limited events rather than full write/delete rights.Like a lobster shell, security has layers — review code before you run it.
latestvk9732m87wkbbtn2ndjg7hk9e157zts9j
License
MIT-0
Free to use, modify, and redistribute. No attribution required.