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

Advisory

Suggest reviewing before use

Optimize this skill with Tessl

npx tessl skill review --optimize ./openclaw/skills/trello/SKILL.md

Quality

Discovery

40%

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 identifies a clear niche (Trello API integration) with distinctive terminology, but suffers from vague action language ('manage') and completely lacks trigger guidance. Adding specific actions and a 'Use when...' clause would significantly improve Claude's ability to select this skill appropriately.

Suggestions

Replace 'Manage' with specific actions like 'Create, update, move, and archive Trello boards, lists, and cards'

Add a 'Use when...' clause such as 'Use when the user mentions Trello, kanban boards, task cards, or wants to organize tasks in lists'

Include action-oriented trigger terms users might say: 'add a card', 'create a board', 'move task', 'organize tasks'

Dimension	Reasoning	Score
Specificity	Names the domain (Trello) and mentions three entities (boards, lists, cards) but uses vague 'manage' rather than listing concrete actions like 'create cards', 'move lists', 'archive boards'.	2 / 3
Completeness	Describes what it does (manage Trello entities) but completely lacks a 'Use when...' clause or any explicit trigger guidance for when Claude should select this skill.	1 / 3
Trigger Term Quality	Includes 'Trello', 'boards', 'lists', 'cards' which are relevant keywords, but misses common variations users might say like 'kanban', 'task board', 'add a card', or action-oriented terms.	2 / 3
Distinctiveness Conflict Risk	Trello is a specific product name with distinct terminology (boards, lists, cards), making it unlikely to conflict with other skills. The Trello REST API reference further narrows the scope.	3 / 3
	Total	8 / 12 Passed

Implementation

87%

Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.

This is a well-crafted API skill that provides concise, executable curl commands for common Trello operations. The setup is clear and all examples are copy-paste ready. The main weakness is the lack of explicit workflow guidance for chaining operations and missing verification steps for destructive actions like archiving.

Suggestions

Add a brief workflow example showing how to chain operations (e.g., 'To create a card: 1. List boards to get boardId, 2. List lists to get listId, 3. Create card')

Add a verification step after archive operations (e.g., 'Verify archived: curl ... | jq .closed')

Dimension	Reasoning	Score
Conciseness	The skill is lean and efficient, providing only necessary setup instructions and executable curl commands without explaining what Trello is or how REST APIs work. Every section earns its place.	3 / 3
Actionability	All commands are fully executable curl commands with proper syntax, environment variable usage, and jq formatting. Copy-paste ready with clear placeholders for IDs.	3 / 3
Workflow Clarity	Commands are clearly presented but there's no explicit workflow for common multi-step operations (e.g., find board -> get lists -> create card). The archive operation lacks a confirmation/verification step for this destructive action.	2 / 3
Progressive Disclosure	For a skill of this size (~80 lines), the content is well-organized with clear sections (Setup, Usage, Notes, Examples). No need for external file references given the scope.	3 / 3
	Total	11 / 12 Passed

Validation

72%

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 — 8 / 11 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	8 / 11 Passed

Repository: trpc-group/trpc-agent-go
Commit: 8763418

Reviewed: 32 minutes 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.