# NousResearch/hermes-agent · Skill lifecycle tracking, staleness, and archival proposals

## Open now

- 1 issue, 0 PRs open on GitHub.
- #11425: \[Feature\]: Skills lifecycle management — usage tracking, stale detection, and auto-cleanup

These members propose features and an RFC for managing skill lifecycle events, including usage metadata tracking, stale skill detection, and archival or cleanup mechanisms. They appear to be related design discussions rather than completed implementations.

## TL;DR

- 3 member(s): 1 open issue(s), 2 closed issue(s), 0 open PR(s), 0 merged PR(s), 0 PR(s) closed without merging.
- No fix found: no merged or attempted fix PR is on record for this cluster.
- **Recommended:** if this matches your symptom, consider adding to the existing issue(s) below rather than opening a new one.

## Maintainer resolution verdict

- Internal-tracker verdict over this cluster's issue members: `unresolved`. This is distinct from the fix status above. Weigh it yourself.

## How this cluster was grouped

- Link evidence (`LLM_ONLY`): no structural link between members; the grouping rests entirely on an automated relevance judgement over their text.
- Read the members yourself before treating them as one problem.
- Pairwise link density `0.24`: the share of member pairs that carry a link, counting a structural link in full and a relevance-only link at 0.36. `1.00` means every pair is linked.

## Open related issues

- #11425: \[Feature\]: Skills lifecycle management — usage tracking, stale detection, and auto-cleanup

## Closed / duplicate issues

- #7816: \[Feature\]: Skill lifecycle management — usage metadata, staleness, archival, and revalidation
- #16077: RFC: review the Curator — background skill maintenance (PR #16049, closes #7816)

## Fix status

- No merged fix on record.
- Subsystem: `skills`