Context user for permissions and metadata
Conversation ID for tracking
Optional dataData context to provide to Skip
Database connection for metadata queries
Optional forceForce refresh of entity metadata cache
Optional includeInclude callback API key and access token for Skip to call back to MJ
Optional includeInclude entity metadata in request
Optional includeInclude agent notes in request
Optional includeInclude saved queries in request
Optional includeInclude agent requests in request
Conversation messages (user/assistant)
Optional onCallback for streaming status updates during execution
Optional responsePhase: stringOptional payloadOptional payload data from a previous response (e.g., PRD in progress). This enables incremental artifact building where structured data accumulates throughout the conversation. When Skip returns a response with a payload, the client should pass that payload back in the next request.
Optional requestRequest phase (initial_request, clarify_question_response, etc.)
Options for making a Skip API call