CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

factor-research

Factor research framework with IC/IR analysis, quantile backtesting, and factor combination. Suitable for cross-sectional factor evaluation across multiple instruments.

Quality

69%

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/factor-research/SKILL.md
SKILL.md
Quality
Evals
Security

Quality

Content

67%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.

A well-structured, highly actionable skill body: concrete tool parameters, interpretation thresholds, executable snippets, and verified one-level-deep references. Its main weakness is token efficiency — the neutralization section inlines library documentation that duplicates references/neutralization.md, and a few pitfalls explain well-known concepts.

Suggestions

Move the library-behavior detail from "Reusable Cross-Sectional Transforms" (WLS weight handling, PCA eigenvalue rotation, rank-deficient fit behavior) into references/neutralization.md, keeping only the contract and a link in SKILL.md.

Trim explanations of widely known concepts (e.g., survivorship bias) to one-line reminders of their factor-research-specific consequence.

Add a short example invocation of the factor_analysis tool so the core workflow step is copy-paste executable.

DimensionReasoningScore

Conciseness

The body is mostly efficient (tables, thresholds, tight code snippets), but the ~30-line "Reusable Cross-Sectional Transforms" prose block inlines library-level detail (WLS weight handling, PCA eigenvalue rotation, rank-deficient fits) despite references/neutralization.md existing, and "Common Pitfalls" explains concepts like survivorship bias that Claude already knows.

3 / 5

Actionability

Concrete parameter and output tables, exact IC/IR thresholds, wrong-vs-correct look-ahead examples, and two copy-paste Python snippets make the guidance mostly executable; the gap is no example invocation of the core factor_analysis tool and no code for constructing the return CSV.

4 / 5

Workflow Clarity

The 5-step workflow is clearly sequenced with checkpoints (row/column alignment key point, IC > 0.10 look-ahead warning, threshold-based interpretation), but there is no explicit verify-inputs step or fix-and-retry loop within the sequence itself.

4 / 5

Progressive Disclosure

All three referenced files (references/combination.md, references/neutralization.md, references/research_contract.md) exist and are linked with clear descriptions of their contents, one level deep; however, some detail that belongs in the references (notably neutralization library behavior) is inlined in SKILL.md.

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 clearly states what the skill does with three concrete, domain-specific capabilities, but it lacks an explicit "Use when..." trigger clause and natural-language synonyms that would help users (and Claude) select it at the right moment. Trigger-term coverage is adequate but jargon-heavy.

Suggestions

Add an explicit trigger clause, e.g., "Use when evaluating factor validity, running IC/IR or quantile backtests on candidate factors, or combining multiple factors into a composite signal."

Include natural synonyms users actually say, such as "alpha", "signal", or "backtest a factor", alongside the technical terms.

Optionally mention the supported use cases from the body (decay analysis, factor screening) to round out coverage toward the top specificity anchor.

DimensionReasoningScore

Specificity

Names the domain and three concrete capabilities ("IC/IR analysis, quantile backtesting, and factor combination"), matching the several-specific-actions anchor; it is not comprehensive since the body also covers screening, decay analysis, and neutralization.

4 / 5

Completeness

The "what" is clear (IC/IR analysis, quantile backtesting, factor combination), but there is no "Use when..." clause; "Suitable for cross-sectional factor evaluation across multiple instruments" is a scope statement that only weakly implies when to use the skill, which caps completeness at 3.

3 / 5

Trigger Term Quality

Core domain keywords like "factor", "backtesting", and "factor evaluation" are present, but the phrasing leans technical ("IC/IR", "quantile", "cross-sectional") and misses natural synonyms and variations such as "alpha", "signal", or "backtest this factor".

3 / 5

Distinctiveness Conflict Risk

The quant factor-research niche is clearly distinct with domain-specific triggers, though minor overlap risk exists with closely related skills (e.g., the "multi-factor" and "alpha-zoo" skills referenced in the body).

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/factor-research/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.