BF supstack
Evidence-based supplement intelligence powered by the SupStack database (220 supplements, 7,780+ studies, 21 health goals). Use when the user asks about supplements, vitamins, minerals, nootropics, adaptogens, mushrooms, amino acids, probiotics, dosing, safety, drug interactions, evidence quality, mechanisms of action, stack building, or health goal optimization through supplementation. Triggers on: "what should I take for", "is [X] safe", "best supplement for [goal]", "evidence for", "how much [supplement]", "can I take [X] with [Y]", "supplement for sleep/energy/focus/recovery", "my stack", "what pairs well with", "drug interaction", "side effects of", "studies on [supplement]", "evidence score", "clinical evidence", "keep me updated", "new research", "research monitor", "track studies", "latest studies on my stack", "experiment", "track my progress", "is it working", "try this supplement", "test if it works", "when should I take", "timing", "optimise my stack", "optimize timing", "what can you do", "what is supstack", "help me with supplements", "supplement help", "stack check", "what's good for", "anything new on", "should I stop taking", "how's my experiment", "how long until it works", "worth taking", "is it worth it", "should I add", "any side effects".
As a process F 65/100 · Will not run — References files that are not bundled: url
How to improve
- Shorten the description to 1024 characters.
- The SKILL.md body is over 5,000 tokens: move reference detail into references/ and load it when needed.
- The text references files that are not there: add them or drop the references.
- 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: 6. Evidence is masked. Grey chips explain why severity was lowered.
Against the Agent Skills spec
- error
description-longdescription is 1281 chars, limit 1024 - warning
body-longSKILL.md body ≈ 14626 tokens (recommended < 5000); move details to references/ - warning
missing-refreference to a missing file: url
Process rating: all ten parameters 65/100
- 0Tools and files. 1 referenced file(s) missing: url
- 0Inputs and preconditions. Does not say what the process needs to start
- 40Execution cost. Instruction body is 14626 tokens: crowds the task out of the window
- 85Steps. 209 steps, 1 vague phrases
- 100Result and completion. Output format and completion criterion are stated
- 100When it triggers. States when to use and when not to
- 100Failures and branches. 27 branches, has a failure section
- 100Consistency. Name and required fields are in place
- 100Running it twice. Mutating operations check current state
- 100Progress reporting. Reports progress
- medium Safety rules and hard prohibitions inside a skill: they belong in the system prompt, here they protect nothing
- low 26 top-level sections: this looks like several domains in one skill
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
- +4Description does not say when NOT to use the skill (false activations)
- +3Description length 1280: 120–800 characters recommended
- -214 emoji in the instructions: noise for the model
- +1No license
- +2Single-language instructions
- +5Description quotes 42 example trigger phrases
- +4Structure: 95 headings
- +3Step-by-step instructions: 209 items
- +3Output format is stated explicitly
- +4Has examples (60 code blocks)
- +3All 1 scripts are documented
Quality base 70; lint remarks subtract, signals add up to 100. Result: 49.