qveris

Paid capability marketplace for global multi-asset data; use it when free Vibe-Trading sources lack coverage, depth, or provider quality, and keep free sources as the default for routine OHLCV.

Quality

68%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide

Securityby

Low

Low-risk findings worth noting

Fix and improve this skill with Tessl

tessl review fix ./agent/src/skills/qveris/SKILL.md

Quality

Content

62%

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

A well-organized, operationally dense skill body with a clear gated workflow, but it lacks a complete executable call example, carries some redundancy in the billing section, and its reference links use a path prefix that does not match the actual bundle location.

Suggestions

Fix the reference link paths: change qveris/references/rest-api.md and qveris/references/coverage.md to references/rest-api.md and references/coverage.md so they resolve to the actual bundle files.

Add one complete executable qveris_execute example (full parameters object, max_response_size, session_id/search_id) so the call guidance is copy-paste ready.

Tighten the Billing and Modes section by merging the two redundant free-mode bullets ("unavailable in mode=free" and "mode=free means...QVeris is hidden") into a single statement.

Dimension	Reasoning	Score
Conciseness	The body is largely lean and assumes competence (no explaining of OHLCV or options concepts), but the Billing and Modes section restates the free-mode behavior across two redundant bullets, so not every token earns its place.	2 / 3
Actionability	It gives concrete tool names, parameter names, defaults (max_response_size 20480), enum/status values, CLI commands, and example queries, but provides no complete executable call example (e.g. a full qveris_execute payload), leaving the guidance concrete yet incomplete.	2 / 3
Workflow Clarity	The three-step Discover → Inspect → Execute sequence is clearly ordered with explicit gating checkpoints ("inspect before any paid call", "only after the user has enabled QVeris and the tool has been inspected") plus decision branches for truncation and not-charged outcomes.	3 / 3
Progressive Disclosure	The overview is well-sectioned and points to two one-level-deep bundle files, but the body links target qveris/references/rest-api.md and qveris/references/coverage.md while the real files live at references/*.md, so the referenced paths do not resolve.	2 / 3
	Total	9 / 12 Passed

Description

75%

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

A solid description that clearly states what QVeris is and gives an explicit use-when trigger tied to gaps in free sources. It is distinctive within its ecosystem, though its trigger terms lean technical and it enumerates few concrete capabilities.

Dimension	Reasoning	Score
Specificity	It names the domain ("Paid capability marketplace for global multi-asset data") and policy actions ("use it when...", "keep free sources as the default"), but does not list multiple concrete capabilities the skill performs, stopping at the domain + usage policy rather than enumerated actions.	2 / 3
Completeness	It explicitly answers both what ("Paid capability marketplace for global multi-asset data") and when ("use it when free Vibe-Trading sources lack coverage, depth, or provider quality"), with an explicit Use-when clause.	3 / 3
Trigger Term Quality	It includes relevant trigger conditions ("lack coverage, depth, or provider quality") but leans on jargon ("multi-asset", "OHLCV") and omits plain variations a user might say like "premium data" or "paid data source".	2 / 3
Distinctiveness Conflict Risk	The niche is distinct (paid premium data vs the free Vibe-Trading stack) and the trigger is specific to gaps in free sources, making false triggering for unrelated skills unlikely.	3 / 3
	Total	10 / 12 Passed

Validation

87%

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 — 14 / 16 Passed

Validation for skill structure

Criteria	Description	Result
frontmatter_unknown_keys	Unknown frontmatter key(s) found; consider removing or moving to metadata	Warning
relative_links	Relative link issues: 2 missing, 2 deeper-than-1-level	Warning

	Total	14 / 16 Passed

Repository: HKUDS/Vibe-Trading
Path: agent/src/skills/qveris/SKILL.md
Commit: 8643fcd

Reviewed: 2 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.