hermes-themes

Author a Hermes color theme that skins every surface.

Quality

63%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide

Securityby

Passed

No findings from the security scan

Fix and improve this skill with Tessl

tessl review fix ./skills/hermes-themes/SKILL.md

Quality

Content

77%

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 and a clear, validated workflow, and it avoids explaining concepts Claude already knows. Its main gaps are mild cross-section repetition and a referenced template file (templates/skin.yaml) that is not included in the bundle.

Suggestions

De-duplicate the rules repeated across the Procedure and Pitfalls sections (never hand-edit config.yaml; you apply it not the user; don't fork default for a tweak) by stating each once and consolidating them in Pitfalls.

Ship the referenced templates/skin.yaml in a templates/ bundle directory, or inline a minimal skin template, so the 'Copy templates/skin.yaml' step has a real file to copy.

Dimension	Reasoning	Score
Conciseness	Mostly lean and Hermes-specific with no general-concept padding, but several rules (never hand-edit config.yaml; you apply it not the user; don't fork default for a tweak) are stated twice across the Procedure and Pitfalls sections and could be tightened.	2 / 3
Actionability	Provides concrete, copy-paste-ready commands (hermes config set display.skin, hermes skin set <key> <hex>) with worked examples, a specific element-to-key table, and exact file paths.	3 / 3
Workflow Clarity	Clear sequenced Procedure and How-to-Run steps with an explicit Verification section (read_file the YAML, hermes config get display.skin, user confirm) and a revert path, giving real validation checkpoints.	3 / 3
Progressive Disclosure	Well-organized into clear sections with a one-level pointer to skin_engine.py for the full schema, but the referenced templates/skin.yaml the procedure tells the user to copy is not present in the bundle.	2 / 3
	Total	10 / 12 Passed

Description

50%

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 is clear and domain-specific about what the skill does but is missing any explicit 'when to use' trigger guidance, which caps its completeness. Trigger-term coverage and action specificity are adequate but not rich.

Suggestions

Add an explicit 'Use when...' trigger clause (e.g., 'Use when the user wants a custom Hermes look — a synthwave theme, brand colors, or one palette across the CLI, TUI, and desktop') to clearly answer when Claude should invoke this skill.

Include more natural trigger terms users would say — 'theme', 'colors', 'palette', 'dark mode', 'appearance' — alongside 'color theme' and 'skins'.

List more concrete actions (e.g., 'write a skin YAML, activate it, and tweak individual colors live') to raise specificity beyond the single 'Author' verb.

Dimension	Reasoning	Score
Specificity	Names the domain (Hermes color theme) and one concrete action ('Author'), but lists only a single action rather than multiple specific ones.	2 / 3
Completeness	Clearly states what the skill does (author a theme that skins every surface) but provides no explicit 'Use when...' trigger guidance for when to invoke it.	2 / 3
Trigger Term Quality	Includes some natural terms a user would say ('color theme', 'skins') but misses common variations like 'palette', 'colors', 'dark mode', or 'appearance'.	2 / 3
Distinctiveness Conflict Risk	The Hermes-theming niche is fairly specific, but without explicit triggers it could overlap with a general Hermes appearance/config skill.	2 / 3
	Total	8 / 12 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: skills/hermes-themes/SKILL.md
Commit: b7a05b6

Reviewed: about 13 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.