CtrlK
BlogDocsLog inGet started
Tessl Logo

entry-signals

Entry signal patterns with historical success rates. Use when deciding whether to open a position.

71

1.05x
Quality

56%

Does it follow best practices?

Impact

100%

1.05x

Average score across 3 eval scenarios

SecuritybySnyk

Passed

No findings from the security scan

Fix and improve this skill with Tessl

tessl review fix ./data/skills-md/0xhubed/agent-trading-arena/entry-signals/SKILL.md
SKILL.md
Quality
Evals
Security

Quality

Content

42%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 an auto-generated data dump: a redundant, partially-truncated table plus duplicated detail sections, with no workflow for actually applying the signals to an entry decision. It is organized by headers but lacks conciseness and a clear decision procedure.

Suggestions

De-duplicate: keep either the summary table or the detailed entries, not both, and expand the truncated signal names so every row is actionable.

Move the bulk signal catalog to a reference file (e.g. references/signals.md) and have SKILL.md summarize the top patterns plus a link, reducing inline tokens.

Add a short decision workflow with a validation checkpoint (e.g. 'confirm confidence >= 70% and success rate >= 60% before opening; otherwise skip') so the reference translates into an actionable entry procedure.

DimensionReasoningScore

Conciseness

A 30-row table is followed by a 'Signal Details' section that repeats much of the same data, and entries are truncated mid-phrase ('Multi-timeframe bullish alignment (...'); time-sensitive clutter ('Last updated', 'First seen', other-agent names) adds padding.

2 / 5

Actionability

Concrete guidance exists for the five fully-detailed signals (timeframes, risk-validation requirements), but 25 of 30 table entries are truncated so key details are missing, and metadata like 'skill_aware_oss uses this' is not actionable.

3 / 5

Workflow Clarity

There is no decision procedure or sequence for applying signals to an entry decision, and opening positions is a consequential action with no validation/checklist steps, which caps this dimension at 3.

3 / 5

Progressive Disclosure

Sections (table, details, confidence guide) are present and there are no external bundle files, but the large 30-signal data table is inlined in SKILL.md when it would be better placed in a separate reference file.

3 / 5

Total

11

/

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.

The description is concise, third-person, and includes an explicit 'Use when' trigger with a clear niche. It is solid overall but the 'what' portion is a noun phrase rather than a list of concrete actions, leaving it just short of the top anchor.

DimensionReasoningScore

Specificity

Names the domain ('Entry signal patterns') and one concrete attribute ('historical success rates'), but describes content rather than listing concrete actions, so it is not comprehensive.

3 / 5

Completeness

It states what the skill offers ('Entry signal patterns with historical success rates') and when to use it ('Use when deciding whether to open a position'), but the 'what' is slightly thin and could be more specific.

4 / 5

Trigger Term Quality

Natural trading phrases a user would say ('entry signal', 'open a position') appear, giving good keyword coverage, though a few synonyms (e.g. 'long/short', 'trade setup') are missing.

4 / 5

Distinctiveness Conflict Risk

'Deciding whether to open a position' is a fairly distinct niche with clear triggers, but minor overlap risk exists with broader trading-signal or risk-management skills.

4 / 5

Total

15

/

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.

Validation16 / 16 Passed

Validation for skill structure

No warnings or errors.

Repository
NeverSight/skills_feed
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.