AB hybrid-training-plan
Read and update the user's own Hybrid Training Plan account (hybridtrainingplan.app) — today's and upcoming sessions with suggested weights, log strength sets, runs and rows, mark days complete or skipped, read and set exercise 1RMs. Use only when the user asks about their Hybrid Training Plan, their scheduled sessions, or wants a workout recorded there. Not for general fitness or training advice.
Read and update the user's own Hybrid Training Plan account (hybridtrainingplan.app) — today's and upcoming sessions with suggested weights, log strength…
As a process B 68/100 · Nearly there — weak spots: result and completion, inputs and preconditions, 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 · 1
✓ No critical or high findings
Medium and low: 1
-
low Exfiltration
net-credential-usescripts/htp.sh:23Credential used in a network call (verify the destination is the intended service) (detector / deny-list definition)printf 'Authorization: Bearer %s\n' "$API_KEY" | curl "${args[@]}" "$API_URL$path"detector
Files scanned: 4. 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 68/100
- 0Result and completion. Does not say what the result is
- 0Inputs and preconditions. Does not say what the process needs to start
- 30Running it twice. 4 mutating operations with no state check
- 55Failures and branches. 1 branches
- 100Tools and files. Tools declared in frontmatter
- 100Steps. 7 steps
- 100When it triggers. States when to use and when not to
- 100Consistency. Name and required fields are in place
- 100Execution cost. Instruction body is 916 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 (7 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
- +3Output format is not stated: the model decides each time
- +1No license
- +2Single-language instructions
- +4Description says when NOT to use the skill
- +3Description length 400: enough signal without eating the budget
- +4Structure: 6 headings
- +3Step-by-step instructions: 7 items
- +4Has examples (2 code blocks)
- +4Reference files are cited in the instructions (1 of 1)
- +3All 1 scripts are documented
Quality base 70; lint remarks subtract, signals add up to 100. Result: 95.