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".
Install with Tessl CLI
npx tessl i github:jeremylongshore/claude-code-plugins-plus-skills --skill tracking-crypto-prices85
Does it follow best practices?
If you maintain this skill, you can automatically optimize it using the tessl CLI to improve its score:
npx tessl skill review --optimize ./path/to/skillValidation for skill structure
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 provides specific capabilities, comprehensive trigger terms that match natural user language, explicit guidance on when to use it, and clearly distinguishes itself from related cryptocurrency skills by positioning itself as the price data foundation.
| Dimension | Reasoning | Score |
|---|---|---|
Specificity | Lists multiple concrete actions: track real-time prices, provide historical data, alerts, and serve as price data infrastructure for other skills. Specific capabilities like 'across exchanges' add detail. | 3 / 3 |
Completeness | Clearly answers both what (track prices, historical data, alerts, infrastructure for other skills) and when (explicit 'Use when...' clause plus detailed trigger phrases). Both components are well-developed. | 3 / 3 |
Trigger Term Quality | Excellent coverage of natural user phrases: 'check price', 'BTC price', 'crypto prices', 'price history', 'get quote for', 'what's ETH trading at', 'show me top coins', 'track my watchlist'. These are realistic terms users would actually say. | 3 / 3 |
Distinctiveness Conflict Risk | Clear niche focused specifically on cryptocurrency price tracking. Explicitly distinguishes itself from related skills (portfolio, tax, DeFi, arbitrage) by noting it provides infrastructure for them. Trigger terms are crypto-specific. | 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 excellent actionability - commands are executable and examples are concrete. The progressive disclosure is good with appropriate external references. However, it could be more concise by trimming the overview and moving extensive configuration examples to reference files, and would benefit from explicit validation steps for verifying fetched data quality.
Suggestions
Trim the Overview section - remove the 'Dependent Skills' list and reduce capability bullets to essentials Claude needs to know
Move the full Configuration section to a referenced config.md file, keeping only a brief 'see config.md for customization' note
Add a validation step after fetching data, e.g., 'Verify output contains expected fields before passing to dependent skills'
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The skill is reasonably efficient but includes some unnecessary verbosity like the detailed 'Dependent Skills' list and extensive configuration examples that could be referenced externally. The overview section explains capabilities Claude could infer from the instructions. | 2 / 3 |
Actionability | Provides fully executable bash commands and Python code throughout. Commands are copy-paste ready with clear flags and options. Integration examples show both import and CLI approaches with concrete syntax. | 3 / 3 |
Workflow Clarity | Steps are clearly numbered and sequenced, but lacks explicit validation checkpoints. For a data-fetching skill, there's no guidance on verifying data quality or handling partial failures in batch operations beyond the error table. | 2 / 3 |
Progressive Disclosure | Well-structured with clear sections progressing from quick start to advanced features. References external files appropriately (errors.md, examples.md) with one-level-deep navigation. Content is appropriately split between inline essentials and referenced details. | 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 — 13 / 16 Passed
Validation for skill structure
| Criteria | Description | Result |
|---|---|---|
allowed_tools_field | 'allowed-tools' contains unusual tool name(s) | Warning |
metadata_version | 'metadata' field is not a dictionary | Warning |
frontmatter_unknown_keys | Unknown frontmatter key(s) found; consider removing or moving to metadata | Warning |
Total | 13 / 16 Passed | |
- 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.