SKILLEMALL.ai
GitHub ↗ RU Sign in

BD crypto-tax-agent

Crypto tax compliance skill for AI agents. Covers 1099-DA reconciliation, cost basis methods (FIFO/HIFO/SpecID), multi-chain transaction reconstruction via Etherscan V2 API, Form 8949 generation, DEX gap analysis, staking/airdrop classification, bridge handling, and wash sale analysis. Use when an agent needs to handle crypto tax work, analyze transaction history, or generate tax forms.

LeoYeAI/openclaw-master-skills Agent Skills author: LeoYeAI 2 files body ≈ 3 894 tokens Open the sourcegithub.com↗ analyzed 6 d ago

Crypto tax compliance skill for AI agents.

As a process D 43/100 · Unfinished process — weak spots: result and completion, when it triggers, inputs and preconditions

IntegrationFinanceAI and agentstype and topics are labelled automatically from the skill text
Runs in: OpenClaw Claude / Claude Code ChatGPT / Codex Gemini CLI Cursor GitHub Copilot / VS Code Qwen Code Kimi Code CLI Z.ai (GLM) DeepSeek (Deep Code) Mistral Vibe LangChain (deepagents) Goose OpenCode
JSON
Technical rating
B
94/100
safety, quality, tests
Safety 60%
100
Quality 40%
85
Run on models
none yet
Process rating
D
43/100
Unfinished process
Result and completion w 14
0
Inputs and preconditions w 11
0
Failures and branches w 10
0
the three weakest of ten parameters · all ten

How to improve

    For the model run — optional
    • Your own cases (evals/evals.json, 4–6 real requests with expected answers): the full check would then run those instead of a model-drafted suite.
    • A spec.yaml with trigger phrases and assertions — a behaviour contract for CI; `skilltest init` writes a template.

    Guard findings · 0

    ✓ No critical or high findings

    Files scanned: 2. Evidence is masked. Grey chips explain why severity was lowered.

    Against the Agent Skills spec

    ✓ No remarks against the Agent Skills spec

    Process rating: all ten parameters 43/100

    • 0Result and completion. Does not say what the result is
    • 0Inputs and preconditions. Does not say what the process needs to start
    • 0Failures and branches. Linear process with no failure handling
    • 20When it triggers. No condition that starts the skill
    • 30Running it twice. 3 mutating operations with no state check
    • 60Tools and files. Uses tools (web) that frontmatter does not declare
    • 85Steps. 90 steps, 1 vague phrases
    • 100Consistency. Name and required fields are in place
    • 100Execution cost. Instruction body is 3894 tokens
    • 100Progress reporting. Reports progress
    • medium Safety rules and hard prohibitions inside a skill: they belong in the system prompt, here they protect nothing
    • low 13 top-level sections: this looks like several domains in one skill

    Everything here is measured from the skill text rather than judged by a model, so the numbers are checkable. A parameter weighs more when it is a more common reason for the process to stall.

    Quality signals

    • +5Description has no quoted example phrases that should trigger the skill
    • +4Description does not say when NOT to use the skill (false activations)
    • +3Output format is not stated: the model decides each time
    • +2Single-language instructions
    • +3Description length 389: enough signal without eating the budget
    • +4Structure: 39 headings
    • +3Step-by-step instructions: 90 items
    • +4Has examples (3 code blocks)
    • +1License stated

    Quality base 70; lint remarks subtract, signals add up to 100. Result: 85.