← Back to Skills Marketplace
ivangdavila

Garden

by Iván · GitHub ↗ · v1.1.6
linuxdarwinwin32 ✓ Security Clean
680
Downloads
0
Stars
0
Active Installs
8
Versions
Install in OpenClaw
/install garden
Description
Track your entire garden with structured memory for plants, zones, tasks, harvests, and climate-aware planning that compounds over seasons.
README (SKILL.md)

Setup

If ~/garden/ doesn't exist or is empty, read setup.md and follow it. The user engaging with the skill implies interest — start helping them naturally.

When to Use

User needs help managing their garden: tracking plants, logging activities, planning rotations, diagnosing problems, or reviewing harvests. Agent maintains structured memory across seasons.

Architecture

Memory lives in ~/garden/. See memory-template.md for templates.

~/garden/
├── memory.md      # REQUIRED: context and status
├── climate.md     # Optional: zone, frost dates
├── plants/        # Optional: detailed plant files
├── zones/         # Optional: zone tracking
└── harvests.md    # Optional: yield records

Start minimal (just memory.md). Add others only if user wants detailed tracking.

Quick Reference

Topic File
Setup process setup.md
Memory template memory-template.md
Plant & zone templates tracking.md
Climate configuration climate-setup.md
Problem diagnosis diagnostics.md
Rotation planning planning.md

Core Rules

1. Plant Registry

Each plant gets a file in plants/ with: variety, planting date, zone, care schedule, health history. Load on request, not by default.

2. Zone Management

Each garden area gets a file in zones/ with: conditions, current plants, rotation history. Enforce 3-year minimum before repeating same plant family.

3. Activity Logging

Log actions in log/YYYY-MM.md with icons: 🌱 plant, 💧 water, 🐛 pest, 🍅 harvest, ✂️ prune, 🌡️ weather event.

4. Climate Awareness

User configures climate file with USDA zone and frost dates. Use for planting window calculations and seasonal alerts.

5. Harvest Tracking

Log yields in harvests file with date, plant, zone, quantity. Enables season-over-season comparison and variety evaluation.

6. Problem Diagnosis

When user reports issue: check plant health history, zone conditions, recent weather. See diagnostics.md for symptom reference.

7. Tiered Storage

  • Memory file = current focus, always loaded first
  • Plant/zone files = load on demand
  • Log archives = historical reference only

Common Queries

  • "What needs water?" - check care schedules vs last log
  • "What can I plant now?" - frost dates + rotation rules
  • "Why yellow leaves?" - diagnostic flow in diagnostics.md
  • "Show tomato history" - load plant file
  • "Last year's harvest?" - aggregate from harvests file

Garden Traps

  • Planting same family in same zone within 3 years - diseases compound
  • Ignoring microclimate differences between zones - timing varies
  • Not logging problems when they occur - diagnosis harder later
  • Overwatering based on schedule not soil - check before watering

Security & Privacy

Data that stays local:

  • All garden data stored in ~/garden/
  • No external APIs or network calls
  • No telemetry, analytics, or data collection

What this skill writes:

  • Files in ~/garden/ (memory.md, plants/, etc.)
  • Optionally: one line in user's workspace MEMORY.md (e.g., ~/MEMORY.md or equivalent) — only after asking and receiving explicit "yes"

This skill does NOT:

  • Infer or save preferences without user confirmation
  • Access weather APIs (climate is manually configured)
  • Control hardware or irrigation systems
  • Write outside ~/garden/ without asking first
  • Make any network requests

Related Skills

Install with clawhub install \x3Cslug> if user confirms:

  • plants — Plant care and identification
  • habits — Daily habit tracking
  • journal — General journaling
  • remind — Reminder scheduling
  • daily-planner — Day planning

Feedback

  • If useful: clawhub star garden
  • Stay updated: clawhub sync
