CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

nex-overheidsopdrachten-tender

Analyseert een Belgisch bestek en levert een go of no-go met knock-outs, gunningscriteria, weging en drempelbedragen. Use when: Voer een snelle go of no-go analyse uit per bestek; Genereer een technisch offerteskelet op maat van criteria; Vul het UEA of ESPD formulier correct in voor kmo's.

Quality

65%

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-overheidsopdrachten-tender/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 marketing README rather than operational skill instructions: it advertises capabilities but provides no procedure, data, or examples of how to perform the analysis, and acknowledges its own supporting files are absent. Its saving graces are lean prose and a clear worked example of the expected output.

Suggestions

Add a concrete, sequenced analysis workflow — e.g. extract knock-out criteria and verify each against the company's credentials/references, tabulate award criteria with weights, compare the estimate against the 2026-2027 European and national threshold table, then deliver the structured verdict — with a validation step before issuing the go/no-go.

Include the actual drempelbedragen (threshold amounts) and the award-criteria scoring method, either inline or in a references/ file, instead of only asserting in the FAQ that the thresholds are up-to-date.

Provide an explicit output template for the go/no-go analysis and merge the duplicated 'Beperkingen' and 'Known limitations' sections into one to remove redundant tokens.

DimensionReasoningScore

Conciseness

Mostly lean with no over-explanation of known concepts, but 'Beperkingen' and 'Known limitations' repeat the same two facts nearly verbatim ('Geen juridisch advies maar een werkdocument' vs 'De output is een werkdocument en geen juridisch advies'), and promotional links appear both at the top and bottom.

3 / 5

Actionability

The body is purely descriptive ('Haalt de knock-outcriteria uit het bestek en zegt meteen of je uberhaupt mag meedoen') — it says what the skill does but gives no method, threshold values, criteria taxonomy, or ESPD field guidance; only the Example section hints at an output format.

2 / 5

Workflow Clarity

The four 'Wat het doet' bullets form a rough decomposition (knock-outs, criteria, thresholds, verdict) but are never sequenced as steps, and there are no validation checkpoints for a consequential go/no-go decision.

2 / 5

Progressive Disclosure

In-file section organization is decent, but the body itself states 'Scripts, extension source, and templates from the original package are not in this folder' — detail-heavy material (2026-2027 threshold tables, ESPD mappings) that belongs in reference files is missing rather than referenced, so content is not appropriately split across files.

3 / 5

Total

10

/

20

Passed

Description

78%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, third-person, with an explicit 'Use when' clause and natural domain terminology for a well-defined niche. Its main weakness is that the capability statement covers fewer use cases than its own trigger list promises.

DimensionReasoningScore

Specificity

Names the domain ('Belgisch bestek') and multiple concrete outputs ('knock-outs, gunningscriteria, weging en drempelbedragen', 'go of no-go'), but the 'what' sentence omits two capabilities listed in the 'Use when' triggers (offerteskelet generation, UEA/ESPD form filling), leaving minor gaps in coverage.

4 / 5

Completeness

Explicitly answers both 'what' (analyzes a Belgian bestek, delivers go/no-go with knock-outs, award criteria, weighting, thresholds) and 'when' ('Use when:' followed by three concrete triggers), but the 'what' is narrower than the 'when', creating a coherence gap that keeps it below a 5.

4 / 5

Trigger Term Quality

Includes natural Flemish terms users would say — 'bestek', 'go of no-go', 'gunningscriteria', 'UEA of ESPD', 'kmo's', 'drempelbedragen' — but misses common synonyms such as 'overheidsopdracht', 'aanbesteding', and 'tender'.

4 / 5

Distinctiveness Conflict Risk

A clear niche (Belgian public procurement analysis with domain-specific terminology like ESPD/UEA and 'bestek') with distinct triggers and virtually no overlap risk with other skills.

5 / 5

Total

17

/

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-overheidsopdrachten-tender/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.