agentleFS
claude-worldclaude-world/claude-agent/.claude/skills/trello/SKILL.md

trello

Skill5 starsChanged 8 months agoMITView on GitHub

Manage Trello boards, lists, and cards via the Trello REST API using curl. Use when user wants to view boards, create/move/archive cards, add checklists, or update task status in Trello.

  • Reads credentials
  • Installs packages
  • Sends data out

44 other projects use a version of this, 36 of them edited.

Adopted by

Most recently taken up by

Used with

Projects with it also use creative-project, labs-graduation and 10 more.

Other files people use alongside this one.

Files found in the same public projects as a version of this one, more often than they turn up anywhere else. Each project counts once, large collections count for less, and this file's own repository is left out.
  • openclawSkill

    creative-project

    Design or revise branding, visual identities, logos, posters, illustrations, and social-media assets using project artwork or image references. Inspect the existing visual language, choose references, and iterate on named candidates.

    Also in 5 projects that use this

  • openclawSkill

    labs-graduation

    Move a feature out of Control UI Labs, either on by default or still off by default. Use when asked to promote, graduate or ship a Labs feature.

    Also in 5 projects that use this

  • hkyutongSkill

    node-connect

    Diagnose OpenClaw node connection and pairing failures for Android, iOS, and macOS companion apps. Use when QR/setup code/manual connect fails, local Wi-Fi works but VPS/tailnet does not, or errors mention pairing required, unauthorized, bootstrap token invalid or expired, gateway.bind, gateway.remote.url, Tailscale, or plugins.entries.device-pair.config.publicUrl.

    Also in 18 projects that use this

  • friuns2Skill

    discord-e2e

    Test Discord with Convex-leased QA bots: check credentials without a Gateway, exercise owned messages, or prove OpenClaw replies, files, threads, reactions, streaming, and typing. Distinguish API and Gateway evidence from manual user interactions.

    Also in 10 projects that use this

  • friuns2Skill

    openclaw-repair-sweep

    Run scoped OpenClaw issue/PR repair campaigns: coordinate workers, prove root causes, and land or close verified work under the requested authority.

    Also in 10 projects that use this

  • clawdbotSkill

    openclaw-performance

    Performance work in OpenClaw: a slow or heavy flow (latency, CPU, memory, SQL, RPC, renders), writing or reviewing a perf PR, or adding a cache. Count the work, delete waste first, cache last.

    Also in 8 projects that use this

  • +2 more from friuns2

The file

We split this skill into the rules it gives an agent

7 rules. 0 are common, 3 are distinctive, and 4 are very specific to this project.

  • 0

    Common

    Most of the 43 edited versions we read keep these.

  • 3

    Distinctive

    This author's own choices. Worth a look.

  • 4

    Very specific

    Tied to their project's names, files or tools. Probably skip.

  • Common
  • Distinctive
  • Very specific
  1. Very specific:

    No install needed beyond curl (pre-installed on macOS/Linux).

    line 26
  2. Very specific:

    Always check that TRELLO_API_KEY and TRELLO_TOKEN are set: [ -z "$TRELLO_API_KEY" ] && echo "Not set"

    line 111
  3. Distinctive:

    If not set, guide the user to https://trello.com/app-key and stop

    line 112
  4. Distinctive:

    NEVER log or store API keys/tokens in memory or workspace files

    line 113
  5. Very specific:

    Always pipe curl output through jq for readable formatting.

    line 114
  6. Very specific:

    When looking up board/list/card IDs, do a lookup first and cache the IDs for subsequent calls in the same session

    line 115
  7. Distinctive:

    Keep responses concise: confirm action and show the created/updated item name

    line 117

“Common” is measured: kept by at least 6 in 10 of the 43 edited versions of this file we could read. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.

Keep what fits and drop the rest. Your version, ready for your agents.
Files
SKILL.md

Trello

Manage Trello via the REST API using curl. No separate CLI install needed.

Prerequisites

No install needed beyond curl (pre-installed on macOS/Linux).

Set up credentials as environment variables:

export TRELLO_API_KEY="your_api_key"
export TRELLO_TOKEN="your_token"

Get your credentials:

  1. API Key: https://trello.com/app-key
  2. Token: Click "Token" link on that page and authorize

