tracking-crypto-prices
Track real-time cryptocurrency prices across exchanges with historical data and alerts. Provides price data infrastructure for dependent skills (portfolio, tax, DeFi, arbitrage). Use when checking crypto prices, monitoring markets, or fetching historical price data. Trigger with phrases like "check price", "BTC price", "crypto prices", "price history", "get quote for", "what's ETH trading at", "show me top coins", or "track my watchlist".
87
86%
Does it follow best practices?
Impact
Pending
No eval scenarios have been run
Advisory
Suggest reviewing before use
Quality
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 strong skill description that covers all key dimensions well. It provides specific capabilities, comprehensive natural trigger terms, explicit 'Use when' guidance, and clear differentiation from related skills. The mention of its role as infrastructure for dependent skills adds useful context for skill selection.
| Dimension | Reasoning | Score |
|---|---|---|
Specificity | Lists multiple concrete actions: tracking real-time prices across exchanges, providing historical data, alerts, and serving as price data infrastructure for dependent skills (portfolio, tax, DeFi, arbitrage). | 3 / 3 |
Completeness | Clearly answers both 'what' (track real-time crypto prices, historical data, alerts, price data infrastructure) and 'when' (explicit 'Use when' clause plus detailed trigger phrases). | 3 / 3 |
Trigger Term Quality | Excellent coverage of natural user phrases including 'check price', 'BTC price', 'crypto prices', 'price history', 'what's ETH trading at', 'show me top coins', and 'track my watchlist' — these are highly natural terms users would actually say. | 3 / 3 |
Distinctiveness Conflict Risk | Clearly scoped to cryptocurrency price tracking with distinct triggers like 'BTC price', 'crypto prices', 'ETH trading at'. It also explicitly delineates its role relative to dependent skills (portfolio, tax, DeFi, arbitrage), reducing overlap risk. | 3 / 3 |
Total | 12 / 12 Passed |
Implementation
72%Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.
This is a well-structured skill with strong actionability — concrete CLI commands, clear examples with expected output, and a useful error handling table. The main weaknesses are minor verbosity in the overview section and the lack of validation/verification steps after operations like CSV exports or when dealing with stale cache scenarios. Progressive disclosure is handled well with appropriate delegation to implementation.md.
Suggestions
Add a brief validation step after CSV export (e.g., 'Verify output: `head ${CLAUDE_SKILL_DIR}/data/ETH_90d_*.csv`') to improve workflow clarity.
Trim the Overview section to remove marketing-style language ('10,000+ coins', '10+ other skills depend on it') that doesn't help Claude execute the task.
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | Generally efficient but includes some unnecessary framing ('Foundation skill providing real-time and historical cryptocurrency price data for 10,000+ coins. This is the data layer for the crypto plugin ecosystem -- 10+ other skills depend on it') and the overview section adds little actionable value. The error handling table and examples are well-structured but the content could be tightened. | 2 / 3 |
Actionability | Provides fully concrete, copy-paste ready commands with specific flags, example outputs, and clear CLI patterns. Every instruction includes executable bash commands with real arguments and expected output formats. | 3 / 3 |
Workflow Clarity | Steps are clearly listed and sequenced for different use cases (price check, watchlist, historical data, configuration), but there are no validation checkpoints or feedback loops. For a tool that involves network calls, rate limits, and data exports, there's no guidance on verifying output correctness or confirming successful exports. | 2 / 3 |
Progressive Disclosure | Well-structured with a clear table of contents, concise main content, and appropriate references to implementation.md for detailed output formats and configuration. References are one level deep and clearly signaled throughout. | 3 / 3 |
Total | 10 / 12 Passed |
Validation
81%Checks the skill against the spec for correct structure and formatting. All validation checks must pass before discovery and implementation can be scored.
Validation — 9 / 11 Passed
Validation for skill structure
| Criteria | Description | Result |
|---|---|---|
allowed_tools_field | 'allowed-tools' contains unusual tool name(s) | Warning |
frontmatter_unknown_keys | Unknown frontmatter key(s) found; consider removing or moving to metadata | Warning |
Total | 9 / 11 Passed | |
- Commit
3a2d27d
- 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.