trello-automation

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

1.73x

Quality

65%

Does it follow best practices?

Impact

85%

1.73x

Average score across 3 eval scenarios

Securityby

Low

Low-risk findings worth noting

Fix and improve this skill with Tessl

tessl review fix ./plugins/all-skills/skills/trello-automation/SKILL.md

Quality

Content

61%Weight 40%Scale 1-5

Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.

The content is highly actionable and well-structured for an MCP-tooling skill, with concrete tool slugs and parameters throughout, but redundancy across pitfalls sections and missing validation feedback loops for destructive operations hold conciseness and workflow clarity at the midpoint.

Suggestions

Add explicit validate-then-retry checkpoints to destructive workflows (e.g., confirm a card by name before irreversible attachment deletion or before member-list updates).

De-duplicate the 'Known Pitfalls' section against the per-workflow Pitfalls, or have workflows link up to a single canonical pitfall list.

Consider splitting the full per-tool reference into a separate REFERENCE.md and keeping SKILL.md as an overview to improve progressive disclosure.

Dimension	Reasoning	Score
Conciseness	The body assumes Claude's intelligence and avoids explaining basic concepts, but the 'Known Pitfalls' section largely repeats per-workflow pitfalls already stated, and the Quick Reference table re-lists tool slugs, adding redundancy that could be tightened.	3 / 5
Actionability	Concrete MCP tool slugs, parameter names with explicit formats (24-char hex idList, ISO 8601 due) and per-task pitfalls give mostly executable guidance, though no full example request payloads are provided, leaving minor gaps.	4 / 5
Workflow Clarity	Each of the 6 workflows has a clear numbered tool sequence with Prerequisite/Required/Optional tags, but destructive/batch operations (irreversible attachment deletion, member-list replacement) lack explicit validate-then-retry feedback loops, so per the rubric cap workflow clarity is held at 3.	3 / 5
Progressive Disclosure	Content is well organized with clear headers, per-workflow sections, and a navigable Quick Reference table, but everything lives in a single ~180-line file with no split-out reference for the detailed API surface, leaving minor organization gaps.	4 / 5
	Total	14 / 20 Passed

Description

70%Weight 40%Scale 1-5

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 is specific and well-targeted to a clear Trello niche with strong, natural trigger terms, but it lacks any explicit 'when to use' guidance, which caps its completeness at 3.

Suggestions

Add an explicit 'Use when...' clause, e.g. 'Use when the user wants to manage Trello boards, cards, lists, or team assignments.'

Consider mentioning a couple more common actions (comments, attachments, checklists) to close the coverage gap toward a 5 on specificity.

Include a synonym like 'tasks' alongside 'cards' to broaden natural trigger coverage.

Dimension	Reasoning	Score
Specificity	Lists several concrete actions — 'Create cards, manage lists, assign members, and search across boards' — but omits other Trello capabilities (comments, attachments, checklists, moving cards), leaving minor coverage gaps that keep it just below a 5.	4 / 5
Completeness	The 'what' is clear (automate Trello boards/cards/workflows via Rube MCP), but there is no explicit 'Use when...' trigger clause, so per the rubric completeness is capped at 3.	3 / 5
Trigger Term Quality	Natural user-facing terms like 'Trello boards', 'cards', 'lists', 'assign members', and 'search across boards' map to phrases users actually say, though synonyms such as 'tasks' and a few variations are missing.	4 / 5
Distinctiveness Conflict Risk	The Trello-specific niche plus the explicit 'via Rube MCP (Composio)' qualifier make it clearly distinct with minimal risk of triggering for an unrelated skill.	5 / 5
	Total	16 / 20 Passed

Validation

93%

Warnings & errors only

Checks the skill against the spec for correct structure and formatting. All validation checks must pass before discovery and implementation can be scored.

Validation — 15 / 16 Passed

Validation for skill structure

Criteria	Description	Result
frontmatter_unknown_keys	Unknown frontmatter key(s) found; consider removing or moving to metadata	Warning

	Total	15 / 16 Passed

Repository: davepoon/buildwithclaude
Path: plugins/all-skills/skills/trello-automation/SKILL.md
Commit: a9fa86d

Reviewed: about 20 hours ago

Table of Contents

Discovery Implementation Validation

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.