CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

pair-trade-screener

Statistical arbitrage tool for identifying and analyzing pair trading opportunities. Detects cointegrated stock pairs within sectors, analyzes spread behavior, calculates z-scores, and provides entry/exit recommendations for market-neutral strategies. Use when user requests pair trading opportunities, statistical arbitrage screening, mean-reversion strategies, or market-neutral portfolio construction. Supports correlation analysis, cointegration testing, and spread backtesting.

Quality

85%

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

SKILL.md
Quality
Evals
Security

Quality

Content

73%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 delivers a well-sequenced, validated 8-step workflow with executable commands, specific thresholds, and a clean one-level reference structure. Its main weakness is token efficiency: marketing sections, duplicated trigger guidance, and re-explanations of standard statistical concepts inflate the SKILL.md beyond what Claude needs.

Suggestions

Remove the 'Key Advantages', 'Why Cointegration Matters', and 'When to Use This Skill' sections — the advantages are marketing fluff, the cointegration rationale is knowledge Claude already has, and the triggers duplicate the frontmatter description verbatim.

Move the Step 3–5 statistical interpretation ladders (correlation bands, half-life bands, spread construction methods, z-score/beta formulas) into methodology.md or cointegration_guide.md and reference them the way Steps 6–8 do, keeping only the decision thresholds inline.

Reconcile the duplicated, inconsistent dependency/footer blocks (Python 3.9+ vs 3.8+, dependency lists in both Prerequisites and the footer) into one place, and drop the version/date stamp, which is time-sensitive information that adds no instructional value.

DimensionReasoningScore

Conciseness

The step-by-step core is efficient, but several sections pad the token budget: "Key Advantages" is marketing fluff, "Why Cointegration Matters" and the z-score/beta formulas re-explain concepts Claude already knows, "When to Use This Skill" duplicates the frontmatter description, and the footer repeats dependencies inconsistently ("Python 3.9 or newer" vs "Python 3.8+"). This fits the score-3 anchor (mostly efficient with some unnecessary explanation) rather than score 2, since the majority of the body is actionable domain-specific configuration.

3 / 5

Actionability

Copy-paste-ready `uv run --with 'statsmodels…'` commands cover both the explicit-symbols and sector-screening modes, API endpoints are concrete, and thresholds (ρ ≥ 0.70, p < 0.05, half-life bands, transaction costs) are specific. It stops short of score 5 because minor gaps remain: no inline `analyze_spread.py` usage example and vague directives like "Plot historical z-score distribution" with no method given.

4 / 5

Workflow Clarity

Eight explicitly sequenced steps each with an objective, validation is embedded (Step 2 data validation, Step 3 correlation stability check, Step 4 p-value gate, Step 5 structural-break check), and the Quality Standards checklist plus Troubleshooting problem→solutions section provide checklists and error-recovery feedback loops. The batch API operations do have validation, so the batch-operation cap at 3 does not apply; this matches the score-5 anchor.

5 / 5

Progressive Disclosure

References are well-signaled and one level deep — all six referenced files exist, and the cited section names in trade_rules_and_reporting.md ("Step 6 detail", "Step 7 detail", "Step 8 detail") were verified to be real. It misses score 5 because the inlined Steps 3–5 statistical interpretation ladders (correlation bands, half-life bands, spread methods) duplicate material that methodology.md and cointegration_guide.md already cover, so some content that should be separate remains inline.

4 / 5

Total

16

/

20

Passed

Description

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

A strong description: concrete third-person capability statements, an explicit 'Use when…' trigger clause, and good domain keyword coverage. The only weaknesses are a few missing layperson trigger phrasings and slight overlap risk with portfolio/backtesting skills.

DimensionReasoningScore

Specificity

The description lists multiple concrete actions — "Detects cointegrated stock pairs within sectors, analyzes spread behavior, calculates z-scores, and provides entry/exit recommendations" plus "correlation analysis, cointegration testing, and spread backtesting" — giving comprehensive capability coverage in third-person voice. It clearly matches the score-5 anchor (multiple specific concrete actions) rather than score 4, which anticipates minor gaps in coverage.

5 / 5

Completeness

It explicitly answers both "what" (detects cointegrated pairs, analyzes spreads, calculates z-scores, provides entry/exit recommendations) and "when" ("Use when user requests…") with concrete trigger phrases, exactly matching the score-5 anchor example pattern. Score 4 would require the 'when' clause to be less explicit, which it is not.

5 / 5

Trigger Term Quality

"Use when user requests pair trading opportunities, statistical arbitrage screening, mean-reversion strategies, or market-neutral portfolio construction" covers the main domain synonyms a target user would say. It falls short of the score-5 anchor because natural layperson variations like "which stocks move together" or "relative value" are absent (they appear only in the body, not the description).

4 / 5

Distinctiveness Conflict Risk

The statistical-arbitrage/pair-trading niche is clear with distinct triggers, but "market-neutral portfolio construction" and "spread backtesting" create minor overlap risk with generic portfolio-construction or backtesting skills. This fits the score-4 anchor (mostly distinct, minor overlap with closely related skills) better than score 5's minimal-conflict standard.

4 / 5

Total

18

/

20

Passed

Validation

100%

Checks the skill against the spec for correct structure and formatting. All validation checks must pass before discovery and implementation can be scored.

Validation — 16 / 16 Passed

Validation for skill structure

No warnings or errors.

Repository

tradermonty/claude-trading-skills

Path

skills/pair-trade-screener/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.