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 of specifying concrete Trello actions and is clearly distinctive due to the Trello + Rube MCP scope. However, it lacks an explicit 'Use when...' clause, which is important for Claude to know when to select this skill, and could benefit from broader trigger term coverage.
Suggestions
Add an explicit 'Use when...' clause, e.g., 'Use when the user asks about Trello boards, managing Trello cards, automating Trello workflows, or interacting with Trello via API.'
Include additional natural trigger terms users might say, such as 'move card', 'add label', 'checklist', 'due date', 'Trello automation', or 'Trello API'.
| 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, which caps this dimension at 2 per the rubric. | 2 / 3 |
Trigger Term Quality | Includes good natural keywords like 'Trello', 'boards', 'cards', 'lists', 'members', but misses common user variations like 'move card', 'add label', 'due date', 'checklist', or mentioning Trello-specific terms users might say. | 2 / 3 |
Distinctiveness Conflict Risk | Clearly scoped to Trello via Rube MCP (Composio), which is a very specific niche. The mention of 'Trello' and the specific integration tool makes it highly unlikely to conflict with other skills. | 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-organized skill with clear workflow sequences, good pitfall documentation, and specific tool/parameter references for Trello automation. Its main weaknesses are the lack of concrete executable examples (actual MCP call payloads or response parsing code) and some redundancy between the per-workflow pitfalls and the consolidated Known Pitfalls section. The content would benefit from example inputs/outputs and splitting detailed reference material into supporting files.
Suggestions
Add at least one concrete example showing an actual MCP tool call with input parameters and a sample response, demonstrating how to parse nested response data (e.g., extracting idCard from a TRELLO_ADD_CARDS response).
Remove or consolidate the 'Known Pitfalls' section since its content is already covered in per-workflow pitfall blocks—this would save ~15 lines of redundant tokens.
Consider extracting the Quick Reference table and detailed workflow descriptions into a separate REFERENCE.md file, keeping SKILL.md as a concise overview with links to details.
| 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 tightening is possible, though most content earns its place. | 2 / 3 |
Actionability | Provides specific tool names, parameter names, and clear tool sequences, which is good. However, there are no executable code snippets or concrete example payloads/responses—everything is described at the tool-name level without showing actual MCP call syntax or example JSON inputs/outputs, making it less than fully copy-paste ready. | 2 / 3 |
Workflow Clarity | Multi-step workflows are clearly sequenced with labeled steps (Prerequisite/Required/Optional), explicit 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 for all workflows. | 3 / 3 |
Progressive Disclosure | The content is well-structured with clear sections and a quick reference table, but it's a long monolithic document (~180 lines of dense content) with no references to supporting files. The repeated pitfalls and the detailed workflow descriptions could benefit from being split into separate reference files, especially given no bundle files exist. | 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
d065ead
- 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.