CtrlK
BlogDocsLog inGet started
Tessl Logo

trello

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

77

1.09x
Quality

70%

Does it follow best practices?

Impact

93%

1.09x

Average score across 3 eval scenarios

SecuritybySnyk

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

SKILL.md
Quality
Evals
Security

Quality

Content

76%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 skill body is highly actionable and token-efficient, presenting executable curl commands for the common Trello operations, but it lacks validation checkpoints for its destructive/mutating operations.

Suggestions

Add a verification step after destructive operations, e.g., re-fetch the card with `curl .../cards/{cardId}` to confirm `closed=true` or the new `idList`, to lift workflow clarity above 3.

Trim or differentiate the Examples 'Get all boards' entry to avoid near-duplication of the Usage command.

Consider a short note clarifying that archiving is reversible via `closed=false`, which doubles as a recovery loop for the destructive archive action.

DimensionReasoningScore

Conciseness

The body is a lean curl-command catalog with minimal prose and no over-explanation of concepts, though the Examples section partially repeats the 'Get all boards' command from Usage.

4 / 5

Actionability

Every operation is a complete, copy-paste-ready curl command with real endpoints, auth params, and jq filters, covering the common cases (list/create/move/comment/archive).

5 / 5

Workflow Clarity

Setup is a clear 3-step sequence, but the destructive operations (archive a card, move a card) have no validation or verification checkpoints, capping workflow clarity at 3 per the rubric.

3 / 5

Progressive Disclosure

Content is well organized into Setup, Usage, Notes, and Examples sections and is appropriately self-contained for a compact API catalog; no bundle files exist to reference.

4 / 5

Total

16

/

20

Passed

Description

65%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 names a distinct, well-scoped product niche with natural trigger terms, but it relies on the generic verb 'Manage' and omits any 'Use when...' trigger guidance.

Suggestions

Replace the generic 'Manage' with two or three concrete verbs (e.g., 'Create, move, and archive Trello cards, lists, and boards') to lift specificity toward 4-5.

Add an explicit trigger clause such as 'Use when the user asks to manage Trello boards, lists, or cards' so completeness is not capped at 3.

Include a common synonym or file/URL cue (e.g., 'Trello boards/cards') to round out trigger-term coverage.

DimensionReasoningScore

Specificity

Names the domain ('Trello') and concrete entities ('boards, lists, and cards') but uses only the single generic verb 'Manage' rather than enumerating several specific actions like create/move/archive/comment.

3 / 5

Completeness

There is a clear 'what' ('Manage Trello boards, lists, and cards via the Trello REST API') but no 'Use when...' clause or equivalent explicit trigger guidance, capping completeness at 3 per the rubric guideline.

3 / 5

Trigger Term Quality

'Trello', 'boards', 'lists', and 'cards' are natural terms users would actually say when requesting this skill, giving good keyword coverage with only minor synonyms missing.

4 / 5

Distinctiveness Conflict Risk

'Trello' is a specific named product with a clear niche and distinct triggers, giving minimal risk of overlapping with other skills.

5 / 5

Total

15

/

20

Passed

Validation

81%

Checks the skill against the spec for correct structure and formatting. All validation checks must pass before discovery and implementation can be scored.

Validation13 / 16 Passed

Validation for skill structure

CriteriaDescriptionResult

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
Reviewed

Table of Contents

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.