BF hermes-share
Share Hermes skills with other users — package skills as ZIP, send via any messaging platform, or create temporary expiring download links. Peer-to-peer skill transfer without ClawHub or GitHub.
As a process F 35/100 · Will not run — References files that are not bundled: templates/*.md
How to improve
- Say in the description WHEN to use the skill ("use when…", example requests): that is the agent's main cue.
- For Hermes the description must be one sentence under 60 characters; move the conditions to a "When to Use" section.
- The text references files that are not there: add them or drop the references.
For the model run — optional
- Your own cases (evals/evals.json, 4–6 real requests with expected answers): the full check would then run those instead of a model-drafted suite.
- A spec.yaml with trigger phrases and assertions — a behaviour contract for CI; `skilltest init` writes a template.
Guard findings · 0
✓ No critical or high findings
Files scanned: 7. Evidence is masked. Grey chips explain why severity was lowered.
Against the Agent Skills spec
- warning
description-long-hermesdescription is 194 chars; the Hermes authoring standard requires ≤ 60 (one sentence, ending with a period) - warning
description-no-whenneither description nor a "## When to Use" section says when to use the skill - warning
missing-refreference to a missing file: templates/*.md - note
frontmatter-keyunknown frontmatter key "ar_description" - note
frontmatter-keyunknown frontmatter key "required_commands" - note
frontmatter-keyunknown frontmatter key "required_environment_variables" - note
frontmatter-keyunknown frontmatter key "required_privileges"
Process rating: all ten parameters 35/100
Will not run. References files that are not bundled: templates/*.md
- 0Tools and files. 1 referenced file(s) missing: templates/*.md
- 0Result and completion. Does not say what the result is
- 0Failures and branches. Linear process with no failure handling
- 0Progress reporting. Says nothing while it works
- 20When it triggers. No condition that starts the skill
- 30Running it twice. 8 mutating operations with no state check
- 60Consistency. The Hermes dialect needs category and tags
- 70Inputs and preconditions. Inputs and preconditions are listed
- 70Execution cost. Instruction body is 4062 tokens
- 100Steps. 47 steps
- medium Safety rules and hard prohibitions inside a skill: they belong in the system prompt, here they protect nothing
- low 10 top-level sections: this looks like several domains in one skill
Everything here is measured from the skill text rather than judged by a model, so the numbers are checkable. A parameter weighs more when it is a more common reason for the process to stall.
Quality signals
- +5Description has no quoted example phrases that should trigger the skill
- +4Description does not say when NOT to use the skill (false activations)
- +3Output format is not stated: the model decides each time
- -216 emoji in the instructions: noise for the model
- +2Single-language instructions
- +3Description length 194: enough signal without eating the budget
- +4Structure: 28 headings
- +3Step-by-step instructions: 47 items
- +4Has examples (13 code blocks)
- +4Reference files are cited in the instructions (2 of 2)
- +3All 2 scripts are documented
- +1License stated
Quality base 70; lint remarks subtract, signals add up to 100. Result: 63.
External checks
ClawHub: suspicious
This skill has a legitimate sharing purpose, but it automatically pushes skill archives to public file-sharing services and encourages one-step installation of received code into the agent’s active skills folder.
LLM: suspicious (high) · VirusTotal: suspicious · 27 May 2026