[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M699M0NYCHFS29RSBP9M462K":3,"skill-same:01M699M0NYCHFS29RSBP9M462K":84},{"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":44,"linkOnly":45,"markdownContent":46,"markdownBody":47,"frontMatter":48,"refName":51,"commitSha":52,"skillDirectory":53,"forksCount":54,"repositoryHtmlUrl":55,"repositoryHomepageUrl":56,"ownerHtmlUrl":57,"ownerBlogUrl":58,"ownerDescription":59,"updatedAt":60,"install":61,"resources":73},"01M699M0NYCHFS29RSBP9M462K","create-code-app",null,"Creates Power Apps code apps using React and Vite. Use when building code apps, scaffolding projects, or deploying to Power Platform.","microsoft\u002Fpower-platform-skills","microsoft","https:\u002F\u002Favatars.githubusercontent.com\u002Fu\u002F6154722?v=4","01M698VYDXZ6JW5WH3CRV650R8","Microsoft","01M699JVYJFB75D9JM70BN4H0Q",1149,"MIT","https:\u002F\u002Fgithub.com\u002Fmicrosoft\u002Fpower-platform-skills\u002Fblob\u002Fmain\u002Fplugins\u002Fcode-apps\u002Fskills\u002Fcreate-code-app\u002FSKILL.md",[18],{"categoryNo":19,"categoryName":20,"taxonomyType":21,"taxonomyTypeDesc":22},"01JBSEEDCAT000000000000030","开发工程师","PROFESSION","适用职业",[24,25,26,27,28,29,30,31,32,33,34,35,36,37,38,39,40,41,42,43],"app","code","create","create code app","apps","true","vite","platform","opus","edit","write","read","Bash","when","lsp","scaffolding","power","projects","react","code apps","2026-11-10 10:12:30",false,"---\nname: create-code-app\ndescription: Creates Power Apps code apps using React and Vite. Use when building code apps, scaffolding projects, or deploying to Power Platform.\nuser-invocable: true\nallowed-tools: Read, Edit, Write, Grep, Glob, Bash, LSP, TaskCreate, TaskUpdate, TaskList, TaskGet, AskUserQuestion, Skill, EnterPlanMode, ExitPlanMode\nmodel: opus\n---\n\n**? Shared Instructions: [shared-instructions.md](..\u002F..\u002Fshared\u002Fshared-instructions.md)** - Cross-cutting concerns.\n\n**References:**\n\n- [prerequisites-reference.md](.\u002Freferences\u002Fprerequisites-reference.md) - Prerequisites and required permissions\n- [troubleshooting.md](.\u002Freferences\u002Ftroubleshooting.md) - Common issues, npm scripts, resources\n\n# Create Power Apps Code App\n\n## Workflow\n\n1. Prerequisites → 2. Gather Requirements → 3. Plan → 4. Scaffold → 5. Initialize → 6. Build & Deploy (baseline) → 7. Add Data Sources → 8. Implement App → 9. Final Build & Deploy → 10. Summary\n\n---\n\n### Step 0: Check Memory Bank\n\nCheck for `memory-bank.md` per [shared-instructions.md](..\u002F..\u002Fshared\u002Fshared-instructions.md). Skip completed steps.\n\n### Step 1: Validate Prerequisites\n\nRun prerequisite checks **first** -- no point gathering requirements if the environment isn't ready. See [prerequisites-reference.md](.\u002Freferences\u002Fprerequisites-reference.md) for details.\n\nCheck Node.js and Git (runs natively in bash):\n\n```bash\nnode --version   # Must be v22+\ngit --version    # Optional but recommended\n```\n\n- **Missing Node.js**: Report \"Install Node.js v22+ from https:\u002F\u002Fnodejs.org\u002F\" and STOP.\n- **Node.js below v22**: Report \"Node.js 22+ is required. Please upgrade or switch with `nvm use 22`.\" and STOP.\n- **Missing Git**: Report \"Recommended but optional.\" Continue if approved.\n- **All present**: Report versions and proceed.\n\n\n### Step 2: Gather Requirements\n\n**Skip questions the user already answered in their initial instruction.**\n\n**If the user has not described what they want to build** (i.e., `\u002Fcreate-code-app` was invoked with no arguments or a vague prompt), start with a single open-ended question before asking anything else:\n\n> \"What would you like to build? Describe it in your own words — what it does, who uses it, and what problem it solves.\"\n\nWait for their answer. Use it to frame all follow-up questions. Do NOT present a multiple-choice list of app types before the user has described their idea.\n\nOnce you have their description:\n\n1. Confirm the app name and clarify the purpose if needed\n2. Ask about data -- focus on **what the app needs to do**, not specific technologies:\n   - \"What data does your app need to work with?\" (e.g., company emails, project tasks, custom business records)\n   - \"Does your app need to search existing information, manage its own data, or both?\"\n   - Based on their answers, recommend the best approach:\n     - **Store and manage custom business data** (tables, forms, CRUD) → Dataverse (`\u002Fadd-dataverse`)\n     - **Interact with specific services** (send emails, post messages, manage files) → the appropriate connector\n     - **Search M365 data or get AI-powered answers** (emails, files, people, company knowledge) → Work IQ (`\u002Fadd-workiq`)\n   - If they mention existing Dataverse tables, SharePoint lists, or connectors by name, use those directly\n3. Ask about UI requirements: key screens, layout, interactions, theme preference\n4. Ask any clarifying questions now -- resolve all ambiguity before entering plan mode\n\n### Step 3: Plan\n\n1. Enter plan mode with `EnterPlanMode`\n2. Design the full implementation approach:\n   - Which `\u002Fadd-*` skills to run for data sources\n   - App architecture: components, pages, state management\n   - Feature list with priority order\n3. Present plan for approval, include `allowedPrompts` from [prerequisites-reference.md](.\u002Freferences\u002Fprerequisites-reference.md)\n4. Exit plan mode with `ExitPlanMode` when approved\n\n### Step 4: Scaffold\n\nAsk the user for a folder name. Default to `powerapps-{app-name-slugified}-{timestamp}` if they don't have a preference.\n\n**IMPORTANT: Use `npx degit` to download the template. Do NOT use `git clone`, do NOT manually create files, do NOT download from GitHub UI. `degit` downloads the template without git history.**\n\n```bash\nnpx degit microsoft\u002FPowerAppsCodeApps\u002Ftemplates\u002Fvite {folder} --force\ncd {folder}\nnpm install\nnpm install --save-dev \"@microsoft\u002Fpower-apps-cli@^1.3.0\"\n```\n\n**Notes:**\n\n- Use `--force` to overwrite if the directory already has files (e.g., `.claude` from a planning session)\n- If targeting an existing directory, use `.` as the folder name: `npx degit microsoft\u002FPowerAppsCodeApps\u002Ftemplates\u002Fvite . --force`\n- If `npx degit` fails (network issues, npm not found), retry once, then ask the user to run manually\n- The template doesn't include the Power Apps CLI, so install it into the project as a dev dependency (not globally). Version 1.3.0 or later lets the connector skills find or create connections without asking for a connection ID.\n\nVerify: `package.json` exists, `node_modules\u002F` created, and `@microsoft\u002Fpower-apps-cli` is listed in `devDependencies`. Then resolve the CLI per [cli-binary.md](..\u002F..\u002Fshared\u002Fcli-binary.md); it should resolve to `pa` with `PA_INLINE_CONNECTIONS=yes`.\n\n### Step 5: Initialize\n\n> Resolve the CLI first (see [cli-binary.md](..\u002F..\u002Fshared\u002Fcli-binary.md)): run as `$PA app init …` (`npx --no-install pa …`), never a bare `pa`. On `power-apps`-only projects, translate to `power-apps init …` (the `init` verb and its `-n`\u002F`-e` flags are unchanged on both binaries).\n\n```bash\npa app init -n '{user-provided-app-name}' -e \u003Cenvironment-id>\n```\n\n**Finding the environment ID:** It's the GUID in the make.powerapps.com URL: `https:\u002F\u002Fmake.powerapps.com\u002Fenvironments\u002F\u003Cenv-id>\u002Fhome`. If you don't pass `-e`, the CLI will prompt for it interactively.\n\n**Authentication:** On first run, a browser window opens for Microsoft sign-in. Complete the login and the command continues. No separate auth setup is needed.\n\nSee [preferred-environment.md](..\u002F..\u002Fshared\u002Fpreferred-environment.md) for environment selection details.\n\n**`pa app init` failure:**\n\n- Non-zero exit: Report the exact output and STOP. Do not continue to Step 6.\n- \"environmentId not found\" or environment validation error: Verify the environment ID is correct and the user has maker permissions in that environment, then retry.\n- Example: _\"The `pa app init` command failed: `[error text]`. Please check that environment ID `32a51012-...` is correct and that you have maker permissions in that environment.\"_\n\n**Critical:** Read `power.config.json` after init and verify `environmentId` is set correctly.\n\n### Step 6: Build & Deploy (baseline)\n\n> **Pre-approved**: This baseline deploy is part of the scaffold flow and does not require a separate confirmation prompt.\n\nBuild and deploy the bare template to verify the pipeline works before adding data sources.\n\n```bash\nnpm run build\n```\n\nVerify `dist\u002F` folder created with `index.html` and `assets\u002F`.\n\n> Deploy via the resolved CLI: `$PA app push` on `pa`, or `power-apps push` on `power-apps`-only projects (see [cli-binary.md](..\u002F..\u002Fshared\u002Fcli-binary.md)).\n\n```bash\npa app push\n```\n\n**Capture app URL** from output: `https:\u002F\u002Fapps.powerapps.com\u002Fplay\u002Fe\u002F{env-id}\u002Fapp\u002F{app-id}`\n\n**Common deploy errors:** See [troubleshooting.md](.\u002Freferences\u002Ftroubleshooting.md).\n\n**Create or update `memory-bank.md` in the project root now** -- don't wait until the end. Include:\n\n- Project path, app name, environment ID, app URL\n- Completed steps: scaffold, init, baseline deploy\n- Data sources planned (from Step 2)\n\nThis ensures progress is saved even if the session ends unexpectedly.\n\n### Step 7: Add Data Sources\n\nInvoke the `\u002Fadd-*` skills identified in the plan (Step 3). Run each in sequence. **Pass context as arguments** so sub-skills skip redundant questions (project path, connector name, etc.):\n\n| App needs to...                            | Invoke             |\n| ------------------------------------------ | ------------------ |\n| Store\u002Fmanage custom business data          | `\u002Fadd-dataverse`   |\n| Track work items, bugs, pipelines          | `\u002Fadd-azuredevops` |\n| Send or read Teams messages                | `\u002Fadd-teams`       |\n| Read\u002Fwrite Excel spreadsheet data          | `\u002Fadd-excel`       |\n| Upload, download, or manage files          | `\u002Fadd-onedrive`    |\n| Work with SharePoint lists or docs         | `\u002Fadd-sharepoint`  |\n| Send emails, read inbox, manage calendar   | `\u002Fadd-office365`   |\n| Invoke a Copilot Studio agent              | `\u002Fadd-mcscopilot`  |\n| Search M365 data or get AI-powered answers | `\u002Fadd-workiq`      |\n| Connect to another service                 | `\u002Fadd-connector`   |\n\n**Connections:** every connector except Dataverse needs a connection. With the CLI 1.3.0+ installed in Step 4, the connector skills find or create it themselves: they tell the user first that a connection may be created with the user's account, and ask before running `--use-sso` or `pa connection create`. See [connector-reference.md](..\u002F..\u002Fshared\u002Fconnector-reference.md#connections).\n\nEach `\u002Fadd-*` skill runs `npm run build` to catch errors. Do NOT deploy yet.\n\n**If no data sources needed:** Skip to Step 8.\n\n### Step 8: Implement App\n\n**This is the core step.** Build the actual app features described in the plan from Step 3.\n\n1. **Review generated services**: Use `Grep` to find methods in generated service files (they can be very large -- see [connector-reference.md](..\u002F..\u002Fshared\u002Fconnector-reference.md#inspecting-large-generated-files)). Do NOT read entire generated files.\n2. **Build components**: Create React components for each screen\u002Ffeature in the plan\n3. **Connect data**: Wire components to generated services (use `*Service.getAll()`, `*Service.create()`, etc.)\n4. **Apply theme**: Use the user's theme preference (default: dark theme per development standards)\n5. **Iterate with user**: Show progress, ask for feedback, adjust as needed\n\n**Key rules:**\n\n- Use generated services for all data access -- never use fetch\u002Faxios directly\n- Read [dataverse-reference.md](..\u002Fadd-dataverse\u002Freferences\u002Fdataverse-reference.md) if working with Dataverse (picklist fields, virtual fields, lookups have critical gotchas)\n- Remove unused imports before building (TS6133 strict mode)\n- Don't edit files in `src\u002Fgenerated\u002F` unless fixing known issues\n\n### Step 9: Final Build & Deploy\n\n```bash\nnpm run build\n```\n\nFix any TypeScript errors. Verify `dist\u002F` contains the updated app.\n\nAsk the user: _\"Ready to deploy to [environment name]? This will update the live app.\"_ Wait for explicit confirmation before proceeding.\n\n```bash\npa app push\n```\n\n### Step 10: Summary\n\nProvide:\n\n- App name, environment, app URL, project location\n- What was built: features, data sources, components\n- Next steps: how to iterate (`npm run build && pa app push`), how to add more data sources\n- Suggest what else the app could do:\n  - `\u002Fadd-datasource` -- add another data source (describe what you need, and the plugin will recommend the best approach)\n  - `\u002Fadd-dataverse` -- store and manage custom business data\n  - `\u002Fadd-azuredevops` -- track work items, bugs, and pipelines\n  - `\u002Fadd-teams` -- send and read Teams messages\n  - `\u002Fadd-sharepoint` -- work with SharePoint lists or documents\n  - `\u002Fadd-office365` -- send emails, manage calendar\n  - `\u002Fadd-workiq` -- search M365 data or get AI-powered answers about company info\n  - `\u002Fadd-connector` -- connect to any other service\n- Manage at https:\u002F\u002Fmake.powerapps.com\u002Fenvironments\u002F\u003Cenvironment-id>\u002Fhome\n\n### Update Memory Bank\n\nUpdate the memory bank (created in Step 6) with final state:\n\n- All completed steps (scaffold, data sources, implementation, deploy)\n- Features implemented and components created\n- Data sources connected\n- Suggested next steps\n\n---\n\n## Example Walkthroughs\n\nThese walkthroughs show the full sequence from user request to final output — commands run, files changed, and the verbatim summary format the assistant should use.\n\n---\n\n### Example 1: Create a Task Tracker App with Dataverse\n\n**User request:**\n\n> \"Build me a simple task tracker that stores tasks in Dataverse. I want to add tasks, mark them complete, and see a list.\"\n\n**Commands run (in order):**\n\n```bash\n# Step 1: Prerequisites\nnode --version   # → v22.4.0\n\n# Step 4: Scaffold\nnpx degit microsoft\u002FPowerAppsCodeApps\u002Ftemplates\u002Fvite powerapps-task-tracker-20260302 --force\ncd powerapps-task-tracker-20260302\nnpm install\nnpm install --save-dev \"@microsoft\u002Fpower-apps-cli@^1.3.0\"\n\n# Step 5: Initialize (browser login prompt on first run; CLI prompts for env ID if -e omitted)\npa app init -n 'Task Tracker' -e \u003Cenvironment-id>\n\n# Step 6: Baseline deploy (pre-approved as part of scaffold flow)\nnpm run build\npa app push\n# → App URL: https:\u002F\u002Fapps.powerapps.com\u002Fplay\u002Fe\u002F32a51012-...\u002Fapp\u002F\u003Capp-id>\n\n# Step 7: Add Dataverse (via \u002Fadd-dataverse)\npa app add data-source --connector dataverse --table cr123_task\nnpm run build   # verify connector — no deploy yet\n\n# Step 9: Final deploy (requires user confirmation)\nnpm run build\npa app push\n```\n\n**Files changed:**\n\n| File                                          | Change                                                |\n| --------------------------------------------- | ----------------------------------------------------- |\n| `package.json`                                | Updated — adds `@microsoft\u002Fpower-apps-cli` to `devDependencies` |\n| `power.config.json`                           | Created by `pa app init` — contains `environmentId` |\n| `src\u002Fgenerated\u002Fmodels\u002FCr123_tasksModel.ts`     | Generated by `pa app add data-source`, named after the table's entity set name (here `cr123_tasks`) |\n| `src\u002Fgenerated\u002Fservices\u002FCr123_tasksService.ts` | Generated by `pa app add data-source`               |\n| `src\u002Fcomponents\u002FTaskList.tsx`                 | Created — renders task list with status filter        |\n| `src\u002Fcomponents\u002FAddTaskForm.tsx`              | Created — form to add new tasks                       |\n| `src\u002FApp.tsx`                                 | Updated — wires components to `Cr123_tasksService`    |\n| `memory-bank.md`                              | Created in Step 6, updated at the end                 |\n\n**Final assistant summary (verbatim format):**\n\n```\nTask Tracker is live.\n\nApp: Task Tracker\nEnvironment: \u003Cyour-environment-name> (\u003Cenvironment-id>)\nURL: https:\u002F\u002Fapps.powerapps.com\u002Fplay\u002Fe\u002F\u003Cenvironment-id>\u002Fapp\u002F\u003Capp-id>\nProject: ~\u002Fpowerapps-task-tracker-20260302\u002F\n\nWhat was built:\n- Task list view with Active \u002F Completed filter\n- Add task form (title, description, due date)\n- Mark complete \u002F delete actions\n- Dataverse table `cr123_task` (Title, Description, DueDate, IsComplete)\n\nTo redeploy: npm run build && pa app push (from the project folder)\n\nWhat you can add next:\n- \u002Fadd-teams — post task updates to a Teams channel\n- \u002Fadd-office365 — send email notifications on completion\n```\n\n**What to record in `memory-bank.md`:**\n\n```markdown\n# Task Tracker — Memory Bank\n\n## Project\n\n- Path: ~\u002Fpowerapps-task-tracker-20260302\u002F\n- App name: Task Tracker\n- Environment: \u003Cyour-environment-name> (\u003Cenvironment-id>)\n- App URL: https:\u002F\u002Fapps.powerapps.com\u002Fplay\u002Fe\u002F\u003Cenvironment-id>\u002Fapp\u002F\u003Capp-id>\n- CLI: pa 1.3.0\n\n## Completed Steps\n\n- [x] Step 1: Prerequisites validated\n- [x] Step 4: Scaffold (npx degit)\n- [x] Step 5: Initialize (pa app init)\n- [x] Step 6: Baseline deploy\n- [x] Step 7: Add Dataverse (cr123_task)\n- [x] Step 8: Implement app (TaskList, AddTaskForm)\n- [x] Step 9: Final deploy\n\n## Data Sources\n\n- Dataverse: cr123_task (Title, Description, DueDate, IsComplete)\n\n## Components\n\n- TaskList.tsx — filtered list, mark complete, delete\n- AddTaskForm.tsx — create new tasks\n\n## Next Steps\n\n- Consider \u002Fadd-teams for task assignment notifications\n```\n\n---\n\n### Example 2: Add SharePoint Connector to an Existing App\n\n**User request:**\n\n> \"My app already exists. Add SharePoint so I can read items from a list called 'Project Milestones'.\"\n\n**Commands run (in order):**\n\n```bash\n# Step 6: Get the connection ID (via \u002Flist-connections)\npa connection list --search sharepointonline\n# → one SharePoint connection: conn-sp-xyz789\n\n# Step 7: Discover sites\npa connection list-datasets --connector sharepointonline -c conn-sp-xyz789\n# → https:\u002F\u002Fcontoso.sharepoint.com\u002Fsites\u002FProjects\n\n# Step 8: Discover tables\npa connection list-tables --connector sharepointonline -c conn-sp-xyz789 -d 'https:\u002F\u002Fcontoso.sharepoint.com\u002Fsites\u002FProjects'\n# → Project Milestones, Documents, Team Wiki\n\n# Step 9: Add the list as a table\npa app add data-source --connector sharepointonline -c conn-sp-xyz789 -d 'https:\u002F\u002Fcontoso.sharepoint.com\u002Fsites\u002FProjects' --table 'Project Milestones' --non-interactive\n\n# Step 11: Build to verify\nnpm run build   # → success\n```\n\n**Files changed:**\n\n| File                                                 | Change                                                                  |\n| ---------------------------------------------------- | ----------------------------------------------------------------------- |\n| `src\u002Fgenerated\u002Fservices\u002FProjectMilestonesService.ts` | Generated — `getAll`, `get`, `create`, `update`, `delete` for the list  |\n| `src\u002Fgenerated\u002Fmodels\u002FProjectMilestonesModel.ts`     | Generated — `ProjectMilestonesRead` \u002F `ProjectMilestonesWrite` types    |\n| `.power\u002Fschemas\u002Fsharepointonline\u002F`                   | Generated schema files                                                  |\n| `power.config.json`                                  | Updated — the new data source and its connection reference              |\n| `memory-bank.md`                                     | Updated — connector recorded (no connection ID)                         |\n\n**Final assistant summary (verbatim format):**\n\n```\nSharePoint Online connector added.\n\nConnector: SharePoint Online\nSite: https:\u002F\u002Fcontoso.sharepoint.com\u002Fsites\u002FProjects\nList: Project Milestones\nBuild: Passed ✓\n\nUsage:\n  const result = await ProjectMilestonesService.getAll({ top: 50 });\n  const milestones = result.data ?? [];\n\nNext: Implement your UI components using the generated service, then run \u002Fdeploy when ready.\n```\n","**? Shared Instructions: [shared-instructions.md](..\u002F..\u002Fshared\u002Fshared-instructions.md)** - Cross-cutting concerns.\n\n**References:**\n\n- [prerequisites-reference.md](.\u002Freferences\u002Fprerequisites-reference.md) - Prerequisites and required permissions\n- [troubleshooting.md](.\u002Freferences\u002Ftroubleshooting.md) - Common issues, npm scripts, resources\n\n# Create Power Apps Code App\n\n## Workflow\n\n1. Prerequisites → 2. Gather Requirements → 3. Plan → 4. Scaffold → 5. Initialize → 6. Build & Deploy (baseline) → 7. Add Data Sources → 8. Implement App → 9. Final Build & Deploy → 10. Summary\n\n---\n\n### Step 0: Check Memory Bank\n\nCheck for `memory-bank.md` per [shared-instructions.md](..\u002F..\u002Fshared\u002Fshared-instructions.md). Skip completed steps.\n\n### Step 1: Validate Prerequisites\n\nRun prerequisite checks **first** -- no point gathering requirements if the environment isn't ready. See [prerequisites-reference.md](.\u002Freferences\u002Fprerequisites-reference.md) for details.\n\nCheck Node.js and Git (runs natively in bash):\n\n```bash\nnode --version   # Must be v22+\ngit --version    # Optional but recommended\n```\n\n- **Missing Node.js**: Report \"Install Node.js v22+ from https:\u002F\u002Fnodejs.org\u002F\" and STOP.\n- **Node.js below v22**: Report \"Node.js 22+ is required. Please upgrade or switch with `nvm use 22`.\" and STOP.\n- **Missing Git**: Report \"Recommended but optional.\" Continue if approved.\n- **All present**: Report versions and proceed.\n\n\n### Step 2: Gather Requirements\n\n**Skip questions the user already answered in their initial instruction.**\n\n**If the user has not described what they want to build** (i.e., `\u002Fcreate-code-app` was invoked with no arguments or a vague prompt), start with a single open-ended question before asking anything else:\n\n> \"What would you like to build? Describe it in your own words — what it does, who uses it, and what problem it solves.\"\n\nWait for their answer. Use it to frame all follow-up questions. Do NOT present a multiple-choice list of app types before the user has described their idea.\n\nOnce you have their description:\n\n1. Confirm the app name and clarify the purpose if needed\n2. Ask about data -- focus on **what the app needs to do**, not specific technologies:\n   - \"What data does your app need to work with?\" (e.g., company emails, project tasks, custom business records)\n   - \"Does your app need to search existing information, manage its own data, or both?\"\n   - Based on their answers, recommend the best approach:\n     - **Store and manage custom business data** (tables, forms, CRUD) → Dataverse (`\u002Fadd-dataverse`)\n     - **Interact with specific services** (send emails, post messages, manage files) → the appropriate connector\n     - **Search M365 data or get AI-powered answers** (emails, files, people, company knowledge) → Work IQ (`\u002Fadd-workiq`)\n   - If they mention existing Dataverse tables, SharePoint lists, or connectors by name, use those directly\n3. Ask about UI requirements: key screens, layout, interactions, theme preference\n4. Ask any clarifying questions now -- resolve all ambiguity before entering plan mode\n\n### Step 3: Plan\n\n1. Enter plan mode with `EnterPlanMode`\n2. Design the full implementation approach:\n   - Which `\u002Fadd-*` skills to run for data sources\n   - App architecture: components, pages, state management\n   - Feature list with priority order\n3. Present plan for approval, include `allowedPrompts` from [prerequisites-reference.md](.\u002Freferences\u002Fprerequisites-reference.md)\n4. Exit plan mode with `ExitPlanMode` when approved\n\n### Step 4: Scaffold\n\nAsk the user for a folder name. Default to `powerapps-{app-name-slugified}-{timestamp}` if they don't have a preference.\n\n**IMPORTANT: Use `npx degit` to download the template. Do NOT use `git clone`, do NOT manually create files, do NOT download from GitHub UI. `degit` downloads the template without git history.**\n\n```bash\nnpx degit microsoft\u002FPowerAppsCodeApps\u002Ftemplates\u002Fvite {folder} --force\ncd {folder}\nnpm install\nnpm install --save-dev \"@microsoft\u002Fpower-apps-cli@^1.3.0\"\n```\n\n**Notes:**\n\n- Use `--force` to overwrite if the directory already has files (e.g., `.claude` from a planning session)\n- If targeting an existing directory, use `.` as the folder name: `npx degit microsoft\u002FPowerAppsCodeApps\u002Ftemplates\u002Fvite . --force`\n- If `npx degit` fails (network issues, npm not found), retry once, then ask the user to run manually\n- The template doesn't include the Power Apps CLI, so install it into the project as a dev dependency (not globally). Version 1.3.0 or later lets the connector skills find or create connections without asking for a connection ID.\n\nVerify: `package.json` exists, `node_modules\u002F` created, and `@microsoft\u002Fpower-apps-cli` is listed in `devDependencies`. Then resolve the CLI per [cli-binary.md](..\u002F..\u002Fshared\u002Fcli-binary.md); it should resolve to `pa` with `PA_INLINE_CONNECTIONS=yes`.\n\n### Step 5: Initialize\n\n> Resolve the CLI first (see [cli-binary.md](..\u002F..\u002Fshared\u002Fcli-binary.md)): run as `$PA app init …` (`npx --no-install pa …`), never a bare `pa`. On `power-apps`-only projects, translate to `power-apps init …` (the `init` verb and its `-n`\u002F`-e` flags are unchanged on both binaries).\n\n```bash\npa app init -n '{user-provided-app-name}' -e \u003Cenvironment-id>\n```\n\n**Finding the environment ID:** It's the GUID in the make.powerapps.com URL: `https:\u002F\u002Fmake.powerapps.com\u002Fenvironments\u002F\u003Cenv-id>\u002Fhome`. If you don't pass `-e`, the CLI will prompt for it interactively.\n\n**Authentication:** On first run, a browser window opens for Microsoft sign-in. Complete the login and the command continues. No separate auth setup is needed.\n\nSee [preferred-environment.md](..\u002F..\u002Fshared\u002Fpreferred-environment.md) for environment selection details.\n\n**`pa app init` failure:**\n\n- Non-zero exit: Report the exact output and STOP. Do not continue to Step 6.\n- \"environmentId not found\" or environment validation error: Verify the environment ID is correct and the user has maker permissions in that environment, then retry.\n- Example: _\"The `pa app init` command failed: `[error text]`. Please check that environment ID `32a51012-...` is correct and that you have maker permissions in that environment.\"_\n\n**Critical:** Read `power.config.json` after init and verify `environmentId` is set correctly.\n\n### Step 6: Build & Deploy (baseline)\n\n> **Pre-approved**: This baseline deploy is part of the scaffold flow and does not require a separate confirmation prompt.\n\nBuild and deploy the bare template to verify the pipeline works before adding data sources.\n\n```bash\nnpm run build\n```\n\nVerify `dist\u002F` folder created with `index.html` and `assets\u002F`.\n\n> Deploy via the resolved CLI: `$PA app push` on `pa`, or `power-apps push` on `power-apps`-only projects (see [cli-binary.md](..\u002F..\u002Fshared\u002Fcli-binary.md)).\n\n```bash\npa app push\n```\n\n**Capture app URL** from output: `https:\u002F\u002Fapps.powerapps.com\u002Fplay\u002Fe\u002F{env-id}\u002Fapp\u002F{app-id}`\n\n**Common deploy errors:** See [troubleshooting.md](.\u002Freferences\u002Ftroubleshooting.md).\n\n**Create or update `memory-bank.md` in the project root now** -- don't wait until the end. Include:\n\n- Project path, app name, environment ID, app URL\n- Completed steps: scaffold, init, baseline deploy\n- Data sources planned (from Step 2)\n\nThis ensures progress is saved even if the session ends unexpectedly.\n\n### Step 7: Add Data Sources\n\nInvoke the `\u002Fadd-*` skills identified in the plan (Step 3). Run each in sequence. **Pass context as arguments** so sub-skills skip redundant questions (project path, connector name, etc.):\n\n| App needs to...                            | Invoke             |\n| ------------------------------------------ | ------------------ |\n| Store\u002Fmanage custom business data          | `\u002Fadd-dataverse`   |\n| Track work items, bugs, pipelines          | `\u002Fadd-azuredevops` |\n| Send or read Teams messages                | `\u002Fadd-teams`       |\n| Read\u002Fwrite Excel spreadsheet data          | `\u002Fadd-excel`       |\n| Upload, download, or manage files          | `\u002Fadd-onedrive`    |\n| Work with SharePoint lists or docs         | `\u002Fadd-sharepoint`  |\n| Send emails, read inbox, manage calendar   | `\u002Fadd-office365`   |\n| Invoke a Copilot Studio agent              | `\u002Fadd-mcscopilot`  |\n| Search M365 data or get AI-powered answers | `\u002Fadd-workiq`      |\n| Connect to another service                 | `\u002Fadd-connector`   |\n\n**Connections:** every connector except Dataverse needs a connection. With the CLI 1.3.0+ installed in Step 4, the connector skills find or create it themselves: they tell the user first that a connection may be created with the user's account, and ask before running `--use-sso` or `pa connection create`. See [connector-reference.md](..\u002F..\u002Fshared\u002Fconnector-reference.md#connections).\n\nEach `\u002Fadd-*` skill runs `npm run build` to catch errors. Do NOT deploy yet.\n\n**If no data sources needed:** Skip to Step 8.\n\n### Step 8: Implement App\n\n**This is the core step.** Build the actual app features described in the plan from Step 3.\n\n1. **Review generated services**: Use `Grep` to find methods in generated service files (they can be very large -- see [connector-reference.md](..\u002F..\u002Fshared\u002Fconnector-reference.md#inspecting-large-generated-files)). Do NOT read entire generated files.\n2. **Build components**: Create React components for each screen\u002Ffeature in the plan\n3. **Connect data**: Wire components to generated services (use `*Service.getAll()`, `*Service.create()`, etc.)\n4. **Apply theme**: Use the user's theme preference (default: dark theme per development standards)\n5. **Iterate with user**: Show progress, ask for feedback, adjust as needed\n\n**Key rules:**\n\n- Use generated services for all data access -- never use fetch\u002Faxios directly\n- Read [dataverse-reference.md](..\u002Fadd-dataverse\u002Freferences\u002Fdataverse-reference.md) if working with Dataverse (picklist fields, virtual fields, lookups have critical gotchas)\n- Remove unused imports before building (TS6133 strict mode)\n- Don't edit files in `src\u002Fgenerated\u002F` unless fixing known issues\n\n### Step 9: Final Build & Deploy\n\n```bash\nnpm run build\n```\n\nFix any TypeScript errors. Verify `dist\u002F` contains the updated app.\n\nAsk the user: _\"Ready to deploy to [environment name]? This will update the live app.\"_ Wait for explicit confirmation before proceeding.\n\n```bash\npa app push\n```\n\n### Step 10: Summary\n\nProvide:\n\n- App name, environment, app URL, project location\n- What was built: features, data sources, components\n- Next steps: how to iterate (`npm run build && pa app push`), how to add more data sources\n- Suggest what else the app could do:\n  - `\u002Fadd-datasource` -- add another data source (describe what you need, and the plugin will recommend the best approach)\n  - `\u002Fadd-dataverse` -- store and manage custom business data\n  - `\u002Fadd-azuredevops` -- track work items, bugs, and pipelines\n  - `\u002Fadd-teams` -- send and read Teams messages\n  - `\u002Fadd-sharepoint` -- work with SharePoint lists or documents\n  - `\u002Fadd-office365` -- send emails, manage calendar\n  - `\u002Fadd-workiq` -- search M365 data or get AI-powered answers about company info\n  - `\u002Fadd-connector` -- connect to any other service\n- Manage at https:\u002F\u002Fmake.powerapps.com\u002Fenvironments\u002F\u003Cenvironment-id>\u002Fhome\n\n### Update Memory Bank\n\nUpdate the memory bank (created in Step 6) with final state:\n\n- All completed steps (scaffold, data sources, implementation, deploy)\n- Features implemented and components created\n- Data sources connected\n- Suggested next steps\n\n---\n\n## Example Walkthroughs\n\nThese walkthroughs show the full sequence from user request to final output — commands run, files changed, and the verbatim summary format the assistant should use.\n\n---\n\n### Example 1: Create a Task Tracker App with Dataverse\n\n**User request:**\n\n> \"Build me a simple task tracker that stores tasks in Dataverse. I want to add tasks, mark them complete, and see a list.\"\n\n**Commands run (in order):**\n\n```bash\n# Step 1: Prerequisites\nnode --version   # → v22.4.0\n\n# Step 4: Scaffold\nnpx degit microsoft\u002FPowerAppsCodeApps\u002Ftemplates\u002Fvite powerapps-task-tracker-20260302 --force\ncd powerapps-task-tracker-20260302\nnpm install\nnpm install --save-dev \"@microsoft\u002Fpower-apps-cli@^1.3.0\"\n\n# Step 5: Initialize (browser login prompt on first run; CLI prompts for env ID if -e omitted)\npa app init -n 'Task Tracker' -e \u003Cenvironment-id>\n\n# Step 6: Baseline deploy (pre-approved as part of scaffold flow)\nnpm run build\npa app push\n# → App URL: https:\u002F\u002Fapps.powerapps.com\u002Fplay\u002Fe\u002F32a51012-...\u002Fapp\u002F\u003Capp-id>\n\n# Step 7: Add Dataverse (via \u002Fadd-dataverse)\npa app add data-source --connector dataverse --table cr123_task\nnpm run build   # verify connector — no deploy yet\n\n# Step 9: Final deploy (requires user confirmation)\nnpm run build\npa app push\n```\n\n**Files changed:**\n\n| File                                          | Change                                                |\n| --------------------------------------------- | ----------------------------------------------------- |\n| `package.json`                                | Updated — adds `@microsoft\u002Fpower-apps-cli` to `devDependencies` |\n| `power.config.json`                           | Created by `pa app init` — contains `environmentId` |\n| `src\u002Fgenerated\u002Fmodels\u002FCr123_tasksModel.ts`     | Generated by `pa app add data-source`, named after the table's entity set name (here `cr123_tasks`) |\n| `src\u002Fgenerated\u002Fservices\u002FCr123_tasksService.ts` | Generated by `pa app add data-source`               |\n| `src\u002Fcomponents\u002FTaskList.tsx`                 | Created — renders task list with status filter        |\n| `src\u002Fcomponents\u002FAddTaskForm.tsx`              | Created — form to add new tasks                       |\n| `src\u002FApp.tsx`                                 | Updated — wires components to `Cr123_tasksService`    |\n| `memory-bank.md`                              | Created in Step 6, updated at the end                 |\n\n**Final assistant summary (verbatim format):**\n\n```\nTask Tracker is live.\n\nApp: Task Tracker\nEnvironment: \u003Cyour-environment-name> (\u003Cenvironment-id>)\nURL: https:\u002F\u002Fapps.powerapps.com\u002Fplay\u002Fe\u002F\u003Cenvironment-id>\u002Fapp\u002F\u003Capp-id>\nProject: ~\u002Fpowerapps-task-tracker-20260302\u002F\n\nWhat was built:\n- Task list view with Active \u002F Completed filter\n- Add task form (title, description, due date)\n- Mark complete \u002F delete actions\n- Dataverse table `cr123_task` (Title, Description, DueDate, IsComplete)\n\nTo redeploy: npm run build && pa app push (from the project folder)\n\nWhat you can add next:\n- \u002Fadd-teams — post task updates to a Teams channel\n- \u002Fadd-office365 — send email notifications on completion\n```\n\n**What to record in `memory-bank.md`:**\n\n```markdown\n# Task Tracker — Memory Bank\n\n## Project\n\n- Path: ~\u002Fpowerapps-task-tracker-20260302\u002F\n- App name: Task Tracker\n- Environment: \u003Cyour-environment-name> (\u003Cenvironment-id>)\n- App URL: https:\u002F\u002Fapps.powerapps.com\u002Fplay\u002Fe\u002F\u003Cenvironment-id>\u002Fapp\u002F\u003Capp-id>\n- CLI: pa 1.3.0\n\n## Completed Steps\n\n- [x] Step 1: Prerequisites validated\n- [x] Step 4: Scaffold (npx degit)\n- [x] Step 5: Initialize (pa app init)\n- [x] Step 6: Baseline deploy\n- [x] Step 7: Add Dataverse (cr123_task)\n- [x] Step 8: Implement app (TaskList, AddTaskForm)\n- [x] Step 9: Final deploy\n\n## Data Sources\n\n- Dataverse: cr123_task (Title, Description, DueDate, IsComplete)\n\n## Components\n\n- TaskList.tsx — filtered list, mark complete, delete\n- AddTaskForm.tsx — create new tasks\n\n## Next Steps\n\n- Consider \u002Fadd-teams for task assignment notifications\n```\n\n---\n\n### Example 2: Add SharePoint Connector to an Existing App\n\n**User request:**\n\n> \"My app already exists. Add SharePoint so I can read items from a list called 'Project Milestones'.\"\n\n**Commands run (in order):**\n\n```bash\n# Step 6: Get the connection ID (via \u002Flist-connections)\npa connection list --search sharepointonline\n# → one SharePoint connection: conn-sp-xyz789\n\n# Step 7: Discover sites\npa connection list-datasets --connector sharepointonline -c conn-sp-xyz789\n# → https:\u002F\u002Fcontoso.sharepoint.com\u002Fsites\u002FProjects\n\n# Step 8: Discover tables\npa connection list-tables --connector sharepointonline -c conn-sp-xyz789 -d 'https:\u002F\u002Fcontoso.sharepoint.com\u002Fsites\u002FProjects'\n# → Project Milestones, Documents, Team Wiki\n\n# Step 9: Add the list as a table\npa app add data-source --connector sharepointonline -c conn-sp-xyz789 -d 'https:\u002F\u002Fcontoso.sharepoint.com\u002Fsites\u002FProjects' --table 'Project Milestones' --non-interactive\n\n# Step 11: Build to verify\nnpm run build   # → success\n```\n\n**Files changed:**\n\n| File                                                 | Change                                                                  |\n| ---------------------------------------------------- | ----------------------------------------------------------------------- |\n| `src\u002Fgenerated\u002Fservices\u002FProjectMilestonesService.ts` | Generated — `getAll`, `get`, `create`, `update`, `delete` for the list  |\n| `src\u002Fgenerated\u002Fmodels\u002FProjectMilestonesModel.ts`     | Generated — `ProjectMilestonesRead` \u002F `ProjectMilestonesWrite` types    |\n| `.power\u002Fschemas\u002Fsharepointonline\u002F`                   | Generated schema files                                                  |\n| `power.config.json`                                  | Updated — the new data source and its connection reference              |\n| `memory-bank.md`                                     | Updated — connector recorded (no connection ID)                         |\n\n**Final assistant summary (verbatim format):**\n\n```\nSharePoint Online connector added.\n\nConnector: SharePoint Online\nSite: https:\u002F\u002Fcontoso.sharepoint.com\u002Fsites\u002FProjects\nList: Project Milestones\nBuild: Passed ✓\n\nUsage:\n  const result = await ProjectMilestonesService.getAll({ top: 50 });\n  const milestones = result.data ?? [];\n\nNext: Implement your UI components using the generated service, then run \u002Fdeploy when ready.\n```\n",{"name":5,"model":32,"description":7,"allowed-tools":49,"user-invocable":50},"Read, Edit, Write, Grep, Glob, Bash, LSP, TaskCreate, TaskUpdate, TaskList, TaskGet, AskUserQuestion, Skill, EnterPlanMode, ExitPlanMode",true,"main","9d26fde082b47f04e9bb97cb30a46dd1eaaa776e","plugins\u002Fcode-apps\u002Fskills\u002Fcreate-code-app",232,"https:\u002F\u002Fgithub.com\u002Fmicrosoft\u002Fpower-platform-skills","https:\u002F\u002Fmicrosoft.github.io\u002Fpower-platform-skills\u002F","https:\u002F\u002Fgithub.com\u002Fmicrosoft","https:\u002F\u002Fopensource.microsoft.com","Open source projects and samples from Microsoft","2026-11-14 21:46:39",{"source":8,"skillName":5,"commands":62,"prompt":72,"zipAvailable":50},[63,66,69],{"tool":64,"command":65},"npx","npx skills add microsoft\u002Fpower-platform-skills --skill create-code-app",{"tool":67,"command":68},"bunx","bunx skills add microsoft\u002Fpower-platform-skills --skill create-code-app",{"tool":70,"command":71},"pnpm","pnpm dlx skills add microsoft\u002Fpower-platform-skills --skill create-code-app","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002Fmicrosoft\u002Fpower-platform-skills\u002Fblob\u002Fmain\u002Fplugins\u002Fcode-apps\u002Fskills\u002Fcreate-code-app\u002FSKILL.md",[74,80],{"path":75,"resourceType":76,"resourceTypeDesc":77,"sizeBytes":78,"sourceHtmlUrl":79},"references\u002Fprerequisites-reference.md","REFERENCE","参考文档",2480,"https:\u002F\u002Fgithub.com\u002Fmicrosoft\u002Fpower-platform-skills\u002Fblob\u002Fmain\u002Fplugins\u002Fcode-apps\u002Fskills\u002Fcreate-code-app\u002Freferences\u002Fprerequisites-reference.md",{"path":81,"resourceType":76,"resourceTypeDesc":77,"sizeBytes":82,"sourceHtmlUrl":83},"references\u002Ftroubleshooting.md",3579,"https:\u002F\u002Fgithub.com\u002Fmicrosoft\u002Fpower-platform-skills\u002Fblob\u002Fmain\u002Fplugins\u002Fcode-apps\u002Fskills\u002Fcreate-code-app\u002Freferences\u002Ftroubleshooting.md",[85,93,112,133,151,165],{"skillNo":86,"name":87,"nameZh":6,"description":88,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":89,"categories":90,"keywords":91,"publishedAt":92},"01M78JN2BFRRV1J54Q6WKZQ08D","compare-site-configurations","Compare Power Pages site configurations between two environments, such as dev, test and production, or between a local download and the live site, and explain which differences change site behavior. Use when a site works in one environment but not another (for example, works in dev but fails in test), to check configuration drift before promoting or deploying, or to see what changed between two sites. Produces a shareable HTML report and a JSON file that VS Code can import.","https:\u002F\u002Fgithub.com\u002Fmicrosoft\u002Fpower-platform-skills\u002Fblob\u002Fmain\u002Fplugins\u002Fpower-pages\u002Fskills\u002Fcompare-site-configurations\u002FSKILL.md",[],[],"2026-11-15 14:19:17",{"skillNo":94,"name":95,"nameZh":6,"description":96,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":97,"categories":98,"keywords":99,"publishedAt":44},"01M699WVHX0XN59EPBTTPEKYPG","setup","Use when Process Intelligence needs building, explicit cloud\u002Faccount\u002Fenvironment configuration, sign-in, connection diagnostics, or recovery from an authentication error.","https:\u002F\u002Fgithub.com\u002Fmicrosoft\u002Fpower-platform-skills\u002Fblob\u002Fmain\u002Fplugins\u002Fprocess-intelligence\u002Fskills\u002Fsetup\u002FSKILL.md",[],[95,100,101,102,103,104,37,105,106,107,36,108,109,110,35,111],"configuration","diagnostics","error","environment","cloud","connection","authentication","use","recovery","process","sign","intelligence",{"skillNo":113,"name":114,"nameZh":6,"description":115,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":116,"categories":117,"keywords":121,"publishedAt":44},"01M699WSR9EX55YY1WD9J22FEG","report-issue","Use when the user wants a Process Intelligence bug-report draft or support summary for a failed operation.","https:\u002F\u002Fgithub.com\u002Fmicrosoft\u002Fpower-platform-skills\u002Fblob\u002Fmain\u002Fplugins\u002Fprocess-intelligence\u002Fskills\u002Freport-issue\u002FSKILL.md",[118],{"categoryNo":119,"categoryName":120,"taxonomyType":21,"taxonomyTypeDesc":22},"01JBSEEDCAT000000000000034","行政与办公人员",[122,123,124,125,107,37,126,127,109,128,111,129,130,131,132],"issue","report","report issue","bug-report","operation","draft","bug","summary","user","for","support",{"skillNo":134,"name":135,"nameZh":6,"description":136,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":137,"categories":138,"keywords":139,"publishedAt":44},"01M699WR26YQ9Q21KE6MJF5B2G","investigate-process","Use when a broad Process Mining business question, observed pattern or competing explanation needs investigation across analytical perspectives.","https:\u002F\u002Fgithub.com\u002Fmicrosoft\u002Fpower-platform-skills\u002Fblob\u002Fmain\u002Fplugins\u002Fprocess-intelligence\u002Fskills\u002Finvestigate-process\u002FSKILL.md",[],[140,109,141,142,107,143,144,37,145,146,147,35,148,149,150],"investigate","investigate process","question","process mining","business","across","perspectives","mining","pattern","investigation","analytical",{"skillNo":152,"name":153,"nameZh":6,"description":154,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":155,"categories":156,"keywords":157,"publishedAt":44},"01M699WP9SDG5ZR12P8VYNXKTN","derive-metric","Use when a requested measure is missing, a saved custom metric needs reuse, or an ephemeral formula or derived scalar is needed.","https:\u002F\u002Fgithub.com\u002Fmicrosoft\u002Fpower-platform-skills\u002Fblob\u002Fmain\u002Fplugins\u002Fprocess-intelligence\u002Fskills\u002Fderive-metric\u002FSKILL.md",[],[158,159,160,161,162,163,107,37,164,35],"metric","derive metric","missing","formula","custom","reuse","saved",{"skillNo":166,"name":167,"nameZh":6,"description":168,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":169,"categories":170,"keywords":171,"publishedAt":44},"01M699WMG5R8P6SMTDAS1TKF9E","compare-cohorts","Use when comparing process cohorts, departments, periods or before-and-after results under matched definitions.","https:\u002F\u002Fgithub.com\u002Fmicrosoft\u002Fpower-platform-skills\u002Fblob\u002Fmain\u002Fplugins\u002Fprocess-intelligence\u002Fskills\u002Fcompare-cohorts\u002FSKILL.md",[],[172,173,107,37,174,109,35],"compare","compare cohorts","results"]