trello-automation
Automate Trello boards, cards, and workflows via Rube MCP (Composio). Create cards, manage lists, assign members, and search across boards programmatically.
78
72%
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 distinguishable from other skills due to its Trello focus. However, it lacks an explicit 'Use when...' clause, which is important for Claude to know when to select this skill. The trigger terms could also be expanded to cover more natural user language.
Suggestions
Add an explicit 'Use when...' clause, e.g., 'Use when the user asks about Trello boards, managing tasks in Trello, or automating Trello workflows.'
Include additional natural trigger terms users might say, such as 'kanban', 'task board', 'move cards', 'labels', 'due dates', or 'checklists'.
| 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 at 2 per the rubric guidelines. | 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 cards', 'due dates', 'labels', or 'checklists'. 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'. The mention of the specific integration (Rube MCP/Composio) further distinguishes it from generic task management 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 that provides clear tool sequences, specific parameter requirements, and practical pitfall warnings for Trello automation. Its main weakness is length—there's redundancy between per-workflow pitfalls and the consolidated 'Known Pitfalls' section, and the document could benefit from splitting detailed workflows into a separate file. Overall it's well-crafted for guiding Claude through Trello operations with minimal ambiguity.
Suggestions
Remove the 'Known Pitfalls' summary section since all its points are already covered in individual workflow pitfalls, or consolidate pitfalls only in the summary and remove per-workflow duplicates.
Consider moving detailed workflow descriptions (sections 1-6) into a separate WORKFLOWS.md file, keeping SKILL.md as a concise overview with the Quick Reference table and links to detailed workflows.
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The skill is fairly well-organized but has some redundancy—the 'Known Pitfalls' section largely repeats pitfalls already listed under individual workflows. The Quick Reference table also duplicates information. Some trimming would improve token efficiency, though it mostly avoids explaining concepts Claude already knows. | 2 / 3 |
Actionability | Provides specific tool names, exact parameter names and formats (e.g., '24-char hex ID', 'idMember=me'), clear tool sequences for each workflow, and concrete pitfalls with workarounds. The guidance is specific enough to be directly executable without guesswork. | 3 / 3 |
Workflow Clarity | Each workflow has a clearly sequenced tool chain with labeled steps (Prerequisite/Required/Optional), explicit parameter requirements, and pitfall warnings that serve as validation checkpoints. The setup section includes a verification step before proceeding. The ID resolution pattern enforces a validate-before-act approach. | 3 / 3 |
Progressive Disclosure | The content is well-structured with clear sections and a quick reference table, but it's quite long (~170 lines of substantive content) and could benefit from splitting detailed workflow descriptions into a separate reference file. Everything is inline in a single document with only an external link to Composio docs. | 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 | |
- Repository
- davepoon/buildwithclaude
- Commit
7cc63f3
- 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.