trello-task-management
Create and manage Trello cards, checklists, and boards for kanban workflows. Use when the user says: 'create a kanban board', 'add a task card', 'move card to sprint', or 'track project board'.
77
96%
Does it follow best practices?
Impact
—
No eval scenarios have been run
Advisory
Suggest reviewing before use
Quality
Discovery
100%Based on the skill's description, can an agent find and select it at the right time? Clear, specific descriptions lead to better discovery.
This is a strong skill description that clearly identifies the tool (Trello), the domain (kanban workflows), specific capabilities (cards, checklists, boards), and explicit trigger phrases. It uses third person voice correctly and follows the recommended pattern of 'what it does' followed by 'Use when...' with concrete examples. Minor improvement could include additional trigger variations like 'Trello board' or 'checklist' as standalone triggers.
| Dimension | Reasoning | Score |
|---|---|---|
Specificity | Lists multiple specific concrete actions: 'Create and manage Trello cards, checklists, and boards for kanban workflows.' This covers cards, checklists, and boards as distinct actionable entities. | 3 / 3 |
Completeness | Clearly answers both 'what' (create and manage Trello cards, checklists, and boards for kanban workflows) and 'when' (explicit 'Use when the user says...' clause with specific trigger phrases). | 3 / 3 |
Trigger Term Quality | Includes natural keywords users would say: 'kanban board', 'task card', 'move card to sprint', 'track project board', 'Trello', 'checklists'. These are terms users would naturally use when requesting kanban/Trello functionality. | 3 / 3 |
Distinctiveness Conflict Risk | Clearly scoped to Trello and kanban workflows with distinct triggers like 'kanban board', 'task card', 'move card to sprint'. Unlikely to conflict with generic project management or other tool-specific skills due to the Trello and kanban specificity. | 3 / 3 |
Total | 12 / 12 Passed |
Implementation
92%Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.
This is a strong, well-crafted skill that provides actionable MCP tool invocations with concrete examples, clear workflow transitions, and efficient use of tokens. The card naming conventions and bug triage decision tree are particularly useful additions. Minor improvement could come from verifying the referenced tracker-config.md exists and potentially splitting detailed conventions into a referenced file.
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The content is lean and efficient. It avoids explaining what Trello is or how APIs work, assumes Claude's competence, and every section delivers actionable information without padding. | 3 / 3 |
Actionability | Provides concrete JSON invocation examples with expected responses, specific tool names, exact card naming conventions, and clear transition rules. The examples are copy-paste ready for MCP tool calls. | 3 / 3 |
Workflow Clarity | Multi-step workflows are clearly sequenced: the session continuity section provides an explicit startup sequence, card transitions have a clear from/to/when table, and the bug discovery flow includes a decision tree. The 'verify the returned card ID and URL before proceeding' step serves as a validation checkpoint after mutations. | 3 / 3 |
Progressive Disclosure | References tracker-config.md for project-specific IDs (good separation), but the bundle has no files to verify this reference. The content is well-structured with clear sections, but the discovered issues and card naming sections could potentially be split into referenced files for better organization given the overall length. | 2 / 3 |
Total | 11 / 12 Passed |
Validation
100%Checks the skill against the spec for correct structure and formatting. All validation checks must pass before discovery and implementation can be scored.
Validation — 11 / 11 Passed
Validation for skill structure
No warnings or errors.
- Repository
- monkilabs/opencastle
- Commit
7a69a05
- 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.