Name: trestle
Rating: 55.2 (1 reviews)
Author: membranedev

trestle

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

Quality

62%

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/trestle/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, actionable guide with concrete Membrane CLI commands and a connection workflow that includes real state-checking and retry logic. Its main weaknesses are some explanatory prose padding, placeholder-only examples without a worked end-to-end run, and an undefined "Step 2" reference.

Suggestions

Trim the introductory paragraph and phrases like "so you can focus on the integration logic rather than auth plumbing"; assume Claude's competence and keep only operationally useful context.

Define or remove the undefined "Step 2" — either label the next section as Step 2 (Running actions) or drop the cross-references so the workflow is self-contained.

Add one fully worked example with realistic values (e.g. a concrete connectionId and a sample action run with a real --input JSON body) so the actionability reaches copy-paste readiness.

Dimension	Reasoning	Score
Conciseness	The bulk is lean executable commands, but the intro paragraph ("Trestle is a Ruby on Rails admin framework… It's used by Rails developers…") and prose like "so you can focus on the integration logic rather than auth plumbing" add explanation that could be trimmed, matching the "mostly efficient but includes some unnecessary explanation" anchor.	3 / 5
Actionability	It provides many concrete, runnable commands (install, login, connection ensure, action list/run, request) plus a flags table, but examples rely on placeholders (CONNECTION_ID, <actionId>, QUERY) with no fully worked end-to-end example, fitting the 4-anchor's "minor gaps" rather than copy-paste-ready 5.	4 / 5
Workflow Clarity	The install→authenticate→connect sequence has real checkpoints (poll BUILDING→READY, handle CLIENT_ACTION_REQUIRED, branch on CONFIGURATION_ERROR/SETUP_FAILED) with retry feedback, but the dangling "skip to Step 2" / "Step 2" references point to a step that is never defined, leaving a minor validation gap.	4 / 5
Progressive Disclosure	Content is well-organized into clearly headed sections with no nested or buried references, but everything (~140 lines) is inlined in a single file with no external reference split, fitting the 4-anchor's "good structure; minor organization gaps" rather than the one-level-deep reference pattern of the 5-anchor.	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 cleanly answers both what and when with an explicit Trestle trigger, but its capability verbs are generic rather than concrete. It is distinct thanks to the named integration yet lacks the specific actions and term variations of a top-tier description.

Suggestions

Replace generic verbs ("Manage data, records, and automate workflows") with concrete Trestle operations, e.g. "Create and manage Trestle projects, documents, sections, tasks, and members, and run admin workflows."

Add natural term variations and synonyms beyond "Trestle data", such as "Trestle admin", "Trestle records", or the specific resource names (projects, tasks, members) users would actually say.

Tighten the when-clause to concrete triggers, e.g. "Use when the user wants to manage Trestle projects, tasks, members, or admin workflows."

Dimension	Reasoning	Score
Specificity	"Manage data, records, and automate workflows" names the Trestle domain but the actions are generic management verbs with no concrete operations, fitting the "names the domain but actions are minimal or generic" anchor rather than the 3-anchor's concrete actions.	2 / 5
Completeness	It gives both a what ("Manage data, records, and automate workflows") and an explicit when ("Use when the user wants to interact with Trestle data"), but the what is generic so it stops short of the fully concrete 5-anchor.	4 / 5
Trigger Term Quality	It surfaces "Trestle", "Trestle data", and "interact with Trestle data" — relevant natural terms — but offers no synonyms or variations, matching the "some relevant keywords but missing common variations" anchor.	3 / 5
Distinctiveness Conflict Risk	Naming the specific app Trestle gives a distinct trigger with minimal conflict risk, but the generic "manage data, records, and automate workflows" phrasing could overlap with other data-integration skills, fitting the 4-anchor rather than the clear-niche 5-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/trestle/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.