swarm-sie-agent

Audit SIE4 import/export correctness in gnubok for encoding, record coverage, and migration integrity.

209|46|Updated Feb 13, 2026

Search Tags:#audit #encoding #data-integrity #read-only #import-export #gnubok #sie4

Ready to run

npx skills add https://github.com/erp-mafia/gnubok --skill swarm-sie-agent

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: swarm-sie-agent
Source: https://github.com/erp-mafia/gnubok/tree/main/.claude/skills/swarm-sie-agent
Command: npx skills add https://github.com/erp-mafia/gnubok --skill swarm-sie-agent

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Audits the SIE4 import/export workflow in gnubok using a read-only lens to verify data integrity, encoding handling, and multi-year migration readiness.

Core Features & Use Cases

SIE4 coverage verification: validates record types (#VER, #TRANS, #IB, #UB, #SRU, #KONTO, #FNAMN, #ORGNR) and ensures correct export generation.
Encoding and mojibake handling: detects CP437/Latin-1/UTF-8 issues and maintains robust text integrity.
Audit trail integrity: preserves original voucher numbers and supports multi-year continuity checks.
Non-destructive analysis: never writes data, creates tickets, or commits changes; designed for safe auditing.

Quick Start

Invoke the swarm-sie-agent with the /swarm command to perform a read-only audit of gnubok's SIE4 import/export.

Frequently Asked Questions about swarm-sie-agent

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

FAQPage Schema

How do I audit SIE4 import and export files for encoding and data integrity issues?▼

You can audit SIE4 files for encoding and data integrity by running a read-only analysis that checks record coverage across #VER, #TRANS, #IB, and #UB, while detecting CP437, Latin-1, and UTF-8 encoding issues to ensure text integrity.

What is a read-only SIE4 audit and how does it verify multi-year migration continuity?▼

A read-only SIE4 audit verifies multi-year migration continuity by checking original voucher numbers and record coverage across primary and secondary SIE files without writing data, creating tickets, or committing any code changes.

How do I check if my SIE4 export correctly includes required record types like #TRANS and #SRU?▼

Checking SIE4 export correctness requires validating the presence and structure of mandatory record types including #VER, #TRANS, #IB, #UB, #SRU, #FNAMN, #ORGNR, and #DIM to ensure complete and accurate file generation.

Does the SIE4 audit process support detecting mojibake from mixed CP437 and UTF-8 encodings?▼

Yes, the SIE4 audit process detects mojibake by analyzing text integrity across CP437, Latin-1, and UTF-8 encodings, ensuring character data remains robust and correctly mapped during file imports and exports.

Can I run a safe SIE4 file analysis without risking modifications to my accounting data?▼

You can run a safe SIE4 file analysis using a non-destructive audit approach that preserves original data by strictly avoiding writes, ticket creation, and code commits throughout the entire verification process.

What are the limitations of a read-only approach to SIE4 migration auditing?▼

The limitation of a read-only SIE4 audit is that it can identify encoding errors, missing records, and migration gaps but cannot automatically fix them, requiring manual intervention to correct any detected data integrity issues.