What problem does it solve? Managing MotherDuck organization resources—service accounts, access tokens, Duckling instance sizing, and Dive embed sessions—requires careful use of the REST API with correct auth scopes, payload shapes, and token-handling rules that are easy to get wrong. ## Core Features & Use Cases - Service Account Provisioning: Create and delete service accounts via POST /v1/users with username validation rules and destructive-delete confirmation. - Token Lifecycle Management: Create, list, and revoke read-write and read-scaling access tokens with TTL limits and secure secret handling. - Duckling Configuration: Read and update read-write and read-scaling Duckling configs with instance sizes, flock sizes, and cooldown rules. - Dive Embed Sessions: Mint short-lived embed sessions for embedded analytics iframes. - Use Case: A platform engineer needs to provision a service account for a backend analytics app, mint a read-scaling token, and configure a 2-node read-scaling flock—this Skill walks through each authenticated curl call with validation limits and error handling. ## Quick Start Ask the assistant to create a MotherDuck service account named analytics_app and generate a read-write token for it using the REST API.
