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".

Quality

82%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide

Securityby

Passed

No findings from the security scan

Quality

Content

65%Weight 40%Scale 1-3

Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.

The content is highly actionable and well-sequenced, with real, well-signaled reference files. It loses points for redundancy between the Instructions and Examples sections and for not integrating validation checkpoints or linking all existing reference files.

Suggestions

Remove the standalone 'Examples' section or fold its non-duplicate cases into 'Instructions'; the four examples mostly restate commands already shown, which wastes tokens.

Add an explicit validation checkpoint to the workflow (e.g. reconcile total proceeds against the sum of disposal proceeds, or run with --verbose --show-lots to verify lot matching before generating the final Form 8949).

Link references/errors.md and references/examples.md from the body instead of inlining an Error Handling table and Examples that overlap with those dedicated files.

Dimension	Reasoning	Score
Conciseness	The body is mostly lean and assumes Claude's competence, but the 'Examples' section largely re-shows commands already given in 'Instructions', and the '2025 = tax year' annotation is repeated across many invocations, adding redundant tokens.	2 / 3
Actionability	Every step gives a complete, copy-paste-ready command with concrete flags, file paths, and expected outputs (e.g. '--method hifo --year 2025 --output form_8949.csv --format csv').	3 / 3
Workflow Clarity	The six numbered steps are clearly sequenced, but there is no explicit validation checkpoint in the flow; error handling is presented as a reactive lookup table rather than a validate-then-proceed step integrated into the workflow.	2 / 3
Progressive Disclosure	The two referenced files (exchange_formats.md, implementation.md) are real, one level deep, and clearly signaled, but the inline Error Handling table and Examples section duplicate content that has dedicated reference files (errors.md, examples.md) which are never linked from the body.	2 / 3
	Total	9 / 12 Passed

Description

100%Weight 40%Scale 1-3

Based on the skill's description, can an agent find and select it at the right time? Clear, specific descriptions lead to better discovery.

The description is specific, uses third person, and clearly separates capabilities from triggers. It is a strong, concise description with no significant weaknesses.

Dimension	Reasoning	Score
Specificity	Lists multiple concrete actions — 'cost basis tracking, capital gains computation, and Form 8949 generation' — naming exactly what the skill does rather than speaking generically.	3 / 3
Completeness	Explicitly answers both 'what' (calculate cryptocurrency tax obligations…) and 'when' (a 'Use when…' clause plus a 'Trigger with phrases like…' list), satisfying both requirements.	3 / 3
Trigger Term Quality	Trigger phrases like 'calculate crypto taxes', 'generate tax report', 'cost basis FIFO', 'capital gains', 'Form 8949', and 'crypto taxable events' are natural terms a user would actually say.	3 / 3
Distinctiveness Conflict Risk	The crypto-tax/Form 8949 niche is narrow and the triggers are domain-specific, making collision with unrelated skills unlikely.	3 / 3
	Total	12 / 12 Passed

Validation

87%

Warnings & errors only

Checks the skill against the spec for correct structure and formatting. All validation checks must pass before discovery and implementation can be scored.

Validation — 14 / 16 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	14 / 16 Passed

Repository: jeremylongshore/claude-code-plugins-plus-skills
Path: plugins/crypto/crypto-tax-calculator/skills/calculating-crypto-taxes/SKILL.md
Commit: 4c47e33

Reviewed: 3 days ago

Table of Contents

Discovery Implementation Validation

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.