Skip to content

m4bwav/evergreen

v0.16.0MIT

Self-maintaining, self-proving skills and knowledge: adaptive web research on four tracks (the subject, the skills, plugins, MCP servers and knowledge graphs built for it, how others use agents on the same goal, and how they test that the job was done), never-teach-twice learnings capture, plugin-owned codemaps, a portable AI-preferences profile, and an eval suite per skill (trigger, action, outcome, decoys, baseline) that passes on evidence outside the transcript, with a bounded tuning loop that researches the subject's own testing when a skill fails, and a worth check that warns while a skill is made or changed when it reads as mostly cost and decides KEEP, TRIM or CUT from the with-versus-without A/B. Skills say what they need (tools, packages, keys, servers, models, accounts, and access to databases, telemetry, cloud roles and APIs) and what for: on a new machine or agent harness, or when something is missing, the agent explains it, installs what is safe after saying so, hands the user exact steps for the rest, drafts least-privilege access requests without ever granting itself access, and records the recipe that worked and how each attempt went for that environment. An end-of-session wrap-up harvests the session transcript and keeps only what will save time or tokens or raise quality, routed to its narrowest home. Converts existing skills and makes new ones evergreen by default. Lives in one public git repository (https://github.com/m4bwav/evergreen-protocol): every install is a clone that pulls to stay current and, only if its owner said yes at install, sends improvements to the protocol, skills and scripts back as pull requests it opens itself (log entries go straight to master from a maintainer's clone), with email as the fallback route.

evergreen-merge

Land what other evergreen clones published into the trunk repository: review and merge the plugin's update pull requests on the host (gh), resolve the rare conflict with the delta-edit rule (the logs merge by union; a duplicate entry ID is renumbered), then pull every clone and reinstall where skills or scripts changed. Also folds an email update bundle (a folder, a changes.patch, or the update email saved as text) into the trunk for the fallback route. Use on 'merge the update', 'merge the evergreen PR', 'review the pull requests from the plugin', 'the rebase conflicted', 'apply the patch from work', 'pull in the changes from the email', 'sync the trunk', or when a pull request or update email from another machine has arrived.

Read SKILL.md at the source

Pinned to revision 946faeac0810, so it is the text this page describes rather than whatever the author pushed since.

Files

Every link opens the file at its source, pinned to the revision this page describes.