Content
11%Weight 40%Scale 1-5Reviews 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.
| Dimension | Reasoning | Score |
|---|---|---|
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 |