evergreen

Plugin evergreen in m4bwav/evergreen-protocol. Commands read from the repo's manifest — 4 days ago.

Skills (16)

• evergreen-audit

  Status overview of the whole evergreen catalog (skills, docs, codemaps, profiles) in one table: tier, last check, due date, staleness, drift, test status (untested, overdue, failing), link integrity and budget problems, then hands what is due to evergreen-refresh. Use on catalog-wide questions such

• evergreen-convert

  Convert an existing skill, plugin, knowledge document, or repo doc into a self-maintaining evergreen unit: adds RESEARCH.md, CHANGELOG.md, LEARNINGS.md, evergreen.json, for skills a TESTS.md and evals suite, a Maintenance section in the main file, and either a link to the plugin's protocol or a stan

• evergreen-diff

  Show what the evergreen plugin changed about itself since it was installed or last reported: an update bundle with a human digest (new changelog, research and learning entries, state changes, file list) and a unified diff against the install baseline. Use on 'what changed in evergreen', 'generate th

• evergreen-learn

  Capture a lesson so no one has to teach the agent the same thing twice: user corrections ('no, actually...', 'I told you before', 'remember that', 'stop doing X'), the same error or failed approach happening a second time, a discovered workaround, an environment fact (path, port, tool quirk, what wo

• evergreen-map

  Build or update the plugin's own codemap of a repository or system while exploring it, so the exploration is never repeated. Use when the user asks how an unfamiliar or recurring codebase, service, or system is put together ('walk me through this repo', 'what talks to what', 'where is Y configured',

• 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 skill

• evergreen-new

  Add the self-maintaining layer to a skill being created (research refresh on an adaptive schedule, learnings capture, changelog, an eval suite that proves it triggers and acts, double-linked companion files) and pick its tier. Use whenever the user asks to create, write, draft, or scaffold a skill,

• evergreen-notify

  The email fallback for publishing the evergreen plugin's self-update when a machine cannot reach the trunk git repository (update.transport email): mail the digest and diff to the owner (notify.to in evergreen.config.json) through the script's ladder (classic Outlook COM, Microsoft Graph, Gmail SMTP

• evergreen-pack

  Package the evergreen plugin into a single archive to email, back up, or install elsewhere: a versioned evergreen zip (folder inside, opens in 7-Zip or Explorer), an email-safe variant that Gmail accepts, and evergreen.plugin (flat, for Cowork's Save plugin button). Use on 'zip up evergreen', 'packa

• evergreen-publish

  Publish the evergreen plugin's self-changes (refreshes, learnings, environment facts, test runs) to the trunk git repository: a maintainer's clone commits and pushes straight to master, anyone else's clone pushes an update branch and opens a pull request; then bring a clone up to date with `pull`. U

• evergreen-refresh

  Refresh one named evergreen unit's research from primary web sources and reschedule its next check adaptively; also works through the whole list an audit hands over. Use when the user asks about that specific skill or doc: 'refresh X', 'update X's research', 'is X stale', 'is this still current', 'c

• evergreen-setup

  Get a skill running on this machine: check what it needs outside itself (a tool, a package, an API key, a local server, an AI model, an MCP server, or access to a database, Application Insights, a cloud role or an API), tell the user what each missing piece is for, install what is safe after saying

• evergreen-test

  Write and run the eval suite that proves a skill or plugin works: trigger prompts and decoys, action cases proven by evidence outside the transcript (a tool call in the trace, a file, a marker, a remote record), outcome cases, and a baseline without the skill. Use when a skill has just been written

• evergreen-tune

  Fix a skill or plugin that failed a test or failed in use: it did not trigger, it described an action without performing it (said it delegated, never delegated), it did the job by a forbidden route, or it produced the wrong result. Reproduces the failure in a fresh context, classifies it, writes the

• evergreen-worth

  Judge whether a skill is worth its tokens, one skill or a catalog, as a lite scan in seconds or a heavy measured run: its cost per session and per use, how often it really fires (tests excluded), whether baselines pass without it, what a fresh model already knows, then the with-versus-without A/B th

• evergreen-wrapup

  End-of-session wrap-up that turns what a work session learned into lasting improvements, keeping only what will save time or tokens or raise quality: harvest the transcript (corrections, refused calls, errors, repeated commands, token sinks, slow calls, files and stores touched), drop what fails a u

Subagents (3)

• evergreen-mapper

  Explores a repository in its own context and returns a draft CODEMAP (compass, not encyclopedia) with confidence markers, so the main session does not burn context on the sweep. Use from evergreen-map for the first map of a large or unfamiliar repo, or to re-verify drifted sections; give it the repo

• evergreen-researcher

  Runs the web research pass for an evergreen unit's refresh in its own context and returns findings with per-finding change magnitudes and primary sources, so the main session stays clean. Use from evergreen-refresh whenever a unit is due; give it the unit path, the search plan, last_checked, and the

• evergreen-tester

  Runs one eval case for an evergreen skill in a fresh context and returns a strict trace report (skills invoked, tools called in order with key inputs, files written, the evidence the case asked for, final message), so the caller can grade on evidence rather than on prose. Use from evergreen-test and

Hooks (4)

• SessionStart

  sh "${CLAUDE_PLUGIN_ROOT}/scripts/evergreen-hook.sh"

• SessionEnd

  sh "${CLAUDE_PLUGIN_ROOT}/scripts/evergreen-hook.sh" end

• PostToolUse

  sh "${CLAUDE_PLUGIN_ROOT}/scripts/evergreen-hook.sh" use

• PostToolUse

  sh "${CLAUDE_PLUGIN_ROOT}/scripts/evergreen-hook.sh" worth

Similar plugins