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 domain (Trello) and mentions the key entities (boards, lists, cards), giving it good distinctiveness. However, it lacks specific concrete actions beyond the generic 'manage' and entirely omits a 'Use when...' clause, making it incomplete for skill selection among many options.

Suggestions

Add a 'Use when...' clause with trigger terms like '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 such as 'Create, update, move, and archive Trello cards; add and reorder lists; manage board members and labels.'

Include natural user language variations like 'kanban board', 'task tracking', 'Trello workspace' to improve trigger term coverage.

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 should cap completeness at 2, and since the 'what' is also somewhat vague, this lands 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 integration'.	2 / 3
Distinctiveness Conflict Risk	Trello is a very specific product, and mentioning 'Trello REST API' along with 'boards, lists, and cards' creates a clear niche that is unlikely to conflict with other skills.	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 partial redundancy between the Usage and Examples sections, and the lack of a validation step after setup or before destructive operations like archiving. The skill would benefit from a brief workflow showing the typical discovery chain (boards → lists → cards) and a credential verification step.

Suggestions

Add a validation step after setup, e.g., 'Verify credentials: run the List boards command and confirm you see your boards'

Remove or consolidate the Examples section with the Usage section to eliminate redundancy (the 'Get all boards' example duplicates 'List boards')

Add an explicit workflow sequence showing the typical discovery chain: first list boards to get boardId, then list lists to get listId, then operate on cards

Dimension	Reasoning	Score
Conciseness	The skill is mostly efficient with concrete curl commands, but the Examples section at the bottom is partially redundant with the Usage section (e.g., 'Get all boards' duplicates 'List boards'). The Notes section is useful but the security warning is something Claude already knows.	2 / 3
Actionability	Every operation has a fully executable curl command with proper flags, URL construction, and jq formatting. The commands are copy-paste ready with clear placeholder conventions ({boardId}, {listId}, etc.).	3 / 3
Workflow Clarity	The setup steps are clear and sequenced, but there's no validation checkpoint (e.g., 'verify your credentials work by running the list boards command'). For operations like archiving cards, there's no confirmation or undo guidance, and the typical workflow of board→list→card discovery isn't explicitly sequenced as a workflow.	2 / 3
Progressive Disclosure	The content is reasonably organized with clear section headers, but everything is in a single file with no bundle files. The Examples section could be separated or the content could benefit from a reference file for less common API endpoints. For a skill of this size (~70 lines of content), the inline approach is acceptable but the redundancy between Usage and Examples sections suggests poor organization.	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: 25 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.