CtrlK
BlogDocsLog inGet started
Tessl Logo

ichimoku

Ichimoku Kinko Hyo five-line system signal engine. A standalone Japanese technical-analysis school that generates trading signals from Tenkan/Kijun crossovers, cloud position, and Chikou confirmation. Pure pandas implementation.

60

Quality

75%

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

Quality

Content

71%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 concise, well-organized spec with unambiguous signal rules, parameter defaults, and an explicit output convention. Its weaknesses are the lack of any executable pandas code despite that claim, the orphaned reference files that are never linked, and a Chikou confirmation mentioned in the description but absent from the actual signal logic.

Suggestions

Add a short executable pandas snippet (or a scripts/ entry point) showing line computation, the 26-period shifts, and the crossover+filter check, since the skill claims a pure pandas implementation.

Link the existing reference files explicitly (e.g. "Line calculations: see references/五线计算.md; signal system details: see 信号系统.md") instead of duplicating their content inline.

Either integrate Chikou confirmation into the signal rules or drop it from the stated logic so the description and body agree.

DimensionReasoningScore

Conciseness

The body is lean: compact tables for the five lines and parameters, a two-line signal-logic statement, one warm-up line, and a signal convention. Every section earns its place and nothing explains concepts Claude already knows, matching the anchor-5 example. Minor duplication with the reference files does not rise to the level of anchor 4's "minor instances of over-explanation".

5 / 5

Actionability

Calculations appear only as table shorthand ("(9H+9L)/2", "shifted forward by 26") and rules in prose; despite claiming "Pure pandas implementation", the body contains no executable code, function signature, or example invocation — only a pip-install command. This matches anchor 3 (concrete guidance but incomplete, missing executable detail) rather than 4, which requires mostly concrete code or commands.

3 / 5

Workflow Clarity

The decision sequence is clear and unambiguous for a single-purpose skill: trigger only on TK crossover, apply three explicit filters, stand aside otherwise, with a stated 78-candle warm-up and an explicit 1/-1/0 output convention. It is not a 5 because Chikou confirmation is claimed in the description but never integrated into the signal rules, and the compute order (which lines and shifts first) is not sequenced.

4 / 5

Progressive Disclosure

The body is well sectioned, but it never signals the two existing reference files (references/五线计算.md, references/信号系统.md) and instead inlines line calculations and signal-filter logic that duplicate them, leaving the references undiscoverable. This matches anchor 3 (references present but not clearly signaled; content that should be separate is inline) rather than 4, which requires references to be mostly clear.

3 / 5

Total

15

/

20

Passed

Description

70%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 specific, distinctive description written in third person that clearly states what the skill does, with strong domain keywords. Its main weakness is the complete absence of "when to use it" trigger guidance, which caps completeness at 3 and weakens its value for skill selection.

Suggestions

Add a 'Use when...' clause, e.g. "Use when the user asks about Ichimoku, the Ichimoku cloud, Tenkan/Kijun crossovers, or Japanese technical-analysis trading signals."

Include a couple of natural trigger synonyms such as "Ichimoku cloud indicator" or "five-line indicator" to broaden keyword coverage.

State the concrete output (e.g. "emits 1/-1/0 signals on OHLCV data") so the "what" is fully concrete.

DimensionReasoningScore

Specificity

"generates trading signals from Tenkan/Kijun crossovers, cloud position, and Chikou confirmation" names the domain and several concrete signal-generation mechanisms, but coverage has minor gaps (no data input, parameters, or output format). It lists more than 1-2 actions (not a 3) yet is not fully comprehensive (not a 5).

4 / 5

Completeness

The "what" is clear and specific (a signal engine using crossovers, cloud position, and Chikou confirmation), but there is no "Use when..." clause or equivalent trigger guidance, which caps completeness at 3 per the judging guidelines. It is not a 4 because the "when" is entirely absent rather than merely implicit.

3 / 5

Trigger Term Quality

Natural terms users would say are present — "Ichimoku Kinko Hyo", "trading signals", "technical-analysis", "crossovers", "cloud" — but a few common variations are missing (e.g. "Ichimoku cloud indicator", "Japanese candlesticks"). Good coverage without being exhaustive, matching anchor 4 rather than 5.

4 / 5

Distinctiveness Conflict Risk

"Ichimoku Kinko Hyo five-line system signal engine" occupies a clear niche with highly distinctive terminology (Tenkan/Kijun, Chikou, cloud), so it is unlikely to trigger for unrelated skills. Not a 4 because there is no meaningful overlap with generic strategy or analysis skills.

5 / 5

Total

16

/

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