hermes-desktop-plugins

Write desktop app plugins that add UI panes and commands.

Quality

71%

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-desktop-plugins/SKILL.md

Quality

Content

92%

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

The content is dense, actionable, and well-sequenced with clear verification loops — strong on conciseness, actionability, and workflow clarity. The main weakness is progressive disclosure: referenced bundle files are absent and the detailed API reference is inline rather than split out.

Suggestions

Ship the referenced `templates/plugin.js` file so the "Start from templates/plugin.js" step resolves; verify any other referenced paths exist in the bundle.

Move the long Quick Reference API enumeration into a separate reference file (e.g. references/sdk-api.md) and keep SKILL.md as a tighter overview with a clearly signaled link.

Confirm the `website/docs/developer-guide/desktop-plugin-sdk.md` path is reachable from where the skill is installed, or restate it relative to the skill bundle.

Dimension	Reasoning	Score
Conciseness	The body assumes Claude's competence throughout — no explanation of what plugins/React/Electron are — and every line is non-obvious proprietary SDK detail (import surface, API signatures, pitfalls), so it is lean with every token earning its place.	3 / 3
Actionability	It gives fully executable guidance: exact signatures like `ctx.register({ id, area, order?, render?, data? })`, copy-paste-ready patterns like `dock: { pane: 'workspace', pos: 'bottom' }` with `height: '200px'`, specific theme vars, and import constraints.	3 / 3
Workflow Clarity	"How to Run" and "Procedure" give clear numbered sequences with a fallback (Reload desktop plugins) and an explicit error-recovery feedback loop (toast names the error → fix → reload) plus a Verification checklist.	3 / 3
Progressive Disclosure	The body references `templates/plugin.js` ("relative to this skill directory") and `website/docs/.../desktop-plugin-sdk.md`, but neither exists in the bundle, and the long inline Quick Reference API enumeration is content that could be split into a separate reference file.	2 / 3
	Total	11 / 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 states the what concisely but omits any explicit when-to-use trigger and under-specifies the skill's capabilities, leaving it generic relative to the product. Adding a "Use when..." clause and naming Hermes would raise most dimensions.

Suggestions

Add an explicit trigger clause, e.g. "Use when adding a pane, statusbar widget, command, keybind, route, or theme to the Hermes desktop app without modifying the app itself."

Name the product ("Hermes") so the skill is distinguishable from generic desktop-plugin skills.

Expand the capability list beyond "UI panes and commands" to cover statusbar, keybinds, routes, and themes for full specificity.

Dimension	Reasoning	Score
Specificity	Quotes "desktop app plugins" and two concrete actions ("add UI panes and commands"), but omits most of the skill's actual capabilities (statusbar, keybinds, routes, themes), so it is not comprehensive as the level-3 anchor requires.	2 / 3
Completeness	The "what" is present ("Write desktop app plugins that add UI panes and commands") but the "when" is entirely missing with no "Use when..." clause, so it is capped at 2 per the rubric guideline.	2 / 3
Trigger Term Quality	Terms like "desktop app plugins", "UI panes", and "commands" are natural, but coverage is thin — no product name "Hermes" and no common variations like "extension", "widget", or "statusbar", matching the level-2 anchor.	2 / 3
Distinctiveness Conflict Risk	"Desktop app plugins" is a real niche but without the product name it could overlap with other plugin skills, matching the level-2 anchor of being somewhat specific but still able to overlap.	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-desktop-plugins/SKILL.md
Commit: b7a05b6

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