[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M699P9A015RB77RD9K3WFWFQ":3,"skill-same:01M699P9A015RB77RD9K3WFWFQ":75},{"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":52,"commitSha":53,"skillDirectory":54,"forksCount":55,"repositoryHtmlUrl":56,"repositoryHomepageUrl":57,"ownerHtmlUrl":58,"ownerBlogUrl":59,"ownerDescription":60,"updatedAt":61,"install":62,"resources":74},"01M699P9A015RB77RD9K3WFWFQ","report-issue",null,"Use when the user wants to report a bug, file an issue, submit a bug report, or report any problem with the mobile-app plugin.","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\u002Fmobile-apps\u002Fskills\u002Freport-issue\u002FSKILL.md",[18],{"categoryNo":19,"categoryName":20,"taxonomyType":21,"taxonomyTypeDesc":22},"01JBSEEDCAT000000000000034","行政与办公人员","PROFESSION","适用职业",[24,25,26,27,28,29,30,31,32,33,34,35,36,37,38,39,40,41,42,43],"report","issue","report issue","use","when","true","with","problem","submit","app","mobile","bug","read","grep","haiku","Bash","brief","file","bug report","plugin","2026-11-10 10:12:30",false,"---\nname: report-issue\ndescription: Use when the user wants to report a bug, file an issue, submit a bug report, or report any problem with the mobile-app plugin.\nuser-invocable: true\nargument-hint: \"[optional: brief description of the bug]\"\nallowed-tools: Read, Bash, Glob, Grep, AskUserQuestion\nmodel: haiku\n---\n\n> **Plugin check**: Run `node \"${PLUGIN_ROOT}\u002Fscripts\u002Fcheck-version.js\"` - if it outputs a message, show it to the user before proceeding.\n\n**? Shared instructions: [shared-instructions.md](${PLUGIN_ROOT}\u002Fshared\u002Fshared-instructions.md)** — read this first.\n\n# Report Issue — mobile-app\n\nGenerates a fully-populated GitHub issue body for the `microsoft\u002Fpower-platform-skills` repo, scoped to the `mobile-app` plugin. Read-only — no project modifications.\n\n## Workflow\n\n1. Capture user description → 2. Detect project context → 3. Collect diagnostics → 4. Render issue body → 5. Print URL\n\n---\n\n### Step 1 — Capture user description\n\n**Telemetry checkpoint: `capture_issue_description`**\n\nIf `$ARGUMENTS` contains a description, use it. Otherwise prompt:\n\n> \"What's the issue? Briefly describe what you expected vs. what happened. (You can paste error output if helpful.)\"\n\nThen ask via `AskUserQuestion`:\n\n> \"Issue category?\n> (a) Bug — something broke\n> (b) Unexpected behavior — wrong output but no error\n> (c) Documentation — docs are wrong \u002F missing\n> (d) Feature request\n> (e) Question \u002F discussion\"\n\n> \"How blocking is this?\n> (a) Blocking — can't proceed at all\n> (b) Workaround exists — but painful\n> (c) Annoying — non-critical\n> (d) Polish — nice-to-have\"\n\n### Step 2 — Detect project context\n\nRead-only checks:\n\n```bash\ntest -f power.config.json && echo \"in_project=true\" || echo \"in_project=false\"\npwd\nnode --version\nnpm --version\nnode scripts\u002Fresolve-environment.js \"$(node -e \\\"console.log(require('.\u002Fpower.config.json').environmentId)\\\")\" 2>\u002Fdev\u002Fnull || true\naz --version 2>\u002Fdev\u002Fnull | head -1\nnpx --no-install expo --version 2>\u002Fdev\u002Fnull\nuname -srm\n```\n\nIf in a project:\n\n```bash\nnode -e \"console.log(require('.\u002Fpackage.json').name, require('.\u002Fpackage.json').version)\" 2>\u002Fdev\u002Fnull\nnode -e \"console.log(JSON.stringify({env: require('.\u002Fpower.config.json').environmentId, name: require('.\u002Fpower.config.json').displayName}))\"\ntest -f memory-bank.md && echo \"memory_bank=present\"\ntest -f native-app-plan.md && echo \"plan=present\"\nls src\u002Fgenerated\u002Fservices\u002F 2>\u002Fdev\u002Fnull | head -10\n```\n\nIf the description names a package matching `@microsoft\u002Fpower-apps-native-*`, collect its declared and lockfile-resolved versions from `package.json` and `package-lock.json`. Do not read package source or metadata from `node_modules\u002F`.\n\n```bash\nnode - \u003C\u003C'NODE'\nconst fs = require('node:fs');\nconst manifest = JSON.parse(fs.readFileSync('package.json', 'utf8'));\nconst lockfile = fs.existsSync('package-lock.json')\n  ? JSON.parse(fs.readFileSync('package-lock.json', 'utf8'))\n  : null;\nconst dependencies = { ...manifest.dependencies, ...manifest.devDependencies };\nfor (const [name, declared] of Object.entries(dependencies)) {\n  if (!name.startsWith('@microsoft\u002Fpower-apps-native-')) continue;\n  const resolved = lockfile?.packages?.[`node_modules\u002F${name}`]?.version ?? 'unknown';\n  console.log(`${name}\\tdeclared=${declared}\\tresolved=${resolved}`);\n}\nNODE\n```\n\nFor native-build issues also capture:\n\n```bash\n[ \"$(uname)\" = \"Darwin\" ] && xcode-select -p\n[ \"$(uname)\" = \"Darwin\" ] && pod --version 2>\u002Fdev\u002Fnull\njava -version 2>&1 | head -1\necho \"ANDROID_HOME=$ANDROID_HOME\"\n```\n\n### Step 3 — Collect diagnostics\n\n**Telemetry checkpoint: `collect_issue_diagnostics`**\n\nRun `npx --no-install expo doctor` and capture the text output verbatim.\n\nAsk for the affected workflow's Support ID when available. Use the telemetry\nhelper's read-only `--report` mode from the affected project to inspect only its\nallowlisted timeline. Include the Support ID and relevant step\u002Ferror category in\nthe issue body, not environment, tenant, or organization IDs. Do not\nupload the telemetry directory or raw timing\u002Fauthentication files.\n\nIf the user pasted an error, capture verbatim. Otherwise look for recent failure signals:\n\n- Last 50 lines of any Metro \u002F Gradle \u002F Xcode log if user mentions a build failure\n- `git status --short` if in a git repo (to show modified files — sanitize for secrets first)\n- Output of `npx --no-install tsc --noEmit` if relevant\n\n**Do NOT capture:**\n- Contents of `src\u002FplayerConfig.ts` (contains tenantId \u002F clientId — sensitive)\n- Contents of `.env` or any file matching `.env*`\n- Connection IDs unless the user explicitly opted in (PII \u002F can map to tenant)\n- Anything under `node_modules\u002F`\n- Package source excerpts, patched package contents, or proposed fork code\n- Tenant\u002Fenvironment\u002Forganization IDs in a public issue, even though verified\n  IDs can exist in access-controlled telemetry\n\n### Step 4 — Render issue body\n\n**Telemetry checkpoint: `render_issue_report`**\n\nPrint this block — user copies into a new issue:\n\n```markdown\n### Description\n\n\u003Cuser's description>\n\n### Category\n\n\u003CBug \u002F Unexpected behavior \u002F Docs \u002F Feature \u002F Question>\n\n### Severity\n\n\u003CBlocking \u002F Workaround \u002F Annoying \u002F Polish>\n\n### Environment\n\n| | |\n|---|---|\n| Plugin | mobile-app |\n| Plugin version | \u003Cfrom .plugin\u002Fplugin.json, or legacy .claude-plugin\u002Fplugin.json fallback, or \"unknown\"> |\n| OS | \u003Cuname output> |\n| Node | \u003Cversion> |\n| npm | \u003Cversion> |\n| Power Apps CLI | \u003Cversion> |\n| Expo CLI | \u003Cversion> |\n| Xcode | \u003Cif macOS> |\n| JDK | \u003Cif android> |\n| ANDROID_HOME set | \u003Cyes\u002Fno> |\n\n### Project context\n\n\u003Cif in project>\n- Mobile project detected: yes\n- Support ID: `\u003Caffected workflow run GUID, or unavailable>`\n- Failed step \u002F error category: `\u003Cregistered step and fixed category, or unknown>`\n- Memory bank present: \u003Cyes\u002Fno>\n- Plan present: \u003Cyes\u002Fno>\n- Connector count: \u003Ccount, not generated service or business-table names>\n\u003C\u002Fif>\n\n\u003Cif not in project>\nNot run inside a mobile-app project.\n\u003C\u002Fif>\n\n### Affected native package\n\n\u003Cinclude only when the issue concerns @microsoft\u002Fpower-apps-native-*>\n- Package: `\u003Cpackage name>`\n- Declared version: `\u003Cpackage.json range>`\n- Resolved version: `\u003Cpackage-lock.json version or unknown>`\n- Platform: `\u003CiOS \u002F Android>`\n- Ownership evidence: \u003Cwhy the documented caller contract is satisfied and the failure is package-internal>\n\n### Reproduction steps\n\n1.\n2.\n3.\n\n### Expected\n\n\u003Cwhat should have happened>\n\n### Actual\n\n\u003Cwhat happened>\n\n### Logs \u002F errors\n\n```\n\u003Cpaste verbatim — sensitive values redacted>\n```\n\n### Notes\n\n\u003Canything else>\n```\n\n### Step 5 — Print URL\n\n**Telemetry checkpoint: `generate_issue_submission_url`**\n\nTell the user:\n\n> Open this URL to file the issue:\n>\n> \u003Chttps:\u002F\u002Fgithub.com\u002Fmicrosoft\u002Fpower-platform-skills\u002Fissues\u002Fnew?labels=plugin%3Amobile-app>\n>\n> Paste the block above into the body. Review for any sensitive values before submitting.\n\nIf the user wants to open it, suggest `open \u003Curl>` (macOS) \u002F `xdg-open \u003Curl>` (Linux) \u002F `start \u003Curl>` (Windows). Do not auto-open without confirmation.\n\n## Notes\n\n- This skill never modifies any file or invokes mutating commands. Pure diagnostic.\n- For diagnosing connection-specific failures, suggest the user run `\u002Flist-connections` first and paste that output into the issue.\n- For diagnosing build failures, suggest they include the full Metro\u002FGradle\u002FXcode log (not truncated).\n","> **Plugin check**: Run `node \"${PLUGIN_ROOT}\u002Fscripts\u002Fcheck-version.js\"` - if it outputs a message, show it to the user before proceeding.\n\n**? Shared instructions: [shared-instructions.md](${PLUGIN_ROOT}\u002Fshared\u002Fshared-instructions.md)** — read this first.\n\n# Report Issue — mobile-app\n\nGenerates a fully-populated GitHub issue body for the `microsoft\u002Fpower-platform-skills` repo, scoped to the `mobile-app` plugin. Read-only — no project modifications.\n\n## Workflow\n\n1. Capture user description → 2. Detect project context → 3. Collect diagnostics → 4. Render issue body → 5. Print URL\n\n---\n\n### Step 1 — Capture user description\n\n**Telemetry checkpoint: `capture_issue_description`**\n\nIf `$ARGUMENTS` contains a description, use it. Otherwise prompt:\n\n> \"What's the issue? Briefly describe what you expected vs. what happened. (You can paste error output if helpful.)\"\n\nThen ask via `AskUserQuestion`:\n\n> \"Issue category?\n> (a) Bug — something broke\n> (b) Unexpected behavior — wrong output but no error\n> (c) Documentation — docs are wrong \u002F missing\n> (d) Feature request\n> (e) Question \u002F discussion\"\n\n> \"How blocking is this?\n> (a) Blocking — can't proceed at all\n> (b) Workaround exists — but painful\n> (c) Annoying — non-critical\n> (d) Polish — nice-to-have\"\n\n### Step 2 — Detect project context\n\nRead-only checks:\n\n```bash\ntest -f power.config.json && echo \"in_project=true\" || echo \"in_project=false\"\npwd\nnode --version\nnpm --version\nnode scripts\u002Fresolve-environment.js \"$(node -e \\\"console.log(require('.\u002Fpower.config.json').environmentId)\\\")\" 2>\u002Fdev\u002Fnull || true\naz --version 2>\u002Fdev\u002Fnull | head -1\nnpx --no-install expo --version 2>\u002Fdev\u002Fnull\nuname -srm\n```\n\nIf in a project:\n\n```bash\nnode -e \"console.log(require('.\u002Fpackage.json').name, require('.\u002Fpackage.json').version)\" 2>\u002Fdev\u002Fnull\nnode -e \"console.log(JSON.stringify({env: require('.\u002Fpower.config.json').environmentId, name: require('.\u002Fpower.config.json').displayName}))\"\ntest -f memory-bank.md && echo \"memory_bank=present\"\ntest -f native-app-plan.md && echo \"plan=present\"\nls src\u002Fgenerated\u002Fservices\u002F 2>\u002Fdev\u002Fnull | head -10\n```\n\nIf the description names a package matching `@microsoft\u002Fpower-apps-native-*`, collect its declared and lockfile-resolved versions from `package.json` and `package-lock.json`. Do not read package source or metadata from `node_modules\u002F`.\n\n```bash\nnode - \u003C\u003C'NODE'\nconst fs = require('node:fs');\nconst manifest = JSON.parse(fs.readFileSync('package.json', 'utf8'));\nconst lockfile = fs.existsSync('package-lock.json')\n  ? JSON.parse(fs.readFileSync('package-lock.json', 'utf8'))\n  : null;\nconst dependencies = { ...manifest.dependencies, ...manifest.devDependencies };\nfor (const [name, declared] of Object.entries(dependencies)) {\n  if (!name.startsWith('@microsoft\u002Fpower-apps-native-')) continue;\n  const resolved = lockfile?.packages?.[`node_modules\u002F${name}`]?.version ?? 'unknown';\n  console.log(`${name}\\tdeclared=${declared}\\tresolved=${resolved}`);\n}\nNODE\n```\n\nFor native-build issues also capture:\n\n```bash\n[ \"$(uname)\" = \"Darwin\" ] && xcode-select -p\n[ \"$(uname)\" = \"Darwin\" ] && pod --version 2>\u002Fdev\u002Fnull\njava -version 2>&1 | head -1\necho \"ANDROID_HOME=$ANDROID_HOME\"\n```\n\n### Step 3 — Collect diagnostics\n\n**Telemetry checkpoint: `collect_issue_diagnostics`**\n\nRun `npx --no-install expo doctor` and capture the text output verbatim.\n\nAsk for the affected workflow's Support ID when available. Use the telemetry\nhelper's read-only `--report` mode from the affected project to inspect only its\nallowlisted timeline. Include the Support ID and relevant step\u002Ferror category in\nthe issue body, not environment, tenant, or organization IDs. Do not\nupload the telemetry directory or raw timing\u002Fauthentication files.\n\nIf the user pasted an error, capture verbatim. Otherwise look for recent failure signals:\n\n- Last 50 lines of any Metro \u002F Gradle \u002F Xcode log if user mentions a build failure\n- `git status --short` if in a git repo (to show modified files — sanitize for secrets first)\n- Output of `npx --no-install tsc --noEmit` if relevant\n\n**Do NOT capture:**\n- Contents of `src\u002FplayerConfig.ts` (contains tenantId \u002F clientId — sensitive)\n- Contents of `.env` or any file matching `.env*`\n- Connection IDs unless the user explicitly opted in (PII \u002F can map to tenant)\n- Anything under `node_modules\u002F`\n- Package source excerpts, patched package contents, or proposed fork code\n- Tenant\u002Fenvironment\u002Forganization IDs in a public issue, even though verified\n  IDs can exist in access-controlled telemetry\n\n### Step 4 — Render issue body\n\n**Telemetry checkpoint: `render_issue_report`**\n\nPrint this block — user copies into a new issue:\n\n```markdown\n### Description\n\n\u003Cuser's description>\n\n### Category\n\n\u003CBug \u002F Unexpected behavior \u002F Docs \u002F Feature \u002F Question>\n\n### Severity\n\n\u003CBlocking \u002F Workaround \u002F Annoying \u002F Polish>\n\n### Environment\n\n| | |\n|---|---|\n| Plugin | mobile-app |\n| Plugin version | \u003Cfrom .plugin\u002Fplugin.json, or legacy .claude-plugin\u002Fplugin.json fallback, or \"unknown\"> |\n| OS | \u003Cuname output> |\n| Node | \u003Cversion> |\n| npm | \u003Cversion> |\n| Power Apps CLI | \u003Cversion> |\n| Expo CLI | \u003Cversion> |\n| Xcode | \u003Cif macOS> |\n| JDK | \u003Cif android> |\n| ANDROID_HOME set | \u003Cyes\u002Fno> |\n\n### Project context\n\n\u003Cif in project>\n- Mobile project detected: yes\n- Support ID: `\u003Caffected workflow run GUID, or unavailable>`\n- Failed step \u002F error category: `\u003Cregistered step and fixed category, or unknown>`\n- Memory bank present: \u003Cyes\u002Fno>\n- Plan present: \u003Cyes\u002Fno>\n- Connector count: \u003Ccount, not generated service or business-table names>\n\u003C\u002Fif>\n\n\u003Cif not in project>\nNot run inside a mobile-app project.\n\u003C\u002Fif>\n\n### Affected native package\n\n\u003Cinclude only when the issue concerns @microsoft\u002Fpower-apps-native-*>\n- Package: `\u003Cpackage name>`\n- Declared version: `\u003Cpackage.json range>`\n- Resolved version: `\u003Cpackage-lock.json version or unknown>`\n- Platform: `\u003CiOS \u002F Android>`\n- Ownership evidence: \u003Cwhy the documented caller contract is satisfied and the failure is package-internal>\n\n### Reproduction steps\n\n1.\n2.\n3.\n\n### Expected\n\n\u003Cwhat should have happened>\n\n### Actual\n\n\u003Cwhat happened>\n\n### Logs \u002F errors\n\n```\n\u003Cpaste verbatim — sensitive values redacted>\n```\n\n### Notes\n\n\u003Canything else>\n```\n\n### Step 5 — Print URL\n\n**Telemetry checkpoint: `generate_issue_submission_url`**\n\nTell the user:\n\n> Open this URL to file the issue:\n>\n> \u003Chttps:\u002F\u002Fgithub.com\u002Fmicrosoft\u002Fpower-platform-skills\u002Fissues\u002Fnew?labels=plugin%3Amobile-app>\n>\n> Paste the block above into the body. Review for any sensitive values before submitting.\n\nIf the user wants to open it, suggest `open \u003Curl>` (macOS) \u002F `xdg-open \u003Curl>` (Linux) \u002F `start \u003Curl>` (Windows). Do not auto-open without confirmation.\n\n## Notes\n\n- This skill never modifies any file or invokes mutating commands. Pure diagnostic.\n- For diagnosing connection-specific failures, suggest the user run `\u002Flist-connections` first and paste that output into the issue.\n- For diagnosing build failures, suggest they include the full Metro\u002FGradle\u002FXcode log (not truncated).\n",{"name":5,"model":38,"description":7,"allowed-tools":49,"argument-hint":50,"user-invocable":51},"Read, Bash, Glob, Grep, AskUserQuestion","[optional: brief description of the bug]",true,"main","0a55a88fa2855404029d1e5450faf92878baf763","plugins\u002Fmobile-apps\u002Fskills\u002Freport-issue",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":63,"prompt":73,"zipAvailable":51},[64,67,70],{"tool":65,"command":66},"npx","npx skills add microsoft\u002Fpower-platform-skills --skill report-issue",{"tool":68,"command":69},"bunx","bunx skills add microsoft\u002Fpower-platform-skills --skill report-issue",{"tool":71,"command":72},"pnpm","pnpm dlx skills add microsoft\u002Fpower-platform-skills --skill report-issue","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002Fmicrosoft\u002Fpower-platform-skills\u002Fblob\u002Fmain\u002Fplugins\u002Fmobile-apps\u002Fskills\u002Freport-issue\u002FSKILL.md",[],[76,84,102,116,134,148],{"skillNo":77,"name":78,"nameZh":6,"description":79,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":80,"categories":81,"keywords":82,"publishedAt":83},"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":85,"name":86,"nameZh":6,"description":87,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":88,"categories":89,"keywords":90,"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",[],[86,91,92,93,94,95,28,96,97,27,39,98,99,100,36,101],"configuration","diagnostics","error","environment","cloud","connection","authentication","recovery","process","sign","intelligence",{"skillNo":103,"name":5,"nameZh":6,"description":104,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":105,"categories":106,"keywords":108,"publishedAt":44},"01M699WSR9EX55YY1WD9J22FEG","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",[107],{"categoryNo":19,"categoryName":20,"taxonomyType":21,"taxonomyTypeDesc":22},[25,24,26,109,27,28,110,111,99,35,101,112,113,114,115],"bug-report","operation","draft","summary","user","for","support",{"skillNo":117,"name":118,"nameZh":6,"description":119,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":120,"categories":121,"keywords":122,"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",[],[123,99,124,125,27,126,127,28,128,129,130,36,131,132,133],"investigate","investigate process","question","process mining","business","across","perspectives","mining","pattern","investigation","analytical",{"skillNo":135,"name":136,"nameZh":6,"description":137,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":138,"categories":139,"keywords":140,"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",[],[141,142,143,144,145,146,27,28,147,36],"metric","derive metric","missing","formula","custom","reuse","saved",{"skillNo":149,"name":150,"nameZh":6,"description":151,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":152,"categories":153,"keywords":154,"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",[],[155,156,27,28,157,99,36],"compare","compare cohorts","results"]