add-connector

📋 Shared Instructions: shared-instructions.md — Cross-cutting concerns.

Reference: connector-reference.md — Inline connection creation, Grep-first for large generated files.

Add Connector (Canonical)

This is the single implementation for all connector-binding skills.

Delegation model:

• Specialized /add-* skills (e.g., /add-office365, /add-workiq) delegate to this skill with presets
• If this skill is called from a wrapper, do not delegate back
• If this skill is called directly, complete the workflow without delegation

After the connector is added:

• If invoked via a specialized skill → Refer to that specialized skill's documentation for usage patterns (it was already provided)
• If invoked directly → Identify which specialized skill matches your use case and refer to its documentation for:
  • Correct import paths for generated services
  • Best practices for using the connector
  • Common patterns and implementation examples
  • Error handling guidance

This ensures developers have complete context for implementing features, not just adding the connector.

Workflow

1. Verify workspace + auth.
2. Resolve api-id (discover via ms connector list if the user didn't supply one), mode, and required arguments.
3. Run the matching ms app add ... command.
4. Run npm run build.
5. Record the binding in memory-bank.md if present.

---

Step 1: Verify Project + Env

test -f ms.config.json || { echo "Not in a Microsoft App workspace."; exit 1; }
BIN=ms
$BIN auth status

Step 2: Resolve Inputs

Collect:

• api-id (required — see resolution order below). Passed to the CLI via --connector <api-id>.
• mode = action | table (controls the --as flag). There is no procedure mode — binding a specific SQL stored procedure is not exposed by the current CLI (see note below).
• connection-id (optional interactive, required for non-interactive where applicable)