CtrlK
BlogDocsLog inGet started
Tessl Logo

unzer

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

61

Quality

72%

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

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 strong, highly actionable CLI integration guide with executable commands, explicit error-state feedback loops, and clean section structure, held back only by minor verbosity and an inconsistent step-numbering scheme.

DimensionReasoningScore

Conciseness

The body is largely efficient, dominated by concrete commands, a flags table, and JSON examples, with only minor padding (e.g. "This is the fastest way to get a connection" and the restated Unzer overview paragraph) that could be trimmed, matching the efficient-with-minor-over-explanation anchor.

4 / 5

Actionability

It provides copy-paste-ready membrane commands with flags and --json examples for login, connection ensure/wait, action list/run, and request proxying, plus a flags table, fully covering the common cases as the anchor requires.

5 / 5

Workflow Clarity

The connect workflow has a clear sequence (ensure -> poll --wait -> branch on state) with feedback loops for CLIENT_ACTION_REQUIRED and CONFIGURATION_ERROR, but the step numbering is fragmentary ("1b" then "Step 2") and the end-to-end flow lacks a fully explicit numbered checklist, keeping it just below the 5 anchor.

4 / 5

Progressive Disclosure

With no bundle files present, the single self-contained SKILL.md is organized into clear, well-labeled sections (Install, Authentication, Connecting, Searching, Running, Proxy, Best practices) that place content appropriately, matching the good-structure anchor.

4 / 5

Total

17

/

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 answers both what and when with an explicit Use-when clause and ties to a specific product, but its action language is generic and omits the concrete Unzer concepts (payments, transactions, payouts, webhooks) that would sharpen specificity and trigger terms.

Suggestions

Replace generic verbs ("Manage data, records, and automate workflows") with concrete Unzer actions, e.g. "Process payments and transactions, handle payouts, and manage webhooks."

Add natural trigger terms users would say, such as "payments," "transactions," "payouts," or "webhooks," rather than the generic "interact with Unzer data."

Tighten the Use-when clause to specific intents, e.g. "Use when the user wants to process Unzer payments, issue payouts, or configure webhooks."

DimensionReasoningScore

Specificity

Names the Unzer domain and a few actions ("Manage data, records, and automate workflows"), but the actions are generic rather than concrete, payment-specific operations, matching the domain-plus-1-2-generic-actions anchor rather than the comprehensive coverage of 4-5.

3 / 5

Completeness

It explicitly states both what ("Unzer integration. Manage data, records, and automate workflows") and when ("Use when the user wants to interact with Unzer data"), with the when present but somewhat broad, matching the both-present-but-could-be-more-specific anchor.

4 / 5

Trigger Term Quality

"interact with Unzer data" and "data, records, workflows" provide some relevant keywords, but common variations and synonyms the body itself surfaces (payments, transactions, payout, webhook) are missing from the description, fitting the missing-common-variations anchor.

3 / 5

Distinctiveness Conflict Risk

Naming the specific product Unzer gives it a clear, distinct niche with minimal conflict risk, though the generic action language keeps it just short of the fully comprehensive 5 anchor.

4 / 5

Total

14

/

20

Passed

Validation

93%

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

Validation15 / 16 Passed

Validation for skill structure

CriteriaDescriptionResult

frontmatter_unknown_keys

Unknown frontmatter key(s) found; consider removing or moving to metadata

Warning

Total

15

/

16

Passed

Repository
membranedev/application-skills
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.