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 context and includes an explicit 'Use when' clause, which is positive. However, it lacks concrete actions describing what the skill does (e.g., analyze candlestick patterns, compute indicator signals, generate trade recommendations) and misses common natural language trigger terms users would employ when seeking trading entry guidance.
Suggestions
Add specific concrete actions the skill performs, e.g., 'Identifies candlestick patterns, evaluates technical indicator signals, and computes historical win rates for trade setups.'
Expand trigger terms to include natural user language like 'buy signal', 'trade entry', 'when to buy/sell', 'technical analysis', 'chart patterns', or 'trading setup'.
Clarify the scope to distinguish from related trading skills (e.g., backtesting, risk management, portfolio allocation) by specifying the exact type of signals or markets covered.
| 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 and explicit, but the 'what' portion is weak—it only vaguely references 'entry signal patterns with historical success rates' without explaining what the skill concretely does. | 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, but 'entry signal patterns' is broad enough to overlap with other trading-related skills (e.g., backtesting, technical analysis, portfolio management). More specific triggers would reduce conflict risk. | 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 raw data table with no actionable guidance on how to use the signals for entry decisions. It suffers from extreme redundancy (near-duplicate entries), truncated signal names that obscure meaning, and a complete lack of decision-making workflow. The skill description says 'use when deciding whether to open a position' but provides no decision framework whatsoever.
Suggestions
Add a clear decision workflow: e.g., 'Step 1: Check top signals above 70% success rate. Step 2: Confirm with at least 2 independent signal types. Step 3: Validate risk parameters. Step 4: Enter position only if all checks pass.'
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).
Add concrete decision rules or pseudocode for combining signals, handling conflicts, and determining position sizing based on signal confidence.
Remove the Signal Details section that merely repeats table data, or replace it with genuinely additional information like specific indicator thresholds, entry/exit criteria, or example scenarios.
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | Extremely verbose with massive redundancy. Many signals are near-duplicates (e.g., multiple 'Multi-timeframe bullish alignment' entries with slightly different confidence levels). The Signal Details section repeats information already in the table. The truncated signal names make the table hard to parse while still consuming many tokens. | 1 / 3 |
Actionability | No concrete guidance on how to use these signals. There are no executable steps, no code, no decision logic (e.g., 'if signal X AND signal Y, then enter long'). It's a data dump rather than actionable instructions for deciding whether to open a position. | 1 / 3 |
Workflow Clarity | No workflow is defined. There's no sequence for evaluating signals, no decision tree for combining them, no validation steps, and no guidance on what to do when signals conflict. For a skill about 'deciding whether to open a position,' the absence of any decision-making process is a critical gap. | 1 / 3 |
Progressive Disclosure | There is some structure with a summary table, signal details section, and confidence guide. However, the signal details section only covers 5 of 30 signals and the content that is present is repetitive rather than progressively more detailed. No external references are used despite the volume of data that could be offloaded. | 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
25d5403
- 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.