<?xml version="1.0" encoding="utf-8" standalone="yes"?><rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom"><channel><title>Evaluation on AiSlackin</title><link>https://aislackin.com/tags/evaluation/</link><description>Recent content in Evaluation on AiSlackin</description><generator>Hugo</generator><language>en-us</language><lastBuildDate>Sun, 06 Sep 2026 00:00:00 +0000</lastBuildDate><atom:link href="https://aislackin.com/tags/evaluation/index.xml" rel="self" type="application/rss+xml"/><item><title>MoACubed: teaching Hermes which profiles actually work</title><link>https://aislackin.com/posts/2026-09-06-moacubed/</link><pubDate>Sun, 06 Sep 2026 00:00:00 +0000</pubDate><guid>https://aislackin.com/posts/2026-09-06-moacubed/</guid><description>&lt;p&gt;I have been running Hermes with multiple profiles for a while. That gives me useful specialization, but it also creates an uncomfortable question:&lt;/p&gt;&#10;&lt;p&gt;&lt;strong&gt;Which profile should handle a given kind of task?&lt;/strong&gt;&lt;/p&gt;&#10;&lt;p&gt;It is easy to answer that question with vibes. One profile feels sharper. Another writes cleaner code. A third catches edge cases the others miss. Then one impressive run becomes a permanent routing rule.&lt;/p&gt;&#10;&lt;p&gt;That is not evaluation. That is anecdote with a config file.&lt;/p&gt;</description></item></channel></rss>