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

63%

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

57%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.

A dense, well-structured operational guide with concrete tool sequences and genuinely useful pitfalls, held back by verbatim duplication between workflow sections and 'Known Pitfalls', missing validation checkpoints around destructive/batch operations, and no use of reference files to move the API detail out of SKILL.md.

Suggestions

Remove the duplicated 'Known Pitfalls' entries that already appear in workflow 'Pitfalls' blocks (IDs vs names, search delays, nested responses, rate limit), keeping a single canonical list.

Add validation steps before destructive or batch operations — e.g. verify card name and destination list before TRELLO_UPDATE_CARDS_BY_ID_CARD, and confirm before irreversible attachment deletion or member-list replacement.

Move the Quick Reference table and per-tool parameter detail into a references/ file (e.g. references/tool-reference.md) linked from SKILL.md, keeping the body to workflows and common patterns.

Dimension	Reasoning	Score
Conciseness	Line-by-line the body is lean (tool sequences, key params, pitfalls), but the 'Known Pitfalls' section restates pitfalls already given verbatim in workflow sections (ID requirements, search delays, nested responses, and the 300 req/10s limit stated twice) and the Quick Reference table re-lists the same params — fitting 'mostly efficient but could be tightened' rather than the minor-trim level of 4.	3 / 5
Actionability	Concrete, executable guidance throughout: exact tool slugs (e.g. TRELLO_ADD_CARDS), ordered sequences tagged [Prerequisite]/[Required]/[Optional], and precise parameter formats ("24-char hex ID (NOT list name)", "ISO 8601 format"). It falls short of 5 only because no example argument payloads are shown, relying on runtime schemas from RUBE_SEARCH_TOOLS.	4 / 5
Workflow Clarity	Each workflow has a clear sequence with per-step role tags and a 'When to use' clause, but operations that are destructive or batch-shaped — irreversible attachment deletion, UPDATE_CARDS_ID_MEMBERS replacing the member list, one API call per checklist item with rate-limit risk — lack validation/verification checkpoints, capping workflow clarity at 3 per the rubric.	3 / 5
Progressive Disclosure	The skill is a single ~180-line file with clear section headers but no reference files at all; the per-tool parameter details, pitfalls, and Quick Reference table are exactly the API-reference bulk the anchor-3 example says could live in a separate file. Structure is good, but the content split is not exploited — it is not a 2 because sections are well-organized and navigable.	3 / 5
	Total	13 / 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.

A specific, well-scoped description with concrete named actions and natural Trello vocabulary. Its main weakness is the missing 'when to use' trigger clause, which caps completeness; adding a 'Use when...' sentence naming common user requests would lift it into the top tier.

Suggestions

Add an explicit trigger clause, e.g. 'Use when the user mentions Trello, kanban boards, cards, or wants to create/assign/track tasks on a board.'

Broaden capability and trigger coverage to include comments, attachments, checklists, and moving cards between lists, which the body supports but the description omits.

Consider a natural synonym such as 'kanban' or 'task board' so users who don't say 'Trello' verbatim still trigger the skill.

Dimension	Reasoning	Score
Specificity	"Create cards, manage lists, assign members, and search across boards" lists several specific concrete actions, matching the 'several specific actions; minor gaps in coverage' anchor — comments, attachments, checklists, and card moves are absent, keeping it below the comprehensive 5.	4 / 5
Completeness	The 'what' is clearly stated (automate Trello boards/cards/workflows via Rube MCP with named actions) but there is no 'Use when...' clause or equivalent explicit trigger guidance, which caps completeness at 3; it is not a 2 because the 'what' is concrete, not vague.	3 / 5
Trigger Term Quality	Natural keywords like "Trello", "boards", "cards", "assign members", and "search" match what users would say, but common variations such as "kanban", "move cards", "checklists", and "comments" are missing, fitting the 'good keyword coverage; a few natural terms missing' anchor rather than comprehensive coverage.	4 / 5
Distinctiveness Conflict Risk	The description is tightly scoped to "Trello boards, cards, and workflows via Rube MCP (Composio)" — a clear niche with distinct triggers (Trello-specific vocabulary) and minimal conflict risk with other skills.	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: c9856ea

Reviewed: 6 days 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.