home / skills / athola / claude-night-market / digital-garden-cultivator

This skill helps you design, grow, and maintain digital gardens by linking notes, planning structure, and tracking content maturity.

npx playbooks add skill athola/claude-night-market --skill digital-garden-cultivator

Review the files below or copy the command above to add this skill to your agents.

Files (4)
SKILL.md
4.7 KB
---
name: digital-garden-cultivator
description: 'Consult this skill when cultivating and maintaining digital gardens.
  Use when managing note collections, creating link structures, maintaining knowledge
  bases, tending garden health and growth. Do not use when creating memory palace
  structures - use memory-palace-architect. DO NOT use when: evaluating new knowledge
  - use knowledge-intake.'
category: cultivation
tags:
- digital-garden
- knowledge-base
- linking
- curation
- documentation
dependencies:
- leyline:storage-templates
scripts:
- garden_metrics.py
usage_patterns:
- garden-management
- knowledge-curation
- content-lifecycle
complexity: intermediate
estimated_tokens: 500
---
## Table of Contents

- [What It Is](#what-it-is)
- [Quick Start](#quick-start)
- [Calculate Garden Metrics](#calculate-garden-metrics)
- [Output Formats](#output-formats)
- [When to Use](#when-to-use)
- [Content Maturity Levels](#content-maturity-levels)
- [Core Workflow](#core-workflow)
- [Garden Layout Template](#garden-layout-template)
- [Maintenance Cadence](#maintenance-cadence)
- [Success Metrics](#success-metrics)
- [Detailed Resources](#detailed-resources)
- [Integration](#integration)


# Digital Garden Cultivator

Design, manage, and evolve digital gardens as living knowledge bases. Digital gardens are interconnected note collections that grow organically, emphasizing evolution over perfection.

## What It Is

A digital garden approach to knowledge management that:
- Builds dynamic knowledge bases that evolve over time
- Connects notes through bidirectional links
- Incubates ideas before formalizing as documentation
- Creates discovery paths for information navigation
- Tracks content maturity and maintenance needs

## Quick Start

### Calculate Garden Metrics
```bash
python scripts/garden_metrics.py path/to/garden.json --format brief
```
**Verification:** Run `python --version` to verify Python environment.

### Output Formats
- `json` - Full metrics as JSON
- `brief` - One-line summary
- `prometheus` - Prometheus exposition format

## When To Use

- Building dynamic knowledge bases that evolve over time
- Connecting notes, skills, and palaces through bidirectional links
- Incubating ideas before formalizing as documentation
- Creating discovery paths for navigating information
- Managing content lifecycle (seedling → growing → evergreen)

## When NOT To Use

- Creating memory palace
  structures - use memory-palace-architect
- Evaluating new knowledge
  - use knowledge-intake
- Creating memory palace
  structures - use memory-palace-architect
- Evaluating new knowledge
  - use knowledge-intake

## Content Maturity Levels

| Level | Status | Description |
|-------|--------|-------------|
| **Seedling** | New/rough | Early ideas, incomplete thoughts |
| **Growing** | Developing | Being actively refined |
| **Evergreen** | Mature | Stable, well-developed content |

## Core Workflow

1. **Collect Sources** - Gather notes, bookmarks, ideas
2. **Plan Structure** - Define garden organization
3. **Create Links** - Build bidirectional connections
4. **Schedule Maintenance** - Establish tending cadence
5. **Document Outputs** - Convert mature ideas to formal docs

## Garden Layout Template

```yaml
garden:
  sections: ["research", "patterns", "experiments"]
  plots:
    - name: "My First Note"
      purpose: "reference"  # reference | evergreen | lab
      maturity: "seedling"  # seedling | growing | evergreen
      inbound_links: []
      outbound_links: []
      last_tended: "2025-11-24T10:00:00Z"
```
**Verification:** Run the command with `--help` flag to verify availability.

## Maintenance Cadence

| Action | Frequency | Purpose |
|--------|-----------|---------|
| Quick prune | Every 2 days | Remove dead links, fix typos |
| Stale review | After 7 days inactive | Assess content freshness |
| Archive | After 30 days inactive | Move to archive or delete |

## Success Metrics

- **Link density** - Average links per piece of content
- **Bidirectional coverage** - % of links that are reciprocal
- **Freshness** - Time since last update per area
- **Maturity ratio** - Evergreen content / total content

## Detailed Resources

- **Linking Patterns**: See `modules/linking-patterns.md`
- **Maintenance Guide**: See `modules/maintenance.md`
- **Metrics Integration**: See `modules/maintenance.md`

## Integration

- `memory-palace-architect` - Host garden within palace structure
- `knowledge-locator` - Search garden content
- `session-palace-builder` - Seed garden from session insights
## Troubleshooting

### Common Issues

**Pre-commit hooks failing**
Run `SKIP=... git commit` to bypass temporarily, then fix issues

**Merge conflicts**
Use `git merge --abort` to reset, then resolve conflicts carefully

**Commit rejected**
Check hook output and fix reported issues before committing again

Overview

This skill helps design, manage, and evolve digital gardens as living knowledge bases. It focuses on organizing note collections, creating bidirectional link structures, and tracking content maturity so your garden grows organically. Use it to establish maintenance cadence and measure garden health over time.

How this skill works

The skill inspects your note collection, computes garden metrics (link density, bidirectional coverage, freshness, maturity ratio), and outputs summaries or machine-readable formats. It guides layout planning, link creation, and maintenance scheduling, and produces templates and cadence recommendations so you can tend the garden systematically.

When to use it

  • Building or reorganizing an evolving knowledge base
  • Connecting notes with bidirectional links and discovery paths
  • Incubating ideas before formalizing documentation
  • Scheduling maintenance and tracking content freshness
  • Measuring garden health and content maturity

Best practices

  • Define clear sections (research, patterns, experiments) and simple plot purposes (reference, evergreen, lab)
  • Track maturity levels (seedling → growing → evergreen) and use them to prioritize tending
  • Maintain a regular cadence: quick prunes every 2 days, stale reviews after 7 days, archive after 30 days
  • Measure link density and bidirectional coverage to find isolated notes and improve discoverability
  • Keep small, actionable maintenance tasks in each session to avoid large refactors

Example use cases

  • Audit a notes directory to compute link density and identify low-coverage pages
  • Seed a new garden layout using the provided YAML template and populate initial plots
  • Schedule and track maintenance tasks to improve freshness and move items from seedling to evergreen
  • Export garden metrics in JSON or Prometheus formats for dashboards and integrations
  • Connect with discovery tools or session outputs to import ideas and create bidirectional links

FAQ

What output formats are available?

Metrics can be exported as full JSON, a brief one-line summary, or Prometheus exposition format for monitoring.

How are maturity levels defined?

Seedling is new/rough content, Growing is actively refined, and Evergreen is stable, well-developed content.