BD trello_planner
Read-only Trello planner using official Boards API. 🧠 AI PLANNING: Task prioritization, sprint capacity, board optimization 📊 ANALYSIS: Lists/cards/members from /boards/{id}/* endpoints 🔍 SEARCH: Overdue, assignees, labels across boards REQUIRES: TRELLO_API_KEY + TRELLO_TOKEN (read scope) ENDPOINTS: /1/boards/{id}/lists, /cards, /members (official spec)
As a process D 48/100 · Unfinished process — weak spots: result and completion, when it triggers, inputs and preconditions
How to improve
- Say in the description WHEN to use the skill ("use when…", example requests): that is the agent's main cue.
- Your own cases (evals/evals.json, 4–6 real requests with expected answers): the full check would then run those instead of a model-drafted suite.
- A spec.yaml with trigger phrases and assertions — a behaviour contract for CI; `skilltest init` writes a template.
Guard findings · 0
✓ No critical or high findings
Files scanned: 4. Evidence is masked. Grey chips explain why severity was lowered.
Against the Agent Skills spec
- warning
name-formatname should be kebab-case (lowercase letters, digits, hyphens) - warning
description-no-whendescription does not say WHEN to use the skill (no "use when") - note
frontmatter-keyunknown frontmatter key "web" - note
frontmatter-keyunknown frontmatter key "install" - note
frontmatter-keyunknown frontmatter key "env" - note
frontmatter-keyunknown frontmatter key "primary-credential" - note
frontmatter-keyunknown frontmatter key "gating" - note
frontmatter-keyunknown frontmatter key "slash-commands" - note
frontmatter-keyunknown frontmatter key "categories"
Process rating: all ten parameters 48/100
- 0Result and completion. Does not say what the result is
- 0Inputs and preconditions. Does not say what the process needs to start
- 0Failures and branches. Linear process with no failure handling
- 20When it triggers. No condition that starts the skill
- 30Running it twice. 1 mutating operations with no state check
- 40Consistency. Frontmatter name (trello_planner) differs from the folder (trello-planner)
- 100Tools and files. No external tools needed
- 100Steps. 9 steps
- 100Execution cost. Instruction body is 569 tokens
- 100Progress reporting. Reports progress
Everything here is measured from the skill text rather than judged by a model, so the numbers are checkable. A parameter weighs more when it is a more common reason for the process to stall.
Quality signals
- +5Description has no quoted example phrases that should trigger the skill
- +4Description does not say when NOT to use the skill (false activations)
- +3Output format is not stated: the model decides each time
- +1No license
- +2Single-language instructions
- +3Description length 360: enough signal without eating the budget
- +4Structure: 8 headings
- +3Step-by-step instructions: 9 items
- +4Has examples (3 code blocks)
Quality base 70; lint remarks subtract, signals add up to 100. Result: 64.