CtrlK
BlogDocsLog inGet started
Tessl Logo

tito

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

59

Quality

68%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide

SecuritybySnyk

Low

Low-risk findings worth noting

Fix and improve this skill with Tessl

tessl review fix ./skills/tito/SKILL.md
SKILL.md
Quality
Evals
Security

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 body is actionable and well-structured with executable Membrane CLI commands and a sensible connection workflow including state-polling checkpoints. Its main weaknesses are minor: a few unresolved placeholders, a "Popular actions" section that does not enumerate actions, and slightly broken step labels ("Step 2", "1b").

Suggestions

Fix the broken step labels: define a labeled Step 1/Step 2 sequence or remove the "skip to Step 2" and "1b" references so the workflow is unambiguous.

Make the "Popular actions" section actually list a few common Tito actions (e.g. list events, get tickets, create discount code) instead of only showing the discovery command.

Resolve or explain key placeholders (CONNECTION_ID, actionId) with a concrete worked example so the commands are fully copy-paste runnable.

DimensionReasoningScore

Conciseness

The body is mostly lean commands, flags, and a table, with only minor over-explanation (the "what Tito is" intro line and "auth plumbing" phrasing) that could be trimmed.

4 / 5

Actionability

It provides many copy-paste-ready commands (login, connection ensure, action list/run, request) with a flags table, but leaves placeholders unresolved and the "Popular actions" section does not actually list actions, introducing minor gaps.

4 / 5

Workflow Clarity

The install→login→connect→poll-state→search→run sequence has polling and state-handling feedback loops, but references an undefined "Step 2" and uses an odd "1b" label, leaving minor sequencing gaps.

4 / 5

Progressive Disclosure

With no bundle files present, the skill is self-contained and well-organized into clear sections; at over 50 lines it is dense but coherent, so it lands at good structure with minor organization gaps rather than a 5.

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 answers both what and when and is anchored to a specific product, but its action verbs and trigger terms are generic rather than reflecting Tito's actual domain vocabulary (tickets, events, attendees). Tightening the wording to surface concrete Tito concepts would lift specificity and trigger-term quality.

Suggestions

Replace generic actions ("Manage data, records, and automate workflows") with concrete Tito capabilities such as selling tickets, managing attendees, and handling event releases.

Expand the trigger clause to name natural user phrases, e.g. "Use when the user wants to manage Tito events, tickets, attendees, or discount codes."

Mention key Tito entities (events, tickets, releases, discount codes, webhooks) to improve distinctiveness and trigger-term coverage.

DimensionReasoningScore

Specificity

It names the domain (Tito) and a few actions ("Manage data, records, and automate workflows"), but those actions are generic rather than concrete Tito entities such as tickets, events, or attendees, so it sits just above the minimal-generic anchor.

3 / 5

Completeness

Both a 'what' ("Tito integration. Manage data, records, and automate workflows") and a 'when' ("Use when the user wants to interact with Tito data") are present, but the 'when' is generic rather than concrete trigger phrases, so it stops short of a 5.

4 / 5

Trigger Term Quality

"Use when the user wants to interact with Tito data" includes the keyword "Tito" but misses the natural phrases users actually say (tickets, events, registration, attendees), so coverage is partial.

3 / 5

Distinctiveness Conflict Risk

Naming the specific platform "Tito" gives it a clear niche with minimal conflict risk, though the generic trigger leaves minor overlap with other event/ticketing skills.

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