trello

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

1.09x

Quality

63%

Does it follow best practices?

Impact

93%

1.09x

Average score across 3 eval scenarios

Securityby

Low

Low-risk findings worth noting

Fix and improve this skill with Tessl

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

The canonical home for this skill is trello in openclaw/openclaw

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 delivers lean, concrete, copy-paste-ready curl recipes for the common Trello operations with a sensible setup section, and it is well organized without external files. The main weaknesses are the absence of any response verification for destructive operations and a somewhat duplicative Examples section that pushes length past what a simple skill needs.

Suggestions

Add a verification step for destructive operations (move/archive), e.g. check the curl response with jq or re-fetch the card to confirm the change took effect.

Trim or differentiate the "Examples" section, which repeats the boards-listing command from "Usage", to cut token cost and tighten the body.

Show how to resolve the {boardId}/{listId}/{cardId} placeholders with a concrete end-to-end example (e.g. find board by name, extract its id, then create a card in its list).

Dimension	Reasoning	Score
Conciseness	The body is lean — concrete curl commands with no concept explanations or padding — but the "Examples" section partially duplicates commands already shown in "Usage" (e.g. the boards listing), which could be trimmed.	4 / 5
Actionability	The curl commands are concrete and near copy-paste ready with real endpoints and jq filters, but the {boardId}/{listId}/{cardId} placeholders are not executable as-is and the Notes only loosely explain how to resolve them, so this is 'mostly executable with minor gaps'.	4 / 5
Workflow Clarity	Setup is a clear 1-2-3 sequence and each operation is a single unambiguous command, but destructive operations (move card, archive card) have no verification of the API response before or after, which per the judging guidelines caps workflow clarity at 3.	3 / 5
Progressive Disclosure	Sections are well organized (Setup, Usage, Notes, Examples) with no unnecessary inlining and no external reference files needed, but the body runs ~85 lines (above the under-50 simple-skill guideline) with a partially duplicative Examples section, leaving minor organization gaps.	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, names a distinct niche, and clearly states what the skill does, but it relies on the generic verb "Manage" instead of enumerating concrete actions and entirely lacks a 'when to use' trigger clause. Adding a 'Use when...' sentence covering natural phrases users would say would address the biggest gaps.

Suggestions

Add an explicit trigger clause, e.g. "Use when the user mentions Trello, asks to create or move cards, or wants to work with boards, lists, or kanban cards."

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

Include natural synonyms such as "kanban" or "add a card" alongside "boards, lists, and cards" to broaden trigger-term coverage.

Dimension	Reasoning	Score
Specificity	"Manage Trello boards, lists, and cards" names the domain and objects clearly, but "Manage" is a single generic action verb rather than a list of several concrete actions (create/move/comment/archive), so it matches the '1-2 concrete actions, not comprehensive' anchor.	3 / 5
Completeness	The 'what' is clear (manage Trello boards, lists, and cards via the REST API), but there is no 'Use when...' clause or equivalent trigger guidance, which per the judging guidelines caps completeness at 3.	3 / 5
Trigger Term Quality	"Trello", "boards", "lists", and "cards" are terms users naturally say, but common variations like "kanban", "add/create a card", "checklist", or "comment" are missing, matching the 'some relevant keywords but missing common variations' anchor.	3 / 5
Distinctiveness Conflict Risk	"Trello" names a specific external service with distinct triggers (boards, lists, cards), so it occupies a clear niche with minimal risk of firing for the wrong skill.	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: trpc-group/trpc-agent-go
Path: openclaw/skills/trello/SKILL.md
Commit: 9bb1c42

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