tracking-crypto-portfolio
Track cryptocurrency portfolio with real-time valuations, allocation analysis, and P&L tracking. Use when checking portfolio value, viewing holdings breakdown, analyzing allocations, or exporting portfolio data. Trigger with phrases like "show my portfolio", "check crypto holdings", "portfolio allocation", "track my crypto", or "export portfolio".
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 clearly defines its capabilities (portfolio tracking, valuations, allocation analysis, P&L, export), provides explicit 'Use when' guidance, and includes natural trigger phrases users would actually say. It uses proper third-person voice and is concise without being vague. The cryptocurrency domain focus makes it highly distinctive.
| Dimension | Reasoning | Score |
|---|---|---|
Specificity | Lists multiple specific concrete actions: real-time valuations, allocation analysis, P&L tracking, checking portfolio value, viewing holdings breakdown, analyzing allocations, and exporting portfolio data. | 3 / 3 |
Completeness | Clearly answers both 'what' (track cryptocurrency portfolio with real-time valuations, allocation analysis, P&L tracking) and 'when' (explicit 'Use when...' clause plus specific trigger phrases). | 3 / 3 |
Trigger Term Quality | Excellent coverage of natural trigger phrases users would actually say: 'show my portfolio', 'check crypto holdings', 'portfolio allocation', 'track my crypto', 'export portfolio'. Also includes domain terms like 'cryptocurrency', 'P&L', 'holdings breakdown'. | 3 / 3 |
Distinctiveness Conflict Risk | Clearly scoped to cryptocurrency portfolio tracking with distinct triggers like 'crypto holdings', 'portfolio allocation', and 'track my crypto'. Unlikely to conflict with general finance or non-crypto skills. | 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 cover the full range of use cases. The main weaknesses are some redundancy between the Instructions and Examples sections, and the lack of validation/verification steps in the workflow (e.g., checking portfolio file validity, verifying API responses). Progressive disclosure is handled well with clear references to supporting files.
Suggestions
Add a validation step before running the tracker (e.g., verify the portfolio JSON file exists and is valid) and a verification step after export to check output integrity.
Consolidate the Examples section into the Instructions section to eliminate redundant command listings, or differentiate them more clearly (e.g., Examples showing edge cases not covered in Instructions).
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | Generally efficient but has some redundancy — the Examples section largely repeats commands already shown in Instructions, and the Output section's example is quite long. The error handling table and step 4 ('Present results') add moderate value but could be tighter. | 2 / 3 |
Actionability | Provides fully executable bash commands with specific flags, clear CLI patterns, and concrete examples covering multiple use cases. Commands are copy-paste ready with appropriate variable references. | 3 / 3 |
Workflow Clarity | Steps are clearly sequenced from intent assessment through execution and presentation. However, there are no validation checkpoints — no step to verify the portfolio file is valid before running, no feedback loop if the API fails or returns unexpected results, and no verification of export output correctness. | 2 / 3 |
Progressive Disclosure | Clean overview structure with well-signaled one-level-deep references to implementation.md, errors.md, examples.md, and config/settings.yaml. The main SKILL.md stays focused on the essential workflow while pointing to detailed resources appropriately. | 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.