calculating-crypto-taxes
Calculate cryptocurrency tax obligations with cost basis tracking, capital gains computation, and Form 8949 generation. Use when calculating crypto taxes, generating tax reports, comparing cost basis methods, or identifying taxable events. Trigger with phrases like "calculate crypto taxes", "generate tax report", "cost basis FIFO", "capital gains", "Form 8949", or "crypto taxable events".
78
75%
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 ./plugins/crypto/crypto-tax-calculator/skills/calculating-crypto-taxes/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 an excellent skill description that clearly defines specific capabilities (cost basis tracking, capital gains computation, Form 8949 generation), provides explicit trigger guidance with natural user phrases, and occupies a distinct niche at the intersection of cryptocurrency and tax reporting. The three-part structure (what it does, when to use it, trigger phrases) is exemplary and covers all evaluation dimensions thoroughly.
| Dimension | Reasoning | Score |
|---|---|---|
Specificity | Lists multiple specific concrete actions: 'cost basis tracking', 'capital gains computation', 'Form 8949 generation', 'comparing cost basis methods', 'identifying taxable events'. These are clear, actionable capabilities. | 3 / 3 |
Completeness | Clearly answers both 'what' (calculate crypto tax obligations with cost basis tracking, capital gains computation, Form 8949 generation) and 'when' (explicit 'Use when...' clause and 'Trigger with phrases like...' clause providing detailed trigger guidance). | 3 / 3 |
Trigger Term Quality | Excellent coverage of natural trigger terms users would say: 'calculate crypto taxes', 'generate tax report', 'cost basis FIFO', 'capital gains', 'Form 8949', 'crypto taxable events'. These are terms a user would naturally use when seeking this functionality. | 3 / 3 |
Distinctiveness Conflict Risk | Highly distinctive niche combining cryptocurrency + tax obligations + specific forms (Form 8949) and methods (FIFO cost basis). Unlikely to conflict with general tax skills or general crypto skills due to the specific intersection and detailed trigger terms. | 3 / 3 |
Total | 12 / 12 Passed |
Implementation
50%Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.
The skill provides a well-structured overview of crypto tax calculation with clear CLI commands and good organization. However, it suffers from referencing scripts and files that don't exist in the bundle, redundancy between Instructions and Examples sections, and a lack of validation checkpoints for a workflow where accuracy matters significantly. The content would benefit from actual executable code or at minimum verifiable bundle files.
Suggestions
Add validation checkpoints: include a step to verify CSV format before processing (e.g., a --validate-input flag or a dry-run step) and a step to verify output correctness before filing.
Remove or consolidate the Examples section with the Instructions section to eliminate redundant commands that are nearly identical.
Provide the referenced bundle files (scripts/tax_calculator.py, references/exchange_formats.md, references/implementation.md) or include inline the critical information like expected CSV column formats and sample output.
Remove obvious comments like '# 2025 = tax year' repeated on every command, and drop prerequisites that Claude already knows (Python installation).
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | Generally efficient but has some redundancy: the Examples section largely repeats commands already shown in Instructions, and the repeated '# 2025 = tax year' comments are unnecessary. The disclaimer and prerequisites section explaining things Claude would know (like 'Python 3.8+ installed') add minor bloat. | 2 / 3 |
Actionability | Provides concrete CLI commands which is good, but all commands reference scripts that aren't provided in the bundle, making them not truly executable or verifiable. The CSV format expectations are deferred to a reference file that doesn't exist in the bundle, leaving a gap in practical guidance. | 2 / 3 |
Workflow Clarity | Steps are clearly sequenced and numbered, but there are no validation checkpoints—no step to verify CSV format before processing, no verification that output is correct, and no feedback loop for error recovery beyond a static error table. For a tax calculation workflow where errors could have financial consequences, validation steps are important. | 2 / 3 |
Progressive Disclosure | References to external files like 'references/exchange_formats.md' and 'references/implementation.md' are well-signaled, but no bundle files are actually provided, so the progressive disclosure structure is aspirational rather than functional. The Output section describes formats in prose when it could more effectively point to concrete examples. | 2 / 3 |
Total | 8 / 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.