trello

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

Quality

68%

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

76%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 body provides fully executable, copy-paste-ready curl commands across the common Trello operations with lean prose, but lacks validation checkpoints for its state-changing operations and carries minor redundancy between Usage and Examples.

Suggestions

Add a verification step after state-changing operations, e.g. re-fetch the card to confirm it moved or archived, to establish a feedback loop.

Consolidate the Examples section with Usage or convert it to distinct advanced queries to remove the duplicated list-boards / board-cards commands.

Note how to obtain boardId/listId/cardId from Trello URLs inline at first use rather than only in the Notes section.

Dimension	Reasoning	Score
Conciseness	The body is lean and assumes Claude knows curl/jq with no concept over-explanation; it stops short of 5 because the Examples section repeats the list-boards and board-cards commands already shown in Usage, a minor redundancy that could be trimmed.	4 / 5
Actionability	Every operation ships as a complete, copy-paste-ready curl command with jq parsing, and the seven examples cover the common cases (list boards/lists/cards, create, move, comment, archive).	5 / 5
Workflow Clarity	Setup is sequenced but the state-changing operations (create, move, archive) lack any validation or verification checkpoint, and the rubric caps workflow clarity at 3 for destructive/batch operations without feedback loops.	3 / 5
Progressive Disclosure	Sections are well-organized (Setup, Usage, Notes, Examples) with no nested references needed; it is not a 5 because the body exceeds 50 lines and the Examples section duplicates Usage content rather than splitting material.	4 / 5
	Total	16 / 20 Passed

Description

60%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 names a distinct Trello niche with natural trigger terms but relies on the generic verb 'Manage' and omits any 'Use when' trigger guidance, capping completeness and specificity.

Suggestions

Replace the generic 'Manage' with concrete actions, e.g. 'Create, move, archive, and comment on Trello boards, lists, and cards'.

Add an explicit trigger clause such as 'Use when the user asks to manage Trello boards, lists, or cards'.

Drop or de-emphasize 'via the Trello REST API' technical jargon in favor of user-facing terms.

Dimension	Reasoning	Score
Specificity	The description names the domain ('Trello boards, lists, and cards') but the only action verb is the generic 'Manage', with no concrete operations (create, move, archive) listed, matching the 'names the domain but actions are minimal or generic' anchor.	2 / 5
Completeness	It clearly states what the skill does but has no 'Use when...' trigger clause, and the rubric caps completeness at 3 when explicit trigger guidance is missing.	3 / 5
Trigger Term Quality	'Trello boards, lists, and cards' are exactly the natural terms users say, giving good keyword coverage; it falls short of 5 only because synonyms and file extensions are absent and 'via the Trello REST API' adds technical jargon.	4 / 5
Distinctiveness Conflict Risk	'Trello' is a clear niche with board/list/card triggers that are unique to Trello, giving minimal conflict risk with other skills.	5 / 5
	Total	14 / 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: 017761f

Reviewed: 2 days 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.