All API calls go through the okoro proxy, which signs requests with OAuth 1.0a, enforces permission scopes, and writes an audit trail for every action your agent takes.

Requirements

VariableDescription
OKORO_SERVICE_TOKENService token from the okoro dashboard (svc_...)

How to get your token →

How it works

Rather than giving your agent raw Trello credentials, you configure a service token once. When the skill runs, it exchanges that token for a short-lived operation token scoped to exactly the action being performed. The okoro proxy signs the request, forwards it to Trello, and records the intent in an audit log.

Your Trello credentials never touch your agent environment. Learn more about how okoro works →

What your agent can do

  • Read boards, lists, and cards
  • Create cards and status columns
  • Update card titles, descriptions, due dates, and assignees
  • Move cards between columns
  • Delete cards

License

MIT — see LICENSE.