BF hou-tea-store
Browse, recommend, and purchase Chinese tea from hou-tea.com using the agent-native API (https://hou-tea.com/api/agent/catalog) and x402 USDC payments. Activate when user mentions tea/茶/红茶/绿茶/白茶/普洱/乌龙/龙井/茶叶/hou-tea/候茶/买茶/送茶/推荐茶 or asks for tea recommendations. ALWAYS call the API first — never invent products from prior knowledge.
As a process F 46/100 · Will not run — References files that are not bundled: {hero_image}, {target}
How to improve
- 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 · 4
✓ No critical or high findings
Medium and low: 4
-
low Secrets in code
secret-high-entropy-tokenSKILL.md:109High-entropy token-like string (may be an id, hash or a credential) (quoted — discussed, not commanded)"to": "0x9d…A54",
quoted -
low Secrets in code
secret-high-entropy-tokenSKILL.md:110High-entropy token-like string (may be an id, hash or a credential) (quoted — discussed, not commanded)"asset": "0x83…913",
quoted -
low Secrets in code
secret-high-entropy-tokenSKILL.md:125High-entropy token-like string (may be an id, hash or a credential) (quoted — discussed, not commanded)- **Recipient:** `0x9d…A54`
quoted -
low Secrets in code
secret-high-entropy-tokenSKILL.md:126High-entropy token-like string (may be an id, hash or a credential) (quoted — discussed, not commanded)- **USDC contract (Base):** `0x83…913`
quoted
Files scanned: 2. Evidence is masked. Grey chips explain why severity was lowered.
Against the Agent Skills spec
- warning
missing-refreference to a missing file: {hero_image} - warning
missing-refreference to a missing file: {target}
Process rating: all ten parameters 46/100
- 0Tools and files. 2 referenced file(s) missing: {hero_image}, {target}
- 0Result and completion. Does not say what the result is
- 0Inputs and preconditions. Does not say what the process needs to start
- 0Progress reporting. Says nothing while it works
- 30Running it twice. 1 mutating operations with no state check
- 50When it triggers. No condition that starts the skill
- 100Steps. 38 steps
- 100Failures and branches. 2 branches, has a failure section
- 100Consistency. Name and required fields are in place
- 100Execution cost. Instruction body is 2621 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
- +1No license
- +2Single-language instructions
- +3Description length 332: enough signal without eating the budget
- +4Structure: 21 headings
- +3Step-by-step instructions: 38 items
- +4Has examples (16 code blocks)
Quality base 70; lint remarks subtract, signals add up to 100. Result: 75.