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

Optimize this skill with Tessl

npx tessl skill review --optimize ./skills/trello/SKILL.md

Quality

Discovery

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 niche (Trello API management) and is unlikely to conflict with other skills, but it lacks specificity in the actions it can perform and entirely omits a 'Use when...' clause. The trigger terms are adequate but could be expanded with more natural user language variations.

Suggestions

Add a 'Use when...' clause, e.g., 'Use when the user asks to create, update, move, or archive Trello cards, lists, or boards, or mentions Trello or kanban workflows.'

List more specific concrete actions such as 'create cards, move cards between lists, add labels, assign members, archive cards, create boards'.

Include natural trigger term variations like 'kanban', 'task board', 'Trello workspace', or 'card management'.

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 explicit 'Use when...' clause or equivalent trigger guidance, which per the rubric caps completeness at 2, and the 'what' is also fairly thin, placing this at 1.	1 / 3
Trigger Term Quality	Includes key terms like 'Trello', 'boards', 'lists', 'cards', and 'REST API', which are relevant. However, it misses common user variations like 'kanban', 'task board', 'move card', 'create card', or 'Trello automation'.	2 / 3
Distinctiveness Conflict Risk	Trello is a very specific product with distinct terminology (boards, lists, cards). This is unlikely to conflict with other skills since it clearly targets Trello API interactions.	3 / 3
	Total	8 / 12 Passed

Implementation

64%

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

This is a solid, actionable skill with concrete curl commands for all common Trello operations. Its main weaknesses are redundancy between the Usage and Examples sections, and the lack of error handling/validation guidance for API calls (checking HTTP status codes, handling rate limit responses). The skill would benefit from a clearer end-to-end workflow showing how operations chain together.

Suggestions

Remove or differentiate the Examples section from Usage — currently 'List boards' and 'Get all boards' are near-duplicates. Move the unique examples (filtering by name, getting all cards on a board) into the relevant Usage subsections.

Add error handling guidance: check HTTP response codes, show what a rate-limit error looks like, and include a retry pattern for 429 responses.

Add a brief workflow example showing the typical chain: list boards → pick board → list lists → create/move card, making the sequential dependency explicit.

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, URL structure, and jq formatting. Commands are copy-paste ready with clear placeholder variables like {boardId} and {listId}.	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, handling errors from the API), and the typical workflow of 'list boards → get lists → get/create cards' isn't explicitly sequenced as a connected flow.	2 / 3
Progressive Disclosure	The content is reasonably organized with clear section headers, but everything is in a single file with no references to supporting materials. The Examples section could be separated or the content could be better structured to avoid redundancy with the Usage section.	2 / 3
	Total	9 / 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: deepgram/dglabs-deepclaw
Commit: ec8d4f8

Reviewed: about 8 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.