CtrlK
BlogDocsLog inGet started
Tessl Logo

trello-automation

Automate Trello boards, cards, and workflows via Rube MCP (Composio). Create cards, manage lists, assign members, and search across boards programmatically.

73

1.73x
Quality

65%

Does it follow best practices?

Impact

85%

1.73x

Average score across 3 eval scenarios

SecuritybySnyk

Advisory

Suggest reviewing before use

Optimize this skill with Tessl

npx tessl skill review --optimize ./plugins/all-skills/skills/trello-automation/SKILL.md
SKILL.md
Quality
Evals
Security

Quality

Content

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 solid, well-organized skill for Trello automation that provides clear workflow sequences with good annotations (Prerequisite/Required/Optional) and practical pitfall warnings. Its main weaknesses are the lack of concrete executable examples (actual API call payloads/responses) and some redundancy between per-workflow pitfalls and the consolidated Known Pitfalls section. The content would benefit from progressive disclosure via bundle files to reduce the monolithic length.

Suggestions

Add concrete input/output examples for at least one workflow (e.g., show an actual TRELLO_ADD_CARDS call with sample parameters and the expected response structure including the nested data.data pattern).

Remove the 'Known Pitfalls' summary section or the per-workflow pitfalls to eliminate redundancy — keeping one or the other would save ~15 lines of duplicated content.

Consider splitting detailed workflow descriptions into a separate WORKFLOWS.md file, keeping SKILL.md as a concise overview with the quick reference table and links to details.

DimensionReasoningScore

Conciseness

The skill is reasonably efficient but has some redundancy — the 'Known Pitfalls' section repeats pitfalls already stated in individual workflow sections, and the Quick Reference table partially duplicates information from the workflows. Some sections could be tightened, but overall it respects Claude's intelligence and doesn't over-explain basic concepts.

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 examples showing actual API calls with sample payloads and responses. The guidance is specific but not copy-paste executable — it's more like structured documentation than runnable instructions.

2 / 3

Workflow Clarity

Multi-step workflows are clearly sequenced with labeled steps (Prerequisite/Required/Optional annotations), 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 useful quick reference table, but it's a long monolithic file (~180 lines of content) with no bundle files to offload detailed workflow descriptions or reference material. The six detailed workflows could benefit from being split into separate files with the SKILL.md serving as an overview with links.

2 / 3

Total

9

/

12

Passed

Description

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 due to the Trello product name and integration details. However, it lacks an explicit 'Use when...' clause, which is important for Claude to know when to select this skill, and could benefit from more natural user-facing trigger terms beyond the technical integration name.

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 board', 'task management', 'move cards between lists', 'add labels', or 'set due dates'.

DimensionReasoningScore

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 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 card', 'add label', 'due date'. The mention of 'Rube MCP (Composio)' is technical jargon unlikely to be used by end users.

2 / 3

Distinctiveness Conflict Risk

The description is clearly scoped to Trello via a specific integration (Rube MCP/Composio), making it highly distinctive and unlikely to conflict with other skills. 'Trello' is a very specific product name.

3 / 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.

Validation10 / 11 Passed

Validation for skill structure

CriteriaDescriptionResult

frontmatter_unknown_keys

Unknown frontmatter key(s) found; consider removing or moving to metadata

Warning

Total

10

/

11

Passed

Repository
davepoon/buildwithclaude
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.