Name: pretix
Rating: 56.8 (1 reviews)
Author: membranedev

Blog Docs Log in Get started

pretix

Pretix integration. Manage Events. Use when the user wants to interact with Pretix data.

Quality

65%

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

Quality

Content

67%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 a well-structured, action-oriented guide to driving Pretix through the Membrane CLI, with strong executable commands and a clear connection-state workflow. It is held back by redundant explanation, inconsistent step numbering, and the absence of verification steps before potentially destructive proxy/action calls.

Suggestions

Tighten the opening paragraph and de-duplicate the action-list command between 'Searching for actions' and 'Popular actions' to reduce token overhead.

Fix the step labeling (add a '1a'/'Step 1' header and a clearly labeled 'Step 2') so the 'skip to Step 2' references resolve.

Add a validation/verification checkpoint before destructive proxy or action calls (e.g. 'For mutating requests, confirm the target id and inspect the response state before proceeding').

Dimension	Reasoning	Score
Conciseness	The body is mostly efficient with concrete commands, but the opening paragraph explaining what Pretix is and the repeated action-list command (in both 'Searching for actions' and 'Popular actions') are unnecessary padding that could be tightened, fitting 'mostly efficient but includes some unnecessary explanation.'	3 / 5
Actionability	It provides copy-paste-ready CLI commands (install, login, connection ensure, action run, request) with a thorough proxy-flag table, but relies on placeholders (CONNECTION_ID, <actionId>) and the 'Popular actions' section only offers a discovery command rather than actual actions, leaving minor gaps below 5.	4 / 5
Workflow Clarity	The connection workflow is clearly sequenced with a state machine (READY, BUILDING, CLIENT_ACTION_REQUIRED, CONFIGURATION_ERROR) and polling feedback loops, but step labeling is inconsistent ('skip to Step 2' with no Step 2 header, '1b' without a '1a') and running actions/proxy requests lacks verification checkpoints.	4 / 5
Progressive Disclosure	The single-file body is well-organized into clearly headed sections with no nested references, but at ~157 lines detailed reference material (the connection state machine, proxy flag table) is inlined rather than split into one-level-deep reference files, keeping it below 5.	4 / 5
	Total	15 / 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 is a concise, third-person statement that covers both what the skill does and when to use it, anchored to a clearly named platform. Its main weaknesses are thin action coverage and missing common trigger synonyms (tickets, orders, attendees).

Suggestions

Expand the action list beyond 'Manage Events' to concrete operations like 'create events, sell tickets, manage orders, and process payments'.

Add natural trigger terms users would say, e.g. 'Use when the user mentions Pretix, ticket sales, events, orders, or attendee management.'

Replace the generic 'interact with Pretix data' trigger with specific use-case phrases to sharpen when-to-use guidance.

Dimension	Reasoning	Score
Specificity	Names the domain ("Pretix integration") and one concrete action ("Manage Events"), matching the 'names domain and 1-2 concrete actions, but not comprehensive' anchor; it does not list several actions so it stays below 4.	3 / 5
Completeness	It states what ("Pretix integration. Manage Events.") and when ("Use when the user wants to interact with Pretix data."), satisfying both; the 'when' is explicit but generic rather than concrete trigger phrases, so it does not reach 5.	4 / 5
Trigger Term Quality	"Pretix", "Events", and "Pretix data" are relevant natural terms, but core synonyms users would say like "tickets", "ticketing", "orders", or "attendees" are missing, fitting 'some relevant keywords but missing common variations or synonyms.'	3 / 5
Distinctiveness Conflict Risk	Naming the specific Pretix platform gives it a clear niche with minimal conflict risk, but the generic "Manage Events" phrasing leaves minor overlap risk with general event-management skills, keeping it below 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/pretix/SKILL.md
Commit: f484c82

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