Skip to content

Tool reference list_events

list_events

Upcoming Pirate Skills events, soonest first by date, with a link to each event page (a Forge session links the Forge page, where the seat is sold) and, for a signed-in person, whether they are registered. A Forge cohort appears only as its start – the first session of its Build or Grow part; its weekly sessions are never listed here. Present them in that date order, and give each event its one line from about – what it is and who it is for – so the person knows what they are looking at (an event without about is a one-off; its subtitle says it). When the person asks about their own Forge cohort or its sessions, use my_forge_sessions instead. cadence is how often that event's format meets – weekly only for the Forge (every week of a six-week phase), monthly for Vibe Coding Cologne, the Pirate Lab and AI Compass, quarterly for the Vibe Hackathon, one-off otherwise; give each event its own and never carry one event's cadence over to the others. when is the day and time to quote, in Berlin time; startsAt/endsAt are the same moment in UTC, for working with, never for quoting (the Captain's copy leaves them out, and gives a subtitle an earlier event already carried as null).

  • Public – no key needed
  • Read only

Input

FieldTypeRequiredNotes
typestringNoFilter by event type label, e.g. "Pirate Lab" or "Vibe Coding Cologne". Omit for all.
limitintegerNo – default 101–50

Over HTTP

curl -X POST https://pirateskills.com/api/public/agent/tools/list_events \
  -H "content-type: application/json" \
  -d '{}'

From the CLI

pirateskills run list_events --json '{}'

Over MCP

Call list_events on https://pirateskills.com/mcp. Connect over MCP

JSON Schema

{
  "type": "object",
  "properties": {
    "type": {
      "description": "Filter by event type label, e.g. \"Pirate Lab\" or \"Vibe Coding Cologne\". Omit for all.",
      "type": "string"
    },
    "limit": {
      "default": 10,
      "type": "integer",
      "minimum": 1,
      "maximum": 50
    }
  }
}