Name: digistore24
Rating: 59.2 (1 reviews)
Author: membranedev

digistore24

Digistore24 integration. Manage Users, Roles, Organizations, Projects, Pipelines, Goals and more. Use when the user wants to interact with Digistore24 data.

Quality

68%

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

Quality

Content

75%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 executable commands and a well-structured connection state-machine, but it carries a padded introductory paragraph, slightly inconsistent step numbering, and no progressive disclosure into separate files despite its length.

Suggestions

Trim or remove the opening platform-explanation paragraph; assume Claude knows what an online sales/payment platform is.

Fix the step numbering: either label a 'Step 2' header or drop the 'skip to Step 2' references so the flow is unambiguous.

Add a brief validation/check step before destructive actions like refund-purchase and delete-product (e.g. confirm the target purchase/product id first).

Dimension	Reasoning	Score
Conciseness	The body is mostly efficient CLI commands and tables, but opens with a three-sentence platform explainer ('Digistore24 is an online sales platform and payment processor...') that Claude largely does not need, and the entity overview list partly duplicates the Popular actions table.	3 / 5
Actionability	It provides copy-paste-ready executable commands throughout (npm install, membrane login, connection ensure, action list/run, request) plus a 20-row actions table and a flags table, covering the common cases fully.	5 / 5
Workflow Clarity	The connect workflow is clearly sequenced with state checkpoints (READY/BUILDING/CLIENT_ACTION_REQUIRED/CONFIGURATION_ERROR) and a poll-again feedback loop, but the body references 'Step 2' without a labeled header and offers no validation guidance around the destructive list actions (refund-purchase, delete-product).	4 / 5
Progressive Disclosure	The body is well-organized into clear headed sections with tables and no nested references, but at ~185 lines everything is inlined in a single file with no bundle files or external references, so bulk reference material (the actions table, connection-state breakdown) is not split out.	4 / 5
	Total	16 / 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 covers both what and when with a clear named-platform niche, but its trigger vocabulary is thin and its action list uses one generic verb over generic SaaS entities rather than Digistore24-specific capabilities.

Suggestions

Replace the generic entity list with Digistore24-specific actions users actually request, e.g. 'list products, purchases, buyers, invoices, and transactions; issue refunds; create vouchers'.

Expand the 'Use when' clause with concrete trigger phrases like 'Use when the user wants to manage Digistore24 sales, orders, buyers, products, payouts, or refunds'.

Swap the single generic verb 'Manage ... and more' for several distinct concrete verbs to lift specificity.

Dimension	Reasoning	Score
Specificity	The description names the domain and lists many concrete entities ('Manage Users, Roles, Organizations, Projects, Pipelines, Goals') but relies on a single generic verb ('Manage ... and more'), so concrete action coverage is one generic action applied to a noun list rather than several distinct actions.	3 / 5
Completeness	Both 'what' ('Digistore24 integration. Manage Users, Roles...') and 'when' ('Use when the user wants to interact with Digistore24 data.') are present, matching the anchor 4 example closely; the 'when' clause is explicit but generic rather than listing concrete triggers, keeping it below 5.	4 / 5
Trigger Term Quality	The only natural trigger keyword is 'Digistore24' (repeated via 'interact with Digistore24 data'); common domain variations users would actually say (sales, orders, purchases, products, affiliates) are missing.	3 / 5
Distinctiveness Conflict Risk	'Digistore24' is a named platform giving a clear niche with minimal conflict risk, but the generic 'Manage Users, Roles, Organizations, Projects, Pipelines, Goals and more' phrasing reads like generic SaaS language and lacks domain-specific triggers, so it is not a clean 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/digistore24/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.