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

Blog Docs Log in Get started

trio

Trio integration. Manage data, records, and automate workflows. Use when the user wants to interact with Trio 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/trio/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 body is a well-structured, mostly executable guide with a strong connection workflow that includes explicit validation and retry logic. The main weaknesses are some marketing-style padding in the intro and minor numbering inconsistencies in the workflow steps.

Suggestions

Trim introductory prose that explains what Trio is ('Think of it as a central hub for managing projects...') and the Membrane marketing language; assume Claude's competence.

Fix the workflow step numbering so referenced 'Step 2' and the '1b' section form a coherent, explicitly numbered sequence.

Consider extracting the proxy flag reference table into a bundled reference file to keep SKILL.md a lean overview, and add a one-line verify step after action runs (e.g. checking the output field) to strengthen the feedback loop.

Dimension	Reasoning	Score
Conciseness	Mostly efficient with concrete commands and a flag table, but includes unnecessary marketing/intro prose ('Think of it as a central hub...') and explanatory padding about Membrane that Claude does not need.	3 / 5
Actionability	Provides copy-paste-ready, executable commands throughout (install, login, connection ensure, action list/run, request) plus a flag table; minor gaps remain where placeholders like <actionId> require the prior discovery step to resolve.	4 / 5
Workflow Clarity	The connection workflow is clearly sequenced with explicit state-based validation checkpoints (READY/BUILDING/CLIENT_ACTION_REQUIRED/CONFIGURATION_ERROR) and a poll-retry feedback loop; minor inconsistency in step numbering ('Step 2', '1b') keeps it just below a 5.	4 / 5
Progressive Disclosure	Well-organized into clear sections with no nested/deep references and good navigation; no bundle files exist, and the single-file structure is appropriate, though the inline proxy flag table could arguably live in a reference.	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 covers both what the skill does and when to use it with a Trio-specific trigger, but the capability language is generic and the trigger phrasing could include more natural synonyms. Distinctiveness is mostly carried by the Trio brand name rather than the action wording.

Suggestions

Replace generic verbs ('Manage data, records, automate workflows') with concrete Trio actions such as 'create and assign tasks, manage meeting notes, and update contact records'.

Expand the 'Use when' clause with natural trigger phrases users would say, e.g. 'Use when the user wants to create Trio tasks, take meeting notes, manage contacts, or automate Trio workflows.'

Add a file/extension-style discriminator or explicit object types (tasks, notes, contacts) to sharpen distinctiveness against other project-management integrations.

Dimension	Reasoning	Score
Specificity	Names the Trio domain and lists several actions ('Manage data, records, and automate workflows'), but those actions are generic and high-level rather than concrete, fitting the '1-2 concrete actions, not comprehensive' anchor.	3 / 5
Completeness	Explicitly answers both 'what' (manage data, records, automate workflows) and 'when' (Use when the user wants to interact with Trio data); the 'when' is present and fairly explicit but could be more specific with concrete trigger phrases.	4 / 5
Trigger Term Quality	Includes a natural trigger phrase ('Use when the user wants to interact with Trio data') with relevant keywords ('Trio', 'data'), but lacks common synonyms or variations that users would naturally say.	3 / 5
Distinctiveness Conflict Risk	The Trio app name gives a clear niche and a Trio-specific trigger, but the described actions ('manage data, records, automate workflows') are generic enough to risk minor overlap with similar integration 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/trio/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.