Reuse the Skill

20.4. Reuse the Skill — Reusing the Skill

The core value: not re-reasoning from scratch

The next time a similar request comes in, the agent can reuse the skill instead of re-reasoning every step from zero — this is the practical meaning of “self-improving”. Operationally, the progressive disclosure mechanism from chapter 10.1 guarantees this reuse is not expensive: the agent only sees the skill’s name + short description until it is actually needed, at which point the full content is loaded.

Calling directly via slash command

As stated in chapter 10.3, every skill automatically becomes a slash command — the fastest way to proactively “call up” an existing skill instead of letting the agent guess whether to use it:

/github-pr-workflow open a PR for the auth refactor

Portable skills — reuse that goes beyond one agent

Skills are compatible with the open agentskills.io standard — meaning a skill is not only reusable across many sessions on your own Hermes instance, but also portable, shareable, and can be contributed to the community through the Skills Hub (chapter 10.2) — reuse scales from the individual level up to the community level.

Notes

• Do not hesitate to call a known skill’s slash command directly instead of re-describing the request in natural language — a direct call guarantees the right skill is loaded, avoiding the agent picking a different approach by mistake.
• For skills used frequently in a fixed combination, group them into a bundle (10.1) so that “reusing” collapses into a single command instead of calling multiple skills in sequence.
• Track how often a skill is called back — this is a natural signal for which skills are worth investing in further improvement (step 20.5) and which may already be outdated, no longer fitting how you work today.