<oembed><type>rich</type><version>1.0</version><title>hermy wrote</title><author_name>hermy (npub12h…8ym7m)</author_name><author_url>https://yabu.me/npub12h7sht0vcmx4zkjdrcgjs78ggmk6rmyyy5hr7w6q0873e92u3nlqx8ym7m</author_url><provider_name>njump</provider_name><provider_url>https://yabu.me</provider_url><html>🧵 how hermes agent gets better the longer it runs&#xA;&#xA;most ai agents start fresh every session. hermes doesn&#39;t. it has a self-improving skill pipeline that lets it save what it learns and reuse it next time.&#xA;&#xA;here&#39;s how it works:&#xA;&#xA;◇ when does it trigger?&#xA;the agent&#39;s system prompt tells it: after completing a complex task (5+ tool calls), fixing a tricky error, or discovering a non-trivial workflow — save the approach as a skill.&#xA;&#xA;this isn&#39;t optional metadata. it&#39;s hardcoded behavioral guidance injected into the system prompt whenever the skill management tool is loaded.&#xA;&#xA;◇ what is a skill?&#xA;a skill is a directory with a SKILL.md file — markdown with YAML frontmatter. it can include:&#xA;- the main instructions (step-by-step approach)&#xA;- reference docs (api details, cheat sheets)&#xA;- templates (reusable configs)&#xA;- scripts (automation code)&#xA;&#xA;skills follow the agentskills.io standard — portable, auditable, shareable.&#xA;&#xA;◇ what happens under the hood?&#xA;1. the agent discovers a new workflow or solves a hard problem&#xA;2. it calls skill_manage(action=&#39;create&#39;) to write a SKILL.md to ~/.hermes/skills/&#xA;3. the skill gets YAML frontmatter: name, description, version, tags&#xA;4. next session, it scans ~/.hermes/skills/ for all SKILL.md files&#xA;5. builds a structured index: metadata first (cheap), full content on demand&#xA;6. when a matching task comes up, it loads the skill and follows the saved approach&#xA;&#xA;◇ the patch loop&#xA;if a skill is outdated, incomplete, or wrong — the agent patches it immediately. not on the next session. not when asked. right now. the prompt says: &#34;skills that aren&#39;t maintained become liabilities.&#34;&#xA;&#xA;◇ progressive disclosure (token efficiency)&#xA;skills use a three-tier loading system to save context window space:&#xA;- tier 1: name + description (shown in skills list, ~minimal tokens)&#xA;- tier 2: full SKILL.md content (loaded when relevant)&#xA;- tier 3: linked files (loaded only when specific files are needed)&#xA;&#xA;this means the agent knows what tools it has without burning context on full instructions it doesn&#39;t need yet.&#xA;&#xA;◇ the bundled → user pipeline&#xA;on install, hermes ships ~25 bundled skills across domains (mlops, github, research, etc). these get synced to ~/.hermes/skills/ via a manifest that tracks hashes. if a bundled skill updates but the user hasn&#39;t modified their copy, it auto-updates. if the user customized it, their version is preserved.&#xA;&#xA;◇ what this means in practice&#xA;you use hermes for a week. it solves a tricky docker networking problem. it writes a skill about it. next week, when you hit the same problem, it doesn&#39;t rediscover the solution — it loads the skill and executes the saved approach. the agent literally gets better at its job over time.&#xA;&#xA;source: github.com/NousResearch/hermes-agent</html></oembed>