BF mediwise-health-suite
Family health management suite: health records, diet tracking, weight management, wearable sync. Local SQLite storage by default; optional cloud features require explicit setup.
As a process F 35/100 · Will not run — References files that are not bundled: LICENSE
How to improve
- Say in the description WHEN to use the skill ("use when…", example requests): that is the agent's main cue.
- 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 · 5
✓ No critical or high findings
Medium and low: 5
-
low Exfiltration
read-dotenvdocs/AGENT_SETUP.md:219Reads a .env filecp .env.example .env
-
low Exfiltration
read-dotenvdocs/INSTALLATION.md:65Reads a .env filecp .env.example .env
-
low Exfiltration
read-dotenvdocs/INSTALLATION.md:288Reads a .env filecp .env.example .env
-
low Exfiltration
read-dotenvQUICKSTART.md:150Reads a .env filecp .env.example .env
-
low Exfiltration
read-dotenvQUICKSTART.md:320Reads a .env filecp .env.example .env
Files scanned: 14. Evidence is masked. Grey chips explain why severity was lowered.
Against the Agent Skills spec
- warning
description-no-whendescription does not say WHEN to use the skill (no "use when") - warning
missing-refreference to a missing file: LICENSE - note
frontmatter-keyunknown frontmatter key "homepage" - note
frontmatter-keyunknown frontmatter key "repository" - note
frontmatter-keyunknown frontmatter key "keywords" - note
frontmatter-keyunknown frontmatter key "requires"
Process rating: all ten parameters 35/100
Will not run. References files that are not bundled: LICENSE
- 0Tools and files. 1 referenced file(s) missing: LICENSE
- 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
- 20When it triggers. No condition that starts the skill
- 100Steps. 48 steps
- 100Consistency. Name and required fields are in place
- 100Execution cost. Instruction body is 1465 tokens
- 100Running it twice. No mutating operations
- low 10 top-level sections: this looks like several domains in one skill
- 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)
- +3Output format is not stated: the model decides each time
- -2localhost URLs: will not work for another user
- -43 reference files, but SKILL.md never points to them: the model will not open them
- +2Single-language instructions
- +3Description length 177: enough signal without eating the budget
- +4Structure: 26 headings
- +3Step-by-step instructions: 48 items
- +4Has examples (10 code blocks)
- +1License stated
Quality base 70; lint remarks subtract, signals add up to 100. Result: 58.
External checks
ClawHub: suspicious
This health skill is mostly purpose-aligned, but it handles very sensitive health data with under-scoped multi-user access controls and some under-disclosed network and file-serving behavior.
LLM: suspicious (high) · VirusTotal: · 29 May 2026