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 ./openclaw/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 and 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 users might 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 card to done', '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 since the 'what' is also fairly thin, a score of 1 is appropriate. | 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 a clear end-to-end workflow showing how operations chain together (e.g., discovering IDs before using them). Error handling guidance for common failure modes (bad credentials, rate limiting) would also strengthen it.
Suggestions
Remove or consolidate the Examples section with the Usage section to eliminate duplication (e.g., 'List boards' and 'Get all boards' are essentially the same command).
Add a brief workflow showing the typical chain: list boards → pick board ID → list lists → pick list ID → create/move card, to make the multi-step discovery process explicit.
Add a brief note on error handling: what a 401 response means (bad credentials), what a 429 means (rate limited), and how to verify credentials work before proceeding.
| 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 'List boards'). The Notes section is useful but could be tighter. | 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 conventions ({boardId}, {listId}, etc.). | 3 / 3 |
Workflow Clarity | The setup steps are clearly sequenced, and individual API operations are clear. However, there's no guidance on the typical workflow (e.g., list boards → get board ID → list lists → get list ID → create card), and no validation/error handling for failed API calls or invalid credentials. | 2 / 3 |
Progressive Disclosure | 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 size, the Examples section could be separated or the content could be deduplicated to improve organization. | 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
- trpc-group/trpc-agent-go
- Commit
af8bd5f
- 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.