BF triphasic-execution
Execute→Review→Advance 三步循环执行框架。增强步骤规划能力、增强语义理解；明确空转/重试/换思路/求助完整流转规则；最多重试3次、最多空转3次强制约束。
As a process F 40/100 · Will not run — References files that are not bundled: references/*.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: 20. Evidence is masked. Grey chips explain why severity was lowered.
Against the Agent Skills spec
- warning
description-long-hermesdescription is 87 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: references/*.md - note
frontmatter-keyunknown frontmatter key "trigger" - note
frontmatter-keyunknown frontmatter key "trigger_negative" - note
frontmatter-keyunknown frontmatter key "sensitive_access" - note
frontmatter-keyunknown frontmatter key "critical_write" - note
frontmatter-keyunknown frontmatter key "permission_weight" - note
frontmatter-keyunknown frontmatter key "data_dir" - note
frontmatter-keyunknown frontmatter key "external_data_dir" - note
frontmatter-keyunknown frontmatter key "meta_field_sync" - note
frontmatter-keyunknown frontmatter key "h1_position"
Process rating: all ten parameters 40/100
Will not run. References files that are not bundled: references/*.md
- 0Tools and files. 1 referenced file(s) missing: references/*.md
- 0Result and completion. Does not say what the result is
- 0Inputs and preconditions. Does not say what the process needs to start
- 0Progress reporting. Says nothing while it works
- 20When it triggers. No condition that starts the skill
- 50Failures and branches. 0 branches, has a failure section
- 100Steps. 18 steps
- 100Consistency. Name and required fields are in place
- 100Execution cost. Instruction body is 1548 tokens
- 100Running it twice. No mutating operations
- low 11 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)
- +3Description length 87: 120–800 characters recommended
- +3Output format is not stated: the model decides each time
- -231 emoji in the instructions: noise for the model
- -35 of 8 scripts are never mentioned in SKILL.md
- +2Single-language instructions
- +4Structure: 14 headings
- +3Step-by-step instructions: 18 items
- +4Has examples (5 code blocks)
- +4Reference files are cited in the instructions (5 of 7)
- +1License stated
Quality base 70; lint remarks subtract, signals add up to 100. Result: 54.
External checks
ClawHub: suspicious
This skill is a disclosed execution-workflow helper, but it adds broad command interception, persistent logging, optional background monitoring, and an unauthenticated local settings server that are under-declared and need careful review.
LLM: suspicious (high) · VirusTotal: · 25 Jun 2026