CtrlK
BlogDocsLog inGet started
Tessl Logo

sumup

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

60

Quality

71%

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/sumup/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 content is highly actionable with concrete CLI commands and a well-structured connection workflow that includes validation via state polling. Its main weaknesses are minor verbosity and a couple of dangling cross-references that slightly hurt navigation clarity.

Suggestions

Resolve the dangling 'skip to Step 2' reference and relabel '1b' with a matching '1a' or a clearer step numbering so the connection workflow is unambiguous.

Trim the redundant restatement of the action-list command in 'Popular actions' and condense the opening company description to remove minor padding.

Consider moving the proxy flag reference table and detailed action-discovery output into a separate reference file to keep SKILL.md a lean overview.

DimensionReasoningScore

Conciseness

The body is mostly efficient — dominated by executable commands with brief explanations — but includes minor padding such as the opening company description and a redundant repeat of the action-list command in the 'Popular actions' section.

4 / 5

Actionability

It provides copy-paste-ready commands throughout (install, login, connection ensure/get, action list/run, request) plus a flag options table, covering the common cases concretely.

5 / 5

Workflow Clarity

The connection setup has a clear state-driven sequence with a feedback loop (poll after user action), but the dangling 'skip to Step 2' reference and an unexplained '1b' heading introduce minor navigation gaps.

4 / 5

Progressive Disclosure

The single SKILL.md is well-organized with clear section headers and no broken or nested references, though at ~140 lines some inline reference-style material (proxy options, action discovery) could be split into separate files.

4 / 5

Total

17

/

20

Passed

Description

61%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 uses third-person voice and includes both a what and a when clause, anchored by the distinct SumUp brand. Its weakness is generic action language and limited trigger-term coverage that omits the concrete payment vocabulary users would naturally say.

Suggestions

Replace generic verbs ('Manage data, records, and automate workflows') with concrete SumUp actions such as 'process transactions, issue refunds, and view payouts'.

Expand the 'Use when' clause with natural trigger terms users actually say, e.g. 'Use when the user mentions SumUp payments, transactions, payouts, or refunds'.

Tighten the 'when' trigger from the vague 'interact with SumUp data' to specific payment-related scenarios.

DimensionReasoningScore

Specificity

The description names the domain ('SumUp integration') but the actions ('Manage data, records, and automate workflows') are generic rather than concrete payment-specific actions like processing transactions, issuing refunds, or viewing payouts.

2 / 5

Completeness

Both 'what' (SumUp integration, manage data/records, automate workflows) and 'when' ('Use when the user wants to interact with SumUp data') are present, but the 'when' trigger is somewhat generic rather than concrete.

4 / 5

Trigger Term Quality

It surfaces the natural keyword 'SumUp' and a 'Use when...' trigger, but coverage is thin — missing common variations a user would say such as payments, transactions, payouts, or refunds.

3 / 5

Distinctiveness Conflict Risk

The SumUp brand name is a distinct, specific niche trigger, making conflict with other skills minimal — a user mentioning SumUp clearly points to this skill.

5 / 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.