<?xml version="1.0" encoding="utf-8" standalone="yes"?><rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom"><channel><title>Workflow on AiSlackin</title><link>https://aislackin.com/tags/workflow/</link><description>Recent content in Workflow on AiSlackin</description><generator>Hugo</generator><language>en-us</language><lastBuildDate>Wed, 19 Aug 2026 00:00:00 +0000</lastBuildDate><atom:link href="https://aislackin.com/tags/workflow/index.xml" rel="self" type="application/rss+xml"/><item><title>hermes-skills: a catalog for skills that survive machine rebuilds</title><link>https://aislackin.com/posts/2026-08-19-hermes-skills-catalog/</link><pubDate>Wed, 19 Aug 2026 00:00:00 +0000</pubDate><guid>https://aislackin.com/posts/2026-08-19-hermes-skills-catalog/</guid><description>&lt;p&gt;Hermes Agent skills are just folders with a &lt;code&gt;SKILL.md&lt;/code&gt;, which is exactly why they rot: they end up scattered across profiles and machines, unversioned, unrecorded. This repo is the fix I built for myself — a single maintained collection where every skill is registered in a catalog, installable with one command, and documented well enough that future-me (or anyone) can tell what it does without reverse-engineering the prompt.&lt;/p&gt;&#10;&lt;p&gt;The structure is deliberately boring: a &lt;code&gt;_template&lt;/code&gt; scaffold you copy, a &lt;code&gt;skills/README.md&lt;/code&gt; catalog you register into, and an installer script. Stateful skills keep tracker archives and metric snapshots on the host (under &lt;code&gt;~/.intel/&lt;/code&gt; for Argus), never in the repo; durable user preferences now use Hermes&amp;rsquo;s native persistent memory.&lt;/p&gt;</description></item></channel></rss>