CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

nex-einvoice-es

Navigate Spanish VeriFactu and Crea y Crece compliance with updated 2027 deadlines and technical field requirements. Use when: Map the transition timeline for IS taxpayers and autónomos through 2028; Define technical requirements for SHA-256 hash chaining in invoice records; Evaluate the impact of TicketBAI vs VeriFactu for multi-regional businesses.

Quality

57%

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 ./skills/nex-einvoice-es/SKILL.md
SKILL.md
Quality
Evals
Security

Quality

Content

22%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 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.

DimensionReasoningScore

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

Description

73%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-constructed description with explicit Use-when triggers and highly distinctive domain terminology. Its main weakness is a generic capability verb ('Navigate... compliance') that never states the skill's concrete outputs, and some missing natural synonyms (Spanish e-invoicing, AEAT, factura electrónica).

DimensionReasoningScore

Specificity

The capability statement 'Navigate Spanish VeriFactu and Crea y Crece compliance' is generic, and the concrete actions ('Map the transition timeline for IS taxpayers and autónomos through 2028', 'Define technical requirements for SHA-256 hash chaining', 'Evaluate the impact of TicketBAI vs VeriFactu') all live in the Use-when triggers rather than describing what the skill itself does. Domain is named with several concrete actions, but coverage of actual capabilities (validating software, schema design, questionnaires) is missing, matching anchor 3 rather than 4.

3 / 5

Completeness

Both parts are present with an explicit 'Use when:' clause containing three concrete trigger phrases, so the missing-trigger cap of 3 does not apply and it sits above anchor 4's generic-when example. However, the 'what' ('Navigate... compliance with updated 2027 deadlines and technical field requirements') is too vague to 'clearly and explicitly' answer what the skill does, keeping it below anchor 5.

4 / 5

Trigger Term Quality

Strong natural terms a user with this need would say: 'VeriFactu', 'Crea y Crece', 'TicketBAI', 'SHA-256 hash chaining', 'IS taxpayers', 'autónomos', 'transition timeline', '2027 deadlines'. Common synonyms and variations like 'Spanish e-invoicing', 'factura electrónica', 'AEAT', or 'Spain invoicing mandate' are missing, which fits anchor 4 (good coverage, a few natural terms missing) rather than 5.

4 / 5

Distinctiveness Conflict Risk

The description occupies a clear niche (Spanish VeriFactu / Crea y Crece / TicketBAI regulatory compliance) with distinct, unambiguous trigger terms that would not fire for any other skill. It matches anchor 5's 'clear niche with distinct triggers; minimal conflict risk'.

5 / 5

Total

16

/

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

skills/nex-einvoice-es/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.