[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M699NN1J40NK9QDAF5RH8HRP":3,"skill-same:01M699NN1J40NK9QDAF5RH8HRP":131},{"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":26,"publishedAt":47,"linkOnly":48,"markdownContent":49,"markdownBody":50,"frontMatter":51,"refName":54,"commitSha":55,"skillDirectory":56,"forksCount":57,"repositoryHtmlUrl":58,"repositoryHomepageUrl":59,"ownerHtmlUrl":60,"ownerBlogUrl":61,"ownerDescription":62,"updatedAt":63,"install":64,"resources":76},"01M699NN1J40NK9QDAF5RH8HRP","deploy",null,"Use to deploy, publish, or push an Expo\u002FReact Native Power Apps mobile app to a Power Platform tenant.","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\u002Fdeploy\u002FSKILL.md",[18,23],{"categoryNo":19,"categoryName":20,"taxonomyType":21,"taxonomyTypeDesc":22},"01JBSEEDCAT000000000000011","运维与部署","SCENARIO","使用场景",{"categoryNo":24,"categoryName":25,"taxonomyType":21,"taxonomyTypeDesc":22},"01JBSEEDCAT000000000000023","Skill与智能体开发",[5,27,28,29,30,31,32,33,34,35,36,37,38,39,40,41,42,43,44,45,46],"power","tenant","true","sonnet","native","apps","app","platform","expo","mobile","mobile app","react","use","react native","read","Bash","publish","push","power platform","power apps","2026-11-10 10:12:30",false,"---\nname: deploy\ndescription: Use to deploy, publish, or push an Expo\u002FReact Native Power Apps mobile app to a Power Platform tenant.\nuser-invocable: true\nallowed-tools: Read, Glob, Bash, AskUserQuestion, Skill\nmodel: sonnet\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 first.\n\n# Deploy\n\nBuilds the mobile app in the current directory and pushes it to the Power Platform environment recorded in `power.config.json`.\n\nThis skill uses the standard 4-step deployment flow for this plugin: check memory bank, build, deploy, then update memory bank.\n\n## Out of scope (deliberately)\n\n- `expo run:ios` \u002F `expo run:android` — local native compile is the user's choice; run your platform-specific native command directly when ready.\n- OTA updates and store distribution — out of scope for v0.\n- Starting Metro for local dev — created apps use `npm run dev`; template Metro config writes `.powernative` logs for `\u002Fdebug-app`.\n\n## Workflow\n\n1. Check memory bank → 1.5 App ID preflight → 2. Build → 2.4 Native package → 2.5 Offline profile coverage gate → 3. Deploy → 4. Update memory bank\n\n---\n\n### Step 1 — Check memory bank\n\nRead `memory-bank.md` from the project root if present. Capture:\n\n- Project name\n- Environment (id + display name)\n- Current version\n\nIf absent, continue — the project may have been created without the plugin. Re-derive env from `power.config.json` if needed.\n\n### Step 1.5 — App ID preflight (first-deploy gate)\n\nRead `power.config.json` **before building anything**:\n\n```bash\nnode -e \"const c=require('.\u002Fpower.config.json');console.log(c.appId||'MISSING')\"\n```\n\n- **Prints a GUID** → normal path. Continue to Step 2.\n- **Prints `MISSING`** (null, absent, or empty) → this is a **first deploy**. Say so plainly *before* doing any work:\n\n  > \"⚠️ First deploy detected — `power.config.json` has no `appId` yet. The app ID is minted by the first push, but it is compiled **into** the native bundle at build time. So two full build+push cycles are required. I'll run both; the second is not optional.\"\n\n  Then run Steps 2 → 2.4 → 2.5 → 3 **twice**. In cycle 2, `npm run build` *and* the Step 2.4 native packaging commands must all re-run — the Hermes bundles from cycle 1 have an empty app ID compiled in. Step 2.5 (offline profile gate) may be skipped on cycle 2 **only if** no schema or profile file changed between the two cycles; if in doubt, re-run it — it is a local, no-network check.\n\n**Why two cycles are unavoidable.** `power-apps push` mints the app ID and writes it back to `power.config.json`, but it refuses to run at all without an existing build — it fails immediately if the configured `buildPath` (`.\u002Fdist`) is absent. So the ID cannot be minted before the first build, and the first build cannot contain the ID.\n\n**Why this is so easy to miss.** The runtime guard is:\n\n```js\nPlatform.OS !== 'web' && !isDevPlayer && !hasConfiguredValue(powerConfig.appId)\n```\n\nWeb is **exempt**, and so is Dev Player. The Code App, `npm run dev`, and the browser preview all look perfectly healthy. The failure appears only in the **wrapped native app**, as a full-screen red *\"App ID is missing — Push the mobile app to the Power Platform environment, rebuild it, and try again.\"* That is after a base-package wrap, a signed build, and a device install — the most expensive possible place to discover a one-line config gap.\n\n### Step 2 — Build\n\n**Telemetry checkpoint: `build_power_apps_bundle`**\n\n**Print before starting:**\n> \"→ Building production web bundle via `npm run build` (= `expo export --platform web`). ~30–90 seconds.\"\n\nFirst regenerate `connectorSchemas.ts` so `app\u002F_layout.tsx`'s `schemaMap` import reflects every connector currently in `.power\u002Fschemas\u002F`. The npm `prestart`\u002F`preandroid`\u002F`preios` hooks cover dev runs, but `npm run build` does **not** — if a connector was added since the last `npm run dev`, the bundled JS would ship a stale schema map. Always regenerate before build:\n\n```bash\nnpm run generate-schemas\nnpm run build\n```\n\nIf `package.json` has no `build` script, fall back to:\n\n```bash\nnpx --no-install expo export --platform web\n```\n\n(The current template does not define a `build` script, so this fallback is the normal path for freshly scaffolded apps. Both forms produce the same `dist\u002F` web output.)\n\n**Known issue — `expo export --platform web` never exits.** The export finishes its work (writes `dist\u002F`, prints `Exported: dist` and the asset count) and then **hangs indefinitely**. Reproduced deterministically across separate runs; observed still alive 2h34m after completing. `dist\u002F` is complete and correct when this happens. Suspected cause: the Metro config returned by `createPowerAppsMetroConfig` (`metro.config.js`) installs a dev-server middleware internally, which appears to hold an open handle — a web *export* should not need a dev server. Note the template itself only calls `createPowerAppsMetroConfig`; the middleware is applied inside `@microsoft\u002Fpower-apps-native-host`, not in app code. **Not yet root-caused.**\n\n**Do not wait on the process.** Run it detached and poll for the artifact. Per shared-instructions, scratch files stay project-local in `.tmp\u002F` — a fixed `\u002Ftmp\u002F` path would collide across concurrent projects, and a stale log there could satisfy the grep below and falsely report success:\n\n```bash\nmkdir -p .tmp\nrm -f .tmp\u002Fexpo-web-export.log\nnpx --no-install expo export --platform web > .tmp\u002Fexpo-web-export.log 2>&1 &\nEXPORT_PID=$!\nfor _ in $(seq 1 90); do\n  grep -q \"Exported: dist\" .tmp\u002Fexpo-web-export.log 2>\u002Fdev\u002Fnull && break\n  sleep 2\ndone\nif ! grep -q \"Exported: dist\" .tmp\u002Fexpo-web-export.log 2>\u002Fdev\u002Fnull; then\n  echo \"web export did not complete in 180s\"; tail -30 .tmp\u002Fexpo-web-export.log; exit 1\nfi\ntest -f dist\u002Findex.html || { echo \"dist\u002Findex.html missing\"; exit 1; }\nkill \"$EXPORT_PID\" 2>\u002Fdev\u002Fnull || true\necho \"✓ web export complete (process terminated manually — known hang)\"\n```\n\nTreat a completed `dist\u002F` as success even though the process had to be killed. The Step 2.4 native packaging commands are **not** affected — both exit 0 cleanly and stage into `dist\u002F` via a temp dir, so they do not clear the web build.\n\nIf the build fails:\n\n- **`TS6133` (unused import)** → remove the import and retry once.\n- **Other TypeScript errors** → report file + line and STOP. Don't deploy a broken build.\n- **Metro bundler errors** → surface the full stack and STOP.\n\nVerify `dist\u002F` exists with `index.html` before continuing.\n\n### Step 2.4 — Native package (Hermes bundle + customer assets)\n\n**Print before starting:**\n> \"→ Compiling the native Hermes bundle and hash-addressed asset package for iOS and Android. No JavaScript is compiled inside the wrap pipeline — it only consumes these prebuilt files. ~1–3 minutes.\"\n\n**Node version gate (required).** The native export crashes on **Node \u003C 20.19.4** — it hits `util.styleText(['yellow','inverse','bold'], …)`, which older Node rejects, failing the Metro bundle with a cryptic `ERR_INVALID_ARG_VALUE`. Check first:\n\n```bash\nnode -e 'const [M,m,p]=process.versions.node.split(\".\").map(Number); const ok = M>20 || (M===20 && (m>19 || (m===19 && p>=4))); if (!ok) { console.error(`Node ${process.versions.node} is too old; need >= 20.19.4`); process.exit(1); } console.log(`✓ Node ${process.versions.node}`);'\n```\nIf it exits non-zero, STOP and tell the user to switch (`nvm use 20.19.4`, or install Node ≥ 20.19.4) and rerun. Do **not** run the native packaging commands on older Node.\n\nThe web build above produces `dist\u002Findex.html` (the hosted Code App). Native **wrapped** apps additionally need a precompiled Hermes bundle **and** the customer's images\u002Ffonts as hash-addressed asset files, so the wrap pipeline never compiles or downloads JavaScript. Produce both platforms:\n\n```bash\nnpm run bundle:android\nnpm run bundle:ios\n```\n\nEach command produces that platform's native Hermes bundle **and** its customer asset package, writing next to `dist\u002Findex.html`:\n\n- **Android:** `dist\u002Findex.android.bundle.hbc` (Hermes bytecode) + `dist\u002Fpowerapps-customer-assets-android\u002F` (`manifest.json` + `assets\u002F\u003CfileHash>.\u003Ctype>`)\n- **iOS:** `dist\u002Fmain.jsbundle.hbc` (Hermes bytecode) + `dist\u002Fpowerapps-customer-assets-ios\u002F` (`manifest.json` + `assets\u002F\u003CfileHash>.\u003Ctype>`)\n\nBoth platforms are required — the verification below fails if either bundle or either manifest is missing.\n\nThese sit alongside `index.html` under the same container SAS, so the wrap pipeline fetches them as siblings — no RP or connector change is required.\n\n**Verify before continuing** — STOP on any failure (never push a web-only build for a native-wrapped app):\n\n```bash\n# Hermes magic bytes on both bundles (expect c61fbc03)\nfor f in dist\u002Findex.android.bundle.hbc dist\u002Fmain.jsbundle.hbc; do\n  test -f \"$f\" || { echo \"MISSING $f\"; exit 1; }\n  node -e 'const fs=require(\"fs\"),b=Buffer.alloc(4),fd=fs.openSync(process.argv[1],\"r\");fs.readSync(fd,b,0,4,0);fs.closeSync(fd);process.exit(b.toString(\"hex\")===\"c61fbc03\"?0:1)' \"$f\" || { echo \"$f is not Hermes bytecode\"; exit 1; }\ndone\n# both asset manifests present\ntest -f dist\u002Fpowerapps-customer-assets-android\u002Fmanifest.json || { echo \"MISSING android manifest\"; exit 1; }\ntest -f dist\u002Fpowerapps-customer-assets-ios\u002Fmanifest.json     || { echo \"MISSING ios manifest\"; exit 1; }\necho \"✓ native package + asset manifests present\"\n```\n\nIf a native packaging step fails, surface the error and STOP. If the app renders bundled images\u002Ffonts, also confirm each `manifest.json` `assets` array is non-empty (an empty array means the app doesn't `require()` any static asset yet).\n\n### Step 2.5 — Offline profile coverage gate\n\n**Telemetry checkpoint: `validate_offline_profile_coverage`**\n\nThis is the final chance to catch schema that never made it into the Mobile Offline Profile before it ships — a table added to the data model but not the profile never syncs to devices, and a new column arrives blank offline. Validate that every schema change is covered **before** pushing.\n\nFor this offline gate, first resolve the approved app's absolute `working_dir`\nusing [app-working-directory.md](${PLUGIN_ROOT}\u002Fshared\u002Freferences\u002Fapp-working-directory.md)\nbefore running the check below or any helper. Bind every offline check, file\nread, and helper call to that same root.\n\nRun the local, no-network delta check (`.datamodel-manifest.json` vs `offline-profile.json`):\n\n```bash\ncd -- '\u003Cworking_dir>' || { echo \"BLOCKED: cannot enter working_dir\" >&2; exit 1; }\nnode \"${PLUGIN_ROOT}\u002Fscripts\u002Foffline-profile-delta.js\" --project-root '\u003Cworking_dir>'\n```\n\nBranch on the JSON `status` (full contract in [offline-profile-reconciliation.md](${PLUGIN_ROOT}\u002Fshared\u002Freferences\u002Foffline-profile-reconciliation.md)):\n\n| `status` | Action |\n|---|---|\n| `no-manifest` | Connectors-only app — no Dataverse schema. Continue to Step 3 silently. |\n| `no-profile` | No offline profile in this project. Print one line: `↷ No offline profile — skipping offline coverage check. Run \u002Fsetup-offline-profile if you want offline support.` Continue to Step 3. |\n| `in-sync` | Print `✓ Offline profile covers all schema changes.` Continue to Step 3. |\n| `error` | `offline-profile.json` is unreadable — the script prints `status: error` and **exits non-zero**. Offline coverage can't be validated against a corrupt file, so **STOP before pushing**: surface the `error` string and have the user fix `offline-profile.json` and re-run, or type the `deploy without offline` override (below) to push anyway. |\n| `delta` | **STOP before pushing.** See below. |\n\n**On `delta`** — print the uncovered schema, then gate with `AskUserQuestion`:\n\n```\n⚠ The offline profile is missing schema changes. If you deploy now, these won't be\n  available on disconnected devices:\n\n  Tables not in the profile : \u003CmissingTables[].logicalName>\n  Tables with new columns   : \u003CtablesWithNewColumns[].logicalName (newColumns)>\n```\n\nOptions:\n\n- **Update the offline profile now (recommended)** — use the reconciliation reference's **Scoped helper handoffs** with `orchestrator: deploy`, absolute `working_dir`, `phase: implementation`, and the approved environment\u002Fprofile\u002Ftable scope. Read and execute `${PLUGIN_ROOT}\u002Fskills\u002Fadd-table-to-offline-profile\u002FSKILL.md` with `--working-dir '\u003Cworking_dir>' --table \u003Ct>` for each approved `missingTables[]` entry, then `${PLUGIN_ROOT}\u002Fskills\u002Fedit-offline-profile\u002FSKILL.md` with those arguments plus `--columns add:\u003CnewColumns>` for each approved `tablesWithNewColumns[]` entry. Re-run the guarded delta check; when it reports `in-sync`, continue to Step 3.\n- **Deploy anyway** — requires an explicit override. Wait for the exact phrase `deploy without offline` (case-insensitive); a bare `y`\u002F`yes` is not enough, mirroring the environment-mismatch gate in Step 3. Then continue to Step 3 and note the skipped reconciliation in the Step 4 build-history row.\n\nDo not push until the gate is resolved (reconciled to `in-sync`, or explicitly overridden).\n\n### Step 3 — Deploy\n\n**Telemetry checkpoint: `push_app_to_power_platform`**\n\n**Resolve and confirm the target environment FIRST.** `pa app push` deploys to the environment configured in `power.config.json`. Resolve that ID to a Dataverse URL so the user catches drift before pushing.\n\nRun:\n\n```bash\nENV_ID=$(node -e \"console.log(require('.\u002Fpower.config.json').environmentId)\")\nnode \"${PLUGIN_ROOT}\u002Fscripts\u002Fresolve-environment.js\" \"$ENV_ID\"\n```\n\nFrom `resolve-environment.js` capture the **Environment URL** (e.g. `https:\u002F\u002Fcontoso.crm.dynamics.com\u002F`), **Environment ID**, and **Tenant ID**. Cross-check against `memory-bank.md` \u002F `power.config.json`:\n\n- **Match** → proceed to the confirmation prompt below.\n- **Mismatch** → STOP. Surface both values side-by-side and ask the user to either (a) update `power.config.json` by re-running init in the intended app root, or (b) explicitly type `override` to push to the environment already recorded in `power.config.json`. Do not proceed on a bare `y`.\n- **Cannot resolve\u002Fauthenticate** → STOP with `az login --tenant \u003Cenv-tenant>` instructions, or ask the user to provide the environment URL directly.\n\n**Print before starting:**\n> \"→ Pushing bundle to Power Platform via `pa app push`. ~30–60 seconds.\"\n\nConfirm with the user using the **resolved env URL, not just the friendly name**:\n\n> \"Ready to deploy to **\u003Cenv-name>** (`\u003Cenv-url>`)? This will update the live app for every user in that environment. Type `yes deploy to \u003Cenv-name>` to confirm.\"\n\nWait for the exact phrase `yes deploy to \u003Cenv-name>` (case-insensitive, env-name matching). A bare `y` \u002F `yes` is not enough — too easy to fire on autopilot when the wrong env is active. Then:\n\n> Resolve the CLI first (see [cli-binary.md](${PLUGIN_ROOT}\u002Fshared\u002Fcli-binary.md)): run as `$PA app push` (`npx --no-install pa …`), never a bare `pa`. On `power-apps`-only projects, translate to `power-apps push`.\n\n```bash\n$PA app push --non-interactive\n```\n\nCapture the app URL from the output if printed.\n\n**First-deploy loop-back.** If Step 1.5 reported `MISSING`, re-read the config now:\n\n```bash\nnode -e \"const c=require('.\u002Fpower.config.json');console.log(c.appId||'STILL MISSING')\"\n```\n\n- **GUID** → the app was registered. **Go back to Step 2 and run Build → 2.4 → 2.5 → Deploy one more time.** The artifacts now sitting in `dist\u002F` (and already uploaded to the blob) still have an empty app ID compiled in; without the second cycle the wrapped app fails on-device. Step 2.5 may be skipped on this second pass **only if** nothing under `.datamodel-manifest.json` \u002F `offline-profile.json` changed since cycle 1.\n- **`STILL MISSING`** → push did not register the app. STOP and report. Do not proceed to wrap.\n\nOn the second pass this check is a no-op, and Step 4 runs as normal.\n\nIf deploy fails, report the error and STOP — do not retry silently. Common fixes:\n\n| Error | Fix |\n|---|---|\n| `pa app push` auth error, wrong user, or multiple accounts | Follow shared-instructions command-failure handling. `az login` \u002F `az account set` does not switch the standalone Power Apps CLI account. |\n| Environment mismatch | Re-run `$PA app init -t MobileApp --display-name \u003Cname> --environment-id \u003Cid> --non-interactive` in a fresh\u002Fapp root for the intended target|\n| `$PA` is empty (`PA_KIND=none` — CLI not installed) | Ask the user to run `npm install` in the project root (the template pins `@microsoft\u002Fpower-apps-cli`), then re-resolve `$PA` per [cli-binary.md](${PLUGIN_ROOT}\u002Fshared\u002Fcli-binary.md). Never fall back to a bare `npx pa` or `npx power-apps`. |\n\n### Step 4 — Update memory bank\n\nIf `memory-bank.md` exists, increment the version (`v1.0.0` → `v1.1.0`) and update:\n\n- Current version\n- Last deployed timestamp\n- App URL (if captured)\n- Append a row to the **Build history** section: `| v1.1.0 | \u003Ctimestamp> | deploy | success |`\n\nPrint the summary card:\n\n```\n✅ Deploy — \u003Cproject-name>\n─────────────────────────────────────────────\nVersion       : \u003Cnew-version>\nEnvironment   : \u003Cenv-name>\nApp URL       : \u003Curl or \"see make.powerapps.com\">\nBundle path   : dist\u002F\n\nLocal dev:    npm run dev  (writes .powernative logs for \u002Fdebug-app)\nRe-deploy:    \u002Fdeploy\nList conns:   \u002Flist-connections\n─────────────────────────────────────────────\n```\n\n---\n\n## Local dev (out of scope for this skill — for reference only)\n\nWhen the user wants normal Expo iteration with portable monitoring, they can run:\n\n```bash\nnpm run dev          # Metro + QR + .powernative log\n```\n\nThis launches Metro, prints a QR code, and writes sanitized output to `.powernative\u002Fmetro-logs\u002F` so `\u002Fdebug-app` can reattach after a host\u002Fsession restart. They can:\n\n- Scan the QR with the installed native dev client\n- Reload from the native dev-client menu\n\nDo not use React Native Web, browser automation, direct Metro\u002Flocalhost HTTP probes, or screen-by-screen runtime checks.\n\nIf they want to compile a native binary locally, they run the platform-specific native command directly. Local native compile and manual device testing are user-owned and are not deployment gates for this skill.\n\n## Reference\n\n- [`shared\u002Fversion-check.md`](${PLUGIN_ROOT}\u002Fshared\u002Fversion-check.md) — min versions (only Always-required tier matters here)\n- [`shared\u002Fmemory-bank.md`](${PLUGIN_ROOT}\u002Fshared\u002Fmemory-bank.md) — Build history schema\n- [`shared\u002Freferences\u002Foffline-profile-reconciliation.md`](${PLUGIN_ROOT}\u002Fshared\u002Freferences\u002Foffline-profile-reconciliation.md) — Step 2.5 offline coverage gate\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 first.\n\n# Deploy\n\nBuilds the mobile app in the current directory and pushes it to the Power Platform environment recorded in `power.config.json`.\n\nThis skill uses the standard 4-step deployment flow for this plugin: check memory bank, build, deploy, then update memory bank.\n\n## Out of scope (deliberately)\n\n- `expo run:ios` \u002F `expo run:android` — local native compile is the user's choice; run your platform-specific native command directly when ready.\n- OTA updates and store distribution — out of scope for v0.\n- Starting Metro for local dev — created apps use `npm run dev`; template Metro config writes `.powernative` logs for `\u002Fdebug-app`.\n\n## Workflow\n\n1. Check memory bank → 1.5 App ID preflight → 2. Build → 2.4 Native package → 2.5 Offline profile coverage gate → 3. Deploy → 4. Update memory bank\n\n---\n\n### Step 1 — Check memory bank\n\nRead `memory-bank.md` from the project root if present. Capture:\n\n- Project name\n- Environment (id + display name)\n- Current version\n\nIf absent, continue — the project may have been created without the plugin. Re-derive env from `power.config.json` if needed.\n\n### Step 1.5 — App ID preflight (first-deploy gate)\n\nRead `power.config.json` **before building anything**:\n\n```bash\nnode -e \"const c=require('.\u002Fpower.config.json');console.log(c.appId||'MISSING')\"\n```\n\n- **Prints a GUID** → normal path. Continue to Step 2.\n- **Prints `MISSING`** (null, absent, or empty) → this is a **first deploy**. Say so plainly *before* doing any work:\n\n  > \"⚠️ First deploy detected — `power.config.json` has no `appId` yet. The app ID is minted by the first push, but it is compiled **into** the native bundle at build time. So two full build+push cycles are required. I'll run both; the second is not optional.\"\n\n  Then run Steps 2 → 2.4 → 2.5 → 3 **twice**. In cycle 2, `npm run build` *and* the Step 2.4 native packaging commands must all re-run — the Hermes bundles from cycle 1 have an empty app ID compiled in. Step 2.5 (offline profile gate) may be skipped on cycle 2 **only if** no schema or profile file changed between the two cycles; if in doubt, re-run it — it is a local, no-network check.\n\n**Why two cycles are unavoidable.** `power-apps push` mints the app ID and writes it back to `power.config.json`, but it refuses to run at all without an existing build — it fails immediately if the configured `buildPath` (`.\u002Fdist`) is absent. So the ID cannot be minted before the first build, and the first build cannot contain the ID.\n\n**Why this is so easy to miss.** The runtime guard is:\n\n```js\nPlatform.OS !== 'web' && !isDevPlayer && !hasConfiguredValue(powerConfig.appId)\n```\n\nWeb is **exempt**, and so is Dev Player. The Code App, `npm run dev`, and the browser preview all look perfectly healthy. The failure appears only in the **wrapped native app**, as a full-screen red *\"App ID is missing — Push the mobile app to the Power Platform environment, rebuild it, and try again.\"* That is after a base-package wrap, a signed build, and a device install — the most expensive possible place to discover a one-line config gap.\n\n### Step 2 — Build\n\n**Telemetry checkpoint: `build_power_apps_bundle`**\n\n**Print before starting:**\n> \"→ Building production web bundle via `npm run build` (= `expo export --platform web`). ~30–90 seconds.\"\n\nFirst regenerate `connectorSchemas.ts` so `app\u002F_layout.tsx`'s `schemaMap` import reflects every connector currently in `.power\u002Fschemas\u002F`. The npm `prestart`\u002F`preandroid`\u002F`preios` hooks cover dev runs, but `npm run build` does **not** — if a connector was added since the last `npm run dev`, the bundled JS would ship a stale schema map. Always regenerate before build:\n\n```bash\nnpm run generate-schemas\nnpm run build\n```\n\nIf `package.json` has no `build` script, fall back to:\n\n```bash\nnpx --no-install expo export --platform web\n```\n\n(The current template does not define a `build` script, so this fallback is the normal path for freshly scaffolded apps. Both forms produce the same `dist\u002F` web output.)\n\n**Known issue — `expo export --platform web` never exits.** The export finishes its work (writes `dist\u002F`, prints `Exported: dist` and the asset count) and then **hangs indefinitely**. Reproduced deterministically across separate runs; observed still alive 2h34m after completing. `dist\u002F` is complete and correct when this happens. Suspected cause: the Metro config returned by `createPowerAppsMetroConfig` (`metro.config.js`) installs a dev-server middleware internally, which appears to hold an open handle — a web *export* should not need a dev server. Note the template itself only calls `createPowerAppsMetroConfig`; the middleware is applied inside `@microsoft\u002Fpower-apps-native-host`, not in app code. **Not yet root-caused.**\n\n**Do not wait on the process.** Run it detached and poll for the artifact. Per shared-instructions, scratch files stay project-local in `.tmp\u002F` — a fixed `\u002Ftmp\u002F` path would collide across concurrent projects, and a stale log there could satisfy the grep below and falsely report success:\n\n```bash\nmkdir -p .tmp\nrm -f .tmp\u002Fexpo-web-export.log\nnpx --no-install expo export --platform web > .tmp\u002Fexpo-web-export.log 2>&1 &\nEXPORT_PID=$!\nfor _ in $(seq 1 90); do\n  grep -q \"Exported: dist\" .tmp\u002Fexpo-web-export.log 2>\u002Fdev\u002Fnull && break\n  sleep 2\ndone\nif ! grep -q \"Exported: dist\" .tmp\u002Fexpo-web-export.log 2>\u002Fdev\u002Fnull; then\n  echo \"web export did not complete in 180s\"; tail -30 .tmp\u002Fexpo-web-export.log; exit 1\nfi\ntest -f dist\u002Findex.html || { echo \"dist\u002Findex.html missing\"; exit 1; }\nkill \"$EXPORT_PID\" 2>\u002Fdev\u002Fnull || true\necho \"✓ web export complete (process terminated manually — known hang)\"\n```\n\nTreat a completed `dist\u002F` as success even though the process had to be killed. The Step 2.4 native packaging commands are **not** affected — both exit 0 cleanly and stage into `dist\u002F` via a temp dir, so they do not clear the web build.\n\nIf the build fails:\n\n- **`TS6133` (unused import)** → remove the import and retry once.\n- **Other TypeScript errors** → report file + line and STOP. Don't deploy a broken build.\n- **Metro bundler errors** → surface the full stack and STOP.\n\nVerify `dist\u002F` exists with `index.html` before continuing.\n\n### Step 2.4 — Native package (Hermes bundle + customer assets)\n\n**Print before starting:**\n> \"→ Compiling the native Hermes bundle and hash-addressed asset package for iOS and Android. No JavaScript is compiled inside the wrap pipeline — it only consumes these prebuilt files. ~1–3 minutes.\"\n\n**Node version gate (required).** The native export crashes on **Node \u003C 20.19.4** — it hits `util.styleText(['yellow','inverse','bold'], …)`, which older Node rejects, failing the Metro bundle with a cryptic `ERR_INVALID_ARG_VALUE`. Check first:\n\n```bash\nnode -e 'const [M,m,p]=process.versions.node.split(\".\").map(Number); const ok = M>20 || (M===20 && (m>19 || (m===19 && p>=4))); if (!ok) { console.error(`Node ${process.versions.node} is too old; need >= 20.19.4`); process.exit(1); } console.log(`✓ Node ${process.versions.node}`);'\n```\nIf it exits non-zero, STOP and tell the user to switch (`nvm use 20.19.4`, or install Node ≥ 20.19.4) and rerun. Do **not** run the native packaging commands on older Node.\n\nThe web build above produces `dist\u002Findex.html` (the hosted Code App). Native **wrapped** apps additionally need a precompiled Hermes bundle **and** the customer's images\u002Ffonts as hash-addressed asset files, so the wrap pipeline never compiles or downloads JavaScript. Produce both platforms:\n\n```bash\nnpm run bundle:android\nnpm run bundle:ios\n```\n\nEach command produces that platform's native Hermes bundle **and** its customer asset package, writing next to `dist\u002Findex.html`:\n\n- **Android:** `dist\u002Findex.android.bundle.hbc` (Hermes bytecode) + `dist\u002Fpowerapps-customer-assets-android\u002F` (`manifest.json` + `assets\u002F\u003CfileHash>.\u003Ctype>`)\n- **iOS:** `dist\u002Fmain.jsbundle.hbc` (Hermes bytecode) + `dist\u002Fpowerapps-customer-assets-ios\u002F` (`manifest.json` + `assets\u002F\u003CfileHash>.\u003Ctype>`)\n\nBoth platforms are required — the verification below fails if either bundle or either manifest is missing.\n\nThese sit alongside `index.html` under the same container SAS, so the wrap pipeline fetches them as siblings — no RP or connector change is required.\n\n**Verify before continuing** — STOP on any failure (never push a web-only build for a native-wrapped app):\n\n```bash\n# Hermes magic bytes on both bundles (expect c61fbc03)\nfor f in dist\u002Findex.android.bundle.hbc dist\u002Fmain.jsbundle.hbc; do\n  test -f \"$f\" || { echo \"MISSING $f\"; exit 1; }\n  node -e 'const fs=require(\"fs\"),b=Buffer.alloc(4),fd=fs.openSync(process.argv[1],\"r\");fs.readSync(fd,b,0,4,0);fs.closeSync(fd);process.exit(b.toString(\"hex\")===\"c61fbc03\"?0:1)' \"$f\" || { echo \"$f is not Hermes bytecode\"; exit 1; }\ndone\n# both asset manifests present\ntest -f dist\u002Fpowerapps-customer-assets-android\u002Fmanifest.json || { echo \"MISSING android manifest\"; exit 1; }\ntest -f dist\u002Fpowerapps-customer-assets-ios\u002Fmanifest.json     || { echo \"MISSING ios manifest\"; exit 1; }\necho \"✓ native package + asset manifests present\"\n```\n\nIf a native packaging step fails, surface the error and STOP. If the app renders bundled images\u002Ffonts, also confirm each `manifest.json` `assets` array is non-empty (an empty array means the app doesn't `require()` any static asset yet).\n\n### Step 2.5 — Offline profile coverage gate\n\n**Telemetry checkpoint: `validate_offline_profile_coverage`**\n\nThis is the final chance to catch schema that never made it into the Mobile Offline Profile before it ships — a table added to the data model but not the profile never syncs to devices, and a new column arrives blank offline. Validate that every schema change is covered **before** pushing.\n\nFor this offline gate, first resolve the approved app's absolute `working_dir`\nusing [app-working-directory.md](${PLUGIN_ROOT}\u002Fshared\u002Freferences\u002Fapp-working-directory.md)\nbefore running the check below or any helper. Bind every offline check, file\nread, and helper call to that same root.\n\nRun the local, no-network delta check (`.datamodel-manifest.json` vs `offline-profile.json`):\n\n```bash\ncd -- '\u003Cworking_dir>' || { echo \"BLOCKED: cannot enter working_dir\" >&2; exit 1; }\nnode \"${PLUGIN_ROOT}\u002Fscripts\u002Foffline-profile-delta.js\" --project-root '\u003Cworking_dir>'\n```\n\nBranch on the JSON `status` (full contract in [offline-profile-reconciliation.md](${PLUGIN_ROOT}\u002Fshared\u002Freferences\u002Foffline-profile-reconciliation.md)):\n\n| `status` | Action |\n|---|---|\n| `no-manifest` | Connectors-only app — no Dataverse schema. Continue to Step 3 silently. |\n| `no-profile` | No offline profile in this project. Print one line: `↷ No offline profile — skipping offline coverage check. Run \u002Fsetup-offline-profile if you want offline support.` Continue to Step 3. |\n| `in-sync` | Print `✓ Offline profile covers all schema changes.` Continue to Step 3. |\n| `error` | `offline-profile.json` is unreadable — the script prints `status: error` and **exits non-zero**. Offline coverage can't be validated against a corrupt file, so **STOP before pushing**: surface the `error` string and have the user fix `offline-profile.json` and re-run, or type the `deploy without offline` override (below) to push anyway. |\n| `delta` | **STOP before pushing.** See below. |\n\n**On `delta`** — print the uncovered schema, then gate with `AskUserQuestion`:\n\n```\n⚠ The offline profile is missing schema changes. If you deploy now, these won't be\n  available on disconnected devices:\n\n  Tables not in the profile : \u003CmissingTables[].logicalName>\n  Tables with new columns   : \u003CtablesWithNewColumns[].logicalName (newColumns)>\n```\n\nOptions:\n\n- **Update the offline profile now (recommended)** — use the reconciliation reference's **Scoped helper handoffs** with `orchestrator: deploy`, absolute `working_dir`, `phase: implementation`, and the approved environment\u002Fprofile\u002Ftable scope. Read and execute `${PLUGIN_ROOT}\u002Fskills\u002Fadd-table-to-offline-profile\u002FSKILL.md` with `--working-dir '\u003Cworking_dir>' --table \u003Ct>` for each approved `missingTables[]` entry, then `${PLUGIN_ROOT}\u002Fskills\u002Fedit-offline-profile\u002FSKILL.md` with those arguments plus `--columns add:\u003CnewColumns>` for each approved `tablesWithNewColumns[]` entry. Re-run the guarded delta check; when it reports `in-sync`, continue to Step 3.\n- **Deploy anyway** — requires an explicit override. Wait for the exact phrase `deploy without offline` (case-insensitive); a bare `y`\u002F`yes` is not enough, mirroring the environment-mismatch gate in Step 3. Then continue to Step 3 and note the skipped reconciliation in the Step 4 build-history row.\n\nDo not push until the gate is resolved (reconciled to `in-sync`, or explicitly overridden).\n\n### Step 3 — Deploy\n\n**Telemetry checkpoint: `push_app_to_power_platform`**\n\n**Resolve and confirm the target environment FIRST.** `pa app push` deploys to the environment configured in `power.config.json`. Resolve that ID to a Dataverse URL so the user catches drift before pushing.\n\nRun:\n\n```bash\nENV_ID=$(node -e \"console.log(require('.\u002Fpower.config.json').environmentId)\")\nnode \"${PLUGIN_ROOT}\u002Fscripts\u002Fresolve-environment.js\" \"$ENV_ID\"\n```\n\nFrom `resolve-environment.js` capture the **Environment URL** (e.g. `https:\u002F\u002Fcontoso.crm.dynamics.com\u002F`), **Environment ID**, and **Tenant ID**. Cross-check against `memory-bank.md` \u002F `power.config.json`:\n\n- **Match** → proceed to the confirmation prompt below.\n- **Mismatch** → STOP. Surface both values side-by-side and ask the user to either (a) update `power.config.json` by re-running init in the intended app root, or (b) explicitly type `override` to push to the environment already recorded in `power.config.json`. Do not proceed on a bare `y`.\n- **Cannot resolve\u002Fauthenticate** → STOP with `az login --tenant \u003Cenv-tenant>` instructions, or ask the user to provide the environment URL directly.\n\n**Print before starting:**\n> \"→ Pushing bundle to Power Platform via `pa app push`. ~30–60 seconds.\"\n\nConfirm with the user using the **resolved env URL, not just the friendly name**:\n\n> \"Ready to deploy to **\u003Cenv-name>** (`\u003Cenv-url>`)? This will update the live app for every user in that environment. Type `yes deploy to \u003Cenv-name>` to confirm.\"\n\nWait for the exact phrase `yes deploy to \u003Cenv-name>` (case-insensitive, env-name matching). A bare `y` \u002F `yes` is not enough — too easy to fire on autopilot when the wrong env is active. Then:\n\n> Resolve the CLI first (see [cli-binary.md](${PLUGIN_ROOT}\u002Fshared\u002Fcli-binary.md)): run as `$PA app push` (`npx --no-install pa …`), never a bare `pa`. On `power-apps`-only projects, translate to `power-apps push`.\n\n```bash\n$PA app push --non-interactive\n```\n\nCapture the app URL from the output if printed.\n\n**First-deploy loop-back.** If Step 1.5 reported `MISSING`, re-read the config now:\n\n```bash\nnode -e \"const c=require('.\u002Fpower.config.json');console.log(c.appId||'STILL MISSING')\"\n```\n\n- **GUID** → the app was registered. **Go back to Step 2 and run Build → 2.4 → 2.5 → Deploy one more time.** The artifacts now sitting in `dist\u002F` (and already uploaded to the blob) still have an empty app ID compiled in; without the second cycle the wrapped app fails on-device. Step 2.5 may be skipped on this second pass **only if** nothing under `.datamodel-manifest.json` \u002F `offline-profile.json` changed since cycle 1.\n- **`STILL MISSING`** → push did not register the app. STOP and report. Do not proceed to wrap.\n\nOn the second pass this check is a no-op, and Step 4 runs as normal.\n\nIf deploy fails, report the error and STOP — do not retry silently. Common fixes:\n\n| Error | Fix |\n|---|---|\n| `pa app push` auth error, wrong user, or multiple accounts | Follow shared-instructions command-failure handling. `az login` \u002F `az account set` does not switch the standalone Power Apps CLI account. |\n| Environment mismatch | Re-run `$PA app init -t MobileApp --display-name \u003Cname> --environment-id \u003Cid> --non-interactive` in a fresh\u002Fapp root for the intended target|\n| `$PA` is empty (`PA_KIND=none` — CLI not installed) | Ask the user to run `npm install` in the project root (the template pins `@microsoft\u002Fpower-apps-cli`), then re-resolve `$PA` per [cli-binary.md](${PLUGIN_ROOT}\u002Fshared\u002Fcli-binary.md). Never fall back to a bare `npx pa` or `npx power-apps`. |\n\n### Step 4 — Update memory bank\n\nIf `memory-bank.md` exists, increment the version (`v1.0.0` → `v1.1.0`) and update:\n\n- Current version\n- Last deployed timestamp\n- App URL (if captured)\n- Append a row to the **Build history** section: `| v1.1.0 | \u003Ctimestamp> | deploy | success |`\n\nPrint the summary card:\n\n```\n✅ Deploy — \u003Cproject-name>\n─────────────────────────────────────────────\nVersion       : \u003Cnew-version>\nEnvironment   : \u003Cenv-name>\nApp URL       : \u003Curl or \"see make.powerapps.com\">\nBundle path   : dist\u002F\n\nLocal dev:    npm run dev  (writes .powernative logs for \u002Fdebug-app)\nRe-deploy:    \u002Fdeploy\nList conns:   \u002Flist-connections\n─────────────────────────────────────────────\n```\n\n---\n\n## Local dev (out of scope for this skill — for reference only)\n\nWhen the user wants normal Expo iteration with portable monitoring, they can run:\n\n```bash\nnpm run dev          # Metro + QR + .powernative log\n```\n\nThis launches Metro, prints a QR code, and writes sanitized output to `.powernative\u002Fmetro-logs\u002F` so `\u002Fdebug-app` can reattach after a host\u002Fsession restart. They can:\n\n- Scan the QR with the installed native dev client\n- Reload from the native dev-client menu\n\nDo not use React Native Web, browser automation, direct Metro\u002Flocalhost HTTP probes, or screen-by-screen runtime checks.\n\nIf they want to compile a native binary locally, they run the platform-specific native command directly. Local native compile and manual device testing are user-owned and are not deployment gates for this skill.\n\n## Reference\n\n- [`shared\u002Fversion-check.md`](${PLUGIN_ROOT}\u002Fshared\u002Fversion-check.md) — min versions (only Always-required tier matters here)\n- [`shared\u002Fmemory-bank.md`](${PLUGIN_ROOT}\u002Fshared\u002Fmemory-bank.md) — Build history schema\n- [`shared\u002Freferences\u002Foffline-profile-reconciliation.md`](${PLUGIN_ROOT}\u002Fshared\u002Freferences\u002Foffline-profile-reconciliation.md) — Step 2.5 offline coverage gate\n",{"name":5,"model":30,"description":7,"allowed-tools":52,"user-invocable":53},"Read, Glob, Bash, AskUserQuestion, Skill",true,"main","0a55a88fa2855404029d1e5450faf92878baf763","plugins\u002Fmobile-apps\u002Fskills\u002Fdeploy",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":65,"prompt":75,"zipAvailable":53},[66,69,72],{"tool":67,"command":68},"npx","npx skills add microsoft\u002Fpower-platform-skills --skill deploy",{"tool":70,"command":71},"bunx","bunx skills add microsoft\u002Fpower-platform-skills --skill deploy",{"tool":73,"command":74},"pnpm","pnpm dlx skills add microsoft\u002Fpower-platform-skills --skill deploy","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002Fmicrosoft\u002Fpower-platform-skills\u002Fblob\u002Fmain\u002Fplugins\u002Fmobile-apps\u002Fskills\u002Fdeploy\u002FSKILL.md",[77,83,87,91,97,101,105,109,115,119,123,127],{"path":78,"resourceType":79,"resourceTypeDesc":80,"sizeBytes":81,"sourceHtmlUrl":82},"assets\u002Fmosquitto.conf","ASSET","资产文件",6284,"https:\u002F\u002Fgithub.com\u002Fshengdabai\u002FTony-Claude-Code-Skills\u002Fblob\u002Fmain\u002Fskills\u002F_collections\u002Fdot_claude\u002Fskills\u002Fhardware-protocols\u002Fassets\u002Fmosquitto.conf",{"path":84,"resourceType":79,"resourceTypeDesc":80,"sizeBytes":85,"sourceHtmlUrl":86},"assets\u002Fplatformio_examples\u002Fesp32_mqtt.ini",4221,"https:\u002F\u002Fgithub.com\u002Fshengdabai\u002FTony-Claude-Code-Skills\u002Fblob\u002Fmain\u002Fskills\u002F_collections\u002Fdot_claude\u002Fskills\u002Fhardware-protocols\u002Fassets\u002Fplatformio_examples\u002Fesp32_mqtt.ini",{"path":88,"resourceType":79,"resourceTypeDesc":80,"sizeBytes":89,"sourceHtmlUrl":90},"assets\u002Fplatformio_examples\u002Frp2350_presto.ini",3453,"https:\u002F\u002Fgithub.com\u002Fshengdabai\u002FTony-Claude-Code-Skills\u002Fblob\u002Fmain\u002Fskills\u002F_collections\u002Fdot_claude\u002Fskills\u002Fhardware-protocols\u002Fassets\u002Fplatformio_examples\u002Frp2350_presto.ini",{"path":92,"resourceType":93,"resourceTypeDesc":94,"sizeBytes":95,"sourceHtmlUrl":96},"references\u002Fembedded_bus_protocols.md","REFERENCE","参考文档",8892,"https:\u002F\u002Fgithub.com\u002Fshengdabai\u002FTony-Claude-Code-Skills\u002Fblob\u002Fmain\u002Fskills\u002F_collections\u002Fdot_claude\u002Fskills\u002Fhardware-protocols\u002Freferences\u002Fembedded_bus_protocols.md",{"path":98,"resourceType":93,"resourceTypeDesc":94,"sizeBytes":99,"sourceHtmlUrl":100},"references\u002Fmqtt_reference.md",9238,"https:\u002F\u002Fgithub.com\u002Fshengdabai\u002FTony-Claude-Code-Skills\u002Fblob\u002Fmain\u002Fskills\u002F_collections\u002Fdot_claude\u002Fskills\u002Fhardware-protocols\u002Freferences\u002Fmqtt_reference.md",{"path":102,"resourceType":93,"resourceTypeDesc":94,"sizeBytes":103,"sourceHtmlUrl":104},"references\u002Forbit_integration.md",14278,"https:\u002F\u002Fgithub.com\u002Fshengdabai\u002FTony-Claude-Code-Skills\u002Fblob\u002Fmain\u002Fskills\u002F_collections\u002Fdot_claude\u002Fskills\u002Fhardware-protocols\u002Freferences\u002Forbit_integration.md",{"path":106,"resourceType":93,"resourceTypeDesc":94,"sizeBytes":107,"sourceHtmlUrl":108},"references\u002Fwireless_protocols.md",10806,"https:\u002F\u002Fgithub.com\u002Fshengdabai\u002FTony-Claude-Code-Skills\u002Fblob\u002Fmain\u002Fskills\u002F_collections\u002Fdot_claude\u002Fskills\u002Fhardware-protocols\u002Freferences\u002Fwireless_protocols.md",{"path":110,"resourceType":111,"resourceTypeDesc":112,"sizeBytes":113,"sourceHtmlUrl":114},"scripts\u002Fble_gatt_server.py","SCRIPT","脚本",11891,"https:\u002F\u002Fgithub.com\u002Fshengdabai\u002FTony-Claude-Code-Skills\u002Fblob\u002Fmain\u002Fskills\u002F_collections\u002Fdot_claude\u002Fskills\u002Fhardware-protocols\u002Fscripts\u002Fble_gatt_server.py",{"path":116,"resourceType":111,"resourceTypeDesc":112,"sizeBytes":117,"sourceHtmlUrl":118},"scripts\u002Fi2c_sensor.py",10250,"https:\u002F\u002Fgithub.com\u002Fshengdabai\u002FTony-Claude-Code-Skills\u002Fblob\u002Fmain\u002Fskills\u002F_collections\u002Fdot_claude\u002Fskills\u002Fhardware-protocols\u002Fscripts\u002Fi2c_sensor.py",{"path":120,"resourceType":111,"resourceTypeDesc":112,"sizeBytes":121,"sourceHtmlUrl":122},"scripts\u002Fmqtt_connection.py",10685,"https:\u002F\u002Fgithub.com\u002Fshengdabai\u002FTony-Claude-Code-Skills\u002Fblob\u002Fmain\u002Fskills\u002F_collections\u002Fdot_claude\u002Fskills\u002Fhardware-protocols\u002Fscripts\u002Fmqtt_connection.py",{"path":124,"resourceType":111,"resourceTypeDesc":112,"sizeBytes":125,"sourceHtmlUrl":126},"scripts\u002Fspi_display.py",9309,"https:\u002F\u002Fgithub.com\u002Fshengdabai\u002FTony-Claude-Code-Skills\u002Fblob\u002Fmain\u002Fskills\u002F_collections\u002Fdot_claude\u002Fskills\u002Fhardware-protocols\u002Fscripts\u002Fspi_display.py",{"path":128,"resourceType":111,"resourceTypeDesc":112,"sizeBytes":129,"sourceHtmlUrl":130},"scripts\u002Fuart_parser.py",11379,"https:\u002F\u002Fgithub.com\u002Fshengdabai\u002FTony-Claude-Code-Skills\u002Fblob\u002Fmain\u002Fskills\u002F_collections\u002Fdot_claude\u002Fskills\u002Fhardware-protocols\u002Fscripts\u002Fuart_parser.py",[132,140,159,182,200,214],{"skillNo":133,"name":134,"nameZh":6,"description":135,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":136,"categories":137,"keywords":138,"publishedAt":139},"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":141,"name":142,"nameZh":6,"description":143,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":144,"categories":145,"keywords":146,"publishedAt":47},"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",[],[142,147,148,149,150,151,152,153,154,39,42,155,156,157,41,158],"configuration","diagnostics","error","environment","cloud","when","connection","authentication","recovery","process","sign","intelligence",{"skillNo":160,"name":161,"nameZh":6,"description":162,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":163,"categories":164,"keywords":170,"publishedAt":47},"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",[165],{"categoryNo":166,"categoryName":167,"taxonomyType":168,"taxonomyTypeDesc":169},"01JBSEEDCAT000000000000034","行政与办公人员","PROFESSION","适用职业",[171,172,173,174,39,152,175,176,156,177,158,178,179,180,181],"issue","report","report issue","bug-report","operation","draft","bug","summary","user","for","support",{"skillNo":183,"name":184,"nameZh":6,"description":185,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":186,"categories":187,"keywords":188,"publishedAt":47},"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",[],[189,156,190,191,39,192,193,152,194,195,196,41,197,198,199],"investigate","investigate process","question","process mining","business","across","perspectives","mining","pattern","investigation","analytical",{"skillNo":201,"name":202,"nameZh":6,"description":203,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":204,"categories":205,"keywords":206,"publishedAt":47},"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",[],[207,208,209,210,211,212,39,152,213,41],"metric","derive metric","missing","formula","custom","reuse","saved",{"skillNo":215,"name":216,"nameZh":6,"description":217,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":218,"categories":219,"keywords":220,"publishedAt":47},"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",[],[221,222,39,152,223,156,41],"compare","compare cohorts","results"]