add-dataverse
Adds Microsoft Dataverse through `/add-data-source` with `api-id=shared_commondataserviceforapps`. Use for existing table bindings or Dataverse actions.
- License 许可
- MIT
- 最近更新
- 2026-11-06
- Stars
- ★ 36
- Forks
- 12
01 前言 Front Matter
- name
- add-dataverse
- description
- Adds Microsoft Dataverse through `/add-data-source` with `api-id=shared_commondataserviceforapps`. Use for existing table bindings or Dataverse actions.
- allowed-tools
- Read AskUserQuestion Skill
02 资源文件 4
- 参考文档references/api-authentication-reference.md5.0 KB
- 参考文档references/data-architecture-reference.md3.7 KB
- 参考文档references/dataverse-reference.md9.2 KB
- 参考文档references/table-management-reference.md15.5 KB
03 SKILL.md 正文
? Shared Instructions: shared-instructions.md — Cross-cutting concerns.
Add Dataverse (Wrapper)
This skill is a thin wrapper. Use /add-data-source as the single implementation path.
Delegation contract
Invoke /add-data-source with:
api-id:shared_commondataserviceforappsmode:tablefor a fixed, existing table. Useactionwhen users choose the organization URL or entity-set name inside the app.- Pass through known table logical names,
connection-id, anddataverse-environment-id.
In table mode, ask for missing table logical names before delegation. A logical name identifies the table, such as account.
In action mode, do not ask for a fixed table. The entity-set name identifies the API collection, such as accounts.
This skill binds existing tables. Do not create tables.
Use the exact connector ID. Both connectors have the display name "Microsoft Dataverse".
Do not substitute the older shared_commondataservice connector unless the user explicitly requests it.
04 同仓库更多 Skills
state
Store and query a Microsoft Managed App's built-in state and file attachments with `ms project state` CLI schema commands and generated TypeScript clients. First, with the user signed in to the CLI, run `ms feature status --name state --json`; if `feature.enabled` is not `true`, recommend an alternative connector or data source.
share
Shares (or unshares) a Microsoft App with users via `ms app share` / `ms app unshare`. Use when updating app access control.
share-link
Manages tenant-wide share links for a Microsoft App via `ms app share link create`, `ms app share link list`, and `ms app share link revoke`. Use when you want to distribute app access via a URL instead of named principals.
play
Opens a Microsoft App in the browser via `ms app play`. Use when opening the live deployed version or a cloud-hosted preview (main branch or specific commit SHA) without starting a local dev server.
list-connectors
Lists connectors available in the active environment — including whether each is allowed or blocked by your organization's policy — plus the connection-bound data sources already wired into a Microsoft App. Use when discovering connectors and their operations before adding data sources.
list-apps
Discovers managed apps in the active environment via `ms app list --json` and optional `ms app show --json`. Use when listing or locating apps.