CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

trello-automation

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

Quality

74%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide
SecuritybySnyk

Low

Low-risk findings worth noting

Fix and improve this skill with Tessl

tessl review fix ./plugins/AI-Agents-Safe-Coding-Skills-claude/skills/trello-automation/SKILL.md

The canonical home for this skill is trello-automation in administrakt0r/AI-Agents-Safe-Coding-Skills

SKILL.md
Quality
Evals
Security

Quality

Content

67%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 strong, highly actionable instruction-only skill: exact MCP tool slugs, parameter formats, ordered workflows with tagged prerequisites, and genuinely useful pitfalls. Its main weaknesses are duplicated material across sections (rate limits, search delays, ID rules stated multiple times), a filler closing section, and no worked example payloads or error-recovery loops.

Suggestions

De-duplicate the repeated guidance: state rate limits, search-index delays, and nested-response parsing once (keep them in "Known Pitfalls" or the relevant workflow, not both), and delete the content-free "When to Use" section.

Add one worked example (e.g., a sample TRELLO_ADD_CARDS request/response and the nested data.data checklist extraction) so guidance is fully copy-paste ready.

Weave validation into the workflows as explicit feedback loops — e.g., "verify card ID and confirm before TRELLO_UPDATE_CARDS_BY_ID_CARD", and a confirm-before-delete step given attachment deletion is irreversible.

DimensionReasoningScore

Conciseness

The body is dense with operationally useful material (tool sequences, parameters, pitfalls) but repeats itself: rate limits appear in both "### Rate Limits" and "Known Pitfalls", search-indexing delays and nested-response parsing are each stated twice, and ID-format rules are given three times. The closing "When to Use" section ("This skill is applicable to execute the workflow or actions described in the overview.") is pure filler. Not 4 because the duplication is noticeable rather than minor; not 2 because there is no explanation of concepts Claude already knows.

3 / 5

Actionability

Concrete, executable guidance throughout: exact tool slugs (e.g., "TRELLO_ADD_CARDS"), parameter names and formats ("idList: 24-char hex ID (NOT list name)", "due: ISO 8601"), ordered sequences tagged [Prerequisite]/[Required]/[Optional], and the smart instruction to fetch current schemas via RUBE_SEARCH_TOOLS first. Not anchor 5 because there are no worked example payloads or a sample call, leaving minor gaps for a copy-paste-ready experience.

4 / 5

Workflow Clarity

Each of the six workflows has a clearly numbered sequence with explicit prerequisite chains and ID-resolution steps, plus real checkpoints: "verify card name before updating", "Confirm connection status shows ACTIVE before running any workflows", and "Store returned id (idCard) immediately". Not 5 because recovery loops are thin (pitfalls are listed but not woven back into the sequences as validate-then-retry steps), and the noted irreversible attachment deletion has no verify-before-acting step; not 3 because most checkpoints are present and explicit.

4 / 5

Progressive Disclosure

No bundle files exist (references/, scripts/, assets/ are all absent), and the ~176-line body is well-organized with clear section headers, a "Common Patterns" section, and a scannable Quick Reference table. Not anchor 5 because the body exceeds the simple-skill threshold and carries reference-style material (the 12-row tool table plus six full workflows) that could be split into one-level-deep reference files; not 3 because structure, signaling, and navigation are good with nothing buried.

4 / 5

Total

15

/

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 a distinct product niche, but it entirely lacks a "Use when..." trigger clause and misses some natural vocabulary (kanban, checklists, comments) that would improve routing. Adding explicit trigger guidance would lift it to top-tier quality.

Suggestions

Append a trigger clause such as: "Use when the user mentions Trello, boards, cards, kanban boards, or wants to create/assign/move cards programmatically."

Add missing natural synonyms and task verbs users would say — "kanban", "checklists", "comments", "move cards between lists" — to broaden trigger coverage.

Mention the comment/attachment capability (or explicitly scope it out) so the description's action list matches the skill body's coverage.

DimensionReasoningScore

Specificity

The description lists four concrete actions — "Create cards, manage lists, assign members, and search across boards" — anchored to a specific domain ("Trello boards, cards, and workflows via Rube MCP (Composio)"). It falls short of anchor 5 because coverage has minor gaps: comments, attachments, checklists, and card moves are supported by the skill but not mentioned.

4 / 5

Completeness

The "what" is clear and specific (automate Trello boards/cards via Rube MCP with named actions), but there is no "Use when..." clause or equivalent explicit trigger guidance — "Automate Trello" only weakly implies when. Per the guideline, a missing 'Use when' clause caps completeness at 3; it is not 2 because the 'what' is concrete and comprehensive.

3 / 5

Trigger Term Quality

Natural terms users would say are present: "Trello", "boards", "cards", "create cards", "assign members", "search". Not anchor 5 because common variations are missing — "kanban", "checklists", "comments", "move cards" — and "workflows" alone is generic; not anchor 3 since core product-specific keywords are well covered.

4 / 5

Distinctiveness Conflict Risk

"Trello" and "Rube MCP (Composio)" name a specific product and integration, giving a clear niche with distinct triggers and minimal risk of firing for an unrelated skill. It is not below 5 because no other plausible skill would trigger on these terms.

5 / 5

Total

16

/

20

Passed

Validation

93%

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

CriteriaDescriptionResult

frontmatter_unknown_keys

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

Warning

Total

15

/

16

Passed

Repository

administrakt0r/AI-Agents-Safe-Coding-Skills

Path

plugins/AI-Agents-Safe-Coding-Skills-claude/skills/trello-automation/SKILL.md

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.