data-routing

The single ROUTER for every data need. Load this skill BEFORE any backtest, data-fetch, or research task to pick the best available source/tool, honour auth (env) requirements, and avoid ban-risk providers.

Quality

79%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide

Securityby

Passed

No findings from the security scan

Fix and improve this skill with Tessl

tessl review fix ./agent/src/skills/data-routing/SKILL.md

Quality

Content

75%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 content is a well-structured, information-dense router reference with concrete tools, env keys, symbol formats, and validation/fallback guidance. It is consistently strong across dimensions, with only minor room to tighten redundancy and deepen the decision-tree executability.

Dimension	Reasoning	Score
Conciseness	The body is dense reference material with no concept padding and assumes Claude's competence, but the Source Overview and Source priority sections have minor redundancy that could be tightened.	4 / 5
Actionability	Concrete tool names, env keys, and copy-paste symbol-format examples are highly actionable, though the decision-tree steps remain somewhat high-level rather than fully executable.	4 / 5
Workflow Clarity	The decision tree is clearly sequenced with validation checkpoints (report missing keys, cross-check sources, throttle-to-fallback feedback); minor gaps keep it below a 5.	4 / 5
Progressive Disclosure	A single self-contained file with well-organized, navigable sections and no nested references, but the large inline source table could arguably be split into a reference file.	4 / 5
	Total	16 / 20 Passed

Description

83%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 is strong: it states the skill's purpose concretely, gives an explicit load-before trigger with natural user terms, and occupies a distinct routing niche. Minor gains are possible from adding a few more synonyms and broadening action coverage.

Dimension	Reasoning	Score
Specificity	"pick the best available source/tool, honour auth (env) requirements, and avoid ban-risk providers" lists three concrete routing actions, but coverage is not fully comprehensive enough for a 5.	4 / 5
Completeness	It explicitly answers both what (pick source/tool, honour auth, avoid bans) and when ("Load this skill BEFORE any backtest, data-fetch, or research task") with concrete trigger phrases.	5 / 5
Trigger Term Quality	"backtest, data-fetch, or research task" and "data need" are natural user phrases with good keyword coverage, though a few common synonyms are missing.	4 / 5
Distinctiveness Conflict Risk	"The single ROUTER for every data need" carves a clear niche with distinct triggers, with only minor overlap risk against closely related data skills.	4 / 5
	Total	17 / 20 Passed

Validation

93%

Warnings & errors only

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

Validation — 15 / 16 Passed

Validation for skill structure

Criteria	Description	Result
frontmatter_unknown_keys	Unknown frontmatter key(s) found; consider removing or moving to metadata	Warning

	Total	15 / 16 Passed

Repository: HKUDS/Vibe-Trading
Path: agent/src/skills/data-routing/SKILL.md
Commit: e90b6c6

Reviewed: 4 days ago

Table of Contents

Discovery Implementation Validation

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.