Name: sevdesk
Rating: 54.400000000000006 (1 reviews)
Author: membranedev

Blog Docs Log in Get started

sevdesk

SevDesk integration. Manage Organizations. Use when the user wants to interact with SevDesk data.

Quality

61%

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/sevdesk/SKILL.md

Quality

Content

61%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 strongly actionable with executable CLI commands and a clear connection workflow, but it includes some marketing-fluff padding and lacks validation/verification steps for the destructive accounting operations the skill can perform.

Suggestions

Remove the opening marketing paragraph describing what SevDesk is, since Claude does not need that background to use the integration.

Add an explicit validation/verification checkpoint for mutating actions (e.g. read back or dry-run before creating/deleting invoices and vouchers) to satisfy the destructive/batch feedback-loop requirement.

Flesh out the "Popular actions" section with one or two concrete action examples and parameter snippets instead of only restating the discovery command.

Dimension	Reasoning	Score
Conciseness	The body is mostly command-focused and efficient, but the opening paragraph ("SevDesk is a cloud-based accounting software designed for small businesses in Germany...") and phrases like "so you can focus on the integration logic rather than auth plumbing" are unnecessary explanation that could be trimmed.	3 / 5
Actionability	It provides concrete, copy-paste-ready commands (install, login, connection ensure, action run, request with a full flag table), but the "Popular actions" section only repeats the discovery command without showing real action examples or parameter usage, leaving minor gaps.	4 / 5
Workflow Clarity	The connection-setup flow has a clear sequence with state checkpoints (READY/BUILDING/CLIENT_ACTION_REQUIRED/CONFIGURATION_ERROR) and a poll loop, but the skill performs accounting mutations (invoices, vouchers, transactions) with no validation/verification steps for those destructive or batch operations, capping this dimension at 3.	3 / 5
Progressive Disclosure	The skill is a single well-organized file with clearly labeled sections and no nested references; structure is good and content is appropriately placed, with only minor organization gaps (the entity catalog could optionally live in a reference).	4 / 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 has an explicit 'Use when' trigger and a distinct product niche, but its capability list is thin and generic ('Manage Organizations') and its trigger terms are limited to the brand name with no synonyms.

Suggestions

Replace the generic 'Manage Organizations' with concrete actions that reflect the skill's scope, e.g. 'create and send invoices, manage contacts, record expenses, and reconcile transactions in SevDesk'.

Add natural trigger synonyms and terms users would actually say, such as 'invoices', 'expenses', 'bookkeeping', or 'German accounting', rather than only repeating 'SevDesk'.

Dimension	Reasoning	Score
Specificity	It names the domain ("SevDesk integration") and one action ("Manage Organizations"), but the action is generic and does not reflect the skill's broader scope, matching the anchor for domain + 1-2 actions without comprehensive coverage.	3 / 5
Completeness	Both a 'what' ("SevDesk integration. Manage Organizations.") and an explicit 'when' ("Use when the user wants to interact with SevDesk data") are present; the 'what' is thin but the trigger clause is explicit, fitting the anchor where both exist but could be more specific.	4 / 5
Trigger Term Quality	The only natural keyword is the product name "SevDesk" (and "SevDesk data"), with no synonyms or common variations, fitting the anchor for some relevant keywords but missing common variations.	3 / 5
Distinctiveness Conflict Risk	"SevDesk integration" targets a clear, specific product niche with low conflict risk, but the trigger phrasing ("interact with SevDesk data") is somewhat generic, placing it just below the clearest-niche anchor.	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/sevdesk/SKILL.md
Commit: f484c82

Reviewed: 4 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.