claude-code-plugin-ref…
Explain plugin, skill, command, agent, and hook mechanics used here. Use when authoring or debugging plugins. Do not use for ops; use night-market-operations.
Manages digital garden notes, link structures, and health metrics. Use when curating a knowledge base, pruning stale notes, or tracking content maturity.
$ npx -y skills add athola/claude-night-market --skill digital-garden-cultivator --agent claude-codeHow it fires
How this skill gets triggered: by you, by Claude, or both.
/digital-garden-cultivatorContext preview
The summary Claude sees to decide when to auto-load this skill.
Manages digital garden notes, link structures, and health metrics. Use when curating a knowledge base, pruning stale notes, or tracking content maturity.
name: digital-garden-cultivator description: Manages digital garden notes, link structures, and health metrics. Use when curating a knowledge base, pruning stale notes, or tracking content maturity. alwaysApply: false 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 model_hint: standard estimated_tokens: 500
Design, manage, and evolve digital gardens as living knowledge bases. Digital gardens are interconnected note collections that grow organically, emphasizing evolution over perfection.
A digital garden approach to knowledge management that:
python -m memory_palace.garden_metrics path/to/garden.json --format brief
**Verification:** Run `python --version` to verify Python environment.
structures - use memory-palace-architect
structures - use memory-palace-architect
| Level | Status | Description | |-------|--------|-------------| | **Seedling** | New/rough | Early ideas, incomplete thoughts | | **Growing** | Developing | Being actively refined | | **Evergreen** | Mature | Stable, well-developed content |
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:
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.
| 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 |
**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
`garden.json` and outputs link density, bidirectional coverage, freshness, and maturity ratio
surfaced for the user's review
`seedling`, `growing`, or `evergreen`
or reconnected during the maintenance pass
with the path that was searched rather than silently completing
A plugin marketplace for Claude Code. Install only the plugins you need to run git workflows, code review, spec-driven development, and autonomous agents from inside your Claude Code session.
Explain plugin, skill, command, agent, and hook mechanics used here. Use when authoring or debugging plugins. Do not use for ops; use night-market-operations.
States load-bearing decisions, invariants, and weak points. Use when judging a design change. Do not use for gating; use night-market-change-control.
Rebuild the dev environment: uv, Python tiers, pins, traps. Use when onboarding or toolchain breaks. Do not use for daily commands; use night-market-operations.
Classify, gate, and review changes. Use when landing a PR, releasing, or amending rules. Do not use for failure triage; use night-market-debugging-playbook.
Search and record project memory (Discussions, journal, ADRs). Use before re-investigating anything. Do not use for settled battles; see failure-archaeology.
Bind loop 'done' to unfakeable gates. Use to harden egregore/herald loops or promote completion_integrity. Not for QA gates; use night-market-validation-and-qa.