AD wellness
A personal Wellness hub for OpenClaw. Use when users want an all-in-one way to connect their health/wellness apps and devices (wearables, workouts, sleep, nutrition, weight, vitals) and get unified daily/weekly summaries, insights, and reminders inside OpenClaw (any chat channel). Guides users to add data sources via official personal OAuth/API keys (Tier 1) or via phone OS health aggregators like Apple Health / Android Health Connect (Tier 2).
As a process D 45/100 · Unfinished process — weak spots: result and completion, inputs and preconditions, failures and branches
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 · 4
✓ No critical or high findings
Medium and low: 4
-
low Exfiltration
exfil-webhook-urlreferences/bridge.md:27Webhook / callback URL commonly used for exfiltration (verify the destination) (placeholder value)Cloudflared prints a `https://...trycloudflare.com` URL. That is your **Sync URL**.
placeholder -
low Exfiltration
exfil-webhook-urlreferences/bridge.md:37Webhook / callback URL commonly used for exfiltration (verify the destination) (placeholder value)ngrok prints a public `https://...ngrok-free.app` URL. That is your **Sync URL**.
placeholder -
low Exfiltration
exfil-webhook-urlreferences/exporter-ios-shortcuts.md:20Webhook / callback URL commonly used for exfiltration (verify the destination) (placeholder value)- Ask for Input (Text): **Sync URL** (e.g. `https://xxxxx.trycloudflare.com`)
placeholder -
low Exfiltration
exfil-webhook-urlscripts/bridge_test_client.py:25Webhook / callback URL commonly used for exfiltration (verify the destination) (placeholder value)ap.add_argument("--url", required=True, help="Tunnel base URL, e.g. https://xxxxx.trycloudflare.com")placeholder
Files scanned: 13. 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 45/100
- 0Result and completion. Does not say what the result is
- 0Inputs and preconditions. Does not say what the process needs to start
- 0Failures and branches. Linear process with no failure handling
- 0Progress reporting. Says nothing while it works
- 30Running it twice. 3 mutating operations with no state check
- 50When it triggers. No condition that starts the skill
- 60Tools and files. Uses tools (web) that frontmatter does not declare
- 85Steps. 27 steps, 1 vague phrases
- 100Consistency. Name and required fields are in place
- 100Execution cost. Instruction body is 622 tokens
- medium Safety rules and hard prohibitions inside a skill: they belong in the system prompt, here they protect nothing
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
- -32 of 4 scripts are never mentioned in SKILL.md
- +1No license
- +2Single-language instructions
- +3Description length 448: enough signal without eating the budget
- +4Structure: 6 headings
- +3Step-by-step instructions: 27 items
- +4Reference files are cited in the instructions (7 of 7)
Quality base 70; lint remarks subtract, signals add up to 100. Result: 81.