CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

nex-veiligheidscoordinatie-bouw

Regelt de veiligheidscoordinatie op een Belgische werf: coordinatiedagboek, veiligheids- en gezondheidsplan, postinterventiedossier en werfverslagen. Use when: Genereer een V&G-plan voor ontwerp of verwezenlijking; Maak entries voor het coordinatiedagboek tijdens werfbezoeken; Stel een postinterventiedossier (PID) samen voor de bouwheer.

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 ./plugins/nex-compliance/skills/nex-veiligheidscoordinatie-bouw/SKILL.md

The canonical home for this skill is nex-veiligheidscoordinatie-bouw in NexaiGuy/nex-ai-skills

SKILL.md
Quality
Evals
Security

Quality

Content

40%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 more like a product landing page than an operating guide: it says what the skill does and shows one good example, but provides no templates, decision rules, or step sequences for the four deliverables it claims to manage. Marketing FAQ and promotional boilerplate dilute the token budget, and the note that scripts and templates 'are not in this folder' confirms the actual working material is absent.

Suggestions

Replace the 'Questions' FAQ and the Nex AI/Agensi promotional header and footer with the substantive material they displace: a section structure for the V&G-plan, a coördinatiedagboek entry template (vaststellingen, afspraken, opvolging), and a checklist of PID contents to hand to the bouwheer at oplevering.

Turn 'Wat het doet' into a stepwise workflow: (1) determine whether coordination is verplicht with the explicit criteria (omvang, aantal aannemers, risico's, including the 500m2 and 1.2m graafwerken thresholds the example only hints at), (2) generate the plan for ontwerp and verwezenlijking phases, (3) log dagboek entries per werfbezoek, (4) compile the PID at oplevering — with a validation checkpoint that the output is flagged as a werkdocument pending erkende coordinator approval.

Add 1–2 more worked examples covering the other deliverables (a dagboek entry and a PID excerpt) so the output format for each is concrete rather than only the V&G-plan case.

DimensionReasoningScore

Conciseness

The body carries several padded sections that earn no tokens for execution: the promo header ("Free skill by Nex AI... Scripts, extension source, and templates from the original package are not in this folder"), the five-question marketing FAQ ("Wat ontvang ik precies bij de aankoop", "Met welke AI-platformen is deze skill compatibel"), and the paid-catalog footer. The core sections ("Wat het doet", example) are lean, so this sits above the severely-verbose anchor 1 but clearly at 2.

2 / 5

Actionability

The worked example is genuinely concrete — it shows the regime determination ("Vereenvoudigd (opp. < 500m2)"), a risk-analysis format ("Graafwerken (>1.2m): Risico op bedelving. Maatregel: Beschoeiing verplicht") and [IN TE VULLEN] placeholders — but beyond that single scenario there are no structures, thresholds, or rules for building the V&G-plan, dagboek entries, or PID, which is the 'missing key details' of anchor 3 rather than the executable completeness of 4.

3 / 5

Workflow Clarity

Only a rough implied sequence exists via the capability bullets ("Bepaalt... Bouwt... Houdt... Stelt... samen"); there are no defined steps for any of the four deliverables and no validation checkpoints (e.g., checking regime thresholds, bouwheer sign-off for the PID). This matches 'rough sequence present but many gaps; validation absent' rather than the listed-but-unvalidated steps of anchor 3.

2 / 5

Progressive Disclosure

The skill is a short, self-contained file with clear section headers and no external references to manage, so organization is good overall; the inlined marketing FAQ and promo blocks are content that belongs outside the skill, which keeps it at 'minor organization gaps' rather than fully appropriate placement.

4 / 5

Total

11

/

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 in third-person voice that clearly states what the skill does and gives an explicit 'Use when' clause with three natural, domain-specific trigger phrases. The only weakness is reliance on one generic verb rather than varied concrete action verbs, leaving slightly less capability detail than the top specificity anchor.

DimensionReasoningScore

Specificity

Lists several concrete deliverables — "coordinatiedagboek, veiligheids- en gezondheidsplan, postinterventiedossier en werfverslagen" — but hangs them all on a single generic verb ("Regelt"); a 5 would use multiple distinct action verbs like the "Extract... fill... merge" anchor.

4 / 5

Completeness

Explicitly answers both: a clear what ("Regelt de veiligheidscoordinatie op een Belgische werf" plus four document types) and an explicit "Use when:" with three concrete trigger phrases — a direct match to the top anchor. Not below 5 because neither what nor when is vague or implicit.

5 / 5

Trigger Term Quality

The "Use when" clause uses natural phrases users would say ("Genereer een V&G-plan", "Maak entries voor het coordinatiedagboek", "Stel een postinterventiedossier (PID) samen") with the PID abbreviation covered, but misses some common variations/synonyms a 5 would include.

4 / 5

Distinctiveness Conflict Risk

A clear niche — Belgian construction-site safety coordination under the tijdelijke of mobiele bouwplaatsen regime — with distinct triggers (V&G-plan, PID, bouwheer) that no generic skill would claim, giving minimal conflict risk.

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-veiligheidscoordinatie-bouw/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.