CtrlK
BlogDocsLog inGet started
Tessl Logo

multi-factor

Multi-factor cross-sectional stock ranking. Combines factor standardization, equal-weight or IC-weighted scoring, and TopN portfolio construction. Suitable for multi-instrument portfolio strategies.

55

Quality

62%

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 ./agent/src/skills/multi-factor/SKILL.md
SKILL.md
Quality
Evals
Security

Quality

Content

57%

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

The body is well-structured with actionable tables and a concrete engine example, but the core algorithm is described rather than made executable and the workflow lacks validation checkpoints, leaving it competent but not fully action-ready.

Suggestions

Add an executable code snippet for the core 4-step flow (compute factors → z-score → combine → select TopN), not just the Zoo engine example.

Include a validation checkpoint for cross-sectional standardization (e.g. asserting >=3 valid stocks and finite z-scores before ranking).

Tighten the Zoo Signal Engine prose, moving deeper rationale into a linked reference rather than inline narrative.

DimensionReasoningScore

Conciseness

The factor/parameter tables and pitfalls are lean and earn their tokens, but the "Zoo Signal Engine" prose is somewhat padded with explanatory clauses that could be tightened.

2 / 3

Actionability

It provides a concrete ZooSignalEngine code example plus parameter and factor tables, but the core 4-step signal logic is described in prose rather than given as executable, copy-paste-ready code.

2 / 3

Workflow Clarity

The Signal Logic steps are clearly sequenced (calculate → standardize → score → rank), but there are no validation checkpoints or feedback loops for the cross-sectional computation.

2 / 3

Progressive Disclosure

The single file is organized into clearly labeled sections with one-level cross-references to the alpha-zoo skill and engine modules, and no deeply nested references.

3 / 3

Total

9

/

12

Passed

Description

67%

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 is specific and occupies a clear niche, but it relies on technical jargon rather than natural trigger terms and lacks an explicit "Use when..." clause, leaving the "when to use" guidance only implied.

Suggestions

Add an explicit trigger clause, e.g. "Use when the user wants to rank stocks by combining multiple factors into a composite score and selecting a TopN portfolio."

Soften jargon with natural user-facing terms such as "stock ranking", "factor scoring", and "top stocks" alongside the technical labels.

DimensionReasoningScore

Specificity

"Combines factor standardization, equal-weight or IC-weighted scoring, and TopN portfolio construction" lists multiple specific concrete actions rather than vague language, matching the score-3 anchor.

3 / 3

Completeness

It states what the skill does, but the "when" is only implied ("Suitable for multi-instrument portfolio strategies") with no explicit "Use when..." trigger guidance, which caps completeness at 2.

2 / 3

Trigger Term Quality

Terms like "cross-sectional", "TopN", and "IC-weighted" are technical jargon; relevant but missing common natural variations a user would actually say.

2 / 3

Distinctiveness Conflict Risk

"Multi-factor cross-sectional stock ranking" carves a clear niche with distinct triggers unlikely to overlap with unrelated skills.

3 / 3

Total

10

/

12

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
HKUDS/Vibe-Trading
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.