[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M69AR0SGRQFYSFT071ZAS19V":3,"skill-same:01M69AR0SGRQFYSFT071ZAS19V":55},{"skillNo":4,"name":5,"nameZh":6,"description":7,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":16,"categories":17,"keywords":23,"publishedAt":27,"linkOnly":28,"markdownContent":29,"markdownBody":30,"frontMatter":31,"refName":32,"commitSha":33,"skillDirectory":34,"forksCount":35,"repositoryHtmlUrl":36,"repositoryHomepageUrl":6,"ownerHtmlUrl":37,"ownerBlogUrl":38,"ownerDescription":39,"updatedAt":40,"install":41,"resources":54},"01M69AR0SGRQFYSFT071ZAS19V","dv-security",null,"Security-role assignment, user access, application users, business units, and admin self-elevation in Dataverse environments. Use when the user wants to give someone access, grant a role, become an admin, or add a service principal.","microsoft\u002FDataverse-skills","microsoft","https:\u002F\u002Favatars.githubusercontent.com\u002Fu\u002F6154722?v=4","01M698VYDXZ6JW5WH3CRV650R8","Microsoft","01M69AQ9SHMSQ8KC4EKV8DZW2Y",258,"MIT","https:\u002F\u002Fgithub.com\u002Fmicrosoft\u002FDataverse-skills\u002Fblob\u002Fmain\u002F.github\u002Fplugins\u002Fdataverse\u002Fskills\u002Fdv-security\u002FSKILL.md",[18],{"categoryNo":19,"categoryName":20,"taxonomyType":21,"taxonomyTypeDesc":22},"01JBSEEDCAT000000000000023","Skill与智能体开发","SCENARIO","使用场景",[24,25,26],"security","dv security","dataverse","2026-11-10 10:12:30",false,"---\nname: dv-security\ndescription: Security-role assignment, user access, application users, business units, and admin self-elevation in Dataverse environments. Use when the user wants to give someone access, grant a role, become an admin, or add a service principal.\n---\n\n# Skill: Security — Role Assignment and Self-Elevation\n\n**This skill uses first-party CLIs — PAC CLI for role changes, Dataverse CLI to verify.** Do NOT write Python scripts for role operations.\n\n## Preview Before Running\n\nRole grants and self-elevate are destructive (they change security posture and are logged to Purview). Before running, preview the action in plain prose — target user, role, environment(s) — using placeholders (`\u003CENV_URL>`, `\u003CUSER_EMAIL>`) for anything unknown, and ask for confirmation and missing values in the same turn. Skip the raw `pac admin` block; the user shouldn't have to read CLI syntax to approve a security change.\n\n**Key principle:** the user should be able to evaluate what's about to happen from your first response. A bare *\"which environment?\"* fails that test; a one-line prose preview passes it.\n\n### Examples\n\n**Assign role (user given, env missing):**\n- ❌ \"Which environment should I target?\"\n- ✅ \"I'll assign **System Administrator** to `user@contoso.com` on `\u003CENV_URL>`. Confirm to proceed and provide the target environment URL (or 'all' to list and batch).\"\n\n**Admin access across all environments:**\n- ❌ \"Please provide your email address.\"\n- ✅ \"I'll list your environments, then assign **System Administrator** in parallel on each one for `\u003CYOUR_UPN>`. If `assign-user` fails on any environment, I'll fall back to self-elevate (logged to Purview) for that one. Confirm to proceed and provide your UPN.\"\n\n## Skill boundaries\n\n| Need | Use instead |\n|---|---|\n| Create or modify tables, columns, relationships | **dv-metadata** |\n| Manage org settings, audit, bulk delete, retention | **dv-admin** |\n| Query or read records | **dv-query** |\n| Write, update, or delete records | **dv-data** |\n| Tenant-level governance (DLP, env lifecycle) | `pac admin --help` |\n\n## Prerequisites\n\n- PAC CLI installed and authenticated (`pac auth create`)\n- System Administrator role in target environment (or Global\u002FPP\u002FD365 Admin for self-elevate)\n- Active auth profile: `pac auth list`\n- **Headless \u002F restricted-egress hosts**: SDK handles role \u002F user \u002F business-unit ops; service principal for PAC-only ops; verify egress with `python scripts\u002Fauth.py --check`. See `dv-connect\u002Freferences\u002Fheadless-hosts.md`.\n\n---\n\n## Assign a Security Role to a User\n\n```bash\npac admin assign-user --user \u003Cemail-or-object-id> --role \"System Administrator\" --environment \u003Curl>\n```\n\n### Arguments\n\n| Argument | Alias | Required | Description |\n|----------|-------|----------|-------------|\n| `--user` | `-u` | Yes | User email (UPN) or Azure AD object ID |\n| `--role` | `-r` | Yes | Security role name (e.g., `System Administrator`, `Basic User`) |\n| `--environment` | `-env` | Yes | Target environment URL or ID |\n| `--application-user` | `-au` | No | Treat user as an application user (service principal) |\n| `--business-unit` | `-bu` | No | Business unit ID. Defaults to the caller's business unit |\n\n---\n\n## Verify the assignment — exit code 0 is not proof\n\n`pac admin assign-user` **exits 0 even when it fails** (unresolved environment, wrong role name, unknown user). Never treat a clean exit as success.\n\n1. **Read the output, not just the exit code.** A failed run still exits 0 but prints an error (`environment ... not found`, `role ... does not exist`). Stop if the output contains an error.\n2. **Confirm against the exact `--environment` you used** — do not re-resolve or shorten it; a different id silently \"succeeds\" on the wrong org. Query the user's roles with a Dataverse CLI read:\n\n```bash\n# Resolve the user's systemuserid, then list their assigned roles.\n# --context carries plugin\u002Fskill\u002Fagent attribution on the managed CLI call.\ndataverse api request --target dataverse --method GET \\\n  --path \"\u002Fapi\u002Fdata\u002Fv9.2\u002Fsystemusers?%24select=systemuserid&%24filter=internalemailaddress eq 'user@contoso.com'\" \\\n  --environment \u003Csame-url-as-assign> \\\n  --context \"app=dataverse-skills\u002F\u003Cver>;skill=dv-security;agent=\u003Cagent>\"\ndataverse api request --target dataverse --method GET \\\n  --path \"\u002Fapi\u002Fdata\u002Fv9.2\u002Fsystemusers(\u003Csystemuserid>)\u002Fsystemuserroles_association?%24select=name\" \\\n  --environment \u003Csame-url-as-assign> \\\n  --context \"app=dataverse-skills\u002F\u003Cver>;skill=dv-security;agent=\u003Cagent>\"\n```\n\nIf the first query returns no row, the sign-in identity may live on `domainname` (the AAD UPN) rather than `internalemailaddress` (Primary Email) — retry with `%24filter=domainname eq '\u003Cupn>'`, or `azureactivedirectoryobjectid eq '\u003Cobjectid>'` when you assigned by object id. A missing row is not proof the grant failed.\n\nIf the target role is absent, the assignment did not take — re-run, read the output, or fall back to self-elevate.\n\n---\n\n## Batch Workflow: Assign Role Across Multiple Environments\n\nRun in parallel — never sequentially:\n\n```\nStep 1: pac admin list                                              -> Get all environments\nStep 2: Filter by type if needed (e.g., Developer, Sandbox)        -> Identify targets\nStep 3: Confirm with user — show list of target environments\nStep 4: Run ALL assignments in a single bash call:\n```\n\n```bash\npac admin assign-user --user user@contoso.com --role \"System Administrator\" --environment https:\u002F\u002Fdev1.crm.dynamics.com &\npac admin assign-user --user user@contoso.com --role \"System Administrator\" --environment https:\u002F\u002Fdev2.crm.dynamics.com &\npac admin assign-user --user user@contoso.com --role \"System Administrator\" --environment https:\u002F\u002Fdev3.crm.dynamics.com &\nwait\n```\n\n```\nStep 5: Verify each landed (exit 0 is not proof — see above), then report (\"Assigned + verified on 3\u002F3 environments\")\n```\n\n**Important**: Always confirm which environments will be affected before assigning roles, and verify each assignment landed — a clean exit code does not prove success.\n\n---\n\n## Tenant Admin Self-Elevation (Fallback)\n\n**Self-elevation is materially different from assigning a role to another user.** `pac admin assign-user \u003Cother>` grants privilege *to someone else*; `pac admin self-elevate` grants privilege *to the caller*. The risk profile and audit posture are different, so the confirmation protocol is stricter.\n\nIf `pac admin assign-user` fails with \"user has not been assigned any roles\", use:\n\n```bash\npac admin self-elevate --environment https:\u002F\u002Fmyorg.crm.dynamics.com\n```\n\n- Requires Global Admin, Power Platform Admin, or Dynamics 365 Admin\n- All elevations are logged to Microsoft Purview\n- Uses the active auth profile if `--environment` is omitted\n\n### Self-elevation confirmation protocol (stricter than assign-user)\n\nBefore running `pac admin self-elevate`, the agent MUST:\n\n1. **State the risk explicitly.** Include this wording (or equivalent) in the pre-run summary:\n   > \"This grants YOU System Administrator on `\u003Cenv>`. The action is logged to Microsoft Purview with your identity and timestamp.\"\n2. **Capture a reason.** Ask for a one-line reason — ticket ID, incident number, or a free-form note such as `\"dev sandbox access — no ticket\"`. Echo the reason back in the pre-run summary so the user sees what will be on the record.\n3. **Wait for an explicit confirmation AFTER the user has seen both (1) and (2).** Do NOT accept a bare \"yes\" given before the risk statement and reason are on screen.\n4. **Do NOT silently fall back.** If `pac admin assign-user` fails, surface the failure first, then offer `self-elevate` with this protocol — never chain them automatically.\n\n**Flow**: Always try `pac admin assign-user` first. `admin self-elevate` is the documented fallback, gated by the protocol above.\n\n**CLI fallback**: If `pac admin self-elevate` errors out, self-elevate manually via **Power Platform Admin Center** → select the environment → **Access** → **System Administrator role**. All elevations are still logged to Purview. (In PAC CLI 2.6.4 the command fails with `bolt.authentication.http.AuthenticatedClientException` \u002F `ApiVersionInvalid` because the CLI sends an empty `api-version=` to the backend.)\n\n---\n\n## Safety Rules\n\n- **Always confirm** before assigning System Administrator role\n- Show the list of target environments before batch operations\n- Self-elevation is logged and auditable — warn the user\n","# Skill: Security — Role Assignment and Self-Elevation\n\n**This skill uses first-party CLIs — PAC CLI for role changes, Dataverse CLI to verify.** Do NOT write Python scripts for role operations.\n\n## Preview Before Running\n\nRole grants and self-elevate are destructive (they change security posture and are logged to Purview). Before running, preview the action in plain prose — target user, role, environment(s) — using placeholders (`\u003CENV_URL>`, `\u003CUSER_EMAIL>`) for anything unknown, and ask for confirmation and missing values in the same turn. Skip the raw `pac admin` block; the user shouldn't have to read CLI syntax to approve a security change.\n\n**Key principle:** the user should be able to evaluate what's about to happen from your first response. A bare *\"which environment?\"* fails that test; a one-line prose preview passes it.\n\n### Examples\n\n**Assign role (user given, env missing):**\n- ❌ \"Which environment should I target?\"\n- ✅ \"I'll assign **System Administrator** to `user@contoso.com` on `\u003CENV_URL>`. Confirm to proceed and provide the target environment URL (or 'all' to list and batch).\"\n\n**Admin access across all environments:**\n- ❌ \"Please provide your email address.\"\n- ✅ \"I'll list your environments, then assign **System Administrator** in parallel on each one for `\u003CYOUR_UPN>`. If `assign-user` fails on any environment, I'll fall back to self-elevate (logged to Purview) for that one. Confirm to proceed and provide your UPN.\"\n\n## Skill boundaries\n\n| Need | Use instead |\n|---|---|\n| Create or modify tables, columns, relationships | **dv-metadata** |\n| Manage org settings, audit, bulk delete, retention | **dv-admin** |\n| Query or read records | **dv-query** |\n| Write, update, or delete records | **dv-data** |\n| Tenant-level governance (DLP, env lifecycle) | `pac admin --help` |\n\n## Prerequisites\n\n- PAC CLI installed and authenticated (`pac auth create`)\n- System Administrator role in target environment (or Global\u002FPP\u002FD365 Admin for self-elevate)\n- Active auth profile: `pac auth list`\n- **Headless \u002F restricted-egress hosts**: SDK handles role \u002F user \u002F business-unit ops; service principal for PAC-only ops; verify egress with `python scripts\u002Fauth.py --check`. See `dv-connect\u002Freferences\u002Fheadless-hosts.md`.\n\n---\n\n## Assign a Security Role to a User\n\n```bash\npac admin assign-user --user \u003Cemail-or-object-id> --role \"System Administrator\" --environment \u003Curl>\n```\n\n### Arguments\n\n| Argument | Alias | Required | Description |\n|----------|-------|----------|-------------|\n| `--user` | `-u` | Yes | User email (UPN) or Azure AD object ID |\n| `--role` | `-r` | Yes | Security role name (e.g., `System Administrator`, `Basic User`) |\n| `--environment` | `-env` | Yes | Target environment URL or ID |\n| `--application-user` | `-au` | No | Treat user as an application user (service principal) |\n| `--business-unit` | `-bu` | No | Business unit ID. Defaults to the caller's business unit |\n\n---\n\n## Verify the assignment — exit code 0 is not proof\n\n`pac admin assign-user` **exits 0 even when it fails** (unresolved environment, wrong role name, unknown user). Never treat a clean exit as success.\n\n1. **Read the output, not just the exit code.** A failed run still exits 0 but prints an error (`environment ... not found`, `role ... does not exist`). Stop if the output contains an error.\n2. **Confirm against the exact `--environment` you used** — do not re-resolve or shorten it; a different id silently \"succeeds\" on the wrong org. Query the user's roles with a Dataverse CLI read:\n\n```bash\n# Resolve the user's systemuserid, then list their assigned roles.\n# --context carries plugin\u002Fskill\u002Fagent attribution on the managed CLI call.\ndataverse api request --target dataverse --method GET \\\n  --path \"\u002Fapi\u002Fdata\u002Fv9.2\u002Fsystemusers?%24select=systemuserid&%24filter=internalemailaddress eq 'user@contoso.com'\" \\\n  --environment \u003Csame-url-as-assign> \\\n  --context \"app=dataverse-skills\u002F\u003Cver>;skill=dv-security;agent=\u003Cagent>\"\ndataverse api request --target dataverse --method GET \\\n  --path \"\u002Fapi\u002Fdata\u002Fv9.2\u002Fsystemusers(\u003Csystemuserid>)\u002Fsystemuserroles_association?%24select=name\" \\\n  --environment \u003Csame-url-as-assign> \\\n  --context \"app=dataverse-skills\u002F\u003Cver>;skill=dv-security;agent=\u003Cagent>\"\n```\n\nIf the first query returns no row, the sign-in identity may live on `domainname` (the AAD UPN) rather than `internalemailaddress` (Primary Email) — retry with `%24filter=domainname eq '\u003Cupn>'`, or `azureactivedirectoryobjectid eq '\u003Cobjectid>'` when you assigned by object id. A missing row is not proof the grant failed.\n\nIf the target role is absent, the assignment did not take — re-run, read the output, or fall back to self-elevate.\n\n---\n\n## Batch Workflow: Assign Role Across Multiple Environments\n\nRun in parallel — never sequentially:\n\n```\nStep 1: pac admin list                                              -> Get all environments\nStep 2: Filter by type if needed (e.g., Developer, Sandbox)        -> Identify targets\nStep 3: Confirm with user — show list of target environments\nStep 4: Run ALL assignments in a single bash call:\n```\n\n```bash\npac admin assign-user --user user@contoso.com --role \"System Administrator\" --environment https:\u002F\u002Fdev1.crm.dynamics.com &\npac admin assign-user --user user@contoso.com --role \"System Administrator\" --environment https:\u002F\u002Fdev2.crm.dynamics.com &\npac admin assign-user --user user@contoso.com --role \"System Administrator\" --environment https:\u002F\u002Fdev3.crm.dynamics.com &\nwait\n```\n\n```\nStep 5: Verify each landed (exit 0 is not proof — see above), then report (\"Assigned + verified on 3\u002F3 environments\")\n```\n\n**Important**: Always confirm which environments will be affected before assigning roles, and verify each assignment landed — a clean exit code does not prove success.\n\n---\n\n## Tenant Admin Self-Elevation (Fallback)\n\n**Self-elevation is materially different from assigning a role to another user.** `pac admin assign-user \u003Cother>` grants privilege *to someone else*; `pac admin self-elevate` grants privilege *to the caller*. The risk profile and audit posture are different, so the confirmation protocol is stricter.\n\nIf `pac admin assign-user` fails with \"user has not been assigned any roles\", use:\n\n```bash\npac admin self-elevate --environment https:\u002F\u002Fmyorg.crm.dynamics.com\n```\n\n- Requires Global Admin, Power Platform Admin, or Dynamics 365 Admin\n- All elevations are logged to Microsoft Purview\n- Uses the active auth profile if `--environment` is omitted\n\n### Self-elevation confirmation protocol (stricter than assign-user)\n\nBefore running `pac admin self-elevate`, the agent MUST:\n\n1. **State the risk explicitly.** Include this wording (or equivalent) in the pre-run summary:\n   > \"This grants YOU System Administrator on `\u003Cenv>`. The action is logged to Microsoft Purview with your identity and timestamp.\"\n2. **Capture a reason.** Ask for a one-line reason — ticket ID, incident number, or a free-form note such as `\"dev sandbox access — no ticket\"`. Echo the reason back in the pre-run summary so the user sees what will be on the record.\n3. **Wait for an explicit confirmation AFTER the user has seen both (1) and (2).** Do NOT accept a bare \"yes\" given before the risk statement and reason are on screen.\n4. **Do NOT silently fall back.** If `pac admin assign-user` fails, surface the failure first, then offer `self-elevate` with this protocol — never chain them automatically.\n\n**Flow**: Always try `pac admin assign-user` first. `admin self-elevate` is the documented fallback, gated by the protocol above.\n\n**CLI fallback**: If `pac admin self-elevate` errors out, self-elevate manually via **Power Platform Admin Center** → select the environment → **Access** → **System Administrator role**. All elevations are still logged to Purview. (In PAC CLI 2.6.4 the command fails with `bolt.authentication.http.AuthenticatedClientException` \u002F `ApiVersionInvalid` because the CLI sends an empty `api-version=` to the backend.)\n\n---\n\n## Safety Rules\n\n- **Always confirm** before assigning System Administrator role\n- Show the list of target environments before batch operations\n- Self-elevation is logged and auditable — warn the user\n",{"name":5,"description":7},"main","108370ef5d61358835af476c22c555dadefc55d0",".github\u002Fplugins\u002Fdataverse\u002Fskills\u002Fdv-security",65,"https:\u002F\u002Fgithub.com\u002Fmicrosoft\u002FDataverse-skills","https:\u002F\u002Fgithub.com\u002Fmicrosoft","https:\u002F\u002Fopensource.microsoft.com","Open source projects and samples from Microsoft","2026-11-14 02:05:34",{"source":8,"skillName":5,"commands":42,"prompt":52,"zipAvailable":53},[43,46,49],{"tool":44,"command":45},"npx","npx skills add microsoft\u002FDataverse-skills --skill dv-security",{"tool":47,"command":48},"bunx","bunx skills add microsoft\u002FDataverse-skills --skill dv-security",{"tool":50,"command":51},"pnpm","pnpm dlx skills add microsoft\u002FDataverse-skills --skill dv-security","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002Fmicrosoft\u002FDataverse-skills\u002Fblob\u002Fmain\u002F.github\u002Fplugins\u002Fdataverse\u002Fskills\u002Fdv-security\u002FSKILL.md",true,[],[56,95,124,136,167,191],{"skillNo":57,"name":58,"nameZh":6,"description":59,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":60,"categories":61,"keywords":74,"publishedAt":27},"01M6PJ8NCTZS7PZ5AVHXERS10A","erp-sql","Temporary Finance and Operations SQL access and bounded physical-table reads for unified development environments (UDEs) only, requiring the environment System administrator (sysAdmin) role. Use when the user explicitly requests direct ERP SQL access, a temporary SQL password, a sqlcmd connection, or a table read in an established ERP SQL workflow.","https:\u002F\u002Fgithub.com\u002Fmicrosoft\u002FDataverse-skills\u002Fblob\u002Fmain\u002F.github\u002Fplugins\u002Fdataverse\u002Fskills\u002Ferp-sql\u002FSKILL.md",[62,65,66,71],{"categoryNo":63,"categoryName":64,"taxonomyType":21,"taxonomyTypeDesc":22},"01JBSEEDCAT000000000000010","后端与接口",{"categoryNo":19,"categoryName":20,"taxonomyType":21,"taxonomyTypeDesc":22},{"categoryNo":67,"categoryName":68,"taxonomyType":69,"taxonomyTypeDesc":70},"01JBSEEDCAT000000000000033","数据分析师","PROFESSION","适用职业",{"categoryNo":72,"categoryName":73,"taxonomyType":69,"taxonomyTypeDesc":70},"01JBSEEDCAT000000000000040","财务",[75,76,77,78,79,80,81,82,83,84,85,86,87,88,89,90,91,92,93,94],"erp sql","sql","erp","use","password","requests","operations","only","development","table","bounded","environments","direct","read","workflow","access","environment","system","sqlcmd","for",{"skillNo":96,"name":97,"nameZh":6,"description":98,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":99,"categories":100,"keywords":106,"publishedAt":27},"01M69AR6XKM814KPH4PEEQE7R7","erp-xpp","X++ code development lifecycle for Finance and Operations — scaffold models, author classes, custom services\u002FAPIs, and data entities, install matching SDKs, compile deployable packages, deploy packages, synchronize databases, and verify deployed artifacts. Use when the user explicitly requests creating, building, compiling, packaging, deploying, DB-syncing, or verifying X++ customizations, or an end-to-end ERP code change.","https:\u002F\u002Fgithub.com\u002Fmicrosoft\u002FDataverse-skills\u002Fblob\u002Fmain\u002F.github\u002Fplugins\u002Fdataverse\u002Fskills\u002Ferp-xpp\u002FSKILL.md",[101,104,105],{"categoryNo":102,"categoryName":103,"taxonomyType":21,"taxonomyTypeDesc":22},"01JBSEEDCAT000000000000011","运维与部署",{"categoryNo":19,"categoryName":20,"taxonomyType":21,"taxonomyTypeDesc":22},{"categoryNo":72,"categoryName":73,"taxonomyType":69,"taxonomyTypeDesc":70},[107,108,77,109,110,111,112,113,114,115,116,117,94,118,119,120,83,121,122,123],"xpp","erp xpp","db","compiling","data","install","packages","sdks","code","end","packaging","databases","development lifecycle","change","custom","lifecycle","compile",{"skillNo":125,"name":126,"nameZh":6,"description":127,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":128,"categories":129,"keywords":131,"publishedAt":27},"01M69AR3MEKCYBD8FEKK80KJ5B","dv-solution","Dataverse solution lifecycle — create, export, import, promote across environments, and validate deployments. Use when the user wants to package customizations, deploy to another environment, or move work between dev \u002F test \u002F prod.","https:\u002F\u002Fgithub.com\u002Fmicrosoft\u002FDataverse-skills\u002Fblob\u002Fmain\u002F.github\u002Fplugins\u002Fdataverse\u002Fskills\u002Fdv-solution\u002FSKILL.md",[130],{"categoryNo":19,"categoryName":20,"taxonomyType":21,"taxonomyTypeDesc":22},[132,133,134,135,26],"dv solution","test","deploy","validate",{"skillNo":137,"name":138,"nameZh":6,"description":139,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":140,"categories":141,"keywords":149,"publishedAt":27},"01M69AQX9TXX472D6Q59RYSMXY","dv-query","Bulk reads, multi-page iteration, and analytics over Dataverse data. Use when the user wants to read, list, filter, aggregate, group, join, or analyze records — including pandas DataFrame workflows and notebook exploration. Also covers ERP (Finance and Operations \u002F F&O) business-data reads and runtime entity, schema, or action discovery; load dv-overview first, then this skill.","https:\u002F\u002Fgithub.com\u002Fmicrosoft\u002FDataverse-skills\u002Fblob\u002Fmain\u002F.github\u002Fplugins\u002Fdataverse\u002Fskills\u002Fdv-query\u002FSKILL.md",[142,143,146,147,148],{"categoryNo":63,"categoryName":64,"taxonomyType":21,"taxonomyTypeDesc":22},{"categoryNo":144,"categoryName":145,"taxonomyType":21,"taxonomyTypeDesc":22},"01JBSEEDCAT000000000000013","分析与可视化",{"categoryNo":19,"categoryName":20,"taxonomyType":21,"taxonomyTypeDesc":22},{"categoryNo":67,"categoryName":68,"taxonomyType":69,"taxonomyTypeDesc":70},{"categoryNo":72,"categoryName":73,"taxonomyType":69,"taxonomyTypeDesc":70},[150,151,152,88,153,154,155,78,156,157,158,159,160,161,162,163,164,165,26,166],"dv query","query","analytics","pandas","bulk","user","records","discovery","list","dataframe","analyze","filter","join","notebook","iteration","exploration","workflows",{"skillNo":168,"name":169,"nameZh":6,"description":170,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":171,"categories":172,"keywords":175,"publishedAt":27},"01M69AQSP7EV1XGQAA69Y9MJ8Y","dv-overview","Foundational cross-cutting context for Dataverse \u002F Power Platform work — scope and the skill map, the tool-capability reference, the safety rules, and the safe change lifecycle. Use when the user mentions Dataverse, Dynamics 365, Power Platform, CRM, or ERP; load this first for orientation. Specialist skills self-route via their own frontmatter triggers. Finance and Operations \u002F F&O business-data requests also require this skill first, then dv-query for reads.","https:\u002F\u002Fgithub.com\u002Fmicrosoft\u002FDataverse-skills\u002Fblob\u002Fmain\u002F.github\u002Fplugins\u002Fdataverse\u002Fskills\u002Fdv-overview\u002FSKILL.md",[173,174],{"categoryNo":19,"categoryName":20,"taxonomyType":21,"taxonomyTypeDesc":22},{"categoryNo":72,"categoryName":73,"taxonomyType":69,"taxonomyTypeDesc":70},[176,177,151,77,178,179,180,111,181,182,183,184,185,186,187,188,189,26,190,120],"dv overview","overview","capability","context","frontmatter","Safety","crm","work","route","self","map","skill map","scope","power","safe",{"skillNo":192,"name":193,"nameZh":6,"description":194,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":195,"categories":196,"keywords":198,"publishedAt":27},"01M69AQP3WCSN3K3DCRD0E2PFF","dv-metadata","Dataverse schema authoring and inspection — tables, columns, relationships, forms, and views. Use when the user wants to define, evolve, or inspect the data model — add a column, create a table, set up a lookup, customize a form, build a view, or list existing columns and relationships.","https:\u002F\u002Fgithub.com\u002Fmicrosoft\u002FDataverse-skills\u002Fblob\u002Fmain\u002F.github\u002Fplugins\u002Fdataverse\u002Fskills\u002Fdv-metadata\u002FSKILL.md",[197],{"categoryNo":19,"categoryName":20,"taxonomyType":21,"taxonomyTypeDesc":22},[199,200,26],"dv metadata","customize"]