Finding
Hard or repeated Hermes work is often solved once in chat, then lost as context instead of being turned into a durable skill that improves the installation.
Current
A real Hermes installation can solve complex tasks with tools, delegation, memory, and session history, but the reusable procedure is weak if it remains only in the transcript. The operational gap appears after multi-step debugging, configuration, research, deployment, or tool-use tasks: the agent knows what worked during the session, but the next run must rediscover commands, pitfalls, verification steps, and decision boundaries. That wastes tokens and increases the chance of repeating avoidable mistakes.
Suggested
- Add a post-task skill capture rule for complex work. Exact change: add a short rule to SOUL.md or the main profile instructions: “After any difficult, repeated, or 5+ tool-call task, create or patch a skill containing trigger conditions, exact steps, pitfalls, and verification.”
- Create one skill per reusable operating procedure, not per one-off task. Exact change: add a runbook entry named “Skill capture checklist” that says the skill must include when to use it, required tools, numbered procedure, common failure modes, and a final verification step before it is considered complete.
- Patch existing skills immediately when they fail or drift. Exact change: add a verification habit to the Optimizer Agent review prompt: “Scan recent sessions for repeated errors or manual workarounds; if a matching skill exists, recommend a skill patch, otherwise recommend a new skill.”
Impact
This turns Hermes from a capable assistant into a self-improving operating system. Reusable procedures reduce repeated explanations, lower token use, and make future agent runs safer because the working path is preserved with its pitfalls and checks. It also improves delegation quality: subagents can be given proven workflows instead of vague instructions.
Effort
Small — the technical action is only creating or patching a skill, but it requires discipline to recognize when a solved task has become reusable operational knowledge.
Public page note
Safe public content includes the achievement meaning, the operational rule, generic examples of skill-worthy workflows, and the maturity benefit of durable procedures. Internal-only content includes private task details, raw chat excerpts, credentials, logs, exact environment values, sensitive filesystem paths, and customer- or business-specific workflows.