trello

Manage Trello boards, lists, and cards via the Trello REST API.

1.09x

Quality

52%

Does it follow best practices?

Impact

93%

1.09x

Average score across 3 eval scenarios

Securityby

Advisory

Suggest reviewing before use

Fix and improve this skill with Tessl

tessl review fix ./skills/trello/SKILL.md

Quality

Content

64%

Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.

A solid, actionable skill with executable curl commands for all common Trello operations. Its main weaknesses are redundancy between the Usage and Examples sections, and the lack of any validation/error-checking guidance after API calls. Trimming duplicated examples and adding response validation would meaningfully improve it.

Suggestions

Remove or consolidate the Examples section with the Usage section to eliminate duplication (e.g., 'List boards' appears twice with nearly identical commands).

Add response validation guidance, such as checking HTTP status codes (e.g., appending `-w '\n%{http_code}'` to curl commands) or verifying expected JSON output after create/update operations.

Add a brief error handling note showing what a failed API response looks like and how to interpret common errors (401 unauthorized, 404 not found, 429 rate limited).

Dimension	Reasoning	Score
Conciseness	The skill is mostly efficient with concrete curl commands, but the Examples section at the bottom largely duplicates the Usage section (e.g., 'Get all boards' repeats the list boards command). The Notes section is useful but could be tighter.	2 / 3
Actionability	Every operation has a fully executable curl command with proper flags, environment variable references, and jq formatting. Commands are copy-paste ready with only placeholder IDs needing substitution.	3 / 3
Workflow Clarity	The setup steps are clearly sequenced, and individual API operations are clear. However, there's no validation guidance (e.g., checking response codes, verifying card creation succeeded) and no error handling or feedback loops for operations like archiving or moving cards.	2 / 3
Progressive Disclosure	The content is reasonably organized with clear section headers, but it's somewhat monolithic — the Examples section could be trimmed or merged since it overlaps with Usage. No bundle files exist, so there's no opportunity for external references, but the inline content could still be better structured.	2 / 3
	Total	9 / 12 Passed

Description

40%

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 identifies a clear domain (Trello) and its core entities, making it distinctive, but it lacks specific concrete actions beyond the generic 'manage' and entirely omits a 'Use when...' clause. The trigger terms are adequate but could be expanded with natural user language for common Trello operations.

Suggestions

Add a 'Use when...' clause such as 'Use when the user asks about Trello boards, creating or moving cards, managing lists, or interacting with Trello.'

Replace the vague 'Manage' with specific actions like 'Create, update, move, and archive Trello cards; add and reorder lists; manage board members and labels.'

Include natural trigger terms users might say, such as 'kanban board', 'task tracking', 'add a card', 'move to done', or 'Trello workspace'.

Dimension	Reasoning	Score
Specificity	Names the domain (Trello) and some actions ('manage boards, lists, and cards'), but doesn't list specific concrete actions like creating cards, moving cards between lists, archiving, adding labels, etc.	2 / 3
Completeness	Describes what it does ('Manage Trello boards, lists, and cards') but has no 'Use when...' clause or equivalent explicit trigger guidance, which per the rubric caps completeness at 2, and the 'what' itself is also quite thin, bringing it to 1.	1 / 3
Trigger Term Quality	Includes 'Trello', 'boards', 'lists', 'cards', and 'REST API' which are relevant keywords, but misses common user variations like 'kanban', 'task board', 'add a card', 'move card', or specific Trello operations users would naturally request.	2 / 3
Distinctiveness Conflict Risk	Trello is a very specific product, and mentioning 'Trello REST API' along with its core entities (boards, lists, cards) creates a clear niche that is unlikely to conflict with other skills.	3 / 3
	Total	8 / 12 Passed

Validation

72%

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 — 8 / 11 Passed

Validation for skill structure

Criteria	Description	Result
metadata_version	'metadata.version' is missing	Warning
metadata_field	'metadata' should map string keys to string values	Warning
frontmatter_unknown_keys	Unknown frontmatter key(s) found; consider removing or moving to metadata	Warning

	Total	8 / 11 Passed

Repository: attilaczudor/Test
Commit: b4fc4af

Reviewed: 2 months 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.