entry-signals
Entry signal patterns with historical success rates. Use when deciding whether to open a position.
64
Quality
44%
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
67%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 has a clear structure with both 'what' and 'when' components, which is its main strength. However, it lacks specific concrete actions and comprehensive trigger terms that traders would naturally use. The domain is identifiable but could be more distinctive from other potential trading-related skills.
Suggestions
Add specific concrete actions like 'Identifies candlestick patterns, calculates historical win rates, analyzes entry conditions'
Expand trigger terms to include natural variations: 'buy signal', 'trade entry', 'when to enter a trade', 'entry point', 'trading signals'
| Dimension | Reasoning | Score |
|---|---|---|
Specificity | Names the domain (entry signal patterns, historical success rates) and one action (deciding whether to open a position), but lacks concrete specific actions like 'analyze candlestick patterns', 'calculate win rates', or 'backtest strategies'. | 2 / 3 |
Completeness | Clearly answers both what (entry signal patterns with historical success rates) and when (Use when deciding whether to open a position) with an explicit trigger clause. | 3 / 3 |
Trigger Term Quality | Includes some relevant terms like 'entry signal', 'open a position', and 'success rates', but misses common variations users might say like 'buy signal', 'trade entry', 'when to enter', 'trading signals', or 'market entry'. | 2 / 3 |
Distinctiveness Conflict Risk | Somewhat specific to trading entry decisions, but could overlap with other trading-related skills covering technical analysis, backtesting, or general trading strategy. The term 'position' helps narrow it but isn't fully distinctive. | 2 / 3 |
Total | 9 / 12 Passed |
Implementation
22%Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.
This skill functions as a data reference rather than actionable guidance. While it efficiently presents historical signal performance data, it lacks any concrete instructions on how to detect these signals, when to act on them, or how to combine multiple signals into trading decisions. The content would benefit from transformation into an actionable workflow rather than a passive data dump.
Suggestions
Add a decision workflow: 'When evaluating entry, check signals with >70% success rate AND >100 samples, then verify with...'
Include concrete code or pseudocode for detecting each signal type (e.g., how to identify 'Multi-timeframe bullish alignment')
Add explicit action thresholds: 'Enter position when X signals align with combined confidence >Y%'
Fix truncated signal names in the table or link each row to its full description in the details section
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The content is mostly data-driven and avoids explaining basic concepts, but the table has significant redundancy with truncated signal names that repeat, and the Signal Details section duplicates information already in the table. | 2 / 3 |
Actionability | The skill provides historical data but no concrete guidance on HOW to use these signals - no code for signal detection, no specific entry criteria, no thresholds for action. It describes patterns but doesn't instruct on execution. | 1 / 3 |
Workflow Clarity | There is no workflow defined - no steps for evaluating signals, no decision tree for combining signals, no validation checkpoints. The confidence guide hints at interpretation but provides no actionable process. | 1 / 3 |
Progressive Disclosure | The content has reasonable structure with summary table, details section, and confidence guide. However, the Signal Details section only shows 5 of 30 patterns with no reference to where to find the rest, and the truncated names in the table hurt navigation. | 2 / 3 |
Total | 6 / 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
5342bca
- 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.