CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

nex-webshop-compliance-eu

Audits an EU webshop against consumer law: pre-contract information, the order button, withdrawal rights, price display and cookie consent. Use when: Audit checkout flows for hidden costs and button wording; Generate GPSR-compliant product page checklists; Create legal withdrawal forms and 14-day return policies.

Quality

67%

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-webshop-compliance-eu/SKILL.md

The canonical home for this skill is nex-webshop-compliance-eu in NexaiGuy/nex-ai-skills

SKILL.md
Quality
Evals
Security

Quality

Content

26%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 reads as a product landing page rather than operational skill guidance: it describes what the skill does and shows one sample output, but provides no audit criteria, no templates, and no sequenced workflow for Claude to follow. Structure is decent for a standalone file, yet the bulk of the content (marketing FAQ and promo links) consumes tokens without improving execution.

Suggestions

Replace the high-level "What it does" bullets with a sequenced audit workflow: which funnel areas to inspect in what order, what specifically to check in each (e.g., the required order-button wording, the mandatory pre-contract information items, the withdrawal-form content), and how to compile findings into the audit summary format shown in the Example.

Provide the concrete artifacts the description promises — a withdrawal form template, a GPSR product-page checklist, and the specific legal criteria for button wording and price/delivery-cost display — either inline or in referenced reference files, so the guidance is executable rather than descriptive.

Delete the six-question marketing FAQ and the promotional header/footer; they consume roughly 40% of the body's tokens with zero operational value and are the main conciseness drain.

DimensionReasoningScore

Conciseness

The six-question marketing FAQ ("What exactly is included in the purchase of the nex-webshop-compliance-eu skill?", "Who is the ideal user for this compliance skill?", "Which AI agents can run this compliance auditing skill?") plus the promotional header and footer links constitute roughly 40% of the body and add no operational value. This matches "noticeably verbose; several unnecessary explanations or padded sections"; a 3 would require the padding to be incidental rather than a major structural portion.

2 / 5

Actionability

The body only describes capabilities at a high level ("Checks the pre-contract information duties", "Verifies the order confirmation button wording and the no-hidden-cost rule") without giving Claude any concrete criteria, checklist items, button wording requirements, or withdrawal form text to execute with — the Example shows an output format but no method for producing it. This fits "minimal concrete guidance; high-level hints but missing the specific steps"; it avoids a 1 only because the named audit areas and the sample audit output are concrete high-level hints.

2 / 5

Workflow Clarity

No sequence exists anywhere in the body: the audit process (which areas to inspect, in what order, how to verify findings, how to assemble the output) is never stepped through, and the single Example jumps straight from request to finished result. This matches "steps missing or incoherent; no sequence"; a 2 would require at least a rough sequence to be present.

1 / 5

Progressive Disclosure

The single-file body (~66 lines) is well-organized into clear sections (What it does, Use cases, Known limitations, Example, Questions) with no nested references, and no bundle files exist to mis-organize. It falls short of a 5 because the body exceeds the simple-skill line and the operational detail it promises (legal checklists, withdrawal form templates) clearly belongs in reference files that are explicitly absent ("Scripts, extension source, and templates from the original package are not in this folder").

4 / 5

Total

9

/

20

Passed

Description

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

The description is strong: third-person voice, specific and comprehensive capability statements, an explicit "Use when:" clause with concrete triggers, and a well-delineated niche. The only weakness is moderate synonym coverage (e.g., no "e-commerce", "refund", or "GDPR" phrasing) that leaves a few natural user phrasings unaccounted for.

DimensionReasoningScore

Specificity

The description lists multiple concrete actions — "Audits an EU webshop against consumer law: pre-contract information, the order button, withdrawal rights, price display and cookie consent", "Generate GPSR-compliant product page checklists", "Create legal withdrawal forms and 14-day return policies" — comprehensively covering the skill's stated domain. It matches the anchor for comprehensive concrete actions; a 4 would require minor coverage gaps, which are not evident.

5 / 5

Completeness

It explicitly answers both questions: the "what" (audits pre-contract information, order button, withdrawal rights, price display, cookie consent) and an explicit "Use when:" clause with concrete triggers ("Audit checkout flows for hidden costs and button wording; Generate GPSR-compliant product page checklists; Create legal withdrawal forms and 14-day return policies"). A 4 would require the "when" to be less explicit, which it is not.

5 / 5

Trigger Term Quality

Good natural keyword coverage: "webshop", "consumer law", "checkout", "hidden costs", "withdrawal", "return policies", "GPSR", "cookie consent" are phrases users would plausibly say. It falls short of a 5 because common synonyms like "e-commerce", "online shop", "refund", "GDPR", or "cookie banner" are missing.

4 / 5

Distinctiveness Conflict Risk

"EU webshop against consumer law", "GPSR-compliant product page checklists", and "14-day return policies" carve out a clear niche with distinct triggers, making conflict with other skills unlikely. It clearly matches the minimal-conflict-risk anchor rather than the minor-overlap anchor at 4.

5 / 5

Total

19

/

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-webshop-compliance-eu/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.