Repository navigation
feat(harness-ops): on-demand plugin landscape audit (stale plugins and modern alternatives) #6461
Copy link
Copy link
Closed
Feature
Copy link
Labels
agent-readyFully specified and briefed; eligible for autonomous pickup from the frontier.Fully specified and briefed; eligible for autonomous pickup from the frontier.work-class: scopedA briefed fix or small feature; blast radius bounded by the brief, tests exist.A briefed fix or small feature; blast radius bounded by the brief, tests exist.
Description
Problem
Nothing tells the owner when an installed plugin or marketplace has gone stale, or when a better alternative has appeared (e.g. Playwright vs Vercel's agent-browser CLI). On 2026-10-05 a one-off script found:
- 16 stale third-party plugins (no upstream update in 60+ days)
- 2 stale marketplaces (karpathy-skills 04-20, openai-codex 07-08)
The existing pieces are all manual or single-purpose: discipline:recheck-against-upstream, docs/upstream/, dometrain:sync.
Proposed: on-demand skill (no schedule for now)
- Ages: for every installed plugin and known marketplace, the last upstream commit touching the plugin's source path, via batched
gh api. Flag 60+ days, archived, moved, or a source path that no longer exists. - Overlaps: group plugins that do the same job, across marketplaces including melodic-software, and name the one to keep.
- Alternatives: for each stale or losing plugin, research current alternatives, official docs first, and record the evidence.
- Issues: file one issue per adopt / adapt / drop decision here. Adopt-and-adapt policy: keep an adapted melodic version of an upstream skill until upstream meets Anthropic's skill guidance (frontmatter, description length, body size, progressive disclosure), then drop ours.
Boundary:
- This repo decides what to adopt.
- The owner's dotfiles decide what's installed and on per user and machine, and change only after a decision here.
chezmoi applykeeps things current (marketplace autoUpdate, tool upgrades, fixing renamed or broken sources). It does no landscape research.
Ownership: harness-ops, which already owns plugins sync (see #6309).
🤖 Generated with Claude Code
Done when (owner-approved scope: read-only v1, 2026-10-17)
- A harness-ops skill runs on demand only (no schedule) and is read-only: it files no issues, edits no settings or dotfiles, and installs, updates or removes nothing.
- For every installed plugin and every known marketplace, the report gives the date of the last upstream commit touching the plugin's source path, fetched with batched
gh apicalls. - The report flags each plugin or marketplace with no upstream commit in 60+ days, an archived upstream repository, a moved or renamed repository, or a source path that no longer exists.
- Plugins that do the same job are grouped across marketplaces (melodic-software included), and each group names the one to keep with a stated basis.
- Each stale or losing plugin lists current alternatives with evidence links, official docs first.
- Each adopt, adapt or drop call appears as a recommendation in the report, not as a filed issue; for an adapted melodic copy of an upstream skill, the report says whether upstream now meets Anthropic's skill guidance (frontmatter, description length, body size, progressive disclosure).
- The age and flag logic is covered by tests that use recorded
gh apiresponses, with no network. - Out of v1: filing issues, any change to installed state, and scheduling.
Reactions are currently unavailable
Metadata
Metadata
Assignees
Labels
agent-readyFully specified and briefed; eligible for autonomous pickup from the frontier.Fully specified and briefed; eligible for autonomous pickup from the frontier.work-class: scopedA briefed fix or small feature; blast radius bounded by the brief, tests exist.A briefed fix or small feature; blast radius bounded by the brief, tests exist.
Type
Fields
No fields configured for Feature.
Activity
kyle-sexton commentedon Oct 17, 2026
Added a
## Done when (owner-approved scope: read-only v1, 2026-10-17)section to the body, per the owner decision of 2026-10-17. The criteria come from the issue's own proposal (ages, overlaps, alternatives), scoped to a read-only first version: the report recommends adopt, adapt or drop, and filing issues (proposal step 4) moves out of v1.kyle-sexton commentedon Oct 18, 2026
Agent Brief
Type: Feature
Summary: Add a read-only, on-demand harness-ops skill that reports stale installed plugins and marketplaces, overlaps and alternatives.
Current behavior:
Nothing reports when an installed plugin or marketplace has gone stale or when a better alternative exists; a one-off script found 16 stale plugins and 2 stale marketplaces.
Desired behavior:
Key interfaces:
Acceptance criteria:
scripts/run-test-file.shon the test passes.scripts/check-changelog-fragments.sh.Out of scope:
plugins syncbehavior.This was generated by AI during backlog shaping. Held, not admitted: this brief is drafted and checked, but the issue lane would stop on it today. It is admitted, by adding
agent-ready, once the lane can run the skill-quality check scripts (Automation Lanes' PR #7912). Held under the owner's 2026-10-18 lane-narrowing course correction.