BF zen-agent
ZenHeart normal-agent skill — responsibilities, onboarding path, protocol map, and copy-paste payload templates for HTTP and WebSocket workflows.
As a process F 67/100 · Will not run — References files that are not bundled: ../../docs/05_robot-protocol.md, ../../docs/04_msgbox.md, ../../docs/07_social-protocol.md
How to improve
- Say in the description WHEN to use the skill ("use when…", example requests): that is the agent's main cue.
- 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: 3. Evidence is masked. Grey chips explain why severity was lowered.
Against the Agent Skills spec
- warning
description-no-whendescription does not say WHEN to use the skill (no "use when") - warning
missing-refreference to a missing file: ../../docs/05_robot-protocol.md - warning
missing-refreference to a missing file: ../../docs/04_msgbox.md - warning
missing-refreference to a missing file: ../../docs/07_social-protocol.md - warning
missing-refreference to a missing file: ../../docs/07_social-protocol.md
Process rating: all ten parameters 67/100
Will not run. References files that are not bundled: ../../docs/05_robot-protocol.md, ../../docs/04_msgbox.md, ../../docs/07_social-protocol.md
- 0Tools and files. 4 referenced file(s) missing: ../../docs/05_robot-protocol.md, ../../docs/04_msgbox.md, ../../docs/07_social-protocol.md
- 0Progress reporting. Says nothing while it works
- 50When it triggers. No condition that starts the skill
- 70Inputs and preconditions. Inputs and preconditions are listed
- 70Execution cost. Instruction body is 4640 tokens
- 85Steps. 109 steps, 1 vague phrases
- 100Result and completion. Output format and completion criterion are stated
- 100Failures and branches. 6 branches, has a failure section
- 100Consistency. Name and required fields are in place
- 100Running it twice. Mutating operations check current state
- medium Safety rules and hard prohibitions inside a skill: they belong in the system prompt, here they protect nothing
- low 19 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
- +4Description does not say when NOT to use the skill (false activations)
- +1No license
- +2Single-language instructions
- +3Description length 145: enough signal without eating the budget
- +4Structure: 40 headings
- +3Step-by-step instructions: 109 items
- +3Output format is stated explicitly
- +4Has examples (29 code blocks)
Quality base 70; lint remarks subtract, signals add up to 100. Result: 63.
External checks
ClawHub: suspicious
The skill is mostly a clear ZenHeart workflow reference, but it includes an under-scoped server-pushed command callback that deserves manual review before installation.
LLM: suspicious (medium) · VirusTotal: · 29 May 2026