honcho

Configure and troubleshoot Honcho memory for Hermes.

Quality

64%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide

Securityby

Low

Low-risk findings worth noting

Fix and improve this skill with Tessl

tessl review fix ./optional-skills/autonomous-ai-agents/honcho/SKILL.md

Quality

Content

71%Weight 40%Scale 1-5

Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.

The body is highly actionable with concrete commands, config examples, and tool signatures, and its workflows are clearly sequenced with a verify step. Its main weaknesses are duplicated config tables between sections and a lack of progressive disclosure — the full reference lives inline with no offloaded detail files.

Suggestions

Move the bulk of the Config Reference and CLI Commands tables into a separate reference file (e.g., CONFIG.md) and leave a concise summary plus a one-level-deep link in SKILL.md to improve progressive disclosure.

De-duplicate the dialectic settings: cover them once in 'Three Orthogonal Knobs' and link from 'Config Reference' rather than repeating the full table.

Add an explicit validate-and-retry feedback loop to the setup/multi-profile workflow (e.g., run 'hermes honcho status' after sync and what to fix if the peer is missing) to push workflow clarity toward 5.

Dimension	Reasoning	Score
Conciseness	The body is largely lean and table-driven and assumes competence, but settings like the dialectic knobs are documented twice (in 'Three Orthogonal Knobs' and again in 'Config Reference'), adding redundancy that could be tightened.	3 / 5
Actionability	It provides fully executable, copy-paste-ready commands (e.g., 'hermes honcho status', 'hermes profile create coder --clone'), concrete JSON config blocks, and exact tool signatures with usage examples covering the common cases.	5 / 5
Workflow Clarity	Setup, verify, multi-profile backfill, and tool-usage sequences are clearly ordered with a verify checkpoint, but explicit error-recovery feedback loops are absent, keeping it below a 5.	4 / 5
Progressive Disclosure	Content is well-sectioned with clear headers and tables, but no bundle files exist and a full ~415-line config/tool reference is inlined in SKILL.md rather than offloaded to one-level-deep reference files.	3 / 5
	Total	15 / 20 Passed

Description

57%Weight 40%Scale 1-5

Based on the skill's description, can an agent find and select it at the right time? Clear, specific descriptions lead to better discovery.

The description clearly states what the skill does and targets a distinct, product-specific niche, but it omits any explicit 'Use when...' trigger guidance and has only two named actions. Adding a concrete trigger clause and a few more specific actions would lift the completeness and specificity dimensions.

Suggestions

Add a 'Use when...' clause naming natural user phrases (e.g., 'Use when setting up Honcho memory, troubleshooting peer sync, or tuning dialectic/observation settings for Hermes').

List a few more concrete actions (e.g., 'configure recall modes, tune dialectic cadence/depth, create multi-profile peers') to move specificity from 3 to 4-5.

Include synonym/variation keywords a user would actually say (e.g., 'Honcho', 'memory not persisting', 'peer identity', 'session summary') to broaden trigger coverage.

Dimension	Reasoning	Score
Specificity	Names the domain (Honcho memory) plus two concrete actions ('Configure and troubleshoot'), matching the 1-2 concrete actions anchor; it does not list several specific actions needed for a 4.	3 / 5
Completeness	The 'what' is clear (configure and troubleshoot Honcho memory) but there is no 'Use when...' trigger clause; per the guideline, a missing trigger clause caps completeness at 3.	3 / 5
Trigger Term Quality	It includes relevant product keywords ('Honcho memory', 'Hermes', 'Configure', 'troubleshoot') but lacks natural synonym variations a user might say, fitting the 'some relevant keywords' anchor rather than the fuller coverage of a 4.	3 / 5
Distinctiveness Conflict Risk	It targets the named products Honcho and Hermes, giving it a clear niche with distinct triggers and minimal overlap risk with other skills.	5 / 5
	Total	14 / 20 Passed

Validation

81%

Warnings & errors only

Checks the skill against the spec for correct structure and formatting. All validation checks must pass before discovery and implementation can be scored.

Validation — 13 / 16 Passed

Validation for skill structure

Criteria	Description	Result
metadata_version	'metadata.version' is missing	Warning
metadata_field	'metadata' should map string keys to string values	Warning
frontmatter_unknown_keys	Unknown frontmatter key(s) found; consider removing or moving to metadata	Warning

	Total	13 / 16 Passed

Repository: NousResearch/hermes-agent
Path: optional-skills/autonomous-ai-agents/honcho/SKILL.md
Commit: 6680afb

Reviewed: about 3 hours ago

Table of Contents

Discovery Implementation Validation

Is this your skill?

If you maintain this skill, you can claim it as your own. Once claimed, you can manage eval scenarios, bundle related skills, attach documentation or rules, and ensure cross-agent compatibility.