# Curate Skills

> >-

- **Type:** Skill
- **Install:** `agentstack add skill-justingastby-hermes-mind-skill-curate-skills`
- **Verified:** Yes — security-reviewed for prompt injection and unsafe behavior
- **Seller:** [JustinGastby](https://agentstack.voostack.com/s/justingastby)
- **Installs:** 0
- **Category:** [Agent Skills](https://agentstack.voostack.com/c/agent-skills)
- **Latest version:** 0.1.0
- **License:** MIT
- **Upstream author:** [JustinGastby](https://github.com/JustinGastby)
- **Source:** https://github.com/JustinGastby/Hermes-Mind-Skill/tree/main/cursor/skills/curate-skills

## Install

```sh
agentstack add skill-justingastby-hermes-mind-skill-curate-skills
```

Requires the [AgentStack CLI](https://agentstack.voostack.com/docs/cli). Works with Claude Code, Cursor, and any MCP-compatible agent.

## About

# Curate Skills

A much lighter version of Hermes Agent's Curator: it keeps `.cursor/skills/`
from accumulating stale or near-duplicate entries, but — unlike Hermes's
fully-automatic background Curator — it never touches a file without the
user confirming first. A wrong or premature archive/merge is worse than a
slightly untidy skills folder.

## Two things this does, and neither one deletes anything

1. **Archive** long-unused skills — move the skill's directory into
   `.cursor/skills/.archive/`. Recoverable, never destructive.
2. **Merge** near-duplicate skills into one broader skill, then archive the
   originals (not delete) so nothing is lost if the merge was wrong.

## When to run this

- The `stop` hook's curator sweep (`nudge-skill-distillation.js`) nudged you
  with a list of skills that haven't been read in ~30 days.
- The user explicitly asks to clean up, compress, or prune skills.
- While drafting a new skill in `distill-skill`, you notice 2+ existing
  skills already cover very similar ground.

## Workflow

1. **Survey the current skills.** List `.cursor/skills/*/SKILL.md` (skip
   `.archive/`). For each, read the frontmatter `name` + `description`, and
   check `.cursor/hooks/.state/skill-usage.json` for `use_count` /
   `last_used_at` if present.
2. **Never touch these:**
   - `distill-skill`, `curate-skills` — this project's own bundled skills.
   - Any skill whose `SKILL.md` frontmatter contains `pinned: true`.
   - Bundled/hub-installed skills the user didn't create locally, if that's
     distinguishable (e.g. skills that shipped with another tool/plugin).
3. **Draft a short proposal, not a file edit.** Two independent lists:
   - **Archive candidates**: name + how long unused (from the nudge message
     or `skill-usage.json`).
   - **Merge candidates**: which 2+ skills overlap, a proposed merged name +
     one-sentence description, and which old skills would be absorbed.
4. **Ask the user to confirm each list separately** (a skill might be a
   merge candidate but not stale, or vice versa) — e.g. "这些技能好久没用了，
   要不要归档？" / "这几个技能内容挺重叠的，要不要合并成一个？" Do not modify
   any file before the user agrees.
5. **On confirmed archive:** `mkdir -p .cursor/skills/.archive` then move the
   skill's whole directory there (keep `references/`, `templates/`, `scripts/`
   subfiles together — archive the full package, don't cherry-pick files).
6. **On confirmed merge:**
   - Create `.cursor/skills//SKILL.md` with the combined
     procedure — write it fresh, don't just concatenate the old bodies.
     Fold overlapping steps together; keep pitfalls from all sources.
   - Move any `references/`/`templates/`/`scripts/` subfiles the merged
     skill still needs into the new skill's directory.
   - Archive (not delete) each absorbed skill's original directory into
     `.cursor/skills/.archive/` so the merge is reversible.
7. **On no or no response**, drop it — don't archive/merge and don't ask
   again this session.

## Recovering an archived skill

Just move it back: `mv .cursor/skills/.archive/ .cursor/skills/`.
Nothing about archiving is ever a one-way trip.

## Pinning a skill so it's never flagged as stale

Add `pinned: true` anywhere in the skill's YAML frontmatter:

```yaml
---
name: some-skill
description: ...
pinned: true
---
```

The curator sweep skips pinned skills entirely, and this skill should too —
never propose archiving or merging a pinned skill even if the user asks you
to review "everything."

## Verifying a merge didn't lose anything

Before archiving the absorbed originals, diff the new skill's body against
each original to confirm every concrete step/command/pitfall made it into
the merged version — a merge that silently drops a hard-won pitfall is worse
than not merging at all.

## Source & license

This open-source skill is cataloged on AgentStack and links to its original source — we do not rehost the code.

- **Author:** [JustinGastby](https://github.com/JustinGastby)
- **Source:** [JustinGastby/Hermes-Mind-Skill](https://github.com/JustinGastby/Hermes-Mind-Skill)
- **License:** MIT

Install and usage instructions live in the source repository linked above.

## Pricing

- **Free** — Free

## Security capabilities

Automated source analysis of v0.1.0 — what this tool can access:

- **Network access:** no
- **Filesystem access:** no
- **Shell / process execution:** no
- **Environment & secrets:** no
- **Dynamic code execution:** no

*"Yes" means the capability is present in the source — more access means more to trust, not that it is unsafe.*


## Versions

- **0.1.0** — security scan: passed — Imported from the upstream source.

## Links

- Listing page: https://agentstack.voostack.com/l/skill-justingastby-hermes-mind-skill-curate-skills
- Seller: https://agentstack.voostack.com/s/justingastby
- Browse the marketplace: https://agentstack.voostack.com/browse

---
Listed on AgentStack — the marketplace for AI agent skills and MCP servers. Every listing is security-reviewed. Creators keep 70%.