CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

hermes-attestation-guardian

Hermes-only runtime security attestation and drift detection skill for operator-managed Hermes infrastructure.

Quality

73%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide
SecuritybySnyk

Critical

Do not install without reviewing

Fix and improve this skill with Tessl

tessl review fix ./skills/hermes-attestation-guardian/SKILL.md
SKILL.md
Quality
Evals
Security

Quality

Content

78%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.

This is a strong, execution-first skill body: commands are complete and real, verification is fail-closed throughout, and mutating operations are guarded by preview modes. Its weaknesses are structural — everything lives inline in SKILL.md with no reference split, some referenced bundle paths (lib/, test/) don't exist here, and the overall operating sequence is implied rather than stated.

Suggestions

Add a short numbered workflow (generate → verify → baseline diff → schedule) at the top so the sequence is explicit instead of reconstructed from the Commands list.

Move the ~70-line release-verification script and the advisory-feed environment-variable knobs into a references/ file (e.g. references/release-verification.md and references/advisory-feed.md), keeping one-line pointers in SKILL.md.

Fix the Notes section: either ship the referenced lib/*.mjs and test/*.test.mjs in the bundle or drop those lines, and update the stale 'v0.0.2' version commentary to match version 0.1.7.

DimensionReasoningScore

Conciseness

The body is mostly lean: terse command comments, a compact fail-closed bullet list, and no explanations of concepts Claude already knows. Minor over-explanation/trim opportunities remain — the ~70-line release-verification script is inlined rather than shipped as a script, and the Notes carry stale version commentary ('not implemented in v0.0.2' in a 0.1.7 skill) that is time-sensitive information not placed in a deprecation section, which the guidelines say should penalize conciseness. Not 5 because of those few tokens that do not earn their place; not 3 because padding is incidental, not structural.

4 / 5

Actionability

Every command is fully executable and copy-paste ready: the release verification block is a complete shell script with error handling, and the Commands section covers the common cases (generate, verify, baseline diff, signature verify, cron preview/apply) with real flags and example paths. All referenced scripts/*.mjs files exist in the bundle, so the commands are runnable as written.

5 / 5

Workflow Clarity

The sequence is discernible (verify release → generate attestation → verify/diff → schedule) with real validation checkpoints: 'Only install or extract the archive after this verification succeeds', the fail-closed verifier exit conditions, and the --print-only preview before the crontab-mutating --apply. It falls short of 5 because the overall order of operations is implicit (scattered across Commands, Fail-closed behavior, and Side effects) rather than given as an explicit sequence with error-recovery loops. It is not 3: the mutating crontab operation does have validation (preview mode and managed-block delimiters), so the missing-validation cap does not apply.

4 / 5

Progressive Disclosure

Sections are well-headed and all scripts/ paths referenced in the body exist, but the skill is ~240 lines of monolithic body with no reference files at all: the release-verification script, the advisory-feed override knobs, and the attestation payload spec are natural candidates for one-level-deep references. Additionally, the Notes reference 'lib/*.mjs' and 'test/*.test.mjs' paths that do not exist in this bundle, and the under-50-line exception clearly does not apply. This matches 'Some structure but could be better organized; content that should be separate is inline', not 4, because the split opportunities are substantial rather than minor.

3 / 5

Total

16

/

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 is specific about its niche and highly distinct, but it reads more like a scope statement than a trigger: it states only two actions and gives no guidance on when to invoke the skill. Adding a 'Use when...' clause and a few natural trigger phrases would move it from adequate to strong.

Suggestions

Add an explicit trigger clause, e.g. 'Use when operating Hermes CLI/Gateway deployments that need posture attestations, integrity verification, or baseline drift checks.'

Enumerate the concrete capabilities in the description itself (generate attestations, verify canonical digests and signatures, diff baselines with severity mapping) instead of only 'attestation and drift detection'.

Include natural synonyms users might say, such as 'posture check', 'integrity verification', or 'baseline comparison', to improve trigger-term coverage.

DimensionReasoningScore

Specificity

The description names the domain ("Hermes-only runtime security") and two concrete actions — "security attestation and drift detection" — but stops there, matching the anchor 'Names domain and 1-2 concrete actions, but not comprehensive'. It does not reach 4 because there are not 'several specific actions' (no mention of generating, verifying, or baseline comparison), and it is not 2 because the actions named are concrete rather than generic.

3 / 5

Completeness

The 'what' is clear (runtime security attestation and drift detection for Hermes infrastructure) but there is no 'Use when...' clause or equivalent trigger guidance, so completeness is capped at 3 per the judging guidelines. It is not 2 because the 'what' is specific rather than vague, and not 4 because 'when' is entirely absent rather than merely implicit-but-recoverable.

3 / 5

Trigger Term Quality

Relevant keywords are present ("security attestation", "drift detection", "Hermes", "runtime") and would be said by a user in this niche, but coverage is thin — no synonyms, no variations like "posture", "integrity check", "baseline", or file extensions/formats. This matches 'Some relevant keywords but missing common variations or synonyms', not 4 which requires good coverage with only a few natural terms missing.

3 / 5

Distinctiveness Conflict Risk

"Hermes-only" plus the narrow attestation/drift-detection purpose establishes a clear niche with distinct triggers and minimal conflict risk with general security or document skills. The scope restriction ('Hermes-only', 'operator-managed Hermes infrastructure') makes accidental triggering for another skill unlikely.

5 / 5

Total

14

/

20

Passed

Validation

93%

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

Validation — 15 / 16 Passed

Validation for skill structure

CriteriaDescriptionResult

frontmatter_unknown_keys

Unknown frontmatter key(s) found; consider removing or moving to metadata

Warning

Total

15

/

16

Passed

Repository

prompt-security/clawsec

Path

skills/hermes-attestation-guardian/SKILL.md

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.