Trello Automation via Rube MCP

Overview

This public intake copy packages

plugins/antigravity-awesome-skills-claude/skills/trello-automation

https://github.com/sickn33/antigravity-awesome-skills

Use it when the operator needs the upstream workflow, support files, and repository context to stay intact while the public validator and private enhancer continue their normal downstream flow.

This intake keeps the copied upstream files intact and uses

metadata.json

ORIGIN.md

Trello Automation via Rube MCP Automate Trello board management, card creation, and team workflows through Composio's Rube MCP integration.

Imported source sections that did not map cleanly to the public headings are still preserved below or in the support files. Notable imported sections: Prerequisites, Common Patterns, Known Pitfalls, Limitations.

When to Use This Skill

Use this section as the trigger filter. It should make the activation boundary explicit before the operator loads files, runs commands, or opens a pull request.

• This skill is applicable to execute the workflow or actions described in the overview.
• Use when the request clearly matches the imported source intent: Automate Trello boards, cards, and workflows via Rube MCP (Composio). Create cards, manage lists, assign members, and search across boards programmatically.
• Use when the operator should preserve upstream workflow detail instead of rewriting the process from scratch.
• Use when provenance needs to stay visible in the answer, PR, or review packet.
• Use when copied upstream references, examples, or scripts materially improve the answer.
• Use when the workflow should remain reviewable in the public intake repo before the private enhancer takes over.

Operating Table

metadata.json

ORIGIN.md

SKILL.md

SKILL.md

## Related Skills

Workflow

This workflow is intentionally editorial and operational at the same time. It keeps the imported source useful to the operator while still satisfying the public intake standards that feed the downstream enhancer flow.

1. Verify Rube MCP is available by confirming RUBESEARCHTOOLS responds
2. Call RUBEMANAGECONNECTIONS with toolkit trello
3. If connection is not ACTIVE, follow the returned auth link to complete Trello auth
4. Confirm connection status shows ACTIVE before running any workflows
5. TRELLOGETMEMBERSBOARDSBYIDMEMBER - List boards to find target board ID [Prerequisite]
6. TRELLOGETBOARDSLISTSBYIDBOARD - Get lists on board to find target list ID [Prerequisite]
7. TRELLOADDCARDS - Create the card on the resolved list [Required]

Imported Workflow Notes

Imported: Setup

Get Rube MCP: Add

https://rube.app/mcp

1. Verify Rube MCP is available by confirming

   RUBE_SEARCH_TOOLS

   responds
2. Call

   RUBE_MANAGE_CONNECTIONS

   with toolkit

   trello

3. If connection is not ACTIVE, follow the returned auth link to complete Trello auth
4. Confirm connection status shows ACTIVE before running any workflows

Imported: Core Workflows

1. Create a Card on a Board

When to use: User wants to add a new card/task to a Trello board

Tool sequence:

1. TRELLO_GET_MEMBERS_BOARDS_BY_ID_MEMBER

   - List boards to find target board ID [Prerequisite]

2. TRELLO_GET_BOARDS_LISTS_BY_ID_BOARD

   - Get lists on board to find target list ID [Prerequisite]

3. TRELLO_ADD_CARDS

   - Create the card on the resolved list [Required]

4. TRELLO_ADD_CARDS_CHECKLISTS_BY_ID_CARD

   - Add a checklist to the card [Optional]

5. TRELLO_ADD_CARDS_CHECKLIST_CHECK_ITEM_BY_ID_CARD_BY_ID_CHECKLIST

   - Add items to the checklist [Optional]

Key parameters:

• idList

  : 24-char hex ID (NOT list name)

• name

  : Card title

• desc

  : Card description (supports Markdown)

• pos

  : Position ('top'/'bottom')

• due

  : Due date (ISO 8601 format)

Pitfalls:

• Store returned id (idCard) immediately; downstream checklist operations fail without it
• Checklist payload may be nested (data.data); extract idChecklist from inner object
• One API call per checklist item; large checklists can trigger rate limits

2. Manage Boards and Lists

When to use: User wants to view, browse, or restructure board layout

Tool sequence:

1. TRELLO_GET_MEMBERS_BOARDS_BY_ID_MEMBER

   - List all boards for the user [Required]

