Name: kontomatik
Rating: 60 (1 reviews)
Author: membranedev

kontomatik

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

Quality

70%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide

Securityby

Passed

No findings from the security scan

Fix and improve this skill with Tessl

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

Quality

Content

82%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 a tightly written, executable guide to the Membrane+Kontomatik workflow with a clear connection state machine and feedback loop. Its main weaknesses are minor padding and small structural inconsistencies (dangling 'Step 2', unlabeled '1b') rather than gaps in guidance.

Dimension	Reasoning	Score
Conciseness	The body is dominated by concrete, executable commands with only minor over-explanation such as 'Fintech companies and lenders use it for credit scoring' and 'so you can focus on the integration logic rather than auth plumbing', matching the score-4 anchor. It is above 3 because the bulk is efficient, but not 5 due to those padded sentences.	4 / 5
Actionability	The body provides copy-paste-ready commands for the full lifecycle (install, login, connection ensure, action list/run, request proxy) plus a flag options table, matching the score-5 anchor ('Fully executable; copy-paste ready code or commands; specific examples cover the common cases').	5 / 5
Workflow Clarity	There is a clear install→authenticate→connect→poll/search→run sequence with a state-machine feedback loop (READY / CLIENT_ACTION_REQUIRED → re-poll), matching the score-4 anchor. It is capped below 5 by minor structural gaps: a 'skip to Step 2' reference with no labeled Step 2, and a '1b' subsection with no '1a'.	4 / 5
Progressive Disclosure	No bundle files exist and the skill is a single well-organized file with clear sections (Overview, Authentication, Connecting, Actions, Proxy, Best practices), matching the score-4 anchor for good structure with minor organization gaps. It is not 5 because at ~140 lines some reference-like content (the proxy flag table, detailed clientAction spec) could be split out.	4 / 5
	Total	17 / 20 Passed

Description

57%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 correctly pairs a 'Use when...' trigger with a 'what' statement and anchors on a distinctive product name, but its capability language is generic. Tightening the action list to concrete Kontomatik operations would raise specificity and completeness.

Suggestions

Replace 'Manage data, records, and automate workflows' with concrete Kontomatik actions such as 'connect bank accounts, fetch transaction history, and pull account balances/statements'.

Expand the trigger clause with natural user phrases, e.g. 'Use when the user wants to fetch Kontomatik banking data, transaction history, or account balances'.

Drop generic verbs like 'automate workflows' that do not describe a specific Kontomatik capability.

Dimension	Reasoning	Score
Specificity	The description names the domain (Kontomatik) but the actions 'Manage data, records, and automate workflows' are minimal and generic rather than concrete capabilities, matching the score-2 anchor ('Names the domain but actions are minimal or generic'). It does not reach 3 because no concrete, specific actions are named.	2 / 5
Completeness	Both 'what' ('Kontomatik integration. Manage data, records, and automate workflows.') and an explicit 'when' ('Use when the user wants to interact with Kontomatik data.') are present, matching the score-4 anchor. It is capped below 5 because the 'what' is generic rather than a concrete capability list.	4 / 5
Trigger Term Quality	The phrase 'Use when the user wants to interact with Kontomatik data' surfaces the single natural keyword 'Kontomatik', but there are no synonyms or variations, matching the score-3 anchor ('Some relevant keywords but missing common variations or synonyms'). It is above 2 because a real natural keyword is present, but below 4 due to thin coverage.	3 / 5
Distinctiveness Conflict Risk	Tying triggers to the named product 'Kontomatik' gives it a clear niche with minimal conflict risk, matching the score-4 anchor. It does not reach 5 because the generic verbs 'manage data, records, and automate workflows' could overlap with broad data-management skills.	4 / 5
	Total	13 / 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/kontomatik/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.