CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

kostprijs-calculator

Berekent een concept-raming van de totale aankoopkosten van een onroerend goed in Vlaanderen (verkooprecht, ereloon, aktekosten, btw) via een Python-script met bewerkbaar tarievenbestand. Use when: Bereken registratierechten voor verschillende regimes in Vlaanderen; Genereer een transparante kostentabel voor client-communicatie; Update notariele tarieven via een centraal JSON-bestand.

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/kostprijs-calculator/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 reads as a product landing page rather than an operational skill: well-sectioned and readable, but it describes a Python script and editable rates file that are neither bundled nor invocable, leaving the agent with no executable path to the demonstrated output. Marketing duplication and repeated attribution also cost tokens without adding capability.

Suggestions

Bundle the Python script (or provide its exact path and argparse invocation, e.g. `python scripts/kostprijs.py --prijs 350000 --regime 2`) so the agent can actually execute the calculation the Example demonstrates.

Give the concrete location of tarieven.json and a short example of editing a rate entry, since updating rates is one of the three advertised use cases.

Cut the duplicated description paragraph, the repeated Nex AI attribution/promo lines, and FAQ answers that restate 'When to use'/'Known limitations' to reclaim token budget.

DimensionReasoningScore

Conciseness

The body is short and free of concept over-explanation, but it repeats the frontmatter description nearly verbatim in the opening paragraph, states Nex AI attribution/promotion three times (blockquote, 'Built by Nex AI... https://slopsome.com', and the footer link to a paid catalog), and the Questions section partly restates When to use and Known limitations. This fits anchor 3 — mostly efficient but with unnecessary padding that could be tightened — rather than 4, where only minor trimmable instances remain.

3 / 5

Actionability

The skill's core action depends on a Python script that is referenced only at a high level ('Inclusief een lokaal Python-script (argparse CLI) dat de agent zelf draait') with no path, no invocation command, and no code — the body even admits 'Scripts, extension source, and templates from the original package are not in this folder' — and 'tarieven.json' is named without a location. The worked Example (350.000 euro input with cost breakdown output) is concrete, but the specific steps to execute are missing, matching anchor 2 rather than 3, where guidance would be concrete-but-incomplete rather than high-level hints.

2 / 5

Workflow Clarity

No steps are sequenced anywhere: the body never says how to produce the Example output (run the absent script? compute manually?), and there is no validation checkpoint on calculated figures. The simple-skill exception does not apply because the single action is not unambiguous — the execution path is undefined — leaving a rough implied action with many gaps, matching anchor 2.

2 / 5

Progressive Disclosure

The body is short with well-organized sections (When to use, Known limitations, Example, Questions) and no nested references, and the small-skill exception (under ~50 lines, no external references needed) nearly applies. It scores 4 rather than 5 because it dangles references to a script and tarieven.json that are not in the bundle and are given no paths, a clear organization gap.

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: third-person voice, explicit what-and-when structure, concrete component-level detail, and a well-defined niche with an explicit 'Use when:' trigger list. The only weaknesses are a few missing natural trigger phrasings (e.g., 'notariskosten', 'wat kost') and a trigger ('Update notariele tarieven') that reads as a maintenance task rather than a user moment.

DimensionReasoningScore

Specificity

The description names the domain (aankoopkosten onroerend goed in Vlaanderen), enumerates the concrete cost components ('verkooprecht, ereloon, aktekosten, btw'), and specifies the mechanism ('Python-script met bewerkbaar tarievenbestand') with several trigger actions (generate cost table, update rates). It lists several specific actions with only minor coverage gaps (e.g., output format detail), matching anchor 4 rather than 5, which requires comprehensive multi-action coverage.

4 / 5

Completeness

It explicitly answers both questions: the 'what' ('Berekent een concept-raming van de totale aankoopkosten... via een Python-script met bewerkbaar tarievenbestand') and an explicit 'Use when:' clause with three concrete trigger phrases ('Bereken registratierechten voor verschillende regimes in Vlaanderen; Genereer een transparante kostentabel...; Update notariele tarieven...'). This mirrors the anchor-5 example structure; it is not anchor 4 because the when-clause is explicit and specific rather than vague.

5 / 5

Trigger Term Quality

Natural domain keywords users would say are present: 'Bereken registratierechten', 'kostentabel', 'notariele tarieven', 'verkooprecht', 'aktekosten', 'btw', 'aankoopkosten', 'Vlaanderen'. Coverage is good but misses common user phrasings such as 'notariskosten' or 'wat kost deze aankoop', fitting anchor 4 (good coverage, a few natural terms missing) rather than the synonym- and extension-sweep of anchor 5.

4 / 5

Distinctiveness Conflict Risk

The trigger space is a clear niche — Flemish notarial purchase-cost calculation (registratierechten, ereloon, aktekosten, btw) — with region ('Vlaanderen') and role-specific vocabulary that no general skill would claim, giving minimal conflict risk, matching anchor 5.

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/kostprijs-calculator/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.