CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

nex-favv-food-pack

Builds FAVV registration decision trees, EU 1169/2011 label checklists, HACCP plans, allergen matrices, and recall workflows for Belgian food businesses. Use when: Determine if you need a FAVV registration, permit, or approval; Create EU 1169/2011 compliant food labels in Dutch; Build HACCP and autocontrole structures for small kitchens.

Quality

71%

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-favv-food-pack/SKILL.md
SKILL.md
Quality
Evals
Security

Quality

Content

36%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 brochure rather than a skill: it convincingly describes what the pack produces but contains none of the operational substance — no decision tree, no label field list, no HACCP template, no allergen table, no recall procedure — and confirms the scripts and templates are not bundled. Structure and conciseness are acceptable, but actionability and workflow clarity are near the bottom of the scale.

Suggestions

Replace the descriptive bullets with actual operational content: include the FAVV three-level decision tree criteria, the literal list of the 11 mandatory EU 1169/2011 mentions in order, the fixed nutrition-table column order, and the 14 Annex II allergens — or ship them as reference files and link to them.

Add executable workflows with checkpoints for each capability, e.g. for the meldingsplicht: 1) block the affected lot, 2) trace via the register UIT, 3) report to the LCE, 4) execute consumer recall, 5) document corrective actions — with validation steps such as verifying the trace covers the full lot range before reporting.

Remove the marketing sections ('Why use this', 'Questions' FAQ, promotional footer links) and either bundle the templates/scripts this multi-capability skill requires or add clearly signaled one-level-deep references to where their content lives.

DimensionReasoningScore

Conciseness

The prose itself is tight and avoids explaining concepts Claude already knows, but roughly a third of the body is non-operational padding: the 'Why use this' marketing section, the three-question FAQ that restates the description, and the promotional footer links. Mostly efficient with some unnecessary sections, matching anchor 3; not anchor 2 because the core 'What it does' and 'Known limitations' sections carry real information.

3 / 5

Actionability

The body only describes outputs rather than instructing how to produce them — it names 'the 11 required mentions, the fixed nutrition table order, minimum x-height font sizes' and 'the 7 principles' without ever listing them, and admits 'Scripts, extension source, and templates from the original package are not in this folder'. It sits above anchor 1 (entirely abstract) because the bullets and the worked Example give high-level hints of what the deliverables contain, but the specific steps and content to execute are missing, matching anchor 2.

2 / 5

Workflow Clarity

No multi-step process is actually laid out; the only sequence is a named chain inside one bullet — 'block, trace via register UIT, report to the LCE, consumer recall, corrective documentation' — with steps poorly defined and no validation checkpoints. This matches anchor 2 (rough sequence, many gaps, validation absent) rather than anchor 3, since even the primary workflows (decision tree, HACCP plan, label checklist) have no step listing at all.

2 / 5

Progressive Disclosure

The single file is well-sectioned (What it does, Use cases, Limitations, Example, Questions) with no nesting, but no bundle files exist and no reference files are linked, so the detailed regulatory content and templates this five-capability skill clearly needs are absent entirely. Some structure present but the split-out content is missing, matching anchor 3 rather than 4.

3 / 5

Total

10

/

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.

A strong description: concrete capability list, explicit 'Use when' triggers, and a sharply defined niche. The only weakness is that the trigger phrases cover three of the five capabilities, omitting recall-workflow and allergen-matrix use cases and the AFSCA synonym.

DimensionReasoningScore

Specificity

The description lists five concrete deliverables — 'FAVV registration decision trees, EU 1169/2011 label checklists, HACCP plans, allergen matrices, and recall workflows' — giving comprehensive, specific coverage of the skill's capabilities. It exceeds anchor 4 because there are no meaningful gaps in the action list.

5 / 5

Completeness

Both halves are explicit: the 'what' enumerates the five document types built, and 'Use when: Determine if you need a FAVV registration...; Create EU 1169/2011 compliant food labels...; Build HACCP and autocontrole structures...' provides three concrete trigger phrases. This matches anchor 5; it is not anchor 4 because the 'when' is fully explicit rather than needing more specificity.

5 / 5

Trigger Term Quality

Natural trigger phrases like 'FAVV registration, permit, or approval', 'EU 1169/2011 compliant food labels in Dutch', and 'HACCP and autocontrole structures' match what affected users would say, but common variations are missing — no recall, allergen, or food-safety trigger terms, and no 'AFSCA' synonym for French-speaking users. Good but not comprehensive, matching anchor 4 rather than 5.

4 / 5

Distinctiveness Conflict Risk

The Belgian FAVV/EU 1169/2011/Dutch-language food-compliance niche with triggers like 'FAVV', 'autocontrole', and 'erkenning' is highly distinct and would not fire for unrelated skills. Clear niche with minimal conflict risk, matching anchor 5.

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

skills/nex-favv-food-pack/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.