Mule API Design

Design, author, revise, or assess consumer-facing MuleSoft HTTP API contracts in RAML 1.0 or OpenAPI 3.0 using explicit resource, method, URI, data, error, security, compatibility, and governance decisions. Use for API design workshops, URL and naming guidance, new RAML/OAS contracts, contract-first changes, and contract-only reviews. Maintain RAML 0.8 or OAS 2.0 when required, but do not use for AsyncAPI, event schemas, Mule implementation, MUnit authoring, or general project review.

Avinava Updated
Mule Skills: evidence-backed MuleSoft agent workflows from design to release and operations

File contents

Avinava/mule-skills commit 1094eb3680

Frequently asked questions

npx get-skill add avinava/mule-api-design