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

—

Does it follow best practices?

Impact

85%

1.73x

Average score across 3 eval scenarios

Securityby

Advisory

Suggest reviewing before use

Quality

Content

65%

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 with exact tool slugs and parameters and clear workflow sequencing, but it is held back by duplicated pitfall content, missing validation feedback loops for destructive operations, and a monolithic structure with no progressive disclosure to separate reference files.

Suggestions

Consolidate pitfalls into one location and have per-workflow sections reference it, removing the duplication across "Known Pitfalls" and the "Quick Reference" table.

Add explicit validation checkpoints for destructive operations (e.g., confirm member list before calling UPDATE_CARDS_ID_MEMBERS; confirm before irreversible attachment deletion).

Split the detailed "Quick Reference" table and exhaustive pitfall catalog into a separate REFERENCE.md referenced from SKILL.md to apply progressive disclosure.

Dimension	Reasoning	Score
Conciseness	The body is lean and operational (no basic-concept explanations), but pitfalls are duplicated across per-workflow sections, the consolidated "Known Pitfalls" section, and the "Quick Reference" table, so it could be tightened; not a 3 due to this redundancy.	2 / 3
Actionability	Concrete tool slugs (e.g., TRELLO_ADD_CARDS) and precise parameters (idList as 24-char hex, idMember='me', filter='open') give copy-paste-ready guidance, satisfying the instruction-skill bar for actionability.	3 / 3
Workflow Clarity	Workflows are clearly sequenced with [Prerequisite]/[Required]/[Optional] markers, but destructive operations (irreversible attachment deletion, member-list replacement) lack explicit validate→fix→retry feedback loops, capping clarity at 2.	2 / 3
Progressive Disclosure	Headers are well-organized, but the ~177-line body is a monolithic single file with no split-out reference files or one-level-deep pointers, so content that could be separate stays inline; not a 1 because navigation via sections is clear.	2 / 3
	Total	9 / 12 Passed

Description

82%

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, distinct, and rich in natural Trello trigger terms, but it omits an explicit "Use when..." clause, so it answers "what" well without explicitly answering "when".

Suggestions

Add an explicit "Use when..." clause naming common user phrasings (e.g., "Use when the user wants to create Trello cards, move cards between lists, assign members, or search across boards").

Include a few more natural user phrasings (e.g., "add a card", "move a card", "Trello board") to broaden trigger coverage.

Dimension	Reasoning	Score
Specificity	"Create cards, manage lists, assign members, and search across boards" lists multiple specific concrete actions, matching the level-3 anchor rather than the partial level-2 example.	3 / 3
Completeness	It clearly states what the skill does but lacks any "Use when..." clause or equivalent explicit trigger guidance, which caps completeness at 2 per the guidelines; not a 1 because the "what" is explicit and strong.	2 / 3
Trigger Term Quality	Natural Trello vocabulary users would actually say (boards, cards, lists, members, search) appears with good coverage, not just technical jargon.	3 / 3
Distinctiveness Conflict Risk	"Automate Trello boards, cards, and workflows via Rube MCP (Composio)" carves out a distinct Trello-only niche unlikely to trigger for unrelated skills.	3 / 3
	Total	11 / 12 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
Commit: 366e45b

Reviewed: about 21 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.