Come usare
- Copia il comando e controlla il pacchetto prima di installarlo nel tuo ambiente agente.
- Controlla strumenti, credenziali e ambienti richiesti nel documento originale.
- Descrivi input e risultato desiderato; confronta l’output con le fonti.
npx skills add https://github.com/scale-flow/trello-cli --skill using-trello-cliPrima di iniziare
- L’installazione non include abbonamenti, quote API o accesso ai file.
- Stelle e installazioni indicano attività, non un test indipendente di qualità o sicurezza.
Contenuto dal repository con titoli, esempi, codice, tabelle, link e immagini preservati.
This skill teaches you how to translate natural-language Trello requests into safe, multi-step trello CLI workflows. The CLI outputs deterministic JSON — every response is machine-parseable and follows a stable contract.
Resolve the Binary
Try these in order — use whichever works first:
trelloonPATH./bin/trello(relative to the repo root)- Build from the repo:
go build -o bin/trello ./cmd/trello
Once resolved, use that path for all subsequent commands in the session.
Preflight: Check Auth
Before any resource command, verify credentials are configured:
trello auth statusThe response follows the JSON envelope. If ok is false or the auth mode is key_only, stop and explain the issue to the user. Do not attempt resource commands without valid auth.
Auth can come from three sources:
- Device flow (preferred — via
trello auth loginwith Power-Up pairing) - OS keyring (stored credentials via
trello auth setortrello auth login) - Environment variables
TRELLO_API_KEYandTRELLO_TOKEN
Device Flow Authentication (Preferred)
When authenticating a new user, prefer the device flow over manual API key setup:
- Run
trello auth login— this contacts the pairing service and displays a code - Present the pairing code to the user: "Enter this code in your Trello board's CLI Connector Power-Up: XXXX-XXXX"
- The command blocks until the user completes pairing (up to 15 minutes)
- On success, credentials are stored automatically — no API key or token handling needed
- If the pairing service is unavailable, the CLI falls back to browser-based login automatically
The device flow is ideal for non-technical users and agent-driven workflows because it requires no developer portal access.
Core Workflow: Discover, Mutate, Verify
Every Trello task follows this shape:
- Discover — find the IDs you need (boards, lists, cards) using read commands or search
- Mutate — run the minimum command to accomplish the task
- Verify — re-fetch the resource to confirm the change took effect
This matters because the CLI uses IDs, not names. Never guess an ID — always discover it first.
Example: "Create a card in the Doing list on the Marketing board"
trello boards list→ find Marketing board IDtrello lists list --board <board-id>→ find Doing list IDtrello cards create --list <list-id> --name "My card"trello cards get --card <card-id>→ confirm creation
JSON Contract
Every command returns one of two envelopes:
{"ok": true, "data": ...}
{"ok": false, "error": {"code": "...", "message": "..."}}Always branch on ok. Read payloads from data, errors from error.code and error.message. The --pretty flag changes formatting only, not the schema.
Use compact JSON (no --pretty) when piping output or extracting values programmatically. Use --pretty when showing results to the user.
Safety Rules
- Prefer reads first when names are ambiguous — list boards/lists before mutating
- Use IDs after discovery — never pass names where an ID is expected
- Never guess IDs — always discover them from a list or search command
- Re-fetch after mutations when confirmation matters
- Validate file paths before
attachments add-file - Use ISO-8601 for
--dueand--datevalues - `cards list` requires exactly one of
--boardor--list, never both - Update commands need at least one mutation field
Intent Interpretation
When the user describes a Trello task in natural language, translate it into a multi-step workflow — not a single command. Think about what IDs you need and how to get them.
Common patterns:
- "Move card X to Done" → discover the Done list ID, then
cards move, then verify - "Add a checklist to card X" →
checklists create, add items, list to confirm - "Find boards about marketing" →
search boards --query marketingorboards listand filter - "Set priority to High on card X" → discover custom field ID, then
custom-fields items set
Read references/task-recipes.md for complete workflow recipes covering all resource types.
Command Reference
The CLI has 12 top-level command groups: auth, boards, lists, cards, comments, checklists, attachments, custom-fields, labels, members, search, version.
Read references/command-digest.md for the full command surface, flags, and validation rules.
Error Handling
When a command returns ok: false, check the error code:
| Code | Meaning | What to do |
|---|---|---|
AUTH_REQUIRED | No credentials configured | Guide user through auth set or auth login |
AUTH_INVALID | Credentials rejected by Trello | Credentials may be expired — re-authenticate |
NOT_FOUND | Resource ID doesn't exist | Re-discover the ID |
VALIDATION_ERROR | Bad input (missing flag, wrong format) | Fix the command flags |
RATE_LIMITED | Trello API rate limit hit | Wait and retry |
CONFLICT | Resource state conflict | Re-fetch and retry |