AB auteur
Design and build cinematic, award-level web pages.
Design and build cinematic, award-level web pages.
As a process B 65/100 · Nearly there — weak spots: result and completion, running it twice, progress reporting
GeneratorPlaywrightSoftware developmentData and analyticsMarketingtype and topics are labelled automatically from the skill text
Runs in: Hermes Agent
How to improve
- The SKILL.md body is over 5,000 tokens: move reference detail into references/ and load it when needed.
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: 27. Evidence is masked. Grey chips explain why severity was lowered.
Against the Agent Skills spec
- warning
body-longSKILL.md body ≈ 5506 tokens (recommended < 5000); move details to references/
Process rating: all ten parameters 65/100
- 0Progress reporting. Says nothing while it works
- 30Running it twice. 26 mutating operations with no state check
- 40Result and completion. Does not say what the result is
- 50When it triggers. No condition that starts the skill
- 60Tools and files. Uses tools (bash, web, node) that frontmatter does not declare
- 60Consistency. The Hermes dialect needs category and tags
- 70Inputs and preconditions. Inputs and preconditions are listed
- 70Execution cost. Instruction body is 5506 tokens
- 100Steps. 56 steps
- 100Failures and branches. 1 branches, has a failure section
- medium Safety rules and hard prohibitions inside a skill: they belong in the system prompt, here they protect nothing
- low The response is described with custom markup (3 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
- +3Description length 50: 120–800 characters recommended
- +3Output format is not stated: the model decides each time
- +4No input/output examples
- +2Single-language instructions
- +4Description says when NOT to use the skill
- +4Structure: 18 headings
- +3Step-by-step instructions: 56 items
- +4Reference files are cited in the instructions (11 of 11)
- +3All 8 scripts are documented
- +1License stated
Quality base 70; lint remarks subtract, signals add up to 100. Result: 79.