메뉴
Canonical add flow for Microsoft Managed Apps. Use when adding any connector through `ms app add connector` (with `--as table` or `--as action`), or when the user wants help discovering which connector / api-id to use.
기본적으로 소스를 먼저 확인하는 Prompt가 선택됩니다. 직접 명령으로 전환하거나 로컬 사본을 다운로드할 수도 있습니다.
설치 여부를 결정하기 전에 SKILL.md와 SkillsMP에 표시된 보조 파일을 읽어 보세요.
Codex 또는 Claude로 설치 이 Prompt를 복사해 Codex, Claude 또는 다른 어시스턴트에 붙여 넣으면 Skill 페이지를 검토하고 설치를 진행할 수 있습니다.
직접 명령은 검토 Prompt를 거치지 않습니다. 실행하기 전에 소스를 확인하세요.
npx skills add https://github.com/microsoft/managed-apps --skill add-connector명령은 한 줄로 유지됩니다. 복사하기 전에 가로로 스크롤해 전체 내용을 확인하세요.
로컬 사본을 원하시나요? SkillsMP에서 현재 제공할 수 있는 파일을 다운로드하세요.
SOC 직업 분류 기준
SKILL.md 표시 중
| name | add-connector |
| description | Canonical add flow for Microsoft Managed Apps. Use when adding any connector through `ms app add connector` (with `--as table` or `--as action`), or when the user wants help discovering which connector / api-id to use. |
| user-invocable | true |
| allowed-tools | Read, Edit, Write, Grep, Glob, Bash, AskUserQuestion, Skill |
| model | sonnet |
📋 Shared Instructions: shared-instructions.md — Cross-cutting concerns.
Reference: connector-reference.md — Inline connection creation, Grep-first for large generated files.
This is the single implementation for all connector-binding skills.
Delegation model:
/add-* skills (e.g., /add-office365, /add-workiq) delegate to this skill with presetsAfter the connector is added:
This ensures developers have complete context for implementing features, not just adding the connector.
api-id (discover via ms connector list if the user didn't supply one), mode, and required arguments.ms app add ... command.npm run build.memory-bank.md if present.test -f ms.config.json || { echo "Not in a Microsoft App workspace."; exit 1; }
BIN=ms
$BIN auth status
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)Additional by mode:
table: dataset, tableSQL stored procedures: the CLI has no
ms app add procedurecommand andms app add connectordoes not accept--sql-stored-procedure. You can still add the SQL connector as a table (--connector shared_sql --as table --dataset <db> --table <tbl>), but binding a specific stored procedure is not currently supported.
api-idTry sources in this order; stop at the first one that yields a value:
Wrapper preset. If invoked by a specialized /add-* skill (see "Common Presets" below), use the preset api-id and skip discovery.
Caller-supplied. If $ARGUMENTS includes an api-id (e.g., api-id=shared_office365), use it verbatim.
User-supplied verbatim string. If the user already typed an api-id (anything matching the shared_* / dataverse / microsoftcopilotstudio shape, or a string they explicitly call an api-id), use it.
Discovery via ms connector list. Do not ask the user to type an api-id from memory. Instead:
a. Ask one question: "Which connector do you need? (a short keyword like 'teams', 'sql', 'sharepoint', 'salesforce' is fine — I'll search the catalog.)" Capture the keyword as {term}.
b. Search the catalog:
$BIN connector list --search "<term>"
Parse the output into a short table (display name + api-id). If the result set is large (more than ~10 rows), narrow with a more specific term and re-run rather than dumping everything.
c. Present the candidates to the user via AskUserQuestion with the display names as choices (and api-ids in parentheses for transparency). Map their selection back to the api-id; never ask them to retype it.
d. If ms connector list --search "<term>" returns no results, fall back to ms connector list with no filter, surface a representative slice, and ask the user to refine the term. Do not proceed with a guessed api-id.
Validation. Once an api-id is chosen, confirm it's real before spending a build cycle on it: $BIN connector list-actions --connector <api-id> --search "" should succeed. If the CLI replies that the api-id is unknown, drop back to step 4 — don't keep retrying with the same value.
When user intent is about knowledge retrieval / grounded Microsoft 365 search summaries (for example: "analyze M365 content", "search my email and Teams", "knowledge-grounded query"), default to:
api-id: shared_a365copilotchatmcpmode: action⚠️ IMPORTANT: If the user is adding Work IQ via /add-connector, ask them to use /add-workiq instead.
Why: Work IQ uses MCP (Model Context Protocol), a stateful protocol that requires special handling. The /add-workiq skill provides:
McpSession wrapper class (handles session initialization, auto-retry, response parsing)Guidance: "I can add the connector, but for Work IQ I recommend using /add-workiq — it provides a production-ready McpSession class and comprehensive patterns to avoid common errors. Would you like to use /add-workiq instead?"
If they insist on /add-connector, proceed but after adding the connector, refer them to the /add-workiq skill documentation so they understand the McpSession requirement.
modeFor api-ids in the "Common Presets" table, use that table's mode. Otherwise ask the user one question, framed by what they want to do:
tableactionmode selects the --as flag. Tabular connectors (e.g. SharePoint, SQL) support both; in
non-interactive runs --as is required for them. Action-only connectors ignore --as.
If the caller is a wrapper skill, use wrapper presets as defaults and only ask for missing fields.
All modes use the single ms app add connector command; --as chooses table vs action. The
connector is passed via --connector (there is no --api-id flag).
Action mode
$BIN app add connector --connector <api-id> --as action
Table mode
$BIN app add connector --connector <api-id> --as table --dataset "<dataset>" --table "<table>"
The CLI resolves a connection inline (interactive picker, or --connection-id <id> / -c <id>
for a specific one). In non-interactive mode, if --connection-id is omitted the CLI prints the
available connections and then errors. Dataverse (--connector dataverse --as table) needs no
--connection-id. See connector-reference.md.
SQL stored procedures have no
ms app add procedurecommand and--sql-stored-procedureis not accepted byms app add connector; binding a specific stored procedure is not currently supported.
npm run build
If memory-bank.md exists, record api-id, mode, and parameters used.
| Wrapper skill | api-id | mode |
|---|---|---|
/add-dataverse | dataverse | table |
/add-sharepoint | shared_sharepointonline | table |
/add-excel | shared_excelonlinebusiness | table |
/add-office365 | shared_office365 | action |
/add-teams | shared_teams | action |
/add-onedrive | shared_onedriveforbusiness | action |
/add-azuredevops | shared_visualstudioteamservices | action |
/add-mcscopilot | microsoftcopilotstudio | action |
/add-workiq | shared_a365copilotchatmcp | action |