trello

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

Quality

63%

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

Fix and improve this skill with Tessl

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

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 body is highly actionable — seven executable curl commands covering the core Trello operations — and well organized into Setup/Usage/Notes/Examples. Its weaknesses are the redundant Examples section and the irrelevant 'PilotDeck Migration Note' process metadata, plus the absence of verification steps around the destructive move/archive operations.

Suggestions

Delete the 'PilotDeck Migration Note' section — it contains local temp paths and review-process metadata that have no value when executing the skill.

Merge the Examples section into Usage (or replace duplicated commands with genuinely new examples like searching cards or adding labels/checklists) to remove redundancy.

Add verification around destructive operations, e.g. 'Run the list-cards command to confirm the card ID before moving or archiving, and check the JSON response confirms the change.'

Dimension	Reasoning	Score
Conciseness	The Usage section is lean copy-paste curl with no padding, but the Examples section repeats commands already shown in Usage (get boards, get cards on a board) and the 'PilotDeck Migration Note' section is process metadata (local temp paths, review status) irrelevant to executing the skill — more than just minor trimming needed.	3 / 5
Actionability	All seven curl commands are fully executable and copy-paste ready with the auth mechanism shown, and they cover the common cases (list boards/lists/cards, create, move, comment, archive) using conventional {boardId}/{listId}/{cardId} placeholders.	5 / 5
Workflow Clarity	Setup → discovery → mutation steps are sequenced and unambiguous, but destructive operations (move card, archive card) lack any validation or verification step (e.g. confirm the card ID or check the response before archiving), which caps workflow clarity at 3 per the scoring notes.	3 / 5
Progressive Disclosure	No bundle files exist so all needed content is inline in clearly headed sections, and the frontmatter homepage link signals the external API reference; minor gaps (the Usage/Examples duplication and the skill exceeding the ~50-line simple-skill threshold) keep it below 5.	4 / 5
	Total	15 / 20 Passed

Description

57%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 and unambiguous about its domain, with strong distinctiveness from the product name, but it uses one generic verb ("Manage") instead of concrete capabilities and entirely lacks a "when to use this" trigger clause. Adding explicit actions and a "Use when..." clause would lift it substantially.

Suggestions

Add a 'Use when...' clause, e.g. "Use when the user mentions Trello, kanban boards, or asks to create, move, or organize cards."

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

Include common user phrasings/synonyms such as 'kanban board', 'add a card', or 'move a card to done' to broaden trigger coverage.

Dimension	Reasoning	Score
Specificity	"Manage Trello boards, lists, and cards via the Trello REST API" names the domain and objects but relies on a single generic verb ("Manage") rather than naming concrete actions like create, move, or archive, matching the anchor for domain plus 1-2 actions that are not comprehensive.	3 / 5
Completeness	The "what" is clear (manage Trello boards, lists, cards via the REST API) but there is no "Use when..." clause or equivalent trigger guidance, which caps completeness at 3 per the judging guidelines.	3 / 5
Trigger Term Quality	"Trello", "boards", "lists", and "cards" are natural terms a user would say, but common variations and synonyms such as "kanban", "move a card", or "add a comment" are missing.	3 / 5
Distinctiveness Conflict Risk	"Trello" is a precise product name establishing a clear niche with distinct triggers; there is minimal risk of this description firing for an unrelated skill.	5 / 5
	Total	14 / 20 Passed

Validation

93%

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

Validation for skill structure

Criteria	Description	Result
frontmatter_unknown_keys	Unknown frontmatter key(s) found; consider removing or moving to metadata	Warning

	Total	15 / 16 Passed

Repository: OpenBMB/PilotDeck
Path: skills/trello/SKILL.md
Commit: 66bfd09

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.