Analyze cryptocurrency support and resistance levels. Use when users ask about crypto price analysis, support/resistance levels, technical analysis for BTC, ETH, or other cryptocurrencies. Provides current price, key levels, and trading insights for crypto pairs like BTC-USDT, ETH-USDT.
69
Quality
67%
Does it follow best practices?
Impact
Pending
No eval scenarios have been run
Passed
No known issues
Optimize this skill with Tessl
npx tessl skill review --optimize ./public/skills/362224222/crypto-levels/SKILL.mdQuality
Discovery
100%Based on the skill's description, can an agent find and select it at the right time? Clear, specific descriptions lead to better discovery.
This is a well-crafted skill description that excels across all dimensions. It clearly specifies what the skill does (crypto support/resistance analysis, price data, trading insights), when to use it (explicit 'Use when...' clause with natural trigger terms), and includes specific examples of supported assets. The description is distinctive enough to avoid conflicts with other financial analysis skills.
| Dimension | Reasoning | Score |
|---|---|---|
Specificity | Lists multiple specific concrete actions: 'Analyze cryptocurrency support and resistance levels', 'Provides current price, key levels, and trading insights'. Also specifies concrete examples like 'BTC-USDT, ETH-USDT'. | 3 / 3 |
Completeness | Clearly answers both what ('Analyze cryptocurrency support and resistance levels', 'Provides current price, key levels, and trading insights') AND when ('Use when users ask about crypto price analysis, support/resistance levels, technical analysis for BTC, ETH, or other cryptocurrencies'). | 3 / 3 |
Trigger Term Quality | Excellent coverage of natural terms users would say: 'crypto price analysis', 'support/resistance levels', 'technical analysis', 'BTC', 'ETH', 'cryptocurrencies', 'crypto pairs', 'BTC-USDT', 'ETH-USDT'. | 3 / 3 |
Distinctiveness Conflict Risk | Clear niche focused specifically on cryptocurrency technical analysis with distinct triggers like 'support/resistance', 'BTC-USDT', 'ETH-USDT'. Unlikely to conflict with general finance or stock analysis skills. | 3 / 3 |
Total | 12 / 12 Passed |
Implementation
35%Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.
This skill is significantly over-documented with content Claude already knows (trading basics, risk disclaimers, what cryptocurrencies are). The example outputs are helpful for understanding expected format, but the skill lacks actual executable implementation details. Most content should be trimmed or moved to reference files.
Suggestions
Remove sections explaining basic concepts Claude knows: risk management basics, what support/resistance means, trading best practices, and legal disclaimers (or move to a separate DISCLAIMER.md)
Add executable code showing how to actually fetch price data and calculate support/resistance levels, rather than just describing the methodology abstractly
Consolidate the Quick Start to just show the input format and one example output, moving detailed examples to an EXAMPLES.md reference file
Move the 'Supported Pairs' list entirely to the referenced SUPPORTED_PAIRS.md file, keeping only a brief mention that pairs are documented there
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | Extremely verbose with extensive explanations Claude already knows (what support/resistance means, basic trading concepts, risk management basics, legal disclaimers). The 300+ line document could be reduced to ~50 lines of actionable content. | 1 / 3 |
Actionability | Provides good example outputs showing expected response format, but lacks executable code for actually fetching data or calculating levels. The 'How It Works' section describes methodology abstractly rather than providing implementation. | 2 / 3 |
Workflow Clarity | The analysis methodology lists steps but they're vague ('Apply technical indicators', 'Generate support/resistance levels'). No validation checkpoints or error recovery for the data fetching process. Troubleshooting section helps but is separate from workflow. | 2 / 3 |
Progressive Disclosure | References external files appropriately (SUPPORTED_PAIRS.md, CONFIGURATION.md, TECHNICAL_GUIDE.md), but the main file contains too much inline content that should be in references (risk management, trading best practices, legal disclaimers, detailed methodology). | 2 / 3 |
Total | 7 / 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.
45f9fac
Table of Contents
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.