# generate-connectivity-knowledge

Generate connectivity knowledge for a SaaS API when no dedicated Mule connector exists. Researches the API from user-defined use cases and documentation, produces an OpenAPI 3.0 specification, asks the user for credentials, validates every operation against the live API with auto-fix, and writes connectivity-schema/<apiName>/ (api-reference.md + <apiName>.yaml + config.properties). The resulting folder feeds downstream HTTP-Connector flow generation in build-mule-integration so an HTTP fallback path inherits the same auth, pagination, and entity awareness a dedicated connector would carry. Use when the user's prompt names a SaaS for which no Exchange connector was found, or asks to "generate api knowledge", "research a SaaS API", "build connectivity schema", "validate spec against live API", or similar phrasings.

- **Skill Source:** [SKILL.md](https://dev-portal.mulesoft.com/skills/mule-development/generate-connectivity-knowledge/SKILL.md)

## Steps
### Step 1: Step 1: Inputs

### Step 2: Step 2: Documentation Discovery

### Step 3: Step 3: Primary Endpoint Identification

### Step 4: Step 4: Primary Entity Extraction

### Step 5: Step 5: CRUD Completion

### Step 6: Step 6: Dependency Analysis

### Step 7: Step 7: Secondary Entity CRUD

### Step 8: Step 8: Action Plan

### Step 9: Step 9: Deep Research

### Step 10: Step 10: api-reference.md Consolidation

### Step 11: Step 11: OpenAPI 3.0 Spec Generation

### Step 12: Step 12: Live Validation — Prerequisites

### Step 13: Step 13: Live Validation — Loop

### Step 14: Step 14: Final Report and Knowledge Ready