Name: ticket-tailor
Rating: 55.2 (1 reviews)
Author: membranedev

ticket-tailor

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

Quality

63%

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

Quality

Content

68%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 copy-paste CLI commands and a solid connection-state workflow, but it carries some unnecessary prose, leaves an undefined "Step 2" reference, and omits validation guidance for destructive proxy/action operations. Tightening the prose and adding verification steps would meaningfully improve it.

Suggestions

Define the referenced "Step 2" (the action-discovery/run step) explicitly so the connection-to-execution flow has no broken link.

Add a validation/verification checkpoint after destructive proxy requests and action runs (e.g. re-fetch the resource or check the response status) to satisfy the feedback-loop requirement.

Trim padded prose such as the marketing intro and "so you can focus on the integration logic rather than auth plumbing" to improve token efficiency.

Dimension	Reasoning	Score
Conciseness	The body is mostly efficient with concrete commands, but includes several trim-able prose sections (the marketing-style intro, "so you can focus on the integration logic rather than auth plumbing", "This is the fastest way to get a connection"), matching the anchor for mostly efficient with some unnecessary explanation.	3 / 5
Actionability	It provides copy-paste ready, fully executable commands for install, login, connection ensure, polling, action list/run, and proxy requests plus a flags table, covering the common cases, matching the anchor for fully executable copy-paste guidance.	5 / 5
Workflow Clarity	The connection setup is well-sequenced with state checkpoints, but "Step 2" is referenced and never defined, and destructive-capable operations (proxy POST/DELETE, action runs) lack validation/verification steps, triggering the destructive-operations cap at 3.	3 / 5
Progressive Disclosure	With no bundle files present, the single-file body is organized into clear, well-labeled sections (Install, Authentication, Connecting, Searching, Running actions, Proxy requests, Best practices); at ~140 lines it exceeds the simple-skill threshold so it sits at the good-structure anchor rather than 5.	4 / 5
	Total	15 / 20 Passed

Description

57%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 names the specific product and includes both a what and a when clause, but its action language is generic and it omits natural trigger synonyms like events, tickets, and orders. Tightening the capabilities and adding concrete trigger phrases would raise it.

Suggestions

Replace generic actions ("Manage data, records, and automate workflows") with concrete capabilities such as creating events, managing ticket types, viewing orders, and running check-in lists.

Expand the "Use when" clause with natural trigger phrases users would say, e.g. "when the user mentions Ticket Tailor, event ticketing, selling tickets, orders, or check-in".

Keep the third-person voice but make the what/when pairing more explicit and specific to lift completeness toward a 5.

Dimension	Reasoning	Score
Specificity	Phrases like "Manage data, records, and automate workflows" name the Ticket Tailor domain but use generic, non-concrete actions rather than specific capabilities, matching the anchor for naming the domain with minimal/generic actions.	2 / 5
Completeness	Both a "what" ("Manage data, records, and automate workflows") and a "when" ("Use when the user wants to interact with Ticket Tailor data") are present, but the when clause is generic rather than concrete trigger phrases, matching the anchor for both present with an improvable when.	4 / 5
Trigger Term Quality	The product name "Ticket Tailor" is a strong natural trigger, but the description misses common synonyms users would say (events, tickets, orders, check-in), matching the anchor for some relevant keywords with missing variations.	3 / 5
Distinctiveness Conflict Risk	"Ticket Tailor" is a specific brand giving a clear niche with minimal conflict risk, though the generic action phrasing leaves minor overlap risk with broad data-management skills, matching the mostly-distinct anchor.	4 / 5
	Total	13 / 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/ticket-tailor/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.