CtrlK
BlogDocsLog inGet started
Tessl Logo

technical-basic

Core technical indicator collection (trend EMA/ADX + mean-reversion BB/RSI + volume-price OBV/volume ratio), generates a composite signal via three-dimensional voting. Pure pandas implementation for any OHLCV data.

64

Quality

76%

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/technical-basic/SKILL.md
SKILL.md
Quality
Evals
Security

Quality

Content

86%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 is token-efficient and well-structured, with concrete formulas and clear signal logic. Its main gap is the absence of a fully runnable example and output-validation guidance.

Suggestions

Add a short, complete copy-paste example that constructs the indicator on a sample OHLCV DataFrame and emits the composite signal column.

Note warmup/edge-case handling (e.g. required history length for EMA/ADX/BB, NaN behavior in the first rows) so outputs can be validated.

Clarify how to verify the signal is sensible (e.g. sanity checks against known trending vs. ranging segments) before acting on it.

DimensionReasoningScore

Conciseness

Lean tables and bullets with no padding; it surfaces only non-obvious detail (e.g. 'RSI and ADX use Wilder EWM (ewm(alpha=1/period)), not a rolling mean') and assumes Claude's competence.

5 / 5

Actionability

Gives concrete, executable specifics — exact pandas formulas like 'OBV = (volume * sign(close.diff())).cumsum()' and the full ADX chain — but lacks a complete copy-paste runnable signal-generation example.

4 / 5

Workflow Clarity

The signal logic is clearly sequenced via the three-dimensional voting conditions (Long/Short/Stand aside), but there are no validation or edge-case checkpoints (e.g. NaN handling, insufficient warmup length).

4 / 5

Progressive Disclosure

A compact (~50 line), single-purpose skill with no external references needed; well-organized into Purpose, Signal Logic, Implementation Details, Parameters, Dependencies, and Signal Convention sections.

5 / 5

Total

18

/

20

Passed

Description

66%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 is specific and domain-distinct, naming concrete indicators and the composite-signal mechanism, but it omits any explicit 'when to use' trigger guidance, which caps completeness.

Suggestions

Add an explicit trigger clause, e.g. 'Use when generating trading signals from OHLCV data or when the user asks for technical-indicator-based entry/exit signals.'

Include a couple of natural synonyms users might say (e.g. 'Bollinger Bands', 'moving averages', 'momentum') to broaden trigger coverage.

Lead with a verb ('Generates...', 'Computes...') rather than the noun phrase 'Core technical indicator collection' for stronger action framing.

DimensionReasoningScore

Specificity

Names the domain and several concrete actions — 'trend EMA/ADX', 'mean-reversion BB/RSI', 'volume-price OBV/volume ratio', 'generates a composite signal via three-dimensional voting' — with only minor coverage gaps.

4 / 5

Completeness

The 'what' is clearly stated, but there is no 'Use when...' or equivalent trigger guidance, which caps completeness at 3 per the rubric guideline.

3 / 5

Trigger Term Quality

Includes domain-natural terms a trader would say ('technical indicator', 'EMA', 'ADX', 'Bollinger Bands', 'RSI', 'OBV', 'volume ratio', 'OHLCV'); a few common synonyms are absent but coverage is good.

4 / 5

Distinctiveness Conflict Risk

Targets a specific niche (composite technical-indicator signal via three-dimensional voting) with distinct triggers; minor overlap risk with other trading-analysis skills.

4 / 5

Total

15

/

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.

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.