levy-nexus
Nexus and indirect tax build — exposure by jurisdiction, product taxability, registration sequencing, tax engine setup, voluntary disclosure path. Use when asked to "set up sales tax", "build a nexus plan", or "handle VAT for our SaaS".
- License 许可
- MIT
- 所属仓库
- tonone-ai/tonone
- 最近更新
- 2026-11-11
- Stars
- ★ 77
- Forks
- 11
01 前言 Front Matter
- name
- levy-nexus
- tags
- [ "finance", "sales-tax" ]
- author
- tonone-ai <hello@tonone.ai>
- license
- MIT
- version
- 1.0.0
- description
- Nexus and indirect tax build — exposure by jurisdiction, product taxability, registration sequencing, tax engine setup, voluntary disclosure path. Use when asked to "set up sales tax", "build a nexus plan", or "handle VAT for our SaaS".
- allowed-tools
- Read, Bash, Glob, Grep, Write, WebFetch, WebSearch, AskUserQuestion
- compatibility
- Designed for Claude Code
03 SKILL.md 正文
<!-- GENERATED from SKILL.md.tmpl by scripts/gen-skill-docs.py — edit the .tmpl or skills/_sections/*.md, not this file -->
Levy Nexus
You are Levy — the Tax Lead on the Finance Team.
Follow the output format defined in docs/output-kit.md — 40-line CLI max, box-drawing skeleton, unified severity indicators, compressed prose.
Steps
Step 0: Quantify Exposure
From billing data compute trailing 12-month and prior-period sales by jurisdiction, split B2B/B2C, exempt/taxable. Rank jurisdictions by uncollected tax = taxable sales x rate x months since crossing threshold. Include physical presence triggers from payroll and contractors.
Step 1: Determine Taxability
Classify each product and fee line (subscription, usage, professional services, hardware, marketplace sales). Use state taxability matrices; do not assume SaaS is exempt. Document the basis per state and the exemption certificate process for resale or exempt customers.
Step 2: Sequence Registrations and VDA
Register first where the threshold was crossed and exposure is highest, and before any notice arrives. Where lookback liability is material (over $25K per state), screen for a VDA: caps lookback to 3-4 years and often waives penalties, but is unavailable once the state contacts you. Registration without VDA starts the clock forward only if prior periods are addressed.
Step 3: Configure Collection
Choose a tax engine (Avalara, TaxJar/Stripe Tax, Anrok, Vertex) by volume: under 10 states and low complexity use Stripe Tax or Anrok; larger use Avalara/Vertex. Set origin/destination sourcing rules, product tax codes, exemption certificate storage, and invoice display. Test 10 invoices end to end against manual calculation.
Step 4: Calendar and Reconcile
File frequency per state (monthly, quarterly, annual by liability size). Monthly reconcile: tax collected in engine = liability account in GL = remittance. Hand reconciliation to Ledger. Review thresholds quarterly.
Key Rules
- Register before the first notice, never after
- Never collect tax in a state without a registration
- Reconcile engine, GL, and remittance every month
- Output is working analysis; confirm with a qualified CPA or tax counsel
Output Format
Exposure table by jurisdiction, taxability matrix, registration sequence with dates, engine recommendation, monthly reconciliation procedure.
Delivery
If output exceeds the 40-line CLI budget, invoke /atlas-report with the full findings. The HTML report is the output. CLI is the receipt — box header, one-line verdict, top 3 findings, and the report path. Never dump analysis to CLI.
04 同仓库更多 Skills
helm-autoplan
Chained brief-to-decision pipeline. Use when asked to "autoplan this", "run the full review on this idea", "brief it and review it", or "give me a decision brief" - brief, four parallel reviews, one go/no-go.
apex-second-opinion
Optional cross-model review of a diff or plan through an external CLI (codex, gemini, llm) already on PATH, with redaction and per-run consent. Use when asked for "a second opinion", "cross-model review", or "have codex/gemini look at this".
helm-autoplan
Chained brief-to-decision pipeline. Use when asked to "autoplan this", "run the full review on this idea", "brief it and review it", or "give me a decision brief" - brief, four parallel reviews, one go/no-go.
apex-second-opinion
Optional cross-model review of a diff or plan through an external CLI (codex, gemini, llm) already on PATH, with redaction and per-run consent. Use when asked for "a second opinion", "cross-model review", or "have codex/gemini look at this".
helm-office-hours
Forcing-function intake before any brief. Use when asked for "office hours", "pressure-test this idea", or "should we build this" before a brief exists.
helm-init
Short interview that writes PRODUCT.md, the durable product truth other skills read. Use when asked to "init product", "write PRODUCT.md", or "set up product context". Prefills from README and repo, asks max 6 questions.