CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

pachtcontract-checklist

Intelligente checklist voor pachtcontracten en landbouwgebruik conform het Vlaams Pachtdecreet. Use when: Analyseer herkwalificatierisico's bij bezetting ter bede of cultuurcontracten; Bereken of de voorgestelde pachtprijs de wettelijke coëfficiënten overschrijdt; Genereer een lijst met ontbrekende documenten voor een pachtdossier.

Quality

62%

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/pachtcontract-checklist/SKILL.md
SKILL.md
Quality
Evals
Security

Quality

Content

28%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 is primarily a product landing page rather than an operational skill: it describes capabilities and includes one useful worked example, but gives Claude no concrete legal criteria, checklist items, or analysis steps to execute the promised checks. It also relies on reference data (coefficients, decree rules) that is explicitly absent from the bundle.

Suggestions

Replace the marketing sections ('Waarom deze skill gebruiken?', 'Questions' FAQ, vendor links) with the actual analysis procedure: a step-by-step method for qualifying the pachtvorm, testing the price against coefficients, and assessing voorkooprecht/opzegging impacts.

Add the concrete checklist content the skill promises, e.g., the specific qualification criteria from the Vlaams Pachtdecreet and an explicit list of required dossier documents (plaatsbeschrijving, etc.) — either inline or in a references/ file.

Since current pachtprijzencoëfficiënten are admitted to be missing, add explicit instructions for where and how to look them up and how to flag uncertainty in the output, turning a known limitation into an actionable workflow step.

DimensionReasoningScore

Conciseness

Roughly half the body is storefront marketing rather than instruction: 'Free skill by Nex AI', the 'Waarom deze skill gebruiken?' sales pitch, links to 'slopsome.com', and a five-question FAQ including 'Wat is inbegrepen bij de aankoop en hoe ziet de installatie eruit?'. Matches anchor 2's 'several unnecessary explanations or padded sections'; it avoids explaining general concepts Claude already knows, so not 1.

2 / 5

Actionability

No code, commands, or concrete legal criteria are provided: no qualification-test rules, no coefficient values, and no actual document checklist items ('Geen actuele pachtprijzencoëfficiënten: handmatige controle vereist'). Only high-level feature descriptions ('Kwalificatietoets: Onderscheid tussen klassieke pacht, loopbaanpacht en seizoenspacht') plus one example output, matching anchor 2's high-level hints without specific steps.

2 / 5

Workflow Clarity

No sequenced analysis process is given; the features list and 'Output' section only imply a rough flow (intake contract, check qualification/price/rights, produce overzicht, actielijst, vragenlijst) with many gaps and no validation checkpoints. Anchor 2's 'rough sequence present but many gaps' fits better than anchor 1 because 'When to use', 'Output', and the worked example provide rough orientation.

2 / 5

Progressive Disclosure

Sections are clearly headed and the body is short, but there are no reference files at all despite the skill depending on legal reference data (decree rules, price coefficients), and the FAQ/marketing content is inlined where it should not exist. Anchor 3's 'some structure but could be better organized'.

3 / 5

Total

9

/

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 with an explicit 'Use when:' clause and concrete, domain-specific trigger phrases in Dutch appropriate for its Flemish notariat audience. Its main weaknesses are the slightly padded 'Intelligente checklist' framing of the what and incomplete synonym coverage.

DimensionReasoningScore

Specificity

Names the legal domain ('pachtcontracten en landbouwgebruik conform het Vlaams Pachtdecreet') and lists three concrete actions ('Analyseer herkwalificatierisico's', 'Bereken of de voorgestelde pachtprijs de wettelijke coëfficiënten overschrijdt', 'Genereer een lijst met ontbrekende documenten'). Falls between anchors 4 and 5: 'Intelligente checklist' is mild fluff and coverage has minor gaps (e.g., voorkooprecht analysis claimed in the body is not mentioned).

4 / 5

Completeness

Explicitly answers 'when' with a 'Use when:' clause containing three concrete triggers, but the 'what' ('Intelligente checklist voor pachtcontracten en landbouwgebruik') is a somewhat vague noun phrase rather than the explicit action statement of anchor 5; it sits between anchors 4 and 5.

4 / 5

Trigger Term Quality

Good coverage of natural terms a Flemish notary would say ('pachtcontracten', 'bezetting ter bede', 'cultuurcontracten', 'pachtprijs', 'pachtdossier'), but common synonyms such as 'pachtovereenkomst', 'grond', or 'voorkooprecht' are missing, so it does not reach anchor 5's comprehensive synonym coverage.

4 / 5

Distinctiveness Conflict Risk

Highly specific niche triggers ('Vlaams Pachtdecreet', 'bezetting ter bede', 'cultuurcontracten', 'pachtprijzencoëfficiënten') make conflict with other skills very unlikely; clear match for anchor 5.

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/pachtcontract-checklist/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.