CtrlK
BlogDocsLog inGet started
Tessl Logo

parabolic-short-trade-planner

Screen US equities for parabolic exhaustion patterns and generate conditional pre-market short plans, then evaluate intraday trigger fires from live 5-min bars. Phase 1 daily 5-factor scorer (MA extension / acceleration / volume climax / range expansion / liquidity), Phase 2 per-candidate plans for ORL break / first-red 5-min / VWAP fail with explicit borrow / SSR / manual-confirmation gating, Phase 3 one-shot intraday FSM that detects trigger fires and resolves concrete share counts. Covers Phase 1 + Phase 2 + Phase 3.

64

Quality

77%

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 ./skills/parabolic-short-trade-planner/SKILL.md
SKILL.md
Quality
Evals
Security

Quality

Content

87%

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

The body is lean, highly actionable, and well-structured with a clean one-level-deep reference layer. Its main weakness is workflow_clarity: inline validation/feedback loops for the destructive and batch-oriented operations are implied via referenced tests rather than spelled out in the steps.

Suggestions

Add an explicit inline validate->fix->retry checkpoint within Phase 1 and Phase 3 (e.g., 'Run tests/test_schema_contract.py; if it fails, fix the JSON and re-run before promoting candidates').

State the schema-contract / smoke-test verification step inside the Output Format section rather than only referencing the test files.

Surface a short pre-flight checklist (API keys set, fixtures available) at the top of Phase 3 to close the implicit gating loop.

DimensionReasoningScore

Conciseness

The body is operationally dense — real commands, flag names, and output field names — and assumes Claude's competence rather than explaining basics; only minor redundancy with the description keeps it from padding, so the 'lean and efficient' anchor fits best.

3 / 3

Actionability

Each phase provides fully executable command lines with concrete flags and example values (e.g., '--account-size 100000 --risk-bps 50') plus offline fixture fallbacks, meeting the 'fully executable, copy-paste ready' anchor.

3 / 3

Workflow Clarity

The three phases are numbered and sequenced with explicit gating notes, but validation checkpoints (validate->fix->retry loops) are mostly deferred to referenced tests and fixtures rather than stated inline, leaving implicit gaps for risky operations.

2 / 3

Progressive Disclosure

A concise overview body points to five clearly-signaled, one-level-deep reference files (all verified present on disk) in a Resources section, with detail appropriately split out rather than inlined.

3 / 3

Total

11

/

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 concrete and distinctive, naming a clear niche and several specific capabilities. It is weakened by jargon-heavy trigger terms and the absence of an explicit 'when to use' clause, capping trigger_term_quality and completeness at 2.

Suggestions

Add an explicit 'Use when...' clause naming natural user phrases (e.g., 'parabolic short setups', 'pre-market short plans', 'intraday short trigger monitoring').

Reduce reliance on technical jargon in the lead sentence; surface plain-language trigger terms a trader would actually say.

Drop the trailing 'Covers Phase 1 + Phase 2 + Phase 3' restatement, which adds length without aiding discoverability.

DimensionReasoningScore

Specificity

Lists multiple concrete actions ('Screen US equities for parabolic exhaustion patterns', 'generate conditional pre-market short plans', 'evaluate intraday trigger fires from live 5-min bars') plus enumerated factors and trigger types, matching the 'lists multiple specific concrete actions' anchor.

3 / 3

Completeness

The 'what' is thorough, but there is no explicit 'Use when...' clause or equivalent trigger guidance, which the guidelines state must cap completeness at 2.

2 / 3

Trigger Term Quality

Some relevant natural terms ('parabolic exhaustion', 'short plans', '5-min bars') appear, but the description leans on technical jargon ('FSM', 'MA extension', 'ORL break', 'VWAP fail') that users would not naturally say, so common variations are missing.

2 / 3

Distinctiveness Conflict Risk

The parabolic-short screening niche is highly specific with distinct triggers, making it unlikely to fire for the wrong skill or conflict with generic screeners.

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

referenced_paths_exist

Referenced path issues: 2 deeper-than-1-level

Warning

Total

15

/

16

Passed

Repository
tradermonty/claude-trading-skills
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.