AB readdy
This skill should be used when the user asks to "create a website", "generate a website", "build a website", "modify a website", "update my Readdy project", "preview my website", "delete a project", "list my projects" or mentions Readdy.ai project management. Provides CLI-based website creation and management through the Readdy.ai platform. Requires a Readdy API Key. Run: node scripts/readdy.mjs config --apiKey <your-key> to configure.
As a process B 71/100 · Nearly there — weak spots: result and completion, consistency, running it twice
How to improve
- 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: 6. Evidence is masked. Grey chips explain why severity was lowered.
Against the Agent Skills spec
✓ No remarks against the Agent Skills spec
Process rating: all ten parameters 71/100
- 0Result and completion. Does not say what the result is
- 30Running it twice. 10 mutating operations with no state check
- 40Consistency. Frontmatter name (readdy) differs from the folder (readdy-website-builder)
- 60Tools and files. Uses tools (bash, web, node) that frontmatter does not declare
- 100Steps. 13 steps
- 100When it triggers. States when to use and when not to
- 100Inputs and preconditions. Inputs and preconditions are listed
- 100Failures and branches. 3 branches, has a failure section
- 100Execution cost. Instruction body is 1518 tokens
- 100Progress reporting. Reports progress
- 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 (8 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
- +4Description does not say when NOT to use the skill (false activations)
- +3Output format is not stated: the model decides each time
- -4Absolute local paths (C:\Users, /home/…): not portable
- +1No license
- +2Single-language instructions
- +5Description quotes 8 example trigger phrases
- +3Description length 439: enough signal without eating the budget
- +4Structure: 11 headings
- +3Step-by-step instructions: 13 items
- +4Has examples (5 code blocks)
- +4Reference files are cited in the instructions (1 of 1)
- +3All 2 scripts are documented
Quality base 70; lint remarks subtract, signals add up to 100. Result: 92.