BB power_oracle
Use when the user wants Power Oracle to compute workout work or power from structured or shorthand workout details. Do not use for coaching or general fitness advice.
Do not use for coaching or general fitness advice.
As a process B 65/100 · Nearly there — weak spots: result and completion, consistency, progress reporting
IntegrationSoftware developmentAI and agentstype and topics are labelled automatically from the skill text
How to improve
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: 3. Evidence is masked. Grey chips explain why severity was lowered.
Against the Agent Skills spec
- warning
name-formatname should be kebab-case (lowercase letters, digits, hyphens) - note
frontmatter-keyunknown frontmatter key "homepage"
Process rating: all ten parameters 65/100
- 0Result and completion. Does not say what the result is
- 0Progress reporting. Says nothing while it works
- 40Consistency. Frontmatter name (power_oracle) differs from the folder (power-oracle)
- 60Tools and files. Uses tools (web) that frontmatter does not declare
- 60Failures and branches. 2 branches
- 70Inputs and preconditions. Inputs and preconditions are listed
- 100Steps. 24 steps
- 100When it triggers. States when to use and when not to
- 100Execution cost. Instruction body is 796 tokens
- 100Running it twice. No mutating operations
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
- +4No input/output examples
- +1No license
- +2Single-language instructions
- +4Description says when NOT to use the skill
- +3Description length 166: enough signal without eating the budget
- +4Structure: 7 headings
- +3Step-by-step instructions: 24 items
- +4Reference files are cited in the instructions (1 of 1)
Quality base 70; lint remarks subtract, signals add up to 100. Result: 82.
External checks
ClawHub: suspicious
The skill is coherent for a paid workout-power API, but it can send personal fitness data and authorize x402 payments without requiring explicit per-transaction user approval.
LLM: suspicious (high) · VirusTotal: · 16 Sept 2026