BF revdoku
Create, update, and publish websites with Revdoku buckets — including interactive app sites backed by a per-bucket server database (visitor submissions, voting/feedback dashboards, searchable support sites, owner notifications), not just static pages. Store files privately until the user asks for a public or protected link.
Create, update, and publish websites with Revdoku buckets — including interactive app sites backed by a per-bucket server database (visitor submissions…
As a process F 59/100 · Will not run — References files that are not bundled: assets/app.css, templates/app-safe-actions.json, templates/app-frontend-example/
How to improve
- Say in the description WHEN to use the skill ("use when…", example requests): that is the agent's main cue.
- The SKILL.md body is over 5,000 tokens: move reference detail into references/ and load it when needed.
- The text references files that are not there: add them or drop the references.
- 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
body-longSKILL.md body ≈ 8715 tokens (recommended < 5000); move details to references/ - warning
missing-refreference to a missing file: assets/app.css - warning
missing-refreference to a missing file: templates/app-safe-actions.json - warning
missing-refreference to a missing file: templates/app-frontend-example/
Process rating: all ten parameters 59/100
- 0Tools and files. 3 referenced file(s) missing: assets/app.css, templates/app-safe-actions.json, templates/app-frontend-example/
- 0Result and completion. Does not say what the result is
- 40Execution cost. Instruction body is 8715 tokens: crowds the task out of the window
- 70Inputs and preconditions. Inputs and preconditions are listed
- 85Steps. 95 steps, 1 vague phrases
- 100When it triggers. States when to use and when not to
- 100Failures and branches. 9 branches, has a failure section
- 100Consistency. Name and required fields are in place
- 100Running it twice. Mutating operations check current state
- 100Progress reporting. Reports progress
- medium Safety rules and hard prohibitions inside a skill: they belong in the system prompt, here they protect nothing
- high The skill tells the model to perform an irreversible action with no human approval
- low The response is described with custom markup (9 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)
- +3Output format is not stated: the model decides each time
- -31 of 1 scripts are never mentioned in SKILL.md
- +1No license
- +2Single-language instructions
- +3Description length 325: enough signal without eating the budget
- +4Structure: 11 headings
- +3Step-by-step instructions: 95 items
- +4Has examples (4 code blocks)
Quality base 70; lint remarks subtract, signals add up to 100. Result: 47.