minute-analysis

Minute-level data analysis and backtesting. Retrieves minute candlesticks through OKX/Tushare/yfinance and can be used both for analysis and as input to the backtest engine.

Quality

73%

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/minute-analysis/SKILL.md

Quality

Content

68%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 a well-organized, actionable reference with real executable code for the primary data source. Its weaknesses are redundancy between the parameters/pitfalls and code examples, implicit rather than explicit workflow sequencing with no validation checkpoints, and missing code coverage for two of the three supported sources.

Suggestions

Remove the redundant Parameters table and the duplicate "300 rows" note, keeping each fact in one place.

Add a short numbered workflow (retrieve → verify data non-empty → compute indicators → configure interval → run backtest) with an explicit validation step for empty or truncated API responses.

Add a minimal Tushare and yfinance retrieval example (or move the per-source API details into a references file) so all three advertised sources have executable guidance.

Dimension	Reasoning	Score
Conciseness	The body is mostly lean tables and executable code, but the Parameters table and the "at most 300 rows" note repeat information already given in the API example and pitfalls, and the VWAP/TWAP formulas are near-common knowledge.	4 / 5
Actionability	The OKX snippet, indicator templates, and config JSON are concrete and executable, but there are no Tushare/yfinance retrieval examples and pagination is only described ("The loader paginates automatically") rather than shown.	4 / 5
Workflow Clarity	The retrieve → compute indicators → configure → run backtest sequence is implicit rather than explicitly ordered, and there are no validation checkpoints (e.g., checking for empty Tushare responses appears only as a pitfall, not as a step).	3 / 5
Progressive Disclosure	No bundle files exist and the body is well-sectioned with tables, code, and pitfalls, but at ~95 lines it exceeds the under-50-line simple-skill exception and the OKX API reference or indicator templates could arguably live in separate reference files.	4 / 5
	Total	15 / 20 Passed

Description

66%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 names concrete capabilities and specific data sources, giving it good specificity and distinctiveness. Its main weakness is the missing explicit "when to use" trigger guidance, which both caps completeness and leaves some natural trigger synonyms absent.

Suggestions

Add an explicit trigger clause, e.g. "Use when the user needs intraday/minute candlestick data or wants to backtest strategies on minute-level intervals."

Include natural synonyms users would say, such as "intraday", "1-minute/5-minute bars", or "K-line", alongside "minute" and "candlesticks".

Mention the supported markets (crypto, A-shares, HK/US equities) briefly to sharpen distinctiveness against generic data-analysis skills.

Dimension	Reasoning	Score
Specificity	"Retrieves minute candlesticks through OKX/Tushare/yfinance" and "input to the backtest engine" list several concrete actions with named sources, but coverage has minor gaps (no indicators, intervals, or markets mentioned).	4 / 5
Completeness	The "what" is clear (retrieve minute candlesticks, analysis, backtest input), but there is no "Use when..." trigger clause; usage is only weakly implied by "can be used both for analysis and as input to the backtest engine", which caps completeness at 3.	3 / 5
Trigger Term Quality	Natural terms like "minute", "candlesticks", "backtesting", and the source names are present, but common variations such as "intraday", "K-line", or "1-minute bars" are missing.	4 / 5
Distinctiveness Conflict Risk	"Minute-level" plus specific sources (OKX/Tushare/yfinance) carve a fairly distinct niche, though the generic phrase "data analysis" leaves minor overlap risk with general analysis skills.	4 / 5
	Total	15 / 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/minute-analysis/SKILL.md
Commit: 251b094

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