trello-automation
Automate Trello boards, cards, and workflows via Rube MCP (Composio). Create cards, manage lists, assign members, and search across boards programmatically.
Install with Tessl CLI
npx tessl i github:davepoon/buildwithclaude --skill trello-automation78
Quality
72%
Does it follow best practices?
Impact
85%
1.73xAverage score across 3 eval scenarios
Optimize this skill with Tessl
npx tessl skill review --optimize ./plugins/all-skills/skills/trello-automation/SKILL.mdDiscovery
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 effectively communicates specific Trello automation capabilities with good distinctiveness through explicit platform naming. However, it lacks an explicit 'Use when...' clause which limits Claude's ability to know exactly when to select this skill, and could benefit from additional natural trigger terms users might employ when requesting Trello help.
Suggestions
Add a 'Use when...' clause with trigger phrases like 'Use when the user asks about Trello, kanban boards, or wants to automate task management workflows.'
Include additional natural trigger terms users might say: 'kanban', 'task board', 'project tracking', 'move cards between lists', 'due dates'.
| Dimension | Reasoning | Score |
|---|---|---|
Specificity | Lists multiple specific concrete actions: 'Create cards, manage lists, assign members, and search across boards programmatically.' These are clear, actionable capabilities. | 3 / 3 |
Completeness | Clearly answers 'what' with specific actions but lacks an explicit 'Use when...' clause or equivalent trigger guidance. The 'when' is only implied through the domain context. | 2 / 3 |
Trigger Term Quality | Includes relevant keywords like 'Trello', 'boards', 'cards', 'lists', 'members' but misses common variations users might say like 'kanban', 'task board', 'project management', or 'move card'. | 2 / 3 |
Distinctiveness Conflict Risk | Clearly scoped to Trello specifically with distinct triggers like 'Trello boards', 'cards', and mentions the specific integration (Rube MCP/Composio). Unlikely to conflict with other project management or automation skills. | 3 / 3 |
Total | 10 / 12 Passed |
Implementation
77%Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.
This is a strong, actionable skill with excellent workflow clarity and specific tool sequences. The main weakness is length - the document could be more concise by eliminating redundancy between the Known Pitfalls summary and individual workflow pitfalls, and by potentially splitting detailed workflows into separate files for better progressive disclosure.
Suggestions
Remove the 'Known Pitfalls' section since all pitfalls are already documented in their respective workflows, or consolidate pitfalls only in the summary section
Consider moving detailed workflow sequences (sections 1-6) to a separate WORKFLOWS.md file, keeping only the Quick Reference table and Common Patterns in the main SKILL.md
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The skill is reasonably efficient but includes some redundancy - the 'Known Pitfalls' section repeats information already covered in individual workflow pitfalls, and some explanations could be tighter. The Quick Reference table adds value but duplicates tool information from workflows. | 2 / 3 |
Actionability | Excellent actionability with specific tool sequences, exact parameter names (idList, idMember='me'), format requirements (24-char hex), and clear step-by-step workflows. Each workflow specifies Required vs Optional steps and includes concrete key parameters. | 3 / 3 |
Workflow Clarity | Clear multi-step sequences with explicit prerequisite/required/optional labeling. Each workflow includes validation context through pitfalls sections that warn about common failure modes. The ID resolution pattern establishes a clear prerequisite workflow for all operations. | 3 / 3 |
Progressive Disclosure | Content is well-organized with clear sections, but the document is quite long (~200 lines) and could benefit from splitting detailed workflows into separate files. The Quick Reference table at the end is good, but advanced patterns like batch operations could be in a separate reference file. | 2 / 3 |
Total | 10 / 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 | |
- 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.