AD fb-car-service-skill
企业用车服务助手，支持即时用车、预约用车、接送机、包车等多种用车场景，提供车型选择、费用预估、订单管理等功能。Invoke when user needs to book a car, schedule a ride, airport transfer, or manage car service orders.
As a process D 46/100 · Unfinished process — weak spots: result and completion, when it triggers, inputs and preconditions
The same skill appears in 4 more places: ClawHub, ClawHub, ClawHub, ClawHub
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 · 0
✓ No critical or high findings
Files scanned: 4. 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 46/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
- 20When it triggers. No condition that starts the skill
- 30Running it twice. 5 mutating operations with no state check
- 40Consistency. Frontmatter name (fb-car-service-skill) differs from the folder (instant-ride)
- 100Tools and files. No external tools needed
- 100Steps. 52 steps
- 100Execution cost. Instruction body is 1647 tokens
- low 12 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
- +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
- -32 of 2 scripts are never mentioned in SKILL.md
- +1No license
- +2Single-language instructions
- +3Description length 157: enough signal without eating the budget
- +4Structure: 26 headings
- +3Step-by-step instructions: 52 items
- +4Has examples (4 code blocks)
Quality base 70; lint remarks subtract, signals add up to 100. Result: 81.