garden

Scan expired documents under .local.claude and archive superseded files.

8|2|Updated May 3, 2026
One-click install
npx skills add https://github.com/ejoongseok/claude-settings --skill garden-ejoongseok
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: garden
Source: https://github.com/ejoongseok/claude-settings/tree/main/claude-code/skills/garden
Command: npx skills add https://github.com/ejoongseok/claude-settings --skill garden-ejoongseok

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

It prevents your growing local knowledge garden from becoming stale by automatically identifying expired documents, harvesting missed insights into durable sources, and archiving what’s no longer needed.

Core Features & Use Cases

  • Expiration scanning & categorization: Detects expired files under .local.claude/ (excluding archive/) using path-based categories and optional frontmatter retention.
  • Harvest check for missed knowledge: Compares expired content (e.g., daily, meetings, learn, reports, cs, memo) against durable “sink” documents (e.g., .local.claude/biz-rules.md, modules/*.md, customers/*.md, team.md, people/*.md) and produces a report of what must be reflected.
  • Controlled archive + INDEX refresh: After approval, applies reflections, moves expired items into .local.claude/archive/YYYY-MM/..., updates frontmatter, and refreshes .local.claude/INDEX.md (kept within a 60-line limit).

Quick Start

Run the garden skill to generate a report for expiring documents under .local.claude/, review the harvest and archive plan, then approve execution to apply updates and archive the expired files.

Frequently Asked Questions about garden

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I automate document lifecycle cleanup and retention for Claude context?

Automate document lifecycle cleanup by scanning `.local.claude` paths for expired items using mtime and line counts. It archives superseded files after generating an approval report, ensuring your Claude context management stays current without manual deletion.

What is knowledge harvesting from expired documents and how does it work?

Knowledge harvesting identifies missed insights in expired files by comparing them against durable sources like biz-rules and modules. It generates a report of reflections needed, updating durable documents before moving expired items into an archive directory.

How do I archive stale `.local.claude` files while preserving frontmatter retention metadata?

Archive stale `.local.claude` files by running an expiration scan that prioritizes frontmatter retention when present. After approval, it moves files to `archive/YYYY-MM/` with `archived/harvested_to` metadata and safely refreshes `INDEX.md`.

Does Claude context management require a root SKILL.md YAML configuration for archiving?

Yes, Claude context management archiving requires a root `SKILL.md` YAML name and description. This configuration drives the category-based scanning logic for daily, meetings, learn, reports, cs, memo, and docs-parsed workflows.

What are the limitations of automated index updating for archived documents?

Automated index updating has a strict 60-line limit for `INDEX.md` and requires user approval before applying any harvest or archive actions. It excludes files already within the `archive/` directory from expiration scanning.