Usage Guidance
This skill appears coherent and local-only, but before installing: 1) Confirm the agent will explicitly ask you before creating ~/garden/ or writing entries to your main workspace MEMORY.md (don't rely on implicit activation). 2) Back up any existing ~/garden/ or ~/MEMORY.md files you care about. 3) Be cautious if the agent later asks to upload photos or connect to cloud services — the current SKILL.md says no network calls, and you should refuse/verify any deviations. 4) If you install related skills (clawhub install ...), review their scopes and any credentials they request before linking them.
Capability Analysis
Type: OpenClaw Skill Name: garden Version: 1.1.6 The OpenClaw Garden skill is classified as benign. All analyzed files, including the critical `SKILL.md` and `setup.md` (which serve as prompt injection surfaces), consistently describe a local-only data management skill. The skill's primary functions involve creating directories (`mkdir -p ~/garden` in `memory-template.md`) and managing markdown files within the `~/garden/` directory. The `SKILL.md` explicitly states 'No external APIs or network calls', 'No telemetry, analytics, or data collection', and 'Does NOT... Make any network requests', which is consistent with the code and instructions. There is no evidence of data exfiltration, remote execution, persistence mechanisms, or obfuscation. The shell commands for directory and file creation are fixed and target the expected local skill directory, which is a necessary and non-malicious capability for a local data management skill.
Capability Assessment
Purpose & Capability
Name/description (garden tracking, planning, diagnostics) match the declared behavior: creating and using files under ~/garden/, templates for plants/zones/logs, and climate-aware planning. No unrelated binaries, credentials, or external services are requested.
Instruction Scope
Runtime instructions are limited to local file I/O within ~/garden/ and conversational flows for diagnosis and planning, which fit the purpose. One ambiguity: the SKILL.md states 'the user engaging with the skill implies interest — start helping them naturally' and the memory-template suggests creating ~/garden/memory.md on first use; however setup.md repeatedly instructs to ask before saving integration preferences. Recommend confirming that the agent explicitly asks the user before creating files or saving persistent integration flags.
Install Mechanism
Instruction-only skill with no install spec and no code files — nothing is downloaded or installed. This is the lowest-risk install model.
Credentials
No environment variables, credentials, or config paths are required. All written files are scoped to ~/garden/ (with an optional single-line write to ~/MEMORY.md only after explicit consent). This is proportionate to the described functionality.
Persistence & Privilege
The skill does not request always: true and does not modify other skills or system-wide settings. It proposes persistent local storage limited to a single directory and requests explicit consent before writing outside that directory.
How to Use
  1. Make sure OpenClaw is installed (local or Docker)
  2. Run the install command in chat: /install garden
  3. After installation, invoke the skill by name or use /garden
  4. Provide required inputs per the skill's parameter spec and get structured output
Version History
v1.1.6
- Simplified setup: using and creating `~/garden/` now starts naturally, no technical jargon. - Explicit consent required for saving to workspace memory — always ask first. - Clarified language throughout documentation for a friendlier, less technical experience. - Added `EXTRA_FILES.txt` for improved project organization.
v1.1.5
Clearer consent language, explicit save confirmations
v1.1.4
Garden 1.1.4 - Improved security and consent language for all writing actions - Now explicitly requires user confirmation before saving outside `~/garden/` - Clarified that no preferences are inferred or saved without user approval - Reinforced: no network calls, telemetry, or hardware control involved - Changelog entry updated for transparency on these changes
v1.1.3
- Simplified memory structure for easier setup and use. - Only creates minimal files (memory.md) by default; detailed tracking files are added only if requested. - No changes to privacy, setup process, or core garden tracking features.
v1.1.2
- Setup is now organic and non-blocking—users can start minimal, adding files as needed. - Workspace integration prompt moved to the beginning of setup for clarity. - Preferences can now be learned from user behavior, reducing explicit questions. - Core architecture and file requirements clarified for flexible, user-driven setup.
v1.1.1
- Setup now split into phases: configuration before adding any data. - Adds explicit user preference questions during setup. - Optional workspace integration—can register in the main memory file with user consent. - Introduces a setup minimum checklist for clearer onboarding. - Updated security: will not write outside `~/garden/` without explicit approval.
v1.1.0
Added setup system with setup.md for proactive onboarding, standardized memory.md format with status tracking
v1.0.1
Initial release
Metadata
Slug garden
Version 1.1.6
License
All-time Installs 0
Active Installs 0
Total Versions 8
Frequently Asked Questions

What is Garden?

Track your entire garden with structured memory for plants, zones, tasks, harvests, and climate-aware planning that compounds over seasons. It is an AI Agent Skill for Claude Code / OpenClaw, with 680 downloads so far.

How do I install Garden?

Run "/install garden" in the OpenClaw or Claude Code chat to install it in one step — no extra setup required.

Is Garden free?

Yes, Garden is completely free (open-source). You can download, install and use it at no cost.

Which platforms does Garden support?

Garden is cross-platform and runs anywhere OpenClaw / Claude Code is available (linux, darwin, win32).

Who created Garden?

It is built and maintained by Iván (@ivangdavila); the current version is v1.1.6.

💬 Comments