@akshay_pachaar: skill bundles in Hermes agent. i found this to be the most underrated feature in Hermes. real workflows need clusters o…

skill bundles in Hermes agent. i found this to be the most underrated feature in Hermes. real workflows need clusters of skills together, not one at a time. for example, writing code might need a code review skill, a testing skill, and a PR workflow skill. every time, you're loading the same group manually. three slash commands in sequence, or asking the agent in natural language and hoping it picks the right ones. a 𝘀𝗸𝗶𝗹𝗹 𝗯𝘂𝗻𝗱𝗹𝗲 fixes this with a single YAML file that groups multiple skills under one slash command. when you invoke it, every listed skill loads at once, plus any custom instruction you've baked in. the image below shows the anatomy of a bundle file and how it expands at invocation. one command, one expansion, shared instruction baked in. but the design choices underneath are what make it practical: 1. 𝗺𝗶𝘀𝘀𝗶𝗻𝗴 𝘀𝗸𝗶𝗹𝗹𝘀 𝗮𝗿𝗲 𝘀𝗸𝗶𝗽𝗽𝗲𝗱, 𝗻𝗼𝘁 𝗳𝗮𝘁𝗮𝗹: if one skill in the bundle is uninstalled, the rest still load. you don't lose the whole workflow because of one missing piece. 2. 𝗯𝘂𝗻𝗱𝗹𝗲𝘀 𝗯𝗲𝗮𝘁 𝘀𝗸𝗶𝗹𝗹𝘀 on name collisions: if a skill and a bundle share a name, the bundle wins. you opted into it. 3. 𝘄𝗼𝗿𝗸𝘀 𝗲𝘃𝗲𝗿𝘆𝘄𝗵𝗲𝗿𝗲: CLI, TUI, dashboard, Telegram, Discord, Slack. one YAML definition, all platforms. 4. 𝗻𝗼 𝗰𝗮𝗰𝗵𝗲 𝗶𝗻𝘃𝗮𝗹𝗶𝗱𝗮𝘁𝗶𝗼𝗻: bundles generate a fresh user message at invocation, same as individual skill loading. no performance cost. once your bundles are stable, the natural next step is 𝘁𝗲𝗮𝗺 𝘀𝗵𝗮𝗿𝗶𝗻𝗴. bundle YAMLs are just files. put them in a Git repo, have each team member symlink into ~/.𝗵𝗲𝗿𝗺𝗲𝘀/𝘀𝗸𝗶𝗹𝗹-𝗯𝘂𝗻𝗱𝗹𝗲𝘀/. update the repo, everyone gets the update. no registry, no central server. this is what turns a personal agent into something a small team can standardize around. i wrote a full deep dive covering hermes agent's self-evolving skills, three-tier memory, GEPA optimization, and setting up multiple specialized agents. the article is quoted below.