CtrlK
BlogDocsLog inGet started
Tessl Logo

hermes-agent-skill-authoring

Author in-repo SKILL.md files: frontmatter and structure.

55

Quality

64%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide

SecuritybySnyk

Passed

No findings from the security scan

Fix and improve this skill with Tessl

tessl review fix ./skills/software-development/hermes-agent-skill-authoring/SKILL.md
SKILL.md
Quality
Evals
Security

Quality

Content

75%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 a strong, actionable authoring walkthrough with concrete commands, a copy-paste validation snippet, and an explicit verification checklist. It is dense and efficient, with only minor duplication and a slightly implicit error-recovery loop.

DimensionReasoningScore

Conciseness

Dense and information-rich, assuming Claude's competence (no explanations of YAML/git/semver), with minor duplication (the validator-limits warning recurs across Overview, Frontmatter rules, and Pitfalls).

4 / 5

Actionability

Concrete executable guidance throughout — exact search_files/write_file calls, a copy-paste Python validation snippet, and precise test/sidebar commands — with only minor high-level advisory steps like 'Survey peers'.

4 / 5

Workflow Clarity

A clear 7-step numbered workflow with explicit validation (local validate assertions, test run, docs scope discipline via git checkout) and a verification checklist, though the validate->fix->retry recovery loop is less explicit than the anchor.

4 / 5

Progressive Disclosure

Well-organized into clearly headed sections with no nested references and no bundle files; some inlined material (the POSIX platform-gating table, the full validation snippet) could live in a references/ dir, keeping it below 5.

4 / 5

Total

16

/

20

Passed

Description

53%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 is concise and names a clear niche, but it answers only the 'what' and omits any explicit 'when to use' trigger guidance, which caps the strongest-weighted dimension. Trigger phrasing is technical rather than natural user language.

Suggestions

Add an explicit trigger clause, e.g. 'Author in-repo SKILL.md files. Use when adding or editing skills under skills/ or optional-skills/.'

Include a natural-language trigger term a user would actually say ('write a skill', 'add a skill to the repo') alongside the technical 'frontmatter and structure'.

Add one more concrete capability verb (e.g. 'validate', 'regen docs') to broaden specificity beyond 'Author'.

DimensionReasoningScore

Specificity

Names the domain ('in-repo SKILL.md files') and two concrete concerns ('frontmatter and structure'), but 'Author' is the only verb and coverage is not comprehensive.

3 / 5

Completeness

The 'what' is clear (author in-repo SKILL.md files with frontmatter and structure) but there is no 'Use when...' clause or equivalent trigger guidance, which caps completeness at 3.

3 / 5

Trigger Term Quality

Relevant technical keywords (SKILL.md, frontmatter, in-repo) are present but common natural phrasings users would voice ('write a skill', 'add a skill', 'skill authoring') are missing.

3 / 5

Distinctiveness Conflict Risk

'in-repo SKILL.md files' carves a distinct niche with minimal conflict risk, though it could still overlap with a user-local skill-authoring skill, keeping it below 5.

4 / 5

Total

13

/

20

Passed

Validation

75%

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

Validation12 / 16 Passed

Validation for skill structure

CriteriaDescriptionResult

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

referenced_paths_exist

Referenced path issues: 2 missing

Warning

Total

12

/

16

Passed

Repository
NousResearch/hermes-agent
Reviewed

Table of Contents

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.