AB ultrahuman-analytics
Advanced Ultrahuman analytics, trends, predictions, and reports. Use this skill when the user asks for weekly report, 7-day summary, recovery trend, sleep consistency, metabolic week, VO2 or movement trend, deep/REM balance, tomorrow readiness, training load check, low-recovery alert, glucose spike risk, sleep-glucose link, sleep-recovery link, rest day effect, weekday vs weekend, PDF summary, coach view, monthly one-pager, best night of the week, streak, personal record, or weekly MVP. Use for any multi-day analysis, prediction, correlation, or export from Ultrahuman ring/CGM data.
As a process B 66/100 · Nearly there — weak spots: result and completion, 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: 2. Evidence is masked. Grey chips explain why severity was lowered.
Against the Agent Skills spec
- note
frontmatter-keyunknown frontmatter key "created" - note
frontmatter-keyunknown frontmatter key "updated"
Process rating: all ten parameters 66/100
- 0Result and completion. Does not say what the result is
- 30Running it twice. 2 mutating operations with no state check
- 60Tools and files. Uses tools (web) that frontmatter does not declare
- 70When it triggers. States when to use, but not when not to
- 70Inputs and preconditions. Inputs and preconditions are listed
- 70Failures and branches. 16 branches
- 100Steps. 84 steps
- 100Consistency. Name and required fields are in place
- 100Execution cost. Instruction body is 3262 tokens
- 100Progress reporting. Reports progress
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
- +4No input/output examples
- +1No license
- +2Single-language instructions
- +3Description length 589: enough signal without eating the budget
- +4Structure: 29 headings
- +3Step-by-step instructions: 84 items
Quality base 70; lint remarks subtract, signals add up to 100. Result: 78.