SKILLEMALL.ai

CD oura

(no description)

sundial-org/awesome-openclaw-skills Agent Skills author: sundial-org 1 file body ≈ 927 tokens Open the sourcegithub.com analyzed 2 d ago

This tool allows retrieving health and biometric data from the Oura Ring API (V2) via a command-line interface.

As a process D 46/100 · Unfinished process — weak spots: result and completion, when it triggers, failures and branches

IntegrationGitHubAI and agentsSoftware developmenttype and topics are labelled automatically from the skill text
JSON
Technical rating
C
74/100
safety, quality, tests
Safety 60%
100
Quality 40%
34
Run on models
none yet
Process rating
D
46/100
Unfinished process
Result and completion w 14
0
When it triggers w 12
0
Failures and branches w 10
0
the three weakest of ten parameters · all ten

How to improve

  1. Add a description to the frontmatter: without it the skill never triggers.
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: 1. Evidence is masked. Grey chips explain why severity was lowered.

Against the Agent Skills spec

  • error description-missing SKILL.md: no `description` — the skill can never trigger

Process rating: all ten parameters 46/100

  • 0Result and completion. Does not say what the result is
  • 0When it triggers. No condition that starts the skill
  • 0Failures and branches. Linear process with no failure handling
  • 0Progress reporting. Says nothing while it works
  • 30Running it twice. 2 mutating operations with no state check
  • 60Tools and files. Uses tools (bash) that frontmatter does not declare
  • 70Inputs and preconditions. Inputs and preconditions are listed
  • 85Steps. 27 steps, 1 vague phrases
  • 100Consistency. Name and required fields are in place
  • 100Execution cost. Instruction body is 927 tokens
  • low The response is described with custom markup (3 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)
  • +3Description length 0: 120–800 characters recommended
  • +3Output format is not stated: the model decides each time
  • -2localhost URLs: will not work for another user
  • +1No license
  • +2Single-language instructions
  • +4Structure: 12 headings
  • +3Step-by-step instructions: 27 items
  • +4Has examples (6 code blocks)

Quality base 70; lint remarks subtract, signals add up to 100. Result: 34.