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 operations) but suffers from vague action language ('manage') and completely lacks trigger guidance. While it won't conflict with other skills due to the explicit Trello reference, Claude may fail to select it appropriately without explicit 'Use when' conditions.

Suggestions

Add a 'Use when...' clause with trigger terms like 'Trello', 'kanban board', 'create card', 'move task', 'project board'

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

Include common user phrases like 'add to Trello', 'update my board', 'create a card for' to improve trigger matching

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 (manage Trello entities via API) 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 users would say, but misses common variations like 'kanban', 'task board', 'project management', or action-oriented terms like 'add card', 'move task'.	2 / 3
Distinctiveness Conflict Risk	Clearly specific to Trello with explicit platform name and API reference; unlikely to conflict with other project management or kanban tools.	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 reference skill that provides concise, executable curl commands for common Trello operations. The content is appropriately lean and actionable. The main weakness is the lack of workflow guidance for multi-step operations (e.g., finding a board ID, then listing its lists, then creating a card) and no validation/error handling patterns.

Suggestions

Add a brief workflow example showing a complete task (e.g., 'To add a card: 1. List boards to get boardId, 2. List lists to get listId, 3. Create card')

Include error handling guidance (e.g., what a 401 response means, how to verify token validity)

Dimension	Reasoning	Score
Conciseness	The skill is lean and efficient, providing only the necessary setup steps and 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 only placeholder IDs needing substitution.	3 / 3
Workflow Clarity	Commands are clearly presented but there's no explicit workflow sequence or validation steps. For operations like archiving cards, there's no confirmation or undo guidance. The skill reads more as a reference than a guided workflow.	2 / 3
Progressive Disclosure	For a skill of this scope (~80 lines), the content is well-organized with clear sections (Setup, Usage, Notes, Examples). No external references needed; the flat structure is appropriate for this API reference skill.	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: 50ef2f3

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.