Nm Memory Palace Digital Garden Cultivator

Cultivate digital gardens: manage notes, link structures, knowledge bases, and garden health

Security Scan

The skill's requests and instructions are consistent with a documentation/knowledge‑management helper — nothing obviously disproportionate or covert — but it's instruction-only and refers to local scripts and a git bypass that you should review before running.

Purpose & Capability

The name and description (manage digital gardens, links, maintenance, metrics) match the SKILL.md content and the included modules. The single declared config path (night-market.leyline:storage-templates) is plausible for a template-driven garden/storage integration and does not appear unrelated.

Instruction Scope

All runtime instructions are prose-only (no code shipped). It suggests running local commands (e.g., python scripts/garden_metrics.py) that are not provided with the skill — expected for an instruction-only plugin but important to note. The SKILL.md also recommends using SKIP=... git commit to bypass pre-commit hooks temporarily; that is a legitimate troubleshooting tip but also a way to bypass local safeguards, so review before using.

Install Mechanism

No install spec and no code files are present; nothing will be written or downloaded by the skill itself. This is the lowest-risk model (instruction-only).

Credentials

The skill declares no required environment variables or credentials. The only declared config dependency (night-market.leyline:storage-templates) is consistent with a template/storage integration for gardens and is proportionate to the described functionality.

Persistence & Privilege

always is false, user-invocable is true, and model invocation is allowed (platform defaults). The skill does not request persistent presence or system-wide configuration changes and does not ask to modify other skills' configs.

Assessment

This is an instruction-only skill that documents workflows and suggests running local tools and scripts that are not bundled. Before using: (1) inspect your repository for the referenced scripts (e.g., scripts/garden_metrics.py) or adapt the commands to your environment; (2) do not blindly run the suggested git bypass (SKIP=...) — only use it if you understand and accept the risk of skipping pre-commit checks; (3) review the night-market.leyline:storage-templates config path for any sensitive data before granting access; (4) run any unfamiliar commands in an isolated/sandbox environment or a disposable branch; and (5) if you want the agent to act on your files, verify exactly which paths it will read or modify.

Night Market Skill — ported from claude-night-market/memory-palace. For the full experience with agents, hooks, and commands, install the Claude Code plugin.

Table of Contents

• What It Is
• Quick Start
• Calculate Garden Metrics
• Output Formats
• When to Use
• Content Maturity Levels
• Core Workflow
• Garden Layout Template
• Maintenance Cadence
• Success Metrics
• Detailed Resources
• 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

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

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