trello
Manage Trello boards, lists, and cards via the Trello REST API.
68
Does it follow best practices?
If you maintain this skill, you can automatically optimize it using the tessl CLI to improve its score:
npx tessl skill review --optimize ./path/to/skillValidation for skill structure
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) which provides good distinctiveness, but suffers from vague action language ('manage') and completely lacks trigger guidance. It would benefit significantly from listing specific operations and adding explicit 'Use when...' conditions.
Suggestions
Add a 'Use when...' clause with trigger terms like 'Trello', 'kanban board', 'create card', 'move task'
Replace vague 'Manage' with specific actions like 'Create, update, move, and archive Trello cards; add and reorder lists; configure board settings'
Include common user phrasings like 'add a task to Trello', 'organize my board', 'check my Trello cards'
| Dimension | Reasoning | Score |
|---|---|---|
Specificity | Names the domain (Trello) and mentions three entities (boards, lists, cards) but uses vague 'manage' rather than listing concrete actions like 'create cards', 'move lists', 'archive boards'. | 2 / 3 |
Completeness | Describes what it does (manage Trello entities) but completely lacks a 'Use when...' clause or any explicit trigger guidance for when Claude should select this skill. | 1 / 3 |
Trigger Term Quality | Includes 'Trello', 'boards', 'lists', 'cards' which are relevant keywords, but misses common variations users might say like 'kanban', 'task board', 'add a card', or action-oriented terms. | 2 / 3 |
Distinctiveness Conflict Risk | Trello is a specific product name that creates a clear niche; unlikely to conflict with other skills since 'Trello' is a distinct trigger term. | 3 / 3 |
Total | 8 / 12 Passed |
Implementation
87%Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.
This is a well-crafted API reference skill that provides executable curl commands for common Trello operations. It excels at conciseness and actionability with copy-paste ready examples. The main weakness is the lack of workflow guidance for chaining operations together and no mention of error handling or response validation.
Suggestions
Add a brief workflow example showing how to chain operations (e.g., 'To create a card: 1. Get board ID, 2. Get list ID, 3. Create card, 4. Verify with GET')
Include a note about checking API response codes or using jq to validate successful operations before proceeding
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The skill is lean and efficient, providing only necessary setup instructions and executable curl commands without explaining what Trello is or how REST APIs work. Every section earns its place. | 3 / 3 |
Actionability | All commands are fully executable curl commands with proper syntax, environment variable usage, and jq formatting. Copy-paste ready with clear placeholder notation for IDs. | 3 / 3 |
Workflow Clarity | While individual commands are clear, there's no explicit workflow for common multi-step operations (e.g., find board -> get lists -> create card). The skill presents isolated commands without sequencing or validation of API responses. | 2 / 3 |
Progressive Disclosure | For a skill of this scope (~80 lines), the content is well-organized with clear sections (Setup, Usage, Notes, Examples). No external references needed; the flat structure is appropriate for the content volume. | 3 / 3 |
Total | 11 / 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 | |
- 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.