CtrlK
BlogDocsLog inGet started
Tessl Logo

asset-allocation

Asset allocation theory and optimizer usage — MPT / Black-Litterman / risk budgeting / all-weather strategy, including guides for 4 optimizers and rebalancing rules.

56

Quality

63%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide

SecuritybySnyk

Passed

No findings from the security scan

Fix and improve this skill with Tessl

tessl review fix ./a_全网优秀资源/10_大模型/07_skill包/vibe_trading_skills/asset-allocation/SKILL.md
SKILL.md
Quality
Evals
Security

Quality

Content

61%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 content is well-organized and actionable with concrete config examples, but it spends significant tokens explaining standard asset-allocation theory Claude already knows and lacks an explicit validation-gated workflow.

Suggestions

Trim or move the 'Asset Allocation Theory' section into a separate reference file, keeping SKILL.md focused on the built-in optimizers and rebalancing rules that Claude does not already know.

Turn the optimizer-selection decision tree plus config and output steps into an explicit numbered workflow with a validation checkpoint (e.g. confirm weight sum ≤ 1.0 before writing config.json).

Make the rebalancing code snippet fully executable by defining or stubbing the referenced helpers (calculate_target_weights, data_map, signals) instead of leaving them abstract.

DimensionReasoningScore

Conciseness

The practical optimizer guide is efficient, but the lengthy 'Asset Allocation Theory' section explains standard finance concepts (MPT, Black-Litterman, risk budgeting, all-weather) that Claude already knows, adding unnecessary padding.

3 / 5

Actionability

Provides copy-paste-ready config.json blocks, parameter tables, a selection decision tree, and an output template, with only minor gaps such as the rebalancing snippet referencing undefined helper functions.

4 / 5

Workflow Clarity

A decision tree gives a selection sequence and the output section frames the deliverable, but there is no explicit multi-step workflow with validation checkpoints or error-feedback loops.

3 / 5

Progressive Disclosure

The body is well-structured with clear headers, tables, and a decision tree, and no broken references; the main gap is that the theory section (which Claude largely already knows) could be split out or trimmed rather than inlined.

4 / 5

Total

14

/

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 clearly conveys what the skill covers and names specific frameworks, but it omits an explicit 'Use when...' trigger clause, which caps completeness. Trigger terms and distinctiveness are solid.

Suggestions

Add an explicit 'Use when...' clause naming concrete trigger phrases (e.g. portfolio construction, optimizer selection, rebalancing rules).

Replace generic verbs like 'optimizer usage' and 'guides for' with more concrete actions (e.g. 'configure optimizers', 'set rebalancing rules').

Include common synonyms users might say (e.g. 'portfolio optimization', 'risk parity', 'rebalance') to broaden trigger coverage.

DimensionReasoningScore

Specificity

Names concrete domains and components — 'MPT / Black-Litterman / risk budgeting / all-weather strategy' and 'guides for 4 optimizers and rebalancing rules' — giving several specific capabilities, though the actions ('optimizer usage', 'guides for') are slightly generic.

4 / 5

Completeness

The 'what' is clearly stated (theory frameworks plus optimizer/rebalancing guidance), but there is no 'Use when...' clause or equivalent explicit trigger guidance, capping completeness at 3 per the rubric.

3 / 5

Trigger Term Quality

Includes natural user-facing terms like 'asset allocation', 'optimizer', and 'rebalancing rules' alongside the framework names, with good but not exhaustive keyword coverage and a few missing synonyms.

4 / 5

Distinctiveness Conflict Risk

The asset-allocation niche with named frameworks (MPT, Black-Litterman, risk budgeting, all-weather) is mostly distinct with only minor overlap risk against closely related portfolio skills.

4 / 5

Total

15

/

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.

Validation15 / 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
charliedream1/ai_quant_trade
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.