CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

nex-einvoice-pl

Technical implementation guide for Polish KSeF e-invoicing, FA(3) schemas, and API onboarding. Use when: Map ERP invoice data to the mandatory FA(3) structured XML format; Design API authentication flows for test and production KSeF environments; Implement the offline24 procedure with required QR code generation logic.

Quality

62%

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-pl/SKILL.md

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

SKILL.md
Quality
Evals
Security

Quality

Content

18%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 implementation guide: it describes capabilities and includes one concrete korekta example, but contains no workflows, no schema/API detail, and no bundled reference files — and admits the actual package contents are absent. It functions as a store listing, not as operational skill content.

Suggestions

Replace the promotional sections ("Why this beats prompting it yourself", the purchase FAQ, creator links) with the actual technical content: FA(3) field mapping tables, KSeF 2.0 endpoint/auth examples, and offline24 QR code requirements.

Add explicit step-by-step workflows with validation checkpoints for the three advertised processes (ERP-to-FA(3) mapping, API onboarding per environment, offline24 contingency submission windows).

Ship the promised materials as one-level-deep reference files (e.g. references/fa3-fields.md, references/onboarding.md, references/offline24.md) and reference them clearly from SKILL.md instead of asserting they exist elsewhere.

DimensionReasoningScore

Conciseness

Several sections are padded sales copy rather than instructions: "Why this beats prompting it yourself", the purchase FAQ ("What specific documentation and assets are included in this purchase", "Which AI agents or models are compatible with this skill"), and trailing creator/promo links. Not 3 because promotional filler is the dominant character of the body rather than incidental over-explanation, and undated time-sensitive claims ("2026 deadlines", "2027 cutoff") add staleness risk.

2 / 5

Actionability

Only one passage gives concrete field-level guidance ("Set RodzajFaktury to 'KOR'... TypKorekty to 'A'... PrzyczynaKorekty... DaneFaKorygowanej"), while the rest describes rather than instructs ("Outlines onboarding workflows", "Defines offline24 contingency procedures", "Generates readiness checklists") with no XML samples, API endpoints, commands, or field tables. Not 3 because concrete guidance is a single isolated example, not 'some concrete guidance' spread across the skill.

2 / 5

Workflow Clarity

No sequenced steps exist anywhere: API onboarding, offline24 handling, and ERP-to-FA(3) mapping are named but never ordered, and there are no validation checkpoints for XML generation and batch submission to KSeF (which alone caps this dimension at 3). Not 2 because not even a rough sequence is present — the body has zero enumerated procedures.

1 / 5

Progressive Disclosure

The skill's claimed depth (FA(3) field mapping guides, onboarding protocols, compliance checklists) belongs in bundled reference files, yet no references/, scripts/, or assets/ exist and the body states "Scripts, extension source, and templates from the original package are not in this folder". Not 3 because the in-file headers organize promotional copy rather than skill content, and there is no reference layer at all for the material the skill promises.

2 / 5

Total

7

/

20

Passed

Description

87%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 strong description: it names a well-defined niche, states concrete capabilities, and provides an explicit 'Use when:' clause with three specific trigger scenarios. Only minor improvements possible around synonym coverage (faktura, KSeF 2.0, VAT invoice) and covering the correction-invoice and compliance-deadline capabilities the body advertises.

DimensionReasoningScore

Specificity

Lists three concrete actions ("Map ERP invoice data to the mandatory FA(3) structured XML format", "Design API authentication flows for test and production KSeF environments", "Implement the offline24 procedure with required QR code generation logic") comparable to the anchor-4 example. Not 5 because capabilities the body claims (correction/advance invoices, compliance checklists, deadline tracking) are absent, leaving minor coverage gaps.

4 / 5

Completeness

Explicitly answers both: "Technical implementation guide for Polish KSeF e-invoicing, FA(3) schemas, and API onboarding" (what) and an explicit "Use when:" clause with three concrete trigger conditions (when). Not 4 because the 'when' is fully explicit with concrete triggers, matching the anchor-5 example pattern.

5 / 5

Trigger Term Quality

Good natural keyword coverage for the domain ("Polish KSeF e-invoicing", "FA(3)", "ERP invoice data", "QR code", "offline24") that users would genuinely say. Not 5 because common synonyms and variations like "faktura", "VAT invoice", "KSeF 2.0", or "Poland e-invoice" are missing.

4 / 5

Distinctiveness Conflict Risk

Occupies a clear niche (Polish KSeF clearing, FA(3) schema, offline24 contingency) with distinct triggers unlikely to fire for any other skill. Minimal conflict risk, matching the anchor-5 example.

5 / 5

Total

18

/

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-pl/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.