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, distinct domain (Trello API management) but is too terse to be effective for skill selection. It lacks a 'Use when...' clause, specific concrete actions beyond the generic 'manage', and natural trigger terms that users would employ when requesting Trello-related tasks.
Suggestions
Add a 'Use when...' clause with explicit triggers, e.g., 'Use when the user asks about Trello boards, creating or moving cards, managing lists, or automating Trello workflows.'
List specific concrete actions instead of the generic 'manage', e.g., 'Create, update, move, and archive Trello cards; add and reorder lists; manage board members and labels.'
Include natural user-facing trigger terms like 'kanban board', 'task tracking', 'add a card', 'move to done', or 'Trello automation' to improve matching.
| 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, which per the rubric caps completeness at 2, and the 'what' is also quite thin, placing this at 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 with distinct terminology (boards, lists, cards), making this unlikely to conflict with other skills. The mention of 'Trello REST API' clearly carves out a unique niche. | 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 failures). The content would benefit from consolidation and adding response validation patterns.
Suggestions
Merge the Examples section into the Usage section or differentiate them clearly (e.g., Examples shows a complete workflow chaining multiple commands) to eliminate duplication.
Add a response validation pattern, e.g., checking HTTP status codes or piping through `jq` to detect error responses, especially for write operations like create/archive.
Add a brief error handling note showing how to detect and handle Trello API errors (e.g., `curl -s -w '%{http_code}' ... | tail -1` or checking for error JSON).
| 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., listing boards appears twice). The Notes section includes some useful info 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. The commands are copy-paste ready with clear placeholder variables ({boardId}, {listId}, etc.). | 3 / 3 |
Workflow Clarity | The setup steps are clearly sequenced, and individual API operations are clear. However, there's no validation guidance—no mention of checking response codes, handling errors, or verifying that operations succeeded (e.g., confirming a card was created). For destructive operations like archiving, this is a gap. | 2 / 3 |
Progressive Disclosure | The content is reasonably organized with clear section headers, but everything is in one file with some redundancy between Usage and Examples sections. For a skill of this length (~70 lines of content), the Examples section could be split out or the duplicate commands consolidated. | 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
- attilaczudor/Test
- Commit
b3cef5f
- 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.