SKILLEMALL.ai

BC withings

Use when linking Withings or reading Withings body measurements, activity, sleep, workout, heart, and intraday data.

asgeirtj/system_prompts_leaks Agent Skills author: asgeirtj CC0-1.0 4 files body ≈ 1 465 tokens Open the sourcegithub.com↗ analyzed 6 d ago

Query Withings body measurements, activity, sleep, and workout data via the bundled withings CLI.

As a process C 51/100 · Has gaps — References files that are not bundled: <connect_url>, <disconnect_url>

ProcedureData and analyticstype and topics are labelled automatically from the skill text
JSON
Technical rating
B
91/100
safety, quality, tests
Safety 60%
100
Quality 40%
78
Run on models
none yet
Process rating
C
51/100
Has gaps
References files that are not bundled: <connect_url>, <disconnect_url>
Tools and files w 18
0
Inputs and preconditions w 11
0
Progress reporting w 2
0
the three weakest of ten parameters · all ten

How to improve

  1. The text references files that are not there: add them or drop the references.
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: 4. Evidence is masked. Grey chips explain why severity was lowered.

Against the Agent Skills spec

  • warning missing-ref reference to a missing file: <connect_url>
  • warning missing-ref reference to a missing file: <disconnect_url>
  • note frontmatter-key unknown frontmatter key "icon"
  • note edit-residue the text marks something as outdated (lines 63, 67, 69): check that old rules are not kept next to new ones — the full check reads the text for contradictions

Process rating: all ten parameters 51/100

Will not run. References files that are not bundled: <connect_url>, <disconnect_url>
  • 0Tools and files. 2 referenced file(s) missing: <connect_url>, <disconnect_url>
  • 0Inputs and preconditions. Does not say what the process needs to start
  • 0Progress reporting. Says nothing while it works
  • 30Running it twice. 2 mutating operations with no state check
  • 60Result and completion. Output format stated, no completion criterion
  • 65Failures and branches. 3 branches
  • 70When it triggers. States when to use, but not when not to
  • 85Steps. 21 steps, 2 vague phrases
  • 100Consistency. Name and required fields are in place
  • 100Execution cost. Instruction body is 1465 tokens
  • 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

  • +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 116: 120–800 characters recommended
  • +1No license
  • +2Single-language instructions
  • +4Structure: 9 headings
  • +3Step-by-step instructions: 21 items
  • +3Output format is stated explicitly
  • +4Has examples (1 code blocks)
  • +4Reference files are cited in the instructions (1 of 1)

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