Name: kvk
Rating: 56.00000000000001 (1 reviews)
Author: membranedev

Blog Docs Log in Get started

kvk

KVK integration. Manage data, records, and automate workflows. Use when the user wants to interact with KVK data.

Quality

63%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide

Securityby

Low

Low-risk findings worth noting

Fix and improve this skill with Tessl

tessl review fix ./skills/kvk/SKILL.md

Quality

Content

64%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 highly actionable with concrete Membrane CLI commands and a well-instrumented connection state machine, but it is marred by a leaked placeholder line, a redundant 'Popular actions' section, a dangling 'Step 2' reference, and a monolithic single-file structure with no progressive disclosure.

Suggestions

Remove the leaked placeholder sentence ('I don't have enough information about that app to provide a description. Can you tell me more about it?').

Fix the dangling 'skip to Step 2' reference by adding a labeled Step 2 heading or rewriting the pointer.

Move the proxy flag table and detailed clientAction state handling into a references/ file (e.g. REFERENCE.md) and link to it from SKILL.md to enable progressive disclosure.

Dimension	Reasoning	Score
Conciseness	Mostly command-driven and efficient, but it opens with leaked placeholder text ('I don't have enough information about that app to provide a description...') and repeats the action-list command in both 'Searching for actions' and 'Popular actions', adding unnecessary tokens, matching the 'mostly efficient but some unnecessary explanation' anchor.	3 / 5
Actionability	Provides concrete, copy-paste-ready commands for the full lifecycle (login, connection ensure, action list/run, request proxy) with flag tables, matching 'mostly executable guidance with minor gaps'; placeholders like CONNECTION_ID/QUERY keep it just short of fully turnkey level 5.	4 / 5
Workflow Clarity	The connect-to-KVK flow has a clear sequence with explicit polling checkpoints and state feedback loops (READY/CLIENT_ACTION_REQUIRED/CONFIGURATION_ERROR), matching 'clear sequence with most checkpoints'; the dangling 'skip to Step 2' reference with no matching Step 2 heading is a minor validation/sequencing gap preventing level 5.	4 / 5
Progressive Disclosure	No bundle files exist and all CLI reference material (the proxy flag table, the detailed clientAction state machine) is inlined in a single ~140-line SKILL.md with section headers but no signaled external references, matching 'some structure but content that should be separate is inline'.	3 / 5
	Total	14 / 20 Passed

Description

62%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.

The description successfully pairs a 'what' with an explicit 'Use when' trigger and is anchored to a recognizable niche (KVK), but its capability wording is generic ('manage data, records, automate workflows') and lacks richer natural trigger synonyms.

Suggestions

Replace generic verbs with concrete KVK actions (e.g. 'Look up company profiles, fetch authorised persons, search business activities').

Add natural user-facing trigger phrases and synonyms (e.g. 'Use when the user asks about Dutch company registrations, KVK numbers, or Chamber of Commerce records').

Mention the data domain explicitly (KVK business registry records) to sharpen distinctiveness from generic data-management skills.

Dimension	Reasoning	Score
Specificity	Names the KVK domain and a few actions ('Manage data, records, and automate workflows'), but the actions are generic rather than concrete, fitting the 'names domain and 1-2 concrete actions but not comprehensive' anchor rather than the fully-vague level 2.	3 / 5
Completeness	States both a 'what' ('Manage data, records, and automate workflows') and an explicit 'when' ('Use when the user wants to interact with KVK data'); the trigger is present though it could be more specific, matching level 4 rather than 3 (which requires a missing/weak 'when').	4 / 5
Trigger Term Quality	Includes relevant terms like 'KVK data', 'records', and 'workflows' but misses common synonyms or variations a user might naturally say, matching the 'some relevant keywords but missing common variations' anchor.	3 / 5
Distinctiveness Conflict Risk	Tied to the specific KVK niche with distinct triggers ('interact with KVK data'), giving mostly-distinct low-conflict behavior, though the generic 'manage data, records' phrasing leaves minor overlap risk, so level 4 rather than the fully-distinct level 5.	4 / 5
	Total	14 / 20 Passed

Validation

93%

Warnings & errors only

Checks the skill against the spec for correct structure and formatting. All validation checks must pass before discovery and implementation can be scored.

Validation — 15 / 16 Passed

Validation for skill structure

Criteria	Description	Result
frontmatter_unknown_keys	Unknown frontmatter key(s) found; consider removing or moving to metadata	Warning

	Total	15 / 16 Passed

Repository: membranedev/application-skills
Path: skills/kvk/SKILL.md
Commit: f484c82

Reviewed: 6 days ago

Table of Contents

Discovery Implementation Validation

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.