# Curator run — 2026-05-21T13:41:50.416102+00:00

Model: `gpt-5.5` via `openai-codex`  ·  Duration: 45s  ·  Agent-created skills: 8 → 8 (+0)

## Auto-transitions (pure, no LLM)

- checked: 8
- marked stale: 0
- archived (no LLM, pure time-based staleness): 0
- reactivated: 0

## LLM consolidation pass

- tool calls: **10** (by name: skill_view=9, skills_list=1)
- consolidated into umbrellas: **0**
- pruned (archived for staleness): **0**
- new skills this run: **0**
- state transitions (active ↔ stale ↔ archived): **0**

## LLM final summary

I scanned the full candidate set of 8 agent-created, unpinned skills and inspected their SKILL.md content.

No consolidation was performed because the provided candidate set contains no 2+ member prefix/domain clusters among agent-created skills that can legally be merged under the stated rules. Each candidate is already a class-level umbrella skill, not a session-specific micro-skill:

- `cronjob` — class-level Hermes cron/scheduling umbrella with linked references already demoted into support files.
- `edge-tts` — class-level Edge TTS provider skill with German voice reference material.
- `finance-system-architecture` — very large class-level finance-system umbrella with many references already attached.
- `mcp-delegation` — class-level MCP/OpenClaw delegation skill with troubleshooting references.
- `vault-architecture` — class-level Obsidian vault design/scaffolding skill.
- `vue-primevue-dashboard-migration` — class-level Vue/Vite/PrimeVue dashboard migration skill with reference notes.
- `web-scraping` — class-level scraping / bot-detection / extraction workflow skill.
- `yazio-integration` — class-level YAZIO API integration skill with scripts/references.

Potential broader ecosystem overlaps exist with bundled or hub-installed skills, such as:

- `yazio-integration` ↔ health skills
- `edge-tts` ↔ `sherpa-onnx-tts`
- `mcp-delegation` ↔ `native-mcp`
- `vault-architecture` ↔ `obsidian`
- `web-scraping` ↔ Tavily/browser skills

…but those targets are outside the provided agent-created candidate list and may be bundled/hub-installed, so I did not touch them per hard rule 1.

No skills were archived, because archiving any of these 8 would either lose an already-valid class-level umbrella or require merging into a non-candidate skill that the instructions forbid touching.

## Structured summary (required)
```yaml
consolidations: []
prunings: []
```

## Recovery

- Restore an archived skill: `hermes curator restore <name>`
- All archives live under `~/.hermes/skills/.archive/` and are recoverable by `mv`
- See `run.json` in this directory for the full machine-readable record.