learn-eventmodelers-api

Documents the eventmodelers.ai platform API endpoints, payloads, and element types for agents.

1|1|Updated Jul 19, 2026
One-click install
npx skills add https://github.com/Powerworks/K9DatingApp --skill learn-eventmodelers-api-powerworks
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: learn-eventmodelers-api
Source: https://github.com/Powerworks/K9DatingApp/tree/main/.claude/skills/learn-eventmodelers-api
Command: npx skills add https://github.com/Powerworks/K9DatingApp --skill learn-eventmodelers-api-powerworks

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Agents building event-modeled slices need accurate knowledge of the eventmodelers.ai platform API, but endpoint details, request payloads, and validation rules are scattered across the platform's source code. This Skill loads a complete API reference into context so agents can call, implement, or reason about any endpoint without guessing. ## Core Features & Use Cases - Full endpoint reference: Covers boards, chapters, timelines, lanes, cells, nodes, images, slices, GWT spec scenarios, config import, slice data, extensions, snapshots, and user management commands and projections. - Request/response schemas: Documents TypeScript payload shapes, headers (Authorization, x-user-id, x-causation-id), status codes, and placement/validation rules such as lane drop constraints and GWT scenario rules. - Element type catalog: Defines all board element types (COMMAND, EVENT, SCREEN, READMODEL, AUTOMATION, etc.) and slice node mappings for state-change, state-view, and automation slices. - Use Case: While running a slice codegen workflow, an agent needs to create a slice on a board; with this Skill loaded it knows to POST to /api/org/:orgId/boards/:boardId/timelines/:timelineId/slices with the correct type and node payload. ## Quick Start Load the eventmodelers API reference and show me how to create a state-change slice on my board.

Frequently Asked Questions about learn-eventmodelers-api

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I create a slice on an eventmodelers.ai board via the API?▼

POST to /api/org/:orgId/boards/:boardId/timelines/:timelineId/slices with a body containing type (state-change, state-view, or automation) and optional node overrides. The endpoint creates one column plus three automatically placed nodes mapped to actor, interaction, and swimlane lanes.

What element types does the eventmodelers platform support?▼

The platform supports MODEL_CONTEXT, CHAPTER, ACTOR, AUTOMATION, API, SCREEN, COMMAND, EVENT, SPEC_ERROR, TABLE, READMODEL, SCENARIO, LANE, and SLICE_BORDER. Each type has placement rules, such as COMMAND and READMODEL only dropping into interaction lanes.

What authentication headers does the eventmodelers API require?▼

Node operations require the x-user-id header, while snapshot and some other routes require a Supabase JWT in the Authorization header. Optional x-causation-id and x-correlation-id headers support event tracing.

How do I add a Given-When-Then scenario to a slice?▼

POST to /api/org/:orgId/boards/:boardId/contexts/:contextName/slices/:sliceName/scenarios with given, when, and then node ID arrays. Validation requires given to be EVENTs, when to hold at most one COMMAND, and then to be all EVENTs or exactly one READMODEL.

Why does dropping a node into a timeline cell return a 400 error?▼

The drop endpoint enforces placement rules per lane type: swimlane lanes accept only EVENTs, interaction lanes accept COMMAND and READMODEL, and actor lanes accept SCREEN and AUTOMATION. A 400 response means the node type violates the target lane's rule.

What are the limits on board snapshots in the eventmodelers platform?▼

Snapshots are limited to 3 per user, a maximum 30-day retention period, and a 50 MB file size cap. All snapshot endpoints require Supabase JWT authentication and support listing, creating, loading, sharing, and deleting.