Content
22%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 brochure for the skill rather than the skill itself: it describes capabilities and includes a FAQ and promotional links, but contains no operational guidance, technical specifics, or workflow that Claude could execute. The detailed content it advertises (field structures, questionnaires, timelines) is neither inline nor in referenced files.
Suggestions
Replace the promotional sections ('Why this beats prompting it yourself', the FAQ, footer links) with operational guidance: a compliance-decision checklist for VeriFactu/TicketBAI/SII/foral regimes and a step-by-step method for validating software against Real Decreto 1007/2023.
Inline or reference the actual technical content promised by the description: the SHA-256 hash-chaining record structure, the high-level and cancellation invoice field layouts, QR code requirements, and a dated table of the 2027/2028 Crea y Crece and VeriFactu deadlines (marked with their legislative source so staleness is detectable).
Turn the 'Example' into a concrete pattern (input facts to collect, classification logic, and the shape of a correct answer) so Claude has a workflow with checkpoints instead of a single marketing sample output.
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The body is a promotional product page with several padded, non-instructional sections: 'Why this beats prompting it yourself', a six-question FAQ that largely restates the description, and creator/store footer links. It does not hit anchor 1's 'explains concepts Claude already knows', but the amount of marketing filler fits anchor 2's 'several unnecessary explanations or padded sections'. | 2 / 5 |
Actionability | There is no code, command, field layout, schema, or step anywhere; the body only describes capabilities ('Outlines the specific technical field structures', 'Generates vendor-specific questionnaires') without delivering them. The single Example Q&A and high-level hints like 'implement SHA-256 hash chaining, event logs, and mandatory QR codes' constitute minimal concrete guidance, placing it above anchor 1 but squarely at anchor 2. | 2 / 5 |
Workflow Clarity | No sequence of steps exists at all — nothing tells Claude how to classify a business under VeriFactu/TicketBAI/SII, validate software, or produce the promised questionnaire, so even a rough sequence is absent per anchor 1. The simple-skill exception does not rescue it because the body never frames an unambiguous single action to perform. | 1 / 5 |
Progressive Disclosure | Sections are clearly labeled and the body is a short, readable overview, but there are no references to any detail files and it openly states 'Scripts, extension source, and templates from the original package are not in this folder', leaving the actual knowledge base absent rather than appropriately split out. This lands at anchor 3 (some structure, organization gaps) rather than 2, since nothing is inlined that belongs elsewhere. | 3 / 5 |
Total | 8 / 20 Passed |