trello-automation
Automate Trello boards, cards, and workflows via Rube MCP (Composio). Create cards, manage lists, assign members, and search across boards programmatically.
73
65%
Does it follow best practices?
Impact
85%
1.73xAverage score across 3 eval scenarios
Advisory
Suggest reviewing before use
Optimize this skill with Tessl
npx tessl skill review --optimize ./plugins/all-skills/skills/trello-automation/SKILL.mdQuality
Discovery
67%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 does a good job listing specific Trello-related actions and is clearly scoped to a distinct domain. However, it lacks an explicit 'Use when...' clause, which limits its completeness score, and the trigger terms could be broader to capture more natural user language. The mention of 'Rube MCP (Composio)' adds implementation detail that doesn't help with skill selection.
Suggestions
Add an explicit 'Use when...' clause, e.g., 'Use when the user asks about Trello boards, managing tasks on Trello, or automating Trello workflows.'
Include additional natural trigger terms users might say, such as 'kanban', 'task board', 'move card', 'add label', 'due date', or 'checklist'.
| Dimension | Reasoning | Score |
|---|---|---|
Specificity | Lists multiple specific concrete actions: 'Create cards, manage lists, assign members, and search across boards programmatically.' Also mentions 'Automate Trello boards, cards, and workflows.' | 3 / 3 |
Completeness | Clearly answers 'what does this do' with specific actions, but lacks an explicit 'Use when...' clause or equivalent trigger guidance. The 'when' is only implied by the domain (Trello). | 2 / 3 |
Trigger Term Quality | Includes good natural keywords like 'Trello', 'boards', 'cards', 'lists', 'members', but misses common user variations like 'kanban', 'task management', 'move card', 'add label', 'due date', or 'checklist'. The mention of 'Rube MCP (Composio)' is technical jargon unlikely to be used by end users. | 2 / 3 |
Distinctiveness Conflict Risk | Clearly scoped to Trello specifically, with distinct triggers like 'Trello', 'boards', 'cards', 'lists'. Unlikely to conflict with other skills unless there's another Trello-specific skill. | 3 / 3 |
Total | 10 / 12 Passed |
Implementation
62%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-structured Trello automation skill with clear workflow sequences, good pitfall documentation, and useful quick reference. Its main weaknesses are the lack of concrete executable examples (actual API call payloads/responses) and some content redundancy between the per-workflow pitfalls and the consolidated Known Pitfalls section. The skill would benefit from trimming duplicated content and adding at least one concrete input/output example.
Suggestions
Add at least one concrete example showing an actual tool call with parameters and a sample response, including how to parse nested response data (e.g., extracting idChecklist from data.data).
Remove or consolidate the 'Known Pitfalls' section since its content is already covered in per-workflow pitfall blocks — this would save ~10 lines of redundant tokens.
Consider splitting the quick reference table and detailed workflow descriptions into a separate REFERENCE.md file to improve progressive disclosure.
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The skill is reasonably efficient but has some redundancy — the 'Known Pitfalls' section largely repeats pitfalls already listed under individual workflows, and the quick reference table duplicates information from the workflow sections. Some trimming would improve token efficiency. | 2 / 3 |
Actionability | The skill provides specific tool names, parameter names, and clear tool sequences, which is good. However, there are no executable code examples or concrete input/output snippets showing actual API calls with real payloads or response parsing. The guidance is specific but not copy-paste executable. | 2 / 3 |
Workflow Clarity | Multi-step workflows are clearly sequenced with labeled steps (Prerequisite/Required/Optional), explicit tool ordering, and pitfall warnings at each stage. The setup section includes a verification checkpoint (confirm ACTIVE status before proceeding). The ID resolution pattern serves as a validation checkpoint before destructive operations. | 3 / 3 |
Progressive Disclosure | The content is well-structured with clear sections and a quick reference table, but it's a long monolithic file (~180 lines) with no references to supporting files. The detailed workflow descriptions, common patterns, and quick reference could be split into separate files for better progressive disclosure, though for a standalone skill without bundle files this is acceptable. | 2 / 3 |
Total | 9 / 12 Passed |
Validation
90%Checks the skill against the spec for correct structure and formatting. All validation checks must pass before discovery and implementation can be scored.
Validation — 10 / 11 Passed
Validation for skill structure
| Criteria | Description | Result |
|---|---|---|
frontmatter_unknown_keys | Unknown frontmatter key(s) found; consider removing or moving to metadata | Warning |
Total | 10 / 11 Passed | |
- Repository
- davepoon/buildwithclaude
- Commit
c911a92
- 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.