CtrlK
BlogDocsLog inGet started
Tessl Logo

trader-hand-skill

Expert knowledge for autonomous market intelligence and trading — technical analysis, risk management, Alpaca API, financial data sources

48

Quality

53%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide

SecuritybySnyk

Medium

Suggest reviewing before use

Fix and improve this skill with Tessl

tessl review fix ./crates/openfang-hands/bundled/trader/SKILL.md
SKILL.md
Quality
Evals
Security

Quality

Content

50%

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

The content is highly actionable for API usage but is a monolithic reference compendium that largely restates general financial knowledge Claude already has, with no file-based progressive disclosure. Workflow sequencing exists for pre-trade checks but lacks execution-time validation loops.

Suggestions

Move well-known reference material (indicator formulas, candlestick tables, risk/bias overviews) into separate files under references/ and keep SKILL.md as a lean overview pointing to them, since no bundles currently exist.

Cut explanations of concepts Claude already knows; retain only the Alpaca-specific endpoints, exact data-source URL patterns, and worked examples that add real value.

Add an order-execution workflow with validation checkpoints (place order -> poll for fill -> confirm position -> verify risk exposure) so the destructive trading path has a feedback loop.

DimensionReasoningScore

Conciseness

The ~928-line body spends most of its tokens explaining concepts Claude already knows (RSI/MACD/Bollinger step-by-step calculations, candlestick pattern tables, Fibonacci, Kelly, Sharpe, cognitive biases), which the rubric penalizes as padded verbosity; only the Alpaca endpoints and data-source URLs are genuinely skill-specific.

1 / 3

Actionability

The Alpaca section provides copy-paste-ready curl commands with exact endpoints, auth headers, and JSON payloads, and the Python snippets (RSI calculation, position parsing) are executable, matching anchor 3.

3 / 3

Workflow Clarity

The 10-step pre-trade checklist gives a clear sequence, but trading is a destructive operation and the execution flow lacks post-order validation/feedback loops (e.g. confirm fill, verify position), which caps workflow clarity at 2 per the guidelines.

2 / 3

Progressive Disclosure

Numbered sections provide decent in-file organization, but no bundle files exist and ~928 lines of reference material (indicators, risk, API, data sources) that belong in separate files is kept entirely inline, matching anchor 2.

2 / 3

Total

8

/

12

Passed

Description

57%

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 conveys a clear, distinctive trading/finance niche but lacks an explicit "Use when..." trigger clause and relies on domains rather than enumerated concrete actions. It is solid but not exemplary.

Suggestions

Add an explicit "Use when..." clause naming natural triggers, e.g. "Use when performing technical analysis, sizing trade risk, or placing orders via the Alpaca API."

Lead with concrete actions ("analyze price charts, size positions, place Alpaca orders") rather than the abstract "Expert knowledge for..." framing.

Surface common trigger terms (stocks, crypto, portfolio, backtesting) directly in the description instead of only in tags.

DimensionReasoningScore

Specificity

Names specific domains ("technical analysis, risk management, Alpaca API, financial data sources") and action-like terms ("trading", "market intelligence"), but does not list multiple concrete actions, so it sits at anchor 2 rather than 3.

2 / 3

Completeness

It answers "what" (expert knowledge for trading and analysis) but has no explicit "Use when..." clause or equivalent trigger guidance, which the guidelines cap at 2.

2 / 3

Trigger Term Quality

Includes natural terms a user would say ("trading", "technical analysis", "risk management") but omits common variations such as stocks, crypto, portfolio, or backtesting that appear only in tags, matching anchor 2.

2 / 3

Distinctiveness Conflict Risk

The finance/trading niche with distinct markers ("Alpaca API", "technical analysis", "risk management") is unlikely to trigger for unrelated skills, matching anchor 3.

3 / 3

Total

9

/

12

Passed

Validation

87%

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

Validation14 / 16 Passed

Validation for skill structure

CriteriaDescriptionResult

skill_md_line_count

SKILL.md is long (938 lines); consider splitting into references/ and linking

Warning

frontmatter_unknown_keys

Unknown frontmatter key(s) found; consider removing or moving to metadata

Warning

Total

14

/

16

Passed

Repository
RightNow-AI/openfang
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.