Store them in your shell profile (~/.zshrc or ~/.bashrc) or in 1Password and inject via op run.

Commands

Base URL: https://api.trello.com/1 Auth params: key=$TRELLO_API_KEY&token=$TRELLO_TOKEN

Boards

# List all boards
curl -s "https://api.trello.com/1/members/me/boards?key=$TRELLO_API_KEY&token=$TRELLO_TOKEN" | jq '.[].name'

# Get board ID by name
curl -s "https://api.trello.com/1/members/me/boards?key=$TRELLO_API_KEY&token=$TRELLO_TOKEN" | jq '.[] | select(.name=="My Board") | .id'

Lists

# Get lists on a board
curl -s "https://api.trello.com/1/boards/<BOARD_ID>/lists?key=$TRELLO_API_KEY&token=$TRELLO_TOKEN" | jq '.[] | {id, name}'

# Create a list
curl -s -X POST "https://api.trello.com/1/lists?name=<NAME>&idBoard=<BOARD_ID>&key=$TRELLO_API_KEY&token=$TRELLO_TOKEN"

Cards

# Get cards on a list
curl -s "https://api.trello.com/1/lists/<LIST_ID>/cards?key=$TRELLO_API_KEY&token=$TRELLO_TOKEN" | jq '.[] | {id, name, due}'

# Create a card
curl -s -X POST "https://api.trello.com/1/cards?idList=<LIST_ID>&name=<NAME>&desc=<DESC>&key=$TRELLO_API_KEY&token=$TRELLO_TOKEN"

# Move card to another list
curl -s -X PUT "https://api.trello.com/1/cards/<CARD_ID>?idList=<NEW_LIST_ID>&key=$TRELLO_API_KEY&token=$TRELLO_TOKEN"

# Archive a card
curl -s -X PUT "https://api.trello.com/1/cards/<CARD_ID>?closed=true&key=$TRELLO_API_KEY&token=$TRELLO_TOKEN"

# Add due date
curl -s -X PUT "https://api.trello.com/1/cards/<CARD_ID>?due=2026-03-25T10:00:00.000Z&key=$TRELLO_API_KEY&token=$TRELLO_TOKEN"

Checklists

# Add checklist to card
curl -s -X POST "https://api.trello.com/1/checklists?idCard=<CARD_ID>&name=<NAME>&key=$TRELLO_API_KEY&token=$TRELLO_TOKEN"

# Add checklist item
curl -s -X POST "https://api.trello.com/1/checklists/<CHECKLIST_ID>/checkItems?name=<ITEM>&key=$TRELLO_API_KEY&token=$TRELLO_TOKEN"

Usage Examples

List all board names:

curl -s "https://api.trello.com/1/members/me/boards?key=$TRELLO_API_KEY&token=$TRELLO_TOKEN" | jq -r '.[].name'

Create a card in "To Do" list:

  1. Get list ID: find the list named "To Do" on your board
  2. Create card:
curl -s -X POST "https://api.trello.com/1/cards?idList=<LIST_ID>&name=Write+blog+post&key=$TRELLO_API_KEY&token=$TRELLO_TOKEN"

Move a card from "In Progress" to "Done":

curl -s -X PUT "https://api.trello.com/1/cards/<CARD_ID>?idList=<DONE_LIST_ID>&key=$TRELLO_API_KEY&token=$TRELLO_TOKEN"

Rules

  • Always check that TRELLO_API_KEY and TRELLO_TOKEN are set: [ -z "$TRELLO_API_KEY" ] && echo "Not set"
  • If not set, guide the user to https://trello.com/app-key and stop
  • NEVER log or store API keys/tokens in memory or workspace files
  • Always pipe curl output through jq for readable formatting; install with brew install jq if needed
  • When looking up board/list/card IDs, do a lookup first and cache the IDs for subsequent calls in the same session
  • URL-encode special characters in names and descriptions (spaces → +, etc.)
  • Keep responses concise: confirm action and show the created/updated item name

Download now (ZIP)

Does it work?

Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.

No reviews yet

People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.

  • It worked
  • Partly
  • It didn't
What did you use it for? e.g. Reviewing pull requests in a Rails app

Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.

Your trail

Files you open will collect here, so you can find them again.

Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.

Now do this for your own.

Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.