BC hermes-code-bridge
Use when connecting Hermes Agent to local coding CLIs such as Codex, Kimi Code, Claude Code, OpenCode, Gemini CLI, or other terminal-based coding assistants. Provides a general bridge workflow for discovering agents, reusing sessions, dispatching prompts, monitoring execution, collecting evidence, and reporting results without pretending Hermes did the delegated work.
Provides a general bridge workflow for discovering agents, reusing sessions, dispatching prompts, monitoring execution, collecting evidence, and reporting…
As a process C 60/100 · Has gaps — weak spots: result and completion, inputs and preconditions, running it twice
How to improve
- For Hermes the description must be one sentence under 60 characters; move the conditions to a "When to Use" section.
- The SKILL.md body is over 5,000 tokens: move reference detail into references/ and load it when needed.
- 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: 2. Evidence is masked. Grey chips explain why severity was lowered.
Against the Agent Skills spec
- warning
description-long-hermesdescription is 370 chars; the Hermes authoring standard requires ≤ 60 (one sentence, ending with a period) - warning
body-longSKILL.md body ≈ 5951 tokens (recommended < 5000); move details to references/
Process rating: all ten parameters 60/100
- 0Inputs and preconditions. Does not say what the process needs to start
- 30Running it twice. 21 mutating operations with no state check
- 40Result and completion. Does not say what the result is
- 60Tools and files. Uses tools (bash) that frontmatter does not declare
- 60Consistency. The Hermes dialect needs category and tags
- 70Failures and branches. 6 branches
- 70Execution cost. Instruction body is 5951 tokens
- 85Steps. 113 steps, 1 vague phrases
- 100When it triggers. States when to use and when not to
- 100Progress reporting. Reports progress
- medium Safety rules and hard prohibitions inside a skill: they belong in the system prompt, here they protect nothing
- low 20 top-level sections: this looks like several domains in one skill
- low The response is described with custom markup (4 tags): a typed call is more reliable
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
- +3Output format is not stated: the model decides each time
- +2Single-language instructions
- +4Description says when NOT to use the skill
- +3Description length 370: enough signal without eating the budget
- +4Structure: 31 headings
- +3Step-by-step instructions: 113 items
- +4Has examples (27 code blocks)
- +1License stated
Quality base 70; lint remarks subtract, signals add up to 100. Result: 73.