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.

60

Quality

71%

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

68%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 skill body is well-structured, actionable, and token-efficient with strong tool sequencing and parameter guidance. Its main gap is the absence of explicit validation/verification steps around destructive and batch operations, which caps workflow clarity.

Suggestions

Add explicit validation checkpoints before irreversible actions — e.g. 'Verify the card name matches before TRELLO_UPDATE_CARDS_BY_ID_CARD' and 'Confirm before deleting attachments (deletion is irreversible)'.

Deduplicate the 'Known Pitfalls' section by linking to the inline pitfalls per workflow, or keep one canonical list and trim the inline copies.

Consider showing one literal MCP tool invocation (tool slug + JSON params) as a copy-paste example to push actionability to fully executable.

DimensionReasoningScore

Conciseness

The body is lean, assumes Claude's competence, and avoids explaining Trello/MCP basics; the only redundancy is the 'Known Pitfalls' section repeating pitfalls already stated inline in each workflow.

4 / 5

Actionability

Concrete tool slugs, exact parameter formats (24-char hex idList, ISO 8601, pos 'top'/'bottom'), and a task→tool→params quick reference make the guidance executable, though literal call/JSON examples are not shown.

4 / 5

Workflow Clarity

Workflows are clearly sequenced with Prerequisite/Required/Optional markers and Setup has a validation checkpoint, but destructive/irreversible operations (attachment deletion, member-list replacement, batch reads) lack explicit validate→fix→retry loops, capping this at 3.

3 / 5

Progressive Disclosure

Well-organized with clear section headers and a navigable Quick Reference table, no nested references, and all content appropriately inline for a self-contained MCP guide; minor room to split the API table into a separate file.

4 / 5

Total

15

/

20

Passed

Description

75%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, distinct, and uses natural Trello trigger terms, but it omits an explicit 'Use when...' trigger clause, which limits completeness. Adding a when-to-use phrase would lift it to the top tier.

Suggestions

Append an explicit 'Use when...' clause, e.g. 'Use when the user wants to automate Trello boards, cards, lists, or member assignments via Rube MCP.'

Consider adding common action terms like 'checklists', 'comments', or 'moving cards' to round out trigger coverage.

DimensionReasoningScore

Specificity

Enumerates multiple concrete actions — 'Create cards, manage lists, assign members, and search across boards' — giving comprehensive coverage of core Trello operations.

5 / 5

Completeness

The 'what' is clear and concrete, but there is no 'Use when...' clause or equivalent explicit trigger guidance, which caps completeness at 3 per the rubric.

3 / 5

Trigger Term Quality

Strong natural keywords ('Trello', 'boards', 'cards', 'lists', 'members') that users would say, but a few common variations ('checklist', 'comments', 'move card') are absent.

4 / 5

Distinctiveness Conflict Risk

Clearly scoped to Trello via Rube MCP (Composio) with distinct triggers; minimal risk of firing for an unrelated skill.

5 / 5

Total

17

/

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