scanner-claw

Extracts OKX account data via ATK CLI into a standardized tax dataset.

Updated Aug 27, 2026
One-click install
npx skills add https://github.com/Skottbie/VeriTax-Plus --skill scanner-claw
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: scanner-claw
Source: https://github.com/Skottbie/VeriTax-Plus/tree/main/skills/scanner-claw
Command: npx skills add https://github.com/Skottbie/VeriTax-Plus --skill scanner-claw

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill requires python-dotenv, requests.

What problem does it solve?

VeriTax scanner-claw eliminates the manual, error-prone extraction of OKX data needed for crypto tax reporting by programmatically collecting balances, trades, deposits, withdrawals, and earn records via the OKX ATK CLI and producing a ready-to-use tax dataset for downstream modules like ComplianceClaw and OptimizerClaw.

Core Features & Use Cases

  • Automatically pulls spot and swap trades, deposits, withdrawals, and earn records from OKX accounts and normalizes them into VeriTax's standard schema.
  • Generates a complete tax dataset for downstream modules like ComplianceClaw, OptimizerClaw, and AuditorClaw, enabling end-to-end tax workflows.
  • Supports full batch scans, incremental daily deltas, and quarterly archives with optional demo and archiving workflows to ensure reproducibility and auditability.

Quick Start

Use the scanner to pull all OKX data for a given year and generate the standardized tax dataset.

Frequently Asked Questions about scanner-claw

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I automate OKX data collection for crypto tax compliance?

You can automate OKX tax data collection by invoking a scanner with a specific year and scope to fetch spot, swap, earn, deposits, withdrawals, and balances via the ATK CLI, producing a normalized dataset for compliance workflows.

What is the best way to extract OKX trades and earn records into a standardized tax dataset?

The best way to extract OKX records into a standardized tax dataset is using a scanner that programmatically pulls and normalizes trades, earn records, deposits, withdrawals, and balances into a verifiable schema for downstream tax modules.

Can I pull incremental daily deltas or quarterly archives from OKX for tax reporting?

Yes, the scanner supports full batch scans, incremental daily deltas, and quarterly archives from OKX. It includes optional demo and archiving workflows to ensure your tax data collection remains reproducible and auditable.

Do I need python-dotenv and requests to run OKX tax data scans?

Yes, you need python-dotenv and requests installed in your environment to run the scanner. These dependencies facilitate the ATK CLI interactions and environment variable management required for secure OKX data extraction.

How does the scanner ensure data provenance and validation for OKX tax reporting?

The scanner enforces data provenance, strict validation, and auditable traces during OKX data collection. This ensures deterministic results and safe operation, yielding a verifiable tax dataset for downstream compliance and auditing.

What limitations exist when using the ATK CLI for OKX tax data collection?

The scanner is limited to fetching OKX account data types explicitly supported by the ATK CLI, specifically spot, swap, earn, deposits, withdrawals, and balances. It relies on python-dotenv and requests without offering external exchange integrations.