2. TRELLO_GET_BOARDS_BY_ID_BOARD

   - Get detailed board info [Required]

3. TRELLO_GET_BOARDS_LISTS_BY_ID_BOARD

   - Get lists (columns) on the board [Optional]

4. TRELLO_GET_BOARDS_MEMBERS_BY_ID_BOARD

   - Get board members [Optional]

5. TRELLO_GET_BOARDS_LABELS_BY_ID_BOARD

   - Get labels on the board [Optional]

Key parameters:

• idMember

  : Use 'me' for authenticated user

• filter

  : 'open', 'starred', or 'all'

• idBoard

  : 24-char hex or 8-char shortLink (NOT board name)

Pitfalls:

• Some runs return boards under response.data.details[]—don't assume flat top-level array
• Lists may be nested under results[0].response.data.details—parse defensively
• ISO 8601 timestamps with trailing 'Z' must be parsed as timezone-aware

3. Move Cards Between Lists

When to use: User wants to change a card's status by moving it to another list

Tool sequence:

1. TRELLO_GET_SEARCH

   - Find the card by name or keyword [Prerequisite]

2. TRELLO_GET_BOARDS_LISTS_BY_ID_BOARD

   - Get destination list ID [Prerequisite]

3. TRELLO_UPDATE_CARDS_BY_ID_CARD

   - Update card's idList to move it [Required]

Key parameters:

• idCard

  : Card ID from search

• idList

  : Destination list ID

• pos

  : Optional ordering within new list

Pitfalls:

• Search returns partial matches; verify card name before updating
• Moving doesn't update position within new list; set pos if ordering matters

4. Assign Members to Cards

When to use: User wants to assign team members to cards

Tool sequence:

1. TRELLO_GET_BOARDS_MEMBERS_BY_ID_BOARD

   - Get member IDs from the board [Prerequisite]

2. TRELLO_ADD_CARDS_ID_MEMBERS_BY_ID_CARD

   - Add a member to the card [Required]

Key parameters:

• idCard

  : Target card ID

• value

  : Member ID to assign

Pitfalls:

• UPDATE_CARDS_ID_MEMBERS replaces entire member list; use ADD_CARDS_ID_MEMBERS to append
• Member must have board permissions

5. Search and Filter Cards

When to use: User wants to find specific cards across boards

Tool sequence:

1. TRELLO_GET_SEARCH

   - Search by query string [Required]

Key parameters:

• query

  : Search string (supports board:, list:, label:, is:open/archived operators)

• modelTypes

  : Set to 'cards'

• partial

  : Set to 'true' for prefix matching

Pitfalls:

• Search indexing has delay; newly created cards may not appear for several minutes
• For exact name matching, use TRELLO_GET_BOARDS_CARDS_BY_ID_BOARD and filter locally
• Query uses word tokenization; common words may be ignored as stop words

6. Add Comments and Attachments

When to use: User wants to add context to an existing card

Tool sequence:

1. TRELLO_ADD_CARDS_ACTIONS_COMMENTS_BY_ID_CARD

   - Post a comment on the card [Required]

2. TRELLO_ADD_CARDS_ATTACHMENTS_BY_ID_CARD

   - Attach a file or URL [Optional]

Key parameters:

• text

  : Comment text (1-16384 chars, supports Markdown and @mentions)

• url

  OR

  file

  : Attachment source (not both)

• name

  : Attachment display name

• mimeType

  : File MIME type

Pitfalls:

• Comments don't support file attachments; use the attachment tool separately
• Attachment deletion is irreversible

Imported: Prerequisites

• Rube MCP must be connected (RUBE_SEARCH_TOOLS available)
• Active Trello connection via

  RUBE_MANAGE_CONNECTIONS

  with toolkit

  trello

• Always call

  RUBE_SEARCH_TOOLS

  first to get current tool schemas

Examples

Example 1: Ask for the upstream workflow directly

Use @trello-automation to handle <task>. Start from the copied upstream workflow, load only the files that change the outcome, and keep provenance visible in the answer.

Explanation: This is the safest starting point when the operator needs the imported workflow, but not the entire repository.

Example 2: Ask for a provenance-grounded review

