cross-market-strategy

Write signal_engine.py for portfolios spanning multiple markets (A-shares + crypto, equity + forex, etc.)

Quality

59%

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/cross-market-strategy/SKILL.md

Quality

Content

65%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 strong on actionability and conciseness, delivering executable code and concrete tables, but it reads as a concept catalog rather than a sequenced workflow and references a supporting file that does not exist in the bundle. Adding an explicit step sequence with validation and ensuring the referenced example file exists would raise the weaker dimensions.

Suggestions

Add a short numbered workflow (detect markets -> group -> per-market signals -> vol-adjust -> return) with a validation checkpoint on the output signals.

Provide the referenced example_signal_engine.py (or move it into a references/ directory) so the one-level-deep link resolves.

Define or inline the _detect_market and _market_signal helpers so the example code is fully executable.

Dimension	Reasoning	Score
Conciseness	The body is largely lean with executable code and tables rather than concept explanation, but a few brief justificatory sentences like 'Different markets have very different dynamics' could be trimmed, keeping it just below fully efficient.	4 / 5
Actionability	Provides concrete, mostly copy-paste-ready code (generate(), _vol_adjust()), parameter tables, and a config.json example, but referenced helpers like _detect_market and _market_signal are used without being defined, leaving minor gaps.	4 / 5
Workflow Clarity	Content is organized as a concept catalog (numbered concepts 1-5) rather than a sequenced multi-step workflow, with no explicit validation checkpoints, fitting the 'sequence present but checkpoints missing' anchor.	3 / 5
Progressive Disclosure	Section structure is reasonable and there is a single one-level-deep reference to example_signal_engine.py, but no bundle directory exists so the referenced file is not present, leaving navigation unverified and structure only partially organized.	3 / 5
	Total	14 / 20 Passed

Description

53%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 states a concrete action and a specific cross-market niche, but it omits any explicit 'when to use' trigger guidance, which caps its completeness and trigger-term quality. Adding a 'Use when...' clause with natural user phrasings would substantially improve it.

Suggestions

Add an explicit trigger clause such as 'Use when backtesting portfolios that span multiple markets (e.g. A-shares + crypto, equity + forex)'.

Include natural synonyms users would say, like 'cross-market backtest' or 'multi-asset portfolio', to improve trigger term quality.

Use third-person active voice consistently (already largely compliant) and keep the single concrete action but pair it with the trigger guidance.

Dimension	Reasoning	Score
Specificity	Names the concrete action 'Write signal_engine.py' and the cross-market domain with examples, but lists only one main action rather than several, fitting the '1-2 concrete actions' anchor.	3 / 5
Completeness	Clearly answers 'what' (write signal_engine.py for cross-market portfolios) but provides no 'Use when...' trigger clause; per the guideline a missing explicit 'when' caps completeness at 3.	3 / 5
Trigger Term Quality	Includes relevant domain keywords like 'A-shares + crypto, equity + forex' but lacks common natural trigger phrasings such as 'cross-market' or 'backtest across markets' that users would say.	3 / 5
Distinctiveness Conflict Risk	The cross-market portfolio niche is mostly distinct from single-market strategy skills with only minor overlap risk, though the absence of explicit trigger phrases keeps it below a 5.	4 / 5
	Total	13 / 20 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: 1 missing	Warning

	Total	14 / 16 Passed

Repository: HKUDS/Vibe-Trading
Path: agent/src/skills/cross-market-strategy/SKILL.md
Commit: 1907e47

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.