CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

nex-kinderopvang-admin

Regelt de administratie van een Vlaamse kinderopvang: inschrijvingen, aanwezigheidsregistratie, facturatie en het fiscaal attest. Use when: Genereer een huishoudelijk reglement volgens de Opgroeien-vereisten; Stel een volledig vergunningsdossier op voor een nieuwe opvanglocatie; Maak schriftelijke ouderovereenkomsten voor IKT of vrije prijs.

Quality

71%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide
SecuritybySnyk

Medium

Suggest reviewing before use

Fix and improve this skill with Tessl

tessl review fix ./skills/nex-kinderopvang-admin/SKILL.md
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 functions as a marketing overview rather than an operational skill: it describes what the skill does and its limitations well, but contains no templates, decision rules, or step sequences that would let Claude actually produce a compliant reglement, overeenkomst, factuur, or attest. The only executable signal is one truncated example output.

Suggestions

Replace the capability bullets and FAQ with concrete operational content: the required sections of a huishoudelijk reglement per the Opgroeien besluit, the mandatory fields of an ouderovereenkomst (IKT vs. vrije prijs), and the field list the fiscus expects on the attest.

Add a step-by-step workflow for the core pipeline (inschrijvingsdossier -> aanwezigheidsregistratie -> omzetting naar gefactureerde dagen -> maandfactuur -> fiscaal attest) including validation checkpoints, such as verifying tariff lines and gerechtvaardigde afwezigheden before generating the invoice.

Remove the promotional footer, Nex AI blockquote, and the note about missing package files, or restore the referenced templates/scripts so the bundle delivers the guidance the body promises.

DimensionReasoningScore

Conciseness

The core sections ('Wat het doet', 'Gebruikssituaties', 'Bekende beperkingen') are lean and non-redundant with no explanations of concepts Claude already knows, but the 'Questions' FAQ section, the Nex AI promo blockquote, and the paid-catalog footer are padded marketing content that earns no tokens. Not a 2 because the padding is limited to a few short sections rather than pervading the document.

3 / 5

Actionability

The body only describes capabilities ('Bouwt het inschrijvingsdossier...', 'Genereert de maandfactuur per kind met de juiste tarieflijnen') and offers one truncated mock output with placeholders like '[VOLLEDIG DOCUMENT GEGENEREERD]', but provides no templates, required-field lists, tariff logic, or concrete steps to execute. This sits between the 1 anchor (describes rather than instructs) and 3 (some concrete guidance), closer to minimal concrete guidance via the example and the limitations notes.

2 / 5

Workflow Clarity

No workflow steps are written anywhere: the multi-step processes this skill covers (enrollment dossier -> attendance registration -> conversion to invoiced days -> monthly invoice -> fiscal attest) appear only as unordered capability bullets, with no sequence, no checkpoints, and no validation (e.g., verifying tariff lines or justified absences). Score 2 rather than 1 because the 'Wat het doet' bullets at least imply a coherent topical order and the Example shows a fragment of one output.

2 / 5

Progressive Disclosure

As a short single-file skill with clear section headers it is well organized and has no nested or buried references, which per the simple-skill guidance supports a high score. It drops below 5 because it explicitly points to absent bundle content ('Scripts, extension source, and templates from the original package are not in this folder') and includes marketing sections that dilute navigation.

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: concrete domain and tasks, explicit third-person 'what', and an explicit 'Use when:' clause with natural, niche-specific trigger phrases. The only improvement space is broader synonym coverage of trigger terms.

DimensionReasoningScore

Specificity

The description names a concrete domain ('Vlaamse kinderopvang') and enumerates four specific areas ('inschrijvingen, aanwezigheidsregistratie, facturatie en het fiscaal attest') plus three concrete generation tasks in the Use when clause. It falls just short of the 5 anchor because the lead verb 'Regelt de administratie' is generic and the coverage has minor gaps (e.g., no mention of subsidies/toeslag rules or inspection prep).

4 / 5

Completeness

It clearly answers 'what' ('Regelt de administratie van een Vlaamse kinderopvang: inschrijvingen, aanwezigheidsregistratie, facturatie en het fiscaal attest') and explicitly answers 'when' with an explicit 'Use when:' clause containing three concrete trigger scenarios. This matches the 5 anchor (both what and when with concrete trigger phrases); it is above the 4 anchor because the when-clause is explicit and specific, not merely present.

5 / 5

Trigger Term Quality

Natural domain phrases a Flemish childcare provider would say are present: 'huishoudelijk reglement', 'vergunningsdossier', 'ouderovereenkomsten', 'IKT', 'vrije prijs', 'Opgroeien-vereisten', plus 'inschrijvingen', 'facturatie', 'fiscaal attest'. It is not a 5 because common variations users might say (e.g., 'oudercontract', 'plaatsing', 'kinderdagverblijf', 'onthaalouder') are missing.

4 / 5

Distinctiveness Conflict Risk

The description occupies a clear niche (Flemish childcare administration under Opgroeien regulation) with distinct triggers (huishoudelijk reglement, vergunningsdossier, IKT/vrije prijs overeenkomsten) that virtually no other 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

skills/nex-kinderopvang-admin/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.