entry-signals
Entry signal patterns with historical success rates. Use when deciding whether to open a position.
51
23%
Does it follow best practices?
Impact
100%
1.05xAverage score across 3 eval scenarios
Passed
No known issues
Optimize this skill with Tessl
npx tessl skill review --optimize ./data/skills-md/0xhubed/agent-trading-arena/entry-signals/SKILL.mdQuality
Discovery
40%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 establishes a trading domain context and includes a 'Use when' clause, which is positive. However, it lacks concrete actions describing what the skill actually does and misses common natural language trigger terms users would employ when seeking trading entry guidance. The vague 'what' significantly weakens its utility for skill selection.
Suggestions
Add specific concrete actions the skill performs, e.g., 'Identifies candlestick patterns, evaluates technical indicators, and scores entry signals with historical win rates.'
Expand trigger terms to include natural user language like 'buy signal', 'trade entry', 'when to buy/sell', 'technical analysis', 'chart patterns'.
Clarify the 'what' more explicitly—does it analyze charts, generate alerts, backtest patterns, or provide recommendations?
| Dimension | Reasoning | Score |
|---|---|---|
Specificity | The description mentions 'entry signal patterns' and 'historical success rates' but does not list any concrete actions (e.g., scan charts, calculate indicators, backtest strategies). The language is abstract and does not specify what the skill actually does. | 1 / 3 |
Completeness | The 'when' clause ('Use when deciding whether to open a position') is present, but the 'what' is weak—it only vaguely references 'entry signal patterns with historical success rates' without explaining what the skill concretely does (analyze, generate, display, etc.). | 2 / 3 |
Trigger Term Quality | Terms like 'entry signal', 'open a position', and 'success rates' are somewhat relevant to trading contexts, but common user variations like 'buy signal', 'trade entry', 'when to buy', 'technical analysis', or 'trading strategy' are missing. | 2 / 3 |
Distinctiveness Conflict Risk | The trading/position-opening context provides some niche specificity, but 'entry signal patterns' is broad enough to overlap with other trading-related skills (e.g., backtesting, technical analysis, portfolio management). | 2 / 3 |
Total | 7 / 12 Passed |
Implementation
7%Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.
This skill is essentially a data dump of entry signal patterns with no actionable guidance on how to use them. It suffers from severe redundancy (near-duplicate entries), truncated signal names that obscure meaning, and a complete lack of decision-making workflow. While the tabular structure and confidence guide show some organizational effort, the content fails to teach Claude how to actually decide whether to open a position.
Suggestions
Add a clear decision workflow: e.g., '1. Check multi-timeframe alignment → 2. Verify with secondary indicators → 3. Validate risk parameters → 4. If all pass, enter position with specified sizing'
Deduplicate near-identical signals (e.g., consolidate the multiple 'Multi-timeframe bullish alignment' entries that differ only in confidence thresholds into a single entry with a confidence range)
Include concrete, executable examples showing how to evaluate signals programmatically or as a decision checklist, rather than just listing historical data
Show full signal names instead of truncated versions, and add a clear threshold rule (e.g., 'Only act on signals with success rate ≥ 65% AND confidence ≥ 75%')
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | Extremely verbose with massive redundancy. The table contains many near-duplicate entries (e.g., multiple 'Multi-timeframe bullish alignment' rows with slightly different confidence values), and the Signal Details section repeats nearly identical descriptions for entries that are barely distinguishable. The truncated signal names make the table hard to parse while still consuming many tokens. | 1 / 3 |
Actionability | The skill provides no concrete, executable guidance on how to use these signals. There are no code examples, no specific commands, no decision logic, and no clear instructions on how to combine signals or act on them when deciding whether to open a position. It's purely descriptive data without actionable steps. | 1 / 3 |
Workflow Clarity | There is no workflow defined. The skill describes entry signals but provides no sequence of steps for evaluating them, no decision tree for when to enter a position, and no validation checkpoints. A user/agent reading this has no clear process to follow. | 1 / 3 |
Progressive Disclosure | The content has some structure with a summary table, detailed breakdowns, and a confidence guide. However, the Signal Details section is incomplete (only 5 of 30 patterns detailed) and the content is a monolithic file with no references to external resources. The truncated signal names in the table hurt navigation. | 2 / 3 |
Total | 5 / 12 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.
Validation — 11 / 11 Passed
Validation for skill structure
No warnings or errors.
- Repository
- NeverSight/skills_feed
- Commit
868a866
- 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.