cross-market-strategy

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

Quality

65%

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

Quality

Content

80%

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

The content is strong and token-efficient: concrete executable code, actionable reference tables, and no generic padding. The main weaknesses are the lack of explicit workflow validation checkpoints and a broken bundle reference (example_signal_engine.py is cited but missing).

Dimension	Reasoning	Score
Conciseness	The body is lean and code-driven with brief, domain-relevant rationale (e.g. 'Without vol-adjustment, crypto eats the entire risk budget') and no padding with concepts Claude already knows, matching 'lean and efficient; every token earns its place'.	3 / 3
Actionability	Provides real, syntactically valid Python (the _vol_adjust function is fully self-contained) plus concrete parameter and market-detection tables and a copy-paste config.json example, clearly above the pseudocode level of score 2.	3 / 3
Workflow Clarity	A loose sequence is implied by the numbered Key Concepts and the generate() code, but there are no explicit validation checkpoints and the multi-step process (group -> signal -> vol-adjust) is only implicitly sequenced, fitting 'steps listed but checkpoints missing or implicit'.	2 / 3
Progressive Disclosure	The body is well-sectioned rather than a monolithic wall, but its single external reference, example_signal_engine.py in the Supporting Files section, does not exist on disk, so the disclosure is broken and content that could be split remains inline.	2 / 3
	Total	10 / 12 Passed

Description

50%

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 conveys a clear domain and one concrete action but is uniformly mediocre: it lacks an explicit 'Use when...' trigger clause, leans on the jargony phrase 'Write signal_engine.py', and does not enumerate multiple specific actions. It is distinguishable but not strongly differentiated from a generic strategy skill.

Suggestions

Add an explicit trigger clause, e.g. 'Use when backtesting portfolios that span multiple markets (e.g. A-shares + crypto, equity + forex).', to satisfy both completeness and distinctiveness.

Replace or supplement the jargony 'Write signal_engine.py' with natural user phrasing such as 'generate a multi-asset trading strategy' and add common trigger terms like 'backtest', 'multi-asset', and 'cross-market'.

Enumerate more concrete actions (e.g. group symbols by market, apply per-market parameters, vol-adjust weights) to lift specificity from a single named action to multiple specific capabilities.

Dimension	Reasoning	Score
Specificity	Names one concrete action ("Write signal_engine.py") and the multi-market domain, but lists only a single action rather than multiple specific concrete actions, matching the 'names domain and some actions, but not comprehensive' anchor.	2 / 3
Completeness	It clearly states WHAT (write signal_engine.py for multi-market portfolios) but provides no explicit 'Use when...' trigger clause, so per the judging guideline completeness is capped at 2.	2 / 3
Trigger Term Quality	Market terms (A-shares, crypto, equity, forex) are natural keywords a user might say, but the lead phrase "Write signal_engine.py" is technical jargon and common variations like 'backtest' or 'multi-asset' are absent, fitting 'some relevant keywords but missing common variations'.	2 / 3
Distinctiveness Conflict Risk	The multi-market portfolio niche is fairly distinct, but the core action (write signal_engine.py) overlaps with a generic single-market strategy skill and there is no explicit trigger to disambiguate, matching 'somewhat specific but could still overlap'.	2 / 3
	Total	8 / 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: 1 missing	Warning

	Total	14 / 16 Passed

Repository: HKUDS/Vibe-Trading
Path: agent/src/skills/cross-market-strategy/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.