$ loading_
Manage Trello boards, lists, and cards to streamline team task tracking.
Overall risk is low to moderate: the material is mainly usage guidance for Trello's official REST API, and it comes from an open-source GitHub source with strong community adoption. However, there is a mismatch with the metadata: the README explicitly requires Trello API credentials and sends requests to api.trello.com, so real use should be treated as having account-data access and network egress.
The README explicitly requires TRELLO_API_KEY and TRELLO_TOKEN and states they provide 'full access' to the Trello account; if exposed, they could be used to read and modify boards, lists, cards, and comments, so they are sensitive credentials. The 'no keys required' metadata conflicts with the README and should be verified.
The material shows curl requests to Trello's official endpoint at https://api.trello.com/1/..., sending board, list, card, and comment data to Trello. This egress matches the stated functionality and is typical SaaS API traffic, but it conflicts with the 'no remote endpoint' metadata.
Based on the objective checks, this is prompt-only and does not ship an executable binary, install script, or MCP server implementation; the curl/jq snippets are example commands. From the material alone, there are no clear red flags of extra local system privileges, persistence, or out-of-scope execution.
Its access scope is focused on boards/lists/cards/comments within the linked Trello account, with both read and write capabilities over business content, but there is no indication of local file, system directory, or unrelated resource access. The main concern is account-level content access rather than excessive local authorization.
The source is an open-source GitHub repository with very high reported community adoption, both of which are positive indicators that lower risk; the material does not show obfuscated installation steps, suspicious downloaders, or clear injection signs. Still, the license is unspecified, maintenance status is unknown, and repository-level trust does not automatically equal a full audit of this specific skill.
Copy the install command and let the AI configure it · recommended for beginners
Please install the "trello" skill from askskill: 1. Download https://raw.githubusercontent.com/openclaw/openclaw/main/skills/trello/SKILL.md 2. Save it as ~/.claude/skills/trello/SKILL.md 3. Reload skills and tell me it's ready
In the Trello board "Product Launch," create 5 cards in the "To Do" list: Requirement Review, Design Review, Development Scheduling, Test Preparation, and Launch Checklist. Add due dates for this week to each card.
Multiple task cards are created in the target board and list with due dates.
Read the Trello board "Marketing Campaigns," list all cards in the "In Progress" list sorted by due date, and move any overdue cards to the "Needs Attention" list.
A sorted list of in-progress tasks is returned, and overdue cards are moved automatically.
Based on these meeting decisions, update the Trello board "Engineering Collaboration": move "API Documentation Update" to "Done," add the comment "Tracking setup must be completed first" to "Login Page Optimization," and create a new card called "Next Week Performance Review."
Cards are updated according to the meeting decisions, including moves, comments, and a new card.
Manage Trello boards, lists, and cards directly from OpenClaw.
export TRELLO_API_KEY="your-api-key"
export TRELLO_TOKEN="your-token"
All commands use curl to hit the Trello REST API.
curl -s "https://api.trello.com/1/members/me/boards?key=$TRELLO_API_KEY&token=$TRELLO_TOKEN" | jq '.[] | {name, id}'
curl -s "https://api.trello.com/1/boards/{boardId}/lists?key=$TRELLO_API_KEY&token=$TRELLO_TOKEN" | jq '.[] | {name, id}'
curl -s "https://api.trello.com/1/lists/{listId}/cards?key=$TRELLO_API_KEY&token=$TRELLO_TOKEN" | jq '.[] | {name, id, desc}'
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"
curl -s -X PUT "https://api.trello.com/1/cards/{cardId}?key=$TRELLO_API_KEY&token=$TRELLO_TOKEN" \
-d "idList={newListId}"
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"
curl -s -X PUT "https://api.trello.com/1/cards/{cardId}?key=$TRELLO_API_KEY&token=$TRELLO_TOKEN" \
-d "closed=true"
/1/members endpoints are limited to 100 requests per 900 seconds# 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}'
Create and review technical docs and agent instruction files in repositories.
Verify an OpenClaw release is fully published and working across all channels.
Fetch GitHub issues, create fixes, open PRs, and handle reviews.
Convert text to speech locally and offline with sherpa-onnx, no cloud needed.
Regenerate OpenClaw release changelog sections from Git history before releases.
Navigate Feishu knowledge bases and surface relevant wiki pages and links.
Manage Trello boards, cards, checklists, and team collaboration with natural language.
Connect to Trello boards and manage cards, lists, labels, and workflows.
Let AI manage Trello boards, cards, and checklists to streamline teamwork.
Search Trello cards by custom fields and manage board data efficiently.
Manage Trello boards, cards, and collaboration workflows using natural language.
Manage Trello boards, lists, and cards directly through an MCP server.