Review @trello-automation against metadata.json and ORIGIN.md, then explain which copied upstream files you would load first and why.

Explanation: Use this before review or troubleshooting when you need a precise, auditable explanation of origin and file selection.

Example 3: Narrow the copied support files before execution

Use @trello-automation for <task>. Load only the copied references, examples, or scripts that change the outcome, and name the files explicitly before proceeding.

Explanation: This keeps the skill aligned with progressive disclosure instead of loading the whole copied package by default.

Example 4: Build a reviewer packet

Review @trello-automation using the copied upstream files plus provenance, then summarize any gaps before merge.

Explanation: This is useful when the PR is waiting for human review and you want a repeatable audit packet.

Best Practices

Treat the generated public skill as a reviewable packaging layer around the upstream repository. The goal is to keep provenance explicit and load only the copied source material that materially improves execution.

• Keep the imported skill grounded in the upstream repository; do not invent steps that the source material cannot support.
• Prefer the smallest useful set of support files so the workflow stays auditable and fast to review.
• Keep provenance, source commit, and imported file paths visible in notes and PR descriptions.
• Point directly at the copied upstream files that justify the workflow instead of relying on generic review boilerplate.
• Treat generated examples as scaffolding; adapt them to the concrete task before execution.
• Route to a stronger native skill when architecture, debugging, design, or security concerns become dominant.

Troubleshooting

Problem: The operator skipped the imported context and answered too generically

Symptoms: The result ignores the upstream workflow in

plugins/antigravity-awesome-skills-claude/skills/trello-automation

metadata.json

ORIGIN.md

Problem: The imported workflow feels incomplete during review

Symptoms: Reviewers can see the generated

SKILL.md

Problem: The task drifted into a different specialization

Symptoms: The imported skill starts in the right place, but the work turns into debugging, architecture, design, security, or release orchestration that a native skill handles better. Solution: Use the related skills section to hand off deliberately. Keep the imported provenance visible so the next skill inherits the right context instead of starting blind.

Related Skills

• @supply-chain-risk-auditor

  - Use when the work is better handled by that native specialization after this imported skill establishes context.

• @sveltekit

  - Use when the work is better handled by that native specialization after this imported skill establishes context.

• @swift-concurrency-expert

  - Use when the work is better handled by that native specialization after this imported skill establishes context.

• @swiftui-expert-skill

  - Use when the work is better handled by that native specialization after this imported skill establishes context.

Additional Resources

Use this support matrix and the linked files below as the operator packet for this imported skill. They should reflect real copied source material, not generic scaffolding.

references

references/n/a

examples

examples/n/a

scripts

scripts/n/a

agents

agents/n/a

assets

assets/n/a

Imported Reference Notes

Imported: Quick Reference

Imported: Common Patterns

ID Resolution

Always resolve display names to IDs before operations:

• Board name → Board ID:

  TRELLO_GET_MEMBERS_BOARDS_BY_ID_MEMBER

  with idMember='me'
• List name → List ID:

  TRELLO_GET_BOARDS_LISTS_BY_ID_BOARD

  with resolved board ID
• Card name → Card ID:

  TRELLO_GET_SEARCH

  with query string
• Member name → Member ID:

  TRELLO_GET_BOARDS_MEMBERS_BY_ID_BOARD

Pagination

Most list endpoints return all items. For boards with 1000+ cards, use

limit

before

Rate Limits

300 requests per 10 seconds per token. Use

TRELLO_GET_BATCH

Imported: Known Pitfalls

• ID Requirements: Nearly every tool requires IDs, not display names. Always resolve names to IDs first.
• Board ID Format: Board IDs must be 24-char hex or 8-char shortLink. URL slugs like 'my-board' are NOT valid.
• Search Delays: Search indexing has delays; newly created/updated cards may not appear immediately.
• Nested Responses: Response data is often nested (data.data or data.details[]); parse defensively.
• Rate Limiting: 300 req/10s per token. Batch reads with TRELLO_GET_BATCH.

Imported: Limitations

• Use this skill only when the task clearly matches the scope described above.
• Do not treat the output as a substitute for environment-specific validation, testing, or expert review.
• Stop and ask for clarification if required inputs, permissions, safety boundaries, or success criteria are missing.