master-claw

Coordinate four Claws to route a VeriTax tax analysis with Merkle proofs.

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

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

The MasterClaw orchestrates an end-to-end VeriTax tax workflow by sequencing four specialized Claws (ScannerClaw, ComplianceClaw, OptimizerClaw, AuditorClaw) to deliver a complete tax analysis for a given year and jurisdiction.

Core Features & Use Cases

  • End-to-end orchestration: coordinates data collection, tax calculation, optimization, and auditable proof generation across the four Claws.
  • Incremental, auditable outputs: records step_hashes and builds a Merkle-proven audit chain for compliance and verification.
  • Model routing and fault tolerance: includes timeouts, downgrade behavior to autonomous MasterClaw execution, and strict anti-repetition rules to ensure safe operation.

Quick Start

To start, run the MasterClaw to auto-route a tax year and jurisdiction through the full end-to-end VeriTax pipeline.

Frequently Asked Questions about master-claw

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

FAQPage Schema
How do I orchestrate an end-to-end tax compliance workflow for a specific jurisdiction?

Tax workflow orchestration coordinates multiple specialized processing steps—scanning, compliance checks, optimization, and auditing—into a single automated pipeline for a given tax year and jurisdiction, producing a structured audit-ready result.

How do I generate Merkle proofs for audit-ready tax analysis outputs?

Incremental hash propagation records step_hashes during the tax workflow to build a Merkle-proven audit chain, ensuring compliance verification and producing a final structured result with an IPFS CID for auditable tax analysis.

What's the best way to handle dynamic optimizer and auditor steps in tax loss harvesting workflows?

Dynamic optimizer and auditor steps are triggered when tax loss harvesting or specific jurisdiction considerations require them, applying end-to-end workflow routing to adapt the tax analysis pipeline dynamically during execution.

Does the VeriTax tax workflow handle timeouts and fault tolerance during compliance orchestration?

Yes, the workflow includes model routing with timeouts, downgrade behavior to autonomous execution, and strict anti-repetition rules to maintain safe operation and fault tolerance during compliance orchestration.

Do I need specialized tools to route a complete tax analysis pipeline?

Yes, routing a complete tax analysis requires coordinating four specialized Claws—ScannerClaw, ComplianceClaw, OptimizerClaw, and AuditorClaw—under a mandatory tool-use protocol to collect data, calculate, optimize, and generate auditable proofs.

When should I not use automated tax workflow orchestration?

Automated tax workflow orchestration may not suit scenarios outside its scope: it is designed for complete VeriTax analysis requiring dynamic optimizer and auditor steps, and may be unnecessary for simple tax calculations not needing Merkle-proven audit chains.