CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

nex-einvoice-de

Expert guide for German E-Rechnung compliance, XRechnung/ZUGFeRD formats, and GoBD archiving. Use when: Determine the correct e-invoice issuance date based on turnover; Generate GoBD-compliant Verfahrensdokumentation templates; Map UStG mandatory fields to structured XML business terms.

Quality

55%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide
SecuritybySnyk

Passed

No findings from the security scan

Fix and improve this skill with Tessl

tessl review fix ./plugins/nex-compliance/skills/nex-einvoice-de/SKILL.md

The canonical home for this skill is nex-einvoice-de in NexaiGuy/nex-ai-skills

SKILL.md
Quality
Evals
Security

Quality

Content

11%Weight 40%Scale 1-5

Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.

The body is a marketing landing page rather than an operational skill: it enumerates capabilities and includes one demo Q&A but contains no decision logic, mappings, templates, or workflows for an agent to execute, and the bundle it advertises is not present. Structurally it reads fine, but nearly every operational dimension fails.

Suggestions

Replace the marketing sections ('The problem', 'Why this beats prompting it yourself', the FAQ) with the actual operational content: the UStG §14-to-EN 16931 field mapping table, the XRechnung/ZUGFeRD profile decision rules, and a Verfahrensdokumentation template skeleton.

Add explicit step-by-step workflows, e.g. for verifying an incoming XML invoice: parse the invoice, check each §14 UStG mandatory field against the EN 16931 business term, report missing fields, and validate against the applicable profile — with a validate/fix/retry checkpoint.

Either include the referenced scripts and templates in the bundle (references/, scripts/, assets/) and link to them from clearly signaled sections, or remove claims about 'full logic package' content that is not shipped, and move dated legal status (June 2026, 2027/2028 waves) into a dedicated maintained section.

DimensionReasoningScore

Conciseness

Marketing padding dominates: 'The problem', 'Why this beats prompting it yourself', and a five-question FAQ ('What exactly is included in the purchase of this skill?') add no operational value, and time-sensitive claims ('verified June 2026 legal status', 'transition waves for 2027 and 2028') are stated inline rather than in a maintained/deprecated section. It avoids lengthy explanations of concepts Claude already knows, so it is not a 1.

2 / 5

Actionability

The body only describes capabilities ('Provides format decision logic', 'Produces templates for GoBD-compliant Verfahrensdokumentation', 'Maps paragraph 14 UStG mandatory invoice fields') without ever providing the decision rules, field-mapping table, template content, or commands to execute them — even the promised scripts and templates are explicitly absent from the folder.

1 / 5

Workflow Clarity

No multi-step process is sequenced anywhere: readiness assessment, format selection, field mapping, and documentation drafting are each named as capabilities but never turned into ordered steps, and a verification use case ('Verify if an incoming XML invoice meets the paragraph 14 UStG mandatory field requirements') lacks any validation loop.

1 / 5

Progressive Disclosure

The body has clear section headers but is a promotional README whose substance lives in bundled files that are declared missing ('Scripts, extension source, and templates from the original package are not in this folder'), and the FAQ plus promotional footer are inline filler. It is navigable, so not a 1, but nothing is appropriately placed or split.

2 / 5

Total

6

/

20

Passed

Description

78%Weight 40%Scale 1-5

Based on the skill's description, can an agent find and select it at the right time? Clear, specific descriptions lead to better discovery.

A well-targeted description with explicit 'Use when' triggers and precise domain vocabulary that users in this space would naturally use. Its main weakness is the vague 'Expert guide' framing for the 'what' half, which lists domains instead of the concrete actions the trigger clauses already contain.

DimensionReasoningScore

Specificity

The 'Use when' clause lists three concrete actions ('Determine the correct e-invoice issuance date based on turnover', 'Generate GoBD-compliant Verfahrensdokumentation templates', 'Map UStG mandatory fields to structured XML business terms'), but the opening 'Expert guide for German E-Rechnung compliance...' is a buzzword-style domain list rather than action verbs, and body-claimed capabilities like readiness checklists and format decision logic are not covered.

4 / 5

Completeness

Both a 'what' ('Expert guide for German E-Rechnung compliance, XRechnung/ZUGFeRD formats, and GoBD archiving') and an explicit 'Use when:' with three concrete trigger phrases are present, but the 'what' half is a vague self-promotional domain list rather than the direct action statements the trigger clause already demonstrates.

4 / 5

Trigger Term Quality

Includes the exact natural terms domain users say ('E-Rechnung', 'XRechnung/ZUGFeRD', 'GoBD archiving', 'UStG mandatory fields', 'Verfahrensdokumentation'), but misses common synonyms such as 'e-invoice', 'electronic invoicing', or 'VAT invoice' that a user might phrase differently.

4 / 5

Distinctiveness Conflict Risk

The description carves out a clear niche (German E-Rechnung compliance with named formats XRechnung/ZUGFeRD and GoBD archiving) with distinct, domain-specific triggers, creating minimal overlap risk with other skills.

5 / 5

Total

17

/

20

Passed

Validation

100%

Checks the skill against the spec for correct structure and formatting. All validation checks must pass before discovery and implementation can be scored.

Validation — 16 / 16 Passed

Validation for skill structure

No warnings or errors.

Repository

NexaiGuy/nex-ai-skills

Path

plugins/nex-compliance/skills/nex-einvoice-de/SKILL.md

Reviewed

Table of Contents

Is this your skill?

If you maintain this skill, you can claim it as your own. Once claimed, you can manage eval scenarios, bundle related skills, attach documentation or rules, and ensure cross-agent compatibility.