Custom plugin maintenance

A "custom plugin" is any plugin NOT listed in the sync table of the upstream-sync skill. Its content is hand-authored or research-grounded and has no upstream source to re-pull. If a plugin is not in that sync table, it falls under this skill.

Custom plugins decay differently than vendored ones. There is no upstream commit to diff against. Versions, framework recommendations, breaking-change notes, and "current as of 2026" claims become stale silently. The maintenance protocol below is the antidote.

Refresh the hand-authored kernel under plugins/<name>/: plugin.toml, roles/, workflows/ with their TOML sidecars, skills/, contracts/ and policies/. Host mechanisms live under adapters/. Exports and root marketplace catalogs are generated; correct their source and rebuild rather than editing package copies.

Freshness risk classes

Classify each plugin into one of four classes. The class determines refresh cadence and triage priority.