trello

Manage Trello boards, lists, and cards via the Trello REST API.

Quality

74%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide

Securityby

Passed

No findings from the security scan

Fix and improve this skill with Tessl

tessl review fix ./skills/trello/SKILL.md

Quality

Content

83%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 content is an exemplar of lean, fully executable API guidance — every operation is a ready-to-run curl command with no padding. Its main weaknesses are the absence of any response verification or safety checks around destructive operations (archive, move) and minor duplication between the Usage and Examples sections.

Suggestions

Add verification steps around destructive operations, e.g. check the curl response for the card's name/id before and after archiving or moving, and confirm success before reporting done.

Consolidate the Examples section, which repeats the Usage "List boards" command; keep only genuinely new patterns like the jq select() board-name lookup.

Show how to read and handle Trello API error responses (e.g. pipe through jq and check for error fields) so failures surface instead of being silently swallowed by curl -s.

Dimension	Reasoning	Score
Conciseness	The body is almost entirely lean, executable curl one-liners with headers and minimal prose ("All commands use curl to hit the Trello REST API"), explaining nothing Claude already knows — anchor 5 (lean and efficient; every token earns its place).	5 / 5
Actionability	Every operation is a copy-paste-ready curl command covering the common cases (list boards/lists/cards, create, move, comment, archive), with {id} placeholders explained in Notes — anchor 5 (fully executable, covers common cases).	5 / 5
Workflow Clarity	Operations are clearly organized per task, but the skill includes destructive operations ("Archive a card" via closed=true, and card moves) with no validation or verification steps — curl responses are never checked — so the destructive-operation cap applies and workflow clarity cannot exceed 3; it is not 2 because the per-task sequence and ID discovery guidance are present.	3 / 5
Progressive Disclosure	Sections (Setup, Usage, Notes, Examples) are well-organized and no external references are needed for a skill of this size (no bundle files exist), but the body exceeds 50 lines and the Examples section duplicates Usage's board-listing command — anchor 4 (good structure, minor organization gaps) rather than 5.	4 / 5
	Total	17 / 20 Passed

Description

65%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 concise, names a distinct niche (Trello), and covers the core objects (boards, lists, cards), but it uses the single generic verb "Manage" and lacks any "Use when..." trigger guidance, capping both specificity and completeness. Adding explicit trigger conditions and enumerating the concrete actions would lift it substantially.

Suggestions

Add an explicit trigger clause, e.g. "Use when the user mentions Trello, boards, kanban cards, or asks to move/comment on/archive cards."

Replace the generic verb "Manage" with the specific actions the skill supports, e.g. "Create, move, comment on, and archive Trello cards; list boards, lists, and cards via the Trello REST API."

Include natural synonyms users might say, such as "kanban" or "checklist", to broaden trigger-term coverage.

Dimension	Reasoning	Score
Specificity	"Manage Trello boards, lists, and cards" names the domain and three concrete objects, but "Manage" is a single generic verb — matching anchor 3 (domain plus limited concrete actions), not anchor 4, which requires several specific actions such as create, move, comment, or archive.	3 / 5
Completeness	The "what" is clear ("Manage Trello boards, lists, and cards via the Trello REST API"), but there is no "Use when..." clause or equivalent explicit trigger guidance, which per the judging guidelines caps completeness at 3; it is not 2 because the "what" is concrete rather than vague.	3 / 5
Trigger Term Quality	"Trello", "boards", "lists", and "cards" are natural terms users would say, giving good keyword coverage, but common synonyms like "kanban", "checklist", or "comment" are missing — anchor 4, not 5.	4 / 5
Distinctiveness Conflict Risk	"Trello" names a clear niche with distinct triggers, so it is unlikely to fire for the wrong skill — matching anchor 5 (clear niche, minimal conflict risk).	5 / 5
	Total	15 / 20 Passed

Validation

81%

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

Validation for skill structure

Criteria	Description	Result
metadata_version	'metadata.version' is missing	Warning
metadata_field	'metadata' should map string keys to string values	Warning
frontmatter_unknown_keys	Unknown frontmatter key(s) found; consider removing or moving to metadata	Warning

	Total	13 / 16 Passed

Repository: Bitterbot-AI/bitterbot-desktop
Path: skills/trello/SKILL.md
Commit: 1c7dc1b

Reviewed: 20 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.