Meals
v1.0.0Build a personal meal planning system with weekly plans, shopping lists, and dietary tracking.
⭐ 2· 991·0 current·0 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
Name and description (personal meal planning, shopping lists, dietary tracking) match the instructions. The only requested system interaction is creating/using a ~/meals/ workspace, which is appropriate for a file-based planner.
Instruction Scope
SKILL.md stays within meal-planning scope: it instructs asking the user questions, building/reading/writing meal and plan files under ~/meals/, generating shopping lists, and tracking preferences. There are no instructions to read unrelated system files or environment variables, nor to send data to external endpoints. It does mention optional integrations (calendar, exports) but does not include automatic credential access or implementation details.
Install Mechanism
No install spec and no code files — instruction-only skill. This is the lowest-risk install profile; nothing will be written to disk by an installer beyond what the agent is instructed to create at runtime (~/meals/).
Credentials
The skill currently requests no environment variables or credentials, which is proportionate. It references potential integrations (calendar, exporting lists, budget tracking) that would require credentials if implemented; those should be declared explicitly before enabling such integrations.
Persistence & Privilege
always is false and the skill is user-invocable — normal. The skill does instruct creating a persistent workspace directory in the user's home (~/meals/). This is expected for the use case but users should be aware it will create and store personal data on disk.
Assessment
This skill appears coherent and limited to local meal-planning tasks. Before installing: 1) understand it will create and maintain files in ~/meals/ (plans, meals, shopping lists, preferences); back up or review that directory if you care about where data is stored. 2) If you later enable calendar or export integrations, expect the skill to require tokens/credentials — only provide those if you trust the integration and the skill declares them. 3) Review any future versions that add code or install steps (this current version is instruction-only). If you want stricter isolation, run it in a limited account or container where writing to your home is acceptable.Like a lobster shell, security has layers — review code before you run it.
latestvk975bwvhrgkpwy133j4t02d79d80yd72
License
MIT-0
Free to use, modify, and redistribute. No attribution required.
Runtime requirements
🍽️ Clawdis
OSLinux · macOS · Windows