Trello
Let your agent list boards, lists, and cards and create or update Trello work items via the REST API using curl and jq.
Overview
Trello is an agent skill most often used in Build (also Operate) that manages Trello boards, lists, and cards through the Trello REST API with curl and jq.
Install
npx skills add https://github.com/steipete/clawdis --skill trelloWhat is this skill?
- Trello REST API workflows: boards, lists, cards—list and create patterns with curl
- OpenClaw metadata: requires jq plus TRELLO_API_KEY and TRELLO_TOKEN environment variables
- Optional Homebrew install path for jq when the agent environment lacks it
- jq-shaped JSON filtering for readable board, list, and card summaries in the terminal
- Requires jq binary and TRELLO_API_KEY plus TRELLO_TOKEN env vars
Adoption & trust: 2.1k installs on skills.sh; 378k GitHub stars; 2/3 security scanners passed (skills.sh audits).
What problem does it solve?
You track work in Trello but copying status by hand between your agent session and boards wastes time and drifts out of date.
Who is it for?
Solo builders on OpenClaw-compatible setups who already use Trello and want API-driven board updates from the agent.
Skip if: Teams standardized on Linear, GitHub Issues only, or environments where outbound API calls and API tokens are disallowed.
When should I use this skill?
You need to read or update Trello boards, lists, or cards via the REST API from an OpenClaw-capable agent environment.
What do I get? / Deliverables
Your agent can query and mutate Trello cards from documented curl commands so backlog state stays aligned with what you ship or discover.
- Executed API calls listing or mutating boards, lists, or cards
- New or updated Trello cards reflecting agent-session work
Recommended Skills
Journey fit
Spans multiple journey phases - primary shelf plus alternate fits below.
Trello is most often wired while you are actively building and tracking tasks, so PM under Build is the canonical shelf even though it also supports ongoing ops. PM matches board/list/card management for solo backlog hygiene rather than frontend UI or deep backend domain code.
Where it fits
After a feature lands, the agent opens the sprint list and creates a card with acceptance notes and links.
Wire a one-off script that mirrors GitHub PR state into Trello using the documented list-cards pattern.
Populate a launch checklist board with cards per channel without manual copy-paste.
File a bug card from debugging output while you stay in the agent thread.
How it compares
REST API integration skill—not a hosted Trello MCP server or a full agile ceremony playbook.
Common Questions / FAQ
Who is trello for?
Indie developers and agent users who keep a Trello board for tasks and want curl-based API commands the agent can run to list or create cards.
When should I use trello?
During Build while logging implementation tasks or QA cards; during Ship for launch checklists on a board; during Operate when triage cards need creating from incident notes.
Is trello safe to install?
The skill uses network access and Trello API secrets in environment variables—review the Security Audits panel on this Prism page and rotate tokens if the skill source changes.
SKILL.md
READMESKILL.md - Trello
# Trello Skill Manage Trello boards, lists, and cards directly from OpenClaw. ## Setup 1. Get your API key: https://trello.com/app-key 2. Generate a token (click "Token" link on that page) 3. Set environment variables: ```bash export TRELLO_API_KEY="your-api-key" export TRELLO_TOKEN="your-token" ``` ## Usage All commands use curl to hit the Trello REST API. ### List boards ```bash curl -s "https://api.trello.com/1/members/me/boards?key=$TRELLO_API_KEY&token=$TRELLO_TOKEN" | jq '.[] | {name, id}' ``` ### List lists in a board ```bash curl -s "https://api.trello.com/1/boards/{boardId}/lists?key=$TRELLO_API_KEY&token=$TRELLO_TOKEN" | jq '.[] | {name, id}' ``` ### List cards in a list ```bash curl -s "https://api.trello.com/1/lists/{listId}/cards?key=$TRELLO_API_KEY&token=$TRELLO_TOKEN" | jq '.[] | {name, id, desc}' ``` ### Create a card ```bash curl -s -X POST "https://api.trello.com/1/cards?key=$TRELLO_API_KEY&token=$TRELLO_TOKEN" \ -d "idList={listId}" \ -d "name=Card Title" \ -d "desc=Card description" ``` ### Move a card to another list ```bash curl -s -X PUT "https://api.trello.com/1/cards/{cardId}?key=$TRELLO_API_KEY&token=$TRELLO_TOKEN" \ -d "idList={newListId}" ``` ### Add a comment to a card ```bash curl -s -X POST "https://api.trello.com/1/cards/{cardId}/actions/comments?key=$TRELLO_API_KEY&token=$TRELLO_TOKEN" \ -d "text=Your comment here" ``` ### Archive a card ```bash curl -s -X PUT "https://api.trello.com/1/cards/{cardId}?key=$TRELLO_API_KEY&token=$TRELLO_TOKEN" \ -d "closed=true" ``` ## Notes - Board/List/Card IDs can be found in the Trello URL or via the list commands - The API key and token provide full access to your Trello account - keep them secret! - Rate limits: 300 requests per 10 seconds per API key; 100 requests per 10 seconds per token; `/1/members` endpoints are limited to 100 requests per 900 seconds ## Examples ```bash # Get all boards curl -s "https://api.trello.com/1/members/me/boards?key=$TRELLO_API_KEY&token=$TRELLO_TOKEN&fields=name,id" | jq # Find a specific board by name curl -s "https://api.trello.com/1/members/me/boards?key=$TRELLO_API_KEY&token=$TRELLO_TOKEN" | jq '.[] | select(.name | contains("Work"))' # Get all cards on a board curl -s "https://api.trello.com/1/boards/{boardId}/cards?key=$TRELLO_API_KEY&token=$TRELLO_TOKEN" | jq '.[] | {name, list: .idList}' ```