CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

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

70%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide
SecuritybySnyk

Critical

Do not install without reviewing

Fix and improve this skill with Tessl

tessl review fix ./agent/src/skills/minute-analysis/SKILL.md
SKILL.md
Quality
Evals
Security

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 tight, executable, and well-organized, with a complete OKX retrieval example and runnable indicator templates. Main gaps are the absent retrieval examples for Tushare/yfinance, implicit rather than sequenced workflows, and minor redundancy around the 300-row pagination limit.

Suggestions

Add short retrieval snippets for Tushare and yfinance (or a pointer to where their call patterns differ), since both are listed as supported sources but only OKX has code.

State the 300-row pagination limit once (the Pitfalls section) and remove the duplicates in the code comment and Parameters table.

Add an explicit validation checkpoint after data retrieval, e.g. "If the returned DataFrame is empty (common with Tushare score < 2000), stop and report rather than running the backtest."

DimensionReasoningScore

Conciseness

The body is lean with no explanation of concepts Claude already knows, but "at most 300 rows per request" appears three times (code comment, Parameters table, Pitfalls) and the Parameters table largely repeats the code-sample comments. This matches anchor 4 (efficient with minor instances that could be trimmed) rather than anchor 5's every-token-earns-its-place.

4 / 5

Actionability

The OKX snippet is fully executable (imports, params, DataFrame construction, dtype conversion) and the indicator templates and config JSON are copy-paste ready, matching anchor 4. It falls short of anchor 5 because Tushare and yfinance are listed as supported sources but have no retrieval code, leaving the common cases for those sources uncovered.

4 / 5

Workflow Clarity

A rough sequence exists (set interval in config.json, run backtest tool; or install deps, call API, compute indicators) but it is implicit across sections with no explicit checkpoints — e.g. the Tushare empty-data caveat is a pitfall note rather than a verify-data step. This fits anchor 3 (sequence present but checkpoints missing or implicit); it exceeds anchor 2 because the steps are well defined, and does not reach anchor 4's most-checkpoints-present.

3 / 5

Progressive Disclosure

A single well-organized ~96-line file with clear sections (Purpose, Backtest Configuration, Data Sources, API, Indicators, Parameters, Pitfalls, Dependencies) and no buried or nested references, matching anchor 4. It misses anchor 5 because it is over the simple-skill threshold and all API/indicator detail is inline where a reference file split could apply.

4 / 5

Total

15

/

20

Passed

Description

58%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 communicates a clear, specific capability set with named data sources, but lacks any explicit trigger guidance ("Use when...") and misses common natural terms like "intraday" or "OHLC". It is distinguishable from sibling skills but would trigger less reliably than a description with an explicit when-clause.

Suggestions

Add an explicit trigger clause, e.g. "Use when the user needs intraday/minute bars, 1m/5m/15m/30m/1H candles, or wants to backtest strategies on sub-daily data."

Include natural synonyms and variations such as "intraday", "OHLC", "crypto candles", and "5-minute bars" alongside "minute candlesticks".

Mention the computed indicators (VWAP, TWAP, volume distribution) in the description so the analysis capability is comprehensively represented.

DimensionReasoningScore

Specificity

"Retrieves minute candlesticks through OKX/Tushare/yfinance" and "input to the backtest engine" list several concrete actions with named data sources, matching anchor 4. It falls short of anchor 5 because coverage is not comprehensive — intervals, indicators, and analysis outputs are left unmentioned.

4 / 5

Completeness

The "what" is clear (retrieve minute candlesticks, support analysis and backtesting), but there is no "Use when..." clause or equivalent explicit trigger guidance, which per the judging guidelines caps completeness at 3. This fits anchor 3 exactly: clear "what" with "when" missing or only weakly implied.

3 / 5

Trigger Term Quality

"Minute-level", "backtesting", and "candlesticks" are relevant keywords, but common natural variations users would say — "intraday", "OHLC", "5-minute bars", "crypto candles" — are missing, matching anchor 3. It does not reach anchor 4's good coverage, and exceeds anchor 2 since the terms present are domain-specific rather than generic.

3 / 5

Distinctiveness Conflict Risk

The "minute-level" qualifier plus the three named sources (OKX/Tushare/yfinance) carve a fairly distinct niche with clear triggers, matching anchor 4. It is not anchor 5 because it could still overlap with a general backtesting or generic data-retrieval skill, but it is well above anchor 3's "could overlap with similar skills".

4 / 5

Total

14

/

20

Passed

Validation

93%

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

CriteriaDescriptionResult

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

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.