trello-task-management

Create and manage Trello cards, checklists, and boards for kanban workflows. Use when the user says: 'create a kanban board', 'add a task card', 'move card to sprint', or 'track project board'.

Quality

86%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide

Securityby

Low

Low-risk findings worth noting

Quality

Content

86%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 tight, operational SKILL.md body: concrete MCP examples, exact configuration, and clear workflows with almost no waste. It falls just short of top marks on actionability and workflow clarity due to a missing checklist example and no error-recovery guidance when post-update verification fails.

Suggestions

Add one example invocation for `add_checklist_to_card` (or drop checklists from the tool list), since checklists are promised in the description and tool summary but never shown.

Extend the post-update verification into a feedback loop: state what to do when the returned card ID/URL is missing or wrong (e.g., re-fetch the card or report the failure) rather than only 'verify before proceeding'.

Clarify or remove the '(ensure proper auth)' aside on the create/update tools line — auth is already fully specified in the MCP Server table, so the aside adds no actionable information.

Dimension	Reasoning	Score
Conciseness	The body is lean and operational throughout — MCP server table, compact tool list, JSON invocation examples, a naming block, a transition table, and short session-startup steps. Nothing explains concepts Claude already knows, and no section is padded.	5 / 5
Actionability	Concrete, copy-paste-ready JSON invocations are given for create_card, update_card, and add_comment_to_card, plus exact env vars (TRELLO_API_KEY, TRELLO_TOKEN) and the npx spawn command. Minor gaps: add_checklist_to_card is listed but never exemplified despite checklists being advertised in the description, and "(ensure proper auth)" is vague given auth is already fully specified above.	4 / 5
Workflow Clarity	Session Continuity gives a clear numbered sequence (get_boards → get_lists → get_cards_by_list_id for In Progress) and card transitions are tabulated with explicit 'When' conditions. An explicit checkpoint exists ("After each create/update, verify the returned card ID and URL before proceeding"), but there is no error-recovery loop for what to do when that verification fails, which keeps it below the 5 anchor.	4 / 5
Progressive Disclosure	No bundle files exist (no references/, scripts/, or assets/ directories), so nothing is inlined that belongs elsewhere. The body is a single appropriately-sized overview with well-organized sections and one clearly signaled, one-level-deep pointer to project config (`.opencastle/project/trello-config.md`) for environment-specific IDs.	5 / 5
	Total	18 / 20 Passed

Description

87%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 strong description: explicit what-and-when structure with natural, product-specific trigger phrases and minimal conflict risk. Its only weakness is that the capability list relies on the generic verb 'manage' rather than enumerating the individual actions (update, move, comment) the skill actually supports.

Dimension	Reasoning	Score
Specificity	"Create and manage Trello cards, checklists, and boards" names the domain and several concrete objects with two verbs, comparable to 'Extracts text from PDF files, fills forms, converts pages to images'. It stops short of the 5 anchor because 'manage' is generic — update, move, and comment actions from the body are not individually enumerated, leaving minor coverage gaps.	4 / 5
Completeness	It explicitly answers both questions: a clear 'what' ("Create and manage Trello cards, checklists, and boards for kanban workflows") and a concrete 'when' with four literal user trigger phrases, matching the 5 anchor example almost exactly. Both parts are explicit, not implied.	5 / 5
Trigger Term Quality	The quoted triggers ('create a kanban board', 'add a task card', 'move card to sprint', 'track project board') are natural phrases a user would plausibly say, matching the good-example pattern of explicit 'Use when the user says' phrases. A few natural variants are missing (e.g., 'Trello', 'to-do card', 'ticket', 'backlog'), which keeps it at the 4 anchor rather than comprehensive synonym coverage.	4 / 5
Distinctiveness Conflict Risk	Trello/kanban is a clear niche with distinct, product-specific trigger phrases; the description is unlikely to fire for document, generic task-list, or other integration skills, matching the 'clear niche with distinct triggers; minimal conflict risk' anchor.	5 / 5
	Total	18 / 20 Passed

Validation

100%

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 — 16 / 16 Passed

Validation for skill structure

No warnings or errors.

Repository: monkilabs/opencastle
Path: src/orchestrator/plugins/trello/SKILL.md
Commit: c0f4566

Reviewed: 1 day 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.