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

—

Does it follow best practices?

Impact

—

No eval scenarios have been run

Securityby

Passed

No known issues

Quality

Content

85%

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

The body is concise and highly actionable with executable commands and clear step sequencing. It loses points only on workflow validation (no verification checkpoint for a batch calculation) and on progressive disclosure (two bundle files are never referenced from the body).

Suggestions

Add an explicit validation/verification step after the calculation (e.g. 'Verify total proceeds + income reconciles against source CSV; confirm every disposal has a matched lot before reporting') to add a feedback loop for this batch operation.

Reference references/examples.md and references/errors.md from the body (e.g. add pointers in the Examples and Error Handling sections) so all bundle files are discoverable one level deep.

Consider collapsing the duplicated 'Examples' section, which repeats commands already shown in Instructions, to tighten token usage.

Dimension	Reasoning	Score
Conciseness	Lean, action-oriented body with copy-paste bash commands and no padding explaining concepts Claude already knows; the disclaimer and prerequisites are short and earn their place.	3 / 3
Actionability	Provides fully executable, specific commands (e.g. 'python ${CLAUDE_SKILL_DIR}/scripts/tax_calculator.py --transactions ... --method fifo --year 2025') with flags and example file names — copy-paste ready.	3 / 3
Workflow Clarity	Steps are clearly numbered and sequenced, but this is a batch financial calculation with no explicit validation/verification checkpoint (e.g. confirm totals, sanity-check lot matching) — the missing feedback loop caps it at 2 per the rubric.	2 / 3
Progressive Disclosure	References to exchange_formats.md and implementation.md are one-level-deep and well-signaled, but two bundle files (examples.md, errors.md) exist with no in-body pointer, leaving them undiscoverable; structure is good but incomplete.	2 / 3
	Total	10 / 12 Passed

Description

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.

A strong description: concrete capabilities, explicit 'Use when' and trigger-phrase guidance, third-person voice, and a distinctive crypto-tax niche. It is concise without padding.

Dimension	Reasoning	Score
Specificity	Lists multiple concrete actions: 'cost basis tracking, capital gains computation, and Form 8949 generation' — three specific, distinct capabilities rather than vague language.	3 / 3
Completeness	Explicitly answers both 'what' (the opening capabilities) and 'when' via a dedicated 'Use when...' clause plus a 'Trigger with phrases like...' clause, matching the top anchor.	3 / 3
Trigger Term Quality	Provides natural trigger phrases a user would say ('calculate crypto taxes', 'generate tax report', 'cost basis FIFO', 'capital gains', 'Form 8949', 'crypto taxable events') with good coverage of common variations.	3 / 3
Distinctiveness Conflict Risk	Niche is clear (crypto tax obligations / cost basis) with distinct triggers unlikely to overlap with unrelated skills; the crypto-tax specificity sets it apart.	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
Commit: 607d11b

Reviewed: 2 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.