trello
Manage Trello boards, lists, and cards via the Trello REST API.
65
52%
Does it follow best practices?
Impact
93%
1.09xAverage score across 3 eval scenarios
Advisory
Suggest reviewing before use
Optimize this skill with Tessl
npx tessl skill review --optimize ./skills/trello/SKILL.mdQuality
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 reasonable distinctiveness. However, it lacks specific concrete actions beyond the generic 'manage' and critically omits any 'Use when...' guidance, making it harder for Claude to know when to select this skill over others.
Suggestions
Add a 'Use when...' clause with trigger terms like 'Use when the user asks to create, update, move, or archive Trello cards, manage Trello boards or lists, or interact 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 phrases and variations like 'kanban board', 'task tracking', 'move card to done', or 'add a Trello card' 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 'Use when...' clause or equivalent explicit trigger guidance. Per the rubric, a missing 'Use when...' clause caps completeness at 2, and since the 'what' is also somewhat vague, this scores a 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 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.
A solid, actionable skill with executable curl commands covering the core Trello API operations. Its main weaknesses are some redundancy between the Usage and Examples sections, and the lack of error handling or validation guidance (e.g., checking response codes after archive/create operations). The content could be tightened by merging examples inline and adding a brief error-handling note.
Suggestions
Merge the Examples section into the Usage section as additional examples under each operation to eliminate redundancy and reduce token count.
Add a brief error handling pattern (e.g., checking HTTP status codes with curl -w '%{http_code}') especially for destructive operations like archiving cards.
Remove the security warning about keeping API keys secret—Claude already knows this—and use the space for more useful guidance like pagination or batch operation patterns.
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The skill is mostly efficient but has some redundancy—the Examples section at the bottom largely duplicates the Usage section with minor variations. 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 patterns, and jq formatting. Commands are copy-paste ready with clear placeholder syntax ({boardId}, {listId}, etc.). | 3 / 3 |
Workflow Clarity | The setup steps are clear and sequenced, and individual API operations are well-documented. However, there's no validation/error handling guidance—no mention of checking HTTP status codes, handling auth failures, or verifying that destructive operations (archive) succeeded before proceeding. | 2 / 3 |
Progressive Disclosure | The content is well-organized with clear headers, but it's somewhat monolithic for its length. The Examples section could be folded into the Usage section or split into a separate file. With no bundle files, there's no progressive disclosure structure, though for a skill of this complexity it's borderline acceptable. | 2 / 3 |
Total | 9 / 12 Passed |
Validation
72%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
- qsimeon/openclaw-engaging
- Commit
4467e04
- Reviewed
Table of Contents
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.