Skills Reference

forage handles session-time operations. harvest handles maintenance. They are installed separately and used in different contexts.

forage

Use during active Claude Code sessions when non-obvious knowledge surfaces. forage is lightweight by design — it queues submissions without touching the live garden.

Operation	When to use	What it does
CAPTURE	A specific gotcha, technique, or undocumented behaviour surfaces	Records a single entry as a submission file, queued for harvest
SWEEP	At the end of a session	Systematically scans the full session for anything worth capturing, proposes entries for review
SEARCH	Looking for prior knowledge before solving a problem	Retrieves matching entries from the live garden using a three-tier search strategy
REVISE	An existing entry needs enrichment or correction	Updates a previously captured entry with new information

        # Invoke forage in any Claude Code session, then tell Claude what you want

        > /forage

        # Examples of natural language directions after invoking:

        # "CAPTURE this gotcha about Maven test skipping"

        # "SWEEP the session for anything worth keeping"

        # "SEARCH for entries about git rebase conflicts"

        # "REVISE GE-0042 with the workaround we just found"

harvest

Run in a dedicated maintenance session — not during active project work. harvest reads many files and is intentionally thorough.

Operation	When to use	What it does
MERGE	Submissions are pending in `submissions/`	Assigns GE-IDs, validates, and integrates queued submissions into the live garden
DEDUPE	After bulk additions or periodically	Finds duplicate or overlapping entries using three-level Jaccard similarity, resolves with review

        # Run harvest in a dedicated Claude Code session

        > /harvest

        # Then tell Claude: "MERGE" or "DEDUPE"

Full reference: The complete skill specifications — trigger conditions, operation details, and submission format — are in the forage SKILL.md and harvest SKILL.md on GitHub.