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 clearly identifies the Trello domain and mentions key entities (boards, lists, cards), giving it reasonable distinctiveness. However, it lacks a 'Use when...' clause, which is critical for Claude to know when to select this skill, and the capabilities listed are too high-level ('manage') rather than enumerating specific actions.

Suggestions

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

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

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

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 completely lacks a 'Use when...' clause or any explicit trigger guidance for when Claude should select this skill. Per rubric guidelines, missing 'Use when' caps completeness at 2, and the 'what' is also only moderately detailed, warranting a 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 a card', or specific Trello operations users would naturally request.	2 / 3
Distinctiveness Conflict Risk	Trello is a very specific product/platform, and the mention of 'Trello REST API' 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 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-handling guidance for API calls. The skill would benefit from response checking patterns and deduplication of examples.

Suggestions

Remove or differentiate the Examples section from Usage — currently 'Get all boards' duplicates 'List boards'. Instead, show a multi-step workflow example (e.g., find board → get lists → create card → verify).

Add response validation patterns, e.g., checking HTTP status codes with `curl -w '%{http_code}'` or verifying created resources by fetching them back.

Include a brief error handling note showing what a typical error response looks like and how to interpret it (e.g., 401 for bad credentials, 429 for rate limiting).

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 clear and sequenced, and individual API operations are well-documented. However, there's no validation guidance (e.g., checking response codes, verifying a card was created successfully) 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 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: Hung-Reo/hungreo-openclaw
Commit: d8d7f4b

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