BF ride
Ambient Ride skill for TADA/Throo ride-hailing and taxi service. Wallet, USDC bridge status and recovery, deposit, collateral, ride, payment, chat, and tipping workflows; use it for wallet balances, starting and resuming USDC bridges, and bridge progress.
Ambient Ride skill for TADA/Throo ride-hailing and taxi service.
As a process F 57/100 · Will not run — References files that are not bundled: url, <approval_url>, references/wallet.md
How to improve
- 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: 0. Evidence is masked. Grey chips explain why severity was lowered.
Against the Agent Skills spec
- warning
body-longSKILL.md body ≈ 15012 tokens (recommended < 5000); move details to references/ - warning
missing-refreference to a missing file: url - warning
missing-refreference to a missing file: <approval_url> - warning
missing-refreference to a missing file: references/wallet.md - warning
missing-refreference to a missing file: references/usage.md - warning
missing-refreference to a missing file: references/ride.md - warning
missing-refreference to a missing file: references/member-payment.md - warning
missing-refreference to a missing file: references/chat.md - warning
missing-refreference to a missing file: references/tip.md
Process rating: all ten parameters 57/100
- 0Tools and files. 8 referenced file(s) missing: url, <approval_url>, references/wallet.md
- 30Inputs and preconditions. Does not say what the process needs to start
- 40Execution cost. Instruction body is 15012 tokens: crowds the task out of the window
- 50When it triggers. No condition that starts the skill
- 60Result and completion. Output format stated, no completion criterion
- 85Steps. 56 steps, 1 vague phrases
- 100Failures and branches. 16 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 13 top-level sections: this looks like several domains in one skill
- low The response is described with custom markup (39 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)
- +1No license
- +2Single-language instructions
- +3Description length 255: enough signal without eating the budget
- +4Structure: 16 headings
- +3Step-by-step instructions: 56 items
- +3Output format is stated explicitly
- +4Has examples (16 code blocks)
Quality base 70; lint remarks subtract, signals add up to 100. Result: 65.