Garden Layout Planner
v1.0.0Plan and design garden layouts with companion planting, spacing, sun requirements, crop rotation, and exportable layout management for small gardens and farms.
⭐ 0· 998·1 current·1 all-time
MIT-0
Download zip
LicenseMIT-0 · Free to use, modify, and redistribute. No attribution required.
Security Scan
OpenClaw
Benign
medium confidencePurpose & Capability
The skill name, SKILL.md usage examples, and the included Python script all implement garden bed/plant management, companion suggestions, spacing, layout display, and export. There are no requests for unrelated cloud credentials, external binaries, or surprising capabilities.
Instruction Scope
SKILL.md instructs running the included CLI and exporting layouts to files. It claims "file exports restricted to safe directories," but the visible parts of scripts/garden_layout.py store the DB at ~/.openclaw/workspace/garden_layout_db.json and perform file exports — I did not see an explicit enforcement of a "safe directories" policy in the visible code. The instructions do not direct the agent to read unrelated system files or network endpoints.
Install Mechanism
There is no install spec; this is instruction + script only. No downloads, package installs, or archive extraction are present in the manifest, minimizing supply-chain risk.
Credentials
The skill declares no required environment variables, no credentials, and no config paths beyond the script's own DB file under the user's home. That matches the apparent needs of a small local CLI tool.
Persistence & Privilege
The skill is not marked always:true and does not request elevated privileges. It writes its own DB under ~/.openclaw/workspace, which is consistent with a local tool storing user data; it does not modify other skills' configs or request system-wide changes.
Assessment
This skill appears to be a simple local CLI for planning gardens: it stores data at ~/.openclaw/workspace/garden_layout_db.json and offers an export command. Before installing or running it, review the export implementation (to confirm that "safe directories" are actually enforced) and verify you are comfortable with the script writing/reading a file in your home directory. If you will run it in an automated agent context, remember the agent can invoke the script and that the DB file will be created/modified under your home. There are no network calls or credential requests visible, which reduces risk; if you need stronger isolation, run the script in a sandbox or review the rest of the file to confirm there are no hidden network or shell-exec operations.Like a lobster shell, security has layers — review code before you run it.
companionvk97ck6wtm76w812g550x5jbs8180s1krdesignvk97ck6wtm76w812g550x5jbs8180s1krfarmvk97ck6wtm76w812g550x5jbs8180s1krgardeningvk97ck6wtm76w812g550x5jbs8180s1krlatestvk97ck6wtm76w812g550x5jbs8180s1krlayoutvk97ck6wtm76w812g550x5jbs8180s1krplanningvk97ck6wtm76w812g550x5jbs8180s1krplantsvk97ck6wtm76w812g550x5jbs8180s1kr
License
MIT-0
Free to use, modify, and redistribute. No attribution required.