BF Xrouter
Xrouter is an open-source inference router that sits between OpenClaw and your LLM providers. It uses a fast, hardware-aware classifier to route each request to the most cost-effective model that c...
Xrouter is an open-source inference router that sits between OpenClaw and your LLM providers.
As a process F 35/100 · Will not run — References files that are not bundled: LICENSE, scripts/check_hw.js, scripts/configure_providers.js
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.
- 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: 2. Evidence is masked. Grey chips explain why severity was lowered.
Against the Agent Skills spec
- warning
name-formatname should be kebab-case (lowercase letters, digits, hyphens) - warning
description-no-whendescription does not say WHEN to use the skill (no "use when") - warning
missing-refreference to a missing file: LICENSE - warning
missing-refreference to a missing file: scripts/check_hw.js - warning
missing-refreference to a missing file: scripts/configure_providers.js - warning
missing-refreference to a missing file: scripts/cloud_model_catalog.json
Process rating: all ten parameters 35/100
- 0Tools and files. 4 referenced file(s) missing: LICENSE, scripts/check_hw.js, scripts/configure_providers.js
- 0Result and completion. Does not say what the result is
- 0Inputs and preconditions. Does not say what the process needs to start
- 20When it triggers. No condition that starts the skill
- 30Running it twice. 4 mutating operations with no state check
- 40Consistency. Frontmatter name (Xrouter) differs from the folder (clawhub-skill-2)
- 50Failures and branches. 0 branches, has a failure section
- 100Steps. 118 steps
- 100Execution cost. Instruction body is 2385 tokens
- 100Progress reporting. Reports progress
- low The response is described with custom markup (5 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)
- +4Structure: 1 headings, hard to scan
- +3Output format is not stated: the model decides each time
- -5Long text without headings
- -2localhost URLs: will not work for another user
- +1No license
- +2Single-language instructions
- +3Description length 200: enough signal without eating the budget
- +3Step-by-step instructions: 118 items
- +4Has examples (9 code blocks)
Quality base 70; lint remarks subtract, signals add up to 100. Result: 44.