hermes - 💡(How to fix) Fix [Skills System] Serious systemic defects in the skills system: no pruning, island isolation, and missing conflict detection [1 participants]

 A user on Toutiao (Chinese social platform) named "小胖有事说" published a video titled "Hermes seems to be truly half-baked!" (2026-04-20),
 providing concentrated feedback on design flaws in Hermes's skill system. The original video has gained some attention and deserves official
 acknowledgment.

 ---

 ## 1. Unreasonable skill creation mechanism: "Only births, no nurturing"

 - **Too low barrier, proliferation of throwaway skills**: As few as 5 tool calls automatically convert temporary experience into a skill. One-off
 debugging sessions or accidentally successful tasks can all trigger this, leading to an overwhelming flood of invalid, temporary skills that bury
 the truly useful ones.
 - **Experience ≠ Skill, lacks consolidation and validation**: Short-term working memory is directly converted to long-term skill with no memory
 consolidation, effectiveness verification, or quality filtering — highly unscientific.

 **Recommendation**: Add quality gates for skill creation, such as requiring N successful uses before creation, placing newly created skills in a
 pending review state, or distinguishing "temporary skills" from "正式技能 (formal skills)".

 ---

 ## 2. No metabolism: only adding, never subtracting — system bloat

 - **No deletion/disable/invalidation mechanism**: Skills created once live forever; users can only delete manually and have no way to know which
 ones to remove.
 - **Lacks regulatory feedback loops**: Violates principles of system stability (cf. "Thinking in Systems"). Nature relies on "death" cycles, but
 Hermes only has additions with no cleanup. Eventually the skill library explodes, making the system slower and dumber.

 **Recommendation**: Introduce skill decay/invalidation (e.g., skills unused for 30 days are auto-demoted or flagged for cleanup), support
 disabling skills, and add usage statistics for user reference.

 ---

 ## 3. Skill islands: no composition, no sharing, redundant duplication

 - **No composition/inheritance/synergy**: Each skill is an isolated island — cannot call each other, share code, or logic.
 - **Massive redundant copying**: The same logic (e.g., TDD, development workflows) is duplicated across multiple skills; updating one doesn't sync
 to other copies.
 - **Official association fields are non-functional**: Fields like `related_skills` exist only for display, with no actual code-level invocation —
 purely decorative.

 **Recommendation**: Support inter-skill dependencies/calls, support shared code libraries (like npm packages), and `related_skills` fields should
 actually trigger cross-skill collaboration or at least provide intelligent recommendations.

 ---

 ## 4. Missing conflict detection: mutual interference, severe internal friction

 - **Only checks name conflicts, not functional conflicts**: Only skills with identical names are blocked. Skills with nearly identical
 functionality but different names are completely undetected.
 - **Skills conflict with and override each other**: Multiple drawing/task skills conflict and vie for execution rights. Some even have `conflict
 with` markers in the source code, resulting in chaotic outputs (e.g., image generation styles are completely inconsistent).

 **Recommendation**: Add functional similarity detection (based on semantic similarity of skill descriptions/tags), explicitly declare skill mutual
 exclusivity, and runtime conflict detection should give users clear selection prompts.

 ---

 ## 5. Overall Consequences

 The skill ecosystem is imbalanced, polluted, and riddled with internal friction. The system grows more bloated, more foolish, and less stable with
 use. The automated skill creation, meant to be a highlight, has become the biggest hidden danger due to lack of maintenance, cleanup, and
 coordination.

 ---

 ## Summary

 | Problem | Root Cause | Consequence |
 |---------|-----------|-------------|
 | Too low barrier | 5 calls = created | Invalid skills flood |
 | No decay mechanism | Only add, never clean | System bloat, heat death |
 | Skill islands | No composition/sharing | Duplicate code, hard to maintain |
 | Missing conflict detection | Only checks same name, not same function | Chaotic output, internal friction |

 Recommended the official treat "skill lifecycle management" as a dedicated project, redesigning the skill ecosystem with reference to the three
 essentials of systems (elements, connections, function/goal) from "Thinking in Systems."

 ---

 *Feedback source: https://www.toutiao.com/video/7630643722442654248/*