CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

clawrouter

Hosted-gateway LLM router — save 84% on inference costs. A local proxy that forwards each request to the blockrun.ai gateway, which routes to the cheapest capable model across 91 models from OpenAI, Anthropic, Google, DeepSeek, xAI, Z.AI, and more. Free open-weight models included. Also exposes realtime market data (global stocks, crypto, FX, commodities), Twitter/X intelligence, prediction-market data across Polymarket, Kalshi, Limitless, Opinion, Predict.Fun, dFlow + UMA oracle resolution + wallet identity & clustering, phone-number intelligence (carrier + SIM-swap fraud detection) plus AI-powered outbound voice calls (Twilio + Bland.ai) as built-in agent tools. Not a local-inference tool — prompts are sent to the blockrun.ai gateway.

Quality

64%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide
SecuritybySnyk

Medium

Suggest reviewing before use

Fix and improve this skill with Tessl

tessl review fix ./skills/clawrouter/SKILL.md
SKILL.md
Quality
Evals
Security

Quality

Content

56%Weight 40%Scale 1-5

Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.

The body is highly actionable, with concrete install/setup/CLI/slash commands, live price-lookup instructions, and explicit safety gating for real-money and real-world-side-effect tools, and its workflows are clearly sequenced. Its weaknesses are token efficiency (an inline 91-model catalog plus version/date-dense asides) and progressive disclosure (heavy catalogs inline and sibling-skill references that are not clearly linked).

Suggestions

Move the 91-model catalog and per-model annotations into a reference file (e.g., references/models.md), keeping only the tier defaults and a pointer in SKILL.md.

Add an executable example of the core integration: the local proxy's base URL/port and a sample OpenAI-compatible request routed through it.

Convert the bare "phone" / "predexon" / "polymarket-trading" skill mentions into real links with paths, and move version/date-stamped detail (Seedance rates, "since 2026-06-01") into those references.

DimensionReasoningScore

Conciseness

Noticeably verbose: a ~600-word single-paragraph catalog of 91 models with per-model annotations, Seedance minutiae ("~20,256 tokens/sec at the 720p+audio default — 2× the prior 480p rate"), and a meta-paragraph explaining why per-tier savings aren't quoted. The rubric directs penalizing dense time-sensitive version/date detail ("Router Core V3.4", "since 2026-06-01", many pinned model versions), which together with the padded sections places it at anchor 2 rather than 3.

2 / 5

Actionability

Concrete, executable guidance throughout: "openclaw plugins install @blockrun/clawrouter", "openclaw models set blockrun/auto", curl commands for the live catalog, "/cr-call +1<E.164> \"<task>\" [--voice nat]", and per-tool prices and parameters. It is not anchor 5 because the core integration step — how a client actually points at the local proxy (base URL/port, OpenAI-compatibility) — has no executable example, and blockrun_polymarket's arguments beyond action: are only sketched.

4 / 5

Workflow Clarity

Install → Setup → routing is clearly sequenced, and risky operations have real checkpoints: polymarket trading hard-requires "confirm:true" (omit → dry-run preview) with per-order caps, and voice calls are fire-and-forget with explicit "Poll blockrun_voice_status every 10–30s" guidance and an only-when-asked rule. It falls short of anchor 5 because there is no verification step for the install/setup path (e.g., a first test call) and no error-recovery loop for payment/402 failures.

4 / 5

Progressive Disclosure

Sections are well-organized with headers, but content that belongs in reference files is inlined — the 91-model catalog, the 8-row billing-mode pricing table, and six dense tool tables — matching anchor 3's "content that should be separate is inline". Cross-references are also unevenly signaled: "the phone skill", "the predexon skill", and "the polymarket-trading skill" are bare backticks with no paths, and only docs/routing-profiles.md is a real link (pointing outside the skill directory), so it does not reach anchor 4.

3 / 5

Total

13

/

20

Passed

Description

62%Weight 40%Scale 1-5

Based on the skill's description, can an agent find and select it at the right time? Clear, specific descriptions lead to better discovery.

The description clearly communicates what ClawRouter does, with many concrete capabilities and good natural keyword coverage. Its weaknesses are the missing explicit "Use when..." trigger guidance (which caps completeness) and its breadth across finance, prediction-market, phone, and voice domains, which creates genuine overlap risk with single-purpose skills.

Suggestions

Add an explicit trigger clause, e.g., "Use when the user wants to cut LLM API costs, route requests to the cheapest capable model, or access BlockRun's market/prediction-market/phone data tools."

Narrow the tool-domain claims (e.g., "plus BlockRun data and voice tools — see the tool list") so generic finance or phone-lookup requests don't trigger this skill over dedicated ones.

Include common user phrasings such as "save on API costs" or "cheap LLM gateway" alongside the existing keywords.

DimensionReasoningScore

Specificity

Quotes: "forwards each request to the blockrun.ai gateway, which routes to the cheapest capable model across 91 models" and "phone-number intelligence (carrier + SIM-swap fraud detection) plus AI-powered outbound voice calls" — many concrete, specific capabilities. It falls short of anchor 5 because "Twitter/X intelligence" and the "save 84%" lead are vague or marketing-flavored, and the actions are feature enumeration with minor coverage gaps.

4 / 5

Completeness

The "what" is explicit (local proxy forwarding to the blockrun.ai gateway for cheapest-model routing, plus data/phone/voice agent tools), but there is no "Use when..." clause or equivalent explicit trigger guidance in the description — the rubric caps completeness at 3 for this. It is not a 4 because the "when" is only weakly implied by the cost-savings framing.

3 / 5

Trigger Term Quality

Contains natural phrases users would say: "LLM router", "inference costs", "cheapest capable model", "stocks, crypto, FX, commodities", "Polymarket, Kalshi", "SIM-swap fraud detection", "outbound voice calls". Good coverage, but common variations like "API costs", "token costs", or "AI gateway" are missing, so it fits anchor 4 rather than the comprehensive anchor 5.

4 / 5

Distinctiveness Conflict Risk

The core identity ("Hosted-gateway LLM router", blockrun.ai) is a clear niche, but the description also claims market data, crypto, prediction markets, phone verification, and voice calls — domains where standalone skills plausibly exist, so a request like "get the BTC price" could trigger this over a dedicated skill. Overlap risk is more than minor, matching anchor 3 rather than 4.

3 / 5

Total

14

/

20

Passed

Validation

75%

Checks the skill against the spec for correct structure and formatting. All validation checks must pass before discovery and implementation can be scored.

Validation — 12 / 16 Passed

Validation for skill structure

CriteriaDescriptionResult

metadata_version

'metadata.version' is missing

Warning

metadata_field

'metadata' should map string keys to string values

Warning

frontmatter_unknown_keys

Unknown frontmatter key(s) found; consider removing or moving to metadata

Warning

relative_links

Relative link issues: 1 suspicious

Warning

Total

12

/

16

Passed

Repository

BlockRunAI/ClawRouter

Path

skills/clawrouter/SKILL.md

Reviewed

Table of Contents

Is this your skill?

If you maintain this skill, you can claim it as your own. Once claimed, you can manage eval scenarios, bundle related skills, attach documentation or rules, and ensure cross-agent compatibility.