Name: trello
Rating: 62.4 (1 reviews)
Author: membranedev

Blog Docs Log in Get started

trello

Trello integration. Manage Boards, Members, Labels. Use when the user wants to interact with Trello data.

Quality

74%

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

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 highly actionable with copy-paste membrane commands and a clear connection workflow including a polling feedback loop. Its main weaknesses are an unnecessary introductory definition of Trello and a long single-file structure that could offload some detail into reference files.

Suggestions

Remove or drastically shorten the opening "Trello is a web-based project management tool..." paragraph; Claude already knows what Trello is.

Add a validation checkpoint after running actions (e.g. check the response `output`/`error` fields before proceeding) to strengthen the workflow feedback loop.

Move the detailed `clientAction` field reference and the proxy flag table into a separate reference file to keep SKILL.md a lean overview.

Dimension	Reasoning	Score
Conciseness	Most of the body is efficient executable commands, but the opening paragraph ("Trello is a web-based project management tool that uses a Kanban board system...") explains what Trello is — a concept Claude already knows — and could be trimmed.	3 / 5
Actionability	Provides fully executable, copy-paste-ready membrane commands for the common cases (login, connection ensure, action list/run, request) plus a concrete flag table for proxy requests.	5 / 5
Workflow Clarity	Clear install → authenticate → connect → poll-for-ready sequence with an explicit state-based feedback loop (READY / CLIENT_ACTION_REQUIRED / CONFIGURATION_ERROR and "poll again" after user action), though later action-running steps lack output validation checkpoints.	4 / 5
Progressive Disclosure	Well-organized into clear sections with no nested references and no bundle files to navigate, but the single-file body is fairly long and some content (detailed clientAction fields, the proxy flag table) could be split into reference files.	4 / 5
	Total	16 / 20 Passed

Description

73%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 is concise, third-person, and clearly answers both what and when, anchored to a distinct product niche. Its main weakness is the generic "Manage" action verb and the lack of richer trigger synonyms (cards, lists, Kanban).

Suggestions

Replace the generic "Manage" with specific concrete actions, e.g. "Create and move Cards, organize Lists, manage Boards, Members, and Labels."

Broaden trigger terms to include natural synonyms users say, such as "cards", "lists", and "Kanban boards".

Make the when clause more concrete with explicit trigger scenarios, e.g. "Use when the user wants to create cards, move tasks across lists, or manage Trello boards."

Dimension	Reasoning	Score
Specificity	Names the Trello domain and concrete entities ("Manage Boards, Members, Labels"), but the only action verb is the generic "Manage" rather than several specific concrete actions.	3 / 5
Completeness	Explicitly answers both what ("Trello integration. Manage Boards, Members, Labels.") and when ("Use when the user wants to interact with Trello data."), though the when clause is generic rather than listing concrete trigger scenarios.	4 / 5
Trigger Term Quality	Includes natural terms users would say ("Trello", "Boards", "Members", "Labels", "interact with Trello data"), but misses common variations like "cards", "lists", and "Kanban".	4 / 5
Distinctiveness Conflict Risk	"Trello" is a specific named product with distinct triggers (Boards, Members, Labels), giving it a clear niche with minimal overlap risk against other skills.	5 / 5
	Total	16 / 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/trello/SKILL.md
Commit: f484c82

Reviewed: ~20 hours 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.