swarm-vat-agent

Audit gnubok VAT handling for Swedish compliance and reporting issues.

209|46|Updated Feb 13, 2026
One-click install
npx skills add https://github.com/erp-mafia/gnubok --skill swarm-vat-agent
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: swarm-vat-agent
Source: https://github.com/erp-mafia/gnubok/tree/main/.claude/skills/swarm-vat-agent
Command: npx skills add https://github.com/erp-mafia/gnubok --skill swarm-vat-agent

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This read-only audit lens identifies VAT handling discrepancies and edge cases in gnubok, helping teams ensure compliance with Swedish VAT rules.

Core Features & Use Cases

  • VAT rule validation across journal entries, rates, and mappings.
  • Edge-case detection for reverse charge, EU acquisitions, and VIES validation.
  • Comprehensive audit scope covering VAT reporting and per-rate allocations.

Quick Start

Review the codebase to audit VAT correctness and surface any issues in VAT handling.

Frequently Asked Questions about swarm-vat-agent

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

FAQPage Schema
How do I audit Swedish VAT correctness without writing custom code?

To audit Swedish VAT correctness without code, apply a read-only audit lens to core files like lib/bookkeeping/vat-entries.ts and lib/invoices/vat-rules.ts to validate BAS 2026 mappings, per-rate splitting, and Rutor mappings.

What edge cases should I check when validating Swedish VAT handling?

When validating Swedish VAT handling, check edge cases for reverse charge scenarios, EU acquisitions, and VIES validation to ensure compliance with per-rate splitting requirements and identify unsafe data flows or dependencies.

How does VIES validation work for Swedish moms reporting?

VIES validation for Swedish moms reporting checks currency handling, rounding, and error messaging across VAT declaration files to ensure reverse charge scenarios and EU acquisitions meet Swedish VAT requirements without unsafe dependencies.

Can I use this approach to audit per-rate splitting in VAT declarations?

Yes, you can audit per-rate splitting in VAT declarations by reviewing files like lib/reports/vat-declaration.ts and types/index.ts to surface discrepancies in Rutor mappings and verify guardrails meet Swedish VAT requirements.

What Swedish VAT reporting issues can automated codebase auditing detect?

Automated codebase auditing detects Swedish VAT reporting issues by identifying discrepancies in BAS 2026 mappings, VIES validation failures, incorrect reverse charge handling, and unsafe data flows within core VAT handling files.

Why does my Swedish VAT calculation fail on reverse charge scenarios?

Swedish VAT calculations fail on reverse charge scenarios when guardrails, error messaging, or currency handling in files like lib/vat/ and lib/invoices/vat-rules.ts do not meet Swedish VAT requirements, causing unsafe data flows.