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

tripetto

Tripetto integration. Manage data, records, and automate workflows. Use when the user wants to interact with Tripetto 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

Low

Low-risk findings worth noting

Fix and improve this skill with Tessl

tessl review fix ./skills/tripetto/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 delivers strong, executable Membrane/Tripetto guidance with a well-sequenced connection workflow and state-based validation checkpoints. It is held back by some unnecessary Tripetto background explanation and redundant command repetition rather than token-lean efficiency.

Suggestions

Remove the introductory paragraph explaining what Tripetto is and who uses it; Claude can infer this from the brand and the user's request.

De-duplicate the action-list guidance: keep it in 'Searching for actions' and have 'Popular actions' reference it rather than restating the command with a different `npx` invocation.

Explicitly label the destination of 'Step 2' so the READY-state jump target is unambiguous.

Dimension	Reasoning	Score
Conciseness	The body is mostly efficient with dense executable command blocks, but includes unnecessary explanation ('Tripetto is a form and survey builder... used by researchers, marketers, and businesses') and redundant repetition of the action-list command in both 'Searching for actions' and 'Popular actions', matching the mostly-efficient-but-could-be-tightened anchor.	3 / 5
Actionability	Provides concrete, copy-paste-ready commands across the common cases (install, login, connection ensure, polling, action list/run, proxy), with only minor gaps such as the inconsistent `npx @membranehq/cli` vs `membrane` invocation in the 'Popular actions' section.	4 / 5
Workflow Clarity	The connection flow is clearly sequenced with state-based checkpoints (READY, BUILDING, CLIENT_ACTION_REQUIRED, CONFIGURATION_ERROR) and an explicit feedback loop ('After the user completes the action, poll again'), but the referenced 'Step 2' is never explicitly defined, leaving a minor gap.	4 / 5
Progressive Disclosure	No bundle files exist and the skill is self-contained with well-organized ##/### sections and no nested references, fitting the good-structure anchor; the only gap is that long inlined material like the proxy flags table and clientAction detail could arguably live elsewhere, though the skill has no external references to navigate.	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 successfully states both what the skill does and when to use it, anchored by a specific brand name that lowers conflict risk. It is weakened by generic action verbs and a lack of natural synonyms like 'forms' or 'surveys' that users would actually say.

Suggestions

Replace generic verbs with concrete Tripetto-specific actions, e.g. 'create forms, collect responses, and manage survey data'.

Add natural trigger synonyms users would say, such as 'forms', 'surveys', or 'questionnaires', to the 'Use when...' clause.

Tighten the 'when' clause to name specific Tripetto objects, e.g. 'Use when the user wants to create Tripetto forms, collect responses, or query form data.'

Dimension	Reasoning	Score
Specificity	Names the Tripetto domain and a few actions ('Manage data, records, and automate workflows'), but the actions are generic rather than concrete like 'extract text' or 'fill forms', landing at the anchor that lists 1-2 actions without comprehensive coverage.	3 / 5
Completeness	Explicitly answers both what ('Tripetto integration. Manage data, records, and automate workflows.') and when ('Use when the user wants to interact with Tripetto data.'), but the 'when' clause is generic and could be more specific, fitting the anchor where both are present yet the trigger could be sharper.	4 / 5
Trigger Term Quality	Includes relevant keywords ('Tripetto', 'data', 'records', 'workflows') and an explicit trigger, but misses natural synonyms users would say like 'forms' or 'surveys', matching the anchor with some relevant keywords but missing common variations.	3 / 5
Distinctiveness Conflict Risk	The 'Tripetto integration' brand name and 'interact with Tripetto data' trigger give it a clear niche with minimal conflict risk, though the generic 'manage data, records, automate workflows' phrasing creates minor overlap with other data/automation skills.	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/tripetto/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.