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

80%

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 lean and highly actionable, packed with copy-paste-ready curl commands and a clear setup sequence. Its main gaps are the absence of verification steps around destructive card operations and an inline reference-style section that could be split out for cleaner progressive disclosure.

Suggestions

Add a verification step after mutating operations (e.g. re-list the list's cards after creating/moving/archiving to confirm the change).

Move the Examples/API-reference block into a separate referenced file and keep SKILL.md as a tighter overview, or trim it to stay under ~50 lines.

Add a brief confirmation note before the destructive archive operation (e.g. confirm the card ID by listing first).

Dimension	Reasoning	Score
Conciseness	The body is almost entirely lean, executable curl snippets with one-line intros and no explanation of concepts Claude already knows (e.g. what Trello or curl is), matching the 'lean and efficient; every token earns its place' anchor.	3 / 3
Actionability	Every section is a complete, copy-paste-ready curl command with auth params, real flags, and HTTP verbs filled in, matching the 'fully executable code/commands; copy-paste ready' anchor.	3 / 3
Workflow Clarity	Setup is a clear numbered sequence and commands are well ordered, but mutating/destructive operations (create, move, archive card) lack any verification step, which per the rubric caps workflow clarity at 2.	2 / 3
Progressive Disclosure	Content is well sectioned (Setup, Usage, Notes, Examples) with no nested references, but the body exceeds 50 lines and the reference-style bulk (e.g. the Examples/API block) is inline rather than split into one-level-deep reference files.	2 / 3
	Total	10 / 12 Passed

Description

57%

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 clearly identifies the Trello-specific domain and is highly distinctive, but it relies on the generic verb 'Manage' and omits any explicit 'when to use' trigger guidance. Adding concrete action verbs and a Use-when clause would raise specificity and completeness.

Suggestions

Replace or expand the generic verb 'Manage' with concrete actions (e.g. 'Create, move, comment on, and archive Trello cards; list boards and lists via the Trello REST API').

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

Broaden trigger coverage with common variations users say, such as 'Trello board', 'Trello card', and 'kanban'.

Dimension	Reasoning	Score
Specificity	Names the domain and concrete objects ('Trello boards, lists, and cards') but uses the single generic verb 'Manage' rather than enumerating specific actions, matching the 'names domain and some actions, but not comprehensive' anchor.	2 / 3
Completeness	Clearly states what the skill does, but provides no 'Use when...' clause or equivalent trigger guidance, which per the rubric caps completeness at 2.	2 / 3
Trigger Term Quality	Includes natural terms a user would say ('Trello', 'boards, lists, and cards') but lacks common variations (e.g. 'Trello board', 'kanban'), matching the 'some relevant keywords but missing common variations' anchor.	2 / 3
Distinctiveness Conflict Risk	Targets a specific named product ('Trello') with a distinct niche via its REST API, making it clearly distinguishable and unlikely to trigger for the wrong skill.	3 / 3
	Total	9 / 12 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: e73c717

Reviewed: about 15 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.