Skip to main content
skill CX Codex

analyze-performance · microsoft, power-pages — Claude Code skill: what it does, how to install

analyze-performance is a Claude Code skill that scans local Power Pages code for performance anti-patterns and suggests AI-assisted fixes for offline review.

MIT ★ 1,167 updated 2026-10-29

Install into Claude Code · Plugin marketplace All methods and platforms ↓
/plugin marketplace add microsoft/power-platform-skills
/plugin install power-pages@power-platform-skills
Open on GitHub

What analyze-performance does

The skill runs a fully offline static scan across a local Power Pages codebase without calling remote environments. It flags unpaginated lists, Web templates serving as custom APIs, FetchXML over-fetching or N+1 loops, unbounded Web API queries, missing output caching, and render-blocking scripts.

Static findings are paired with AI-driven mitigations grounded in real code snippets using the Opus model. For issues with automated remedies, the skill requests explicit confirmation before applying changes and verifies them with a follow-up check.

Local execution requires Node.js for bundled helper scripts. Single-page applications are not supported: the presence of powerpages.config.json halts the scan immediately.

What it helps with

  • detect FetchXML over-fetching and N+1 query loops in Liquid code
  • flag missing list pagination and disabled header or footer caching
  • locate render-blocking scripts and oversized assets in Power Pages projects
  • apply verified performance fixes with manual approval for each file

Example prompts for the agent

  • Audit my Power Pages project for performance bottlenecks
  • Scan this site codebase for FetchXML anti-patterns and unpaginated lists
  • Run a performance review and save results: analyze-performance --review ./perf-out

How to install analyze-performance

1Plugin marketplace

/plugin marketplace add microsoft/power-platform-skills
/plugin install power-pages@power-platform-skills

This installs the whole power-pages plugin with all its skills

2Skills CLI (Vercel)

npx skills add microsoft/power-platform-skills --skill analyze-performance -a claude-code

3Manually: put the files in place

~/.claude/skills/analyze-performance/SKILL.md

Copy the whole skill folder; for one project use .claude/skills/analyze-performance/

Step by step, with commands for each platform: How to install skills in Claude Code: five ways

Questions about analyze-performance

How do I install analyze-performance in Claude Code?

Register the marketplace and install the plugin with /plugin marketplace add microsoft/power-platform-skills followed by /plugin install power-pages@power-platform-skills.

What does the analyze-performance skill do?

It audits non-SPA Power Pages templates and scripts for performance bottlenecks, creates an HTML report, and applies approved fixes directly to local files.

Does the scan require access to Azure or Dataverse?

No, the skill runs entirely offline against your local project folder and requires neither PAC CLI authentication nor active cloud credentials.

Source text

SKILL.md · MIT
---
name: analyze-performance
description: >-
  Statically scans the entire local Power Pages codebase for performance
  anti-patterns — unpaginated Power Pages lists, webpages/web templates used as
  custom data APIs, FetchXML over-fetching / N+1 / advanced query hints / cache
  bypassing, unbounded Web API queries, disabled header/footer output caching,
  sign-in and page tracking, main-thread-blocking JS, CSS @import, frequent Web
  API polling, and oversized assets — then enriches findings with AI-driven
  suggestions and mitigations grounded in the affected customer-code snippets,
  reports them, and offers safe auto-fixes with per-fix approval.
  Use when the user wants to: "check performance", "perf check", "find
  performance issues", "why is my site slow", "optimize my Power Pages site",
  "find anti-patterns", "review FetchXML performance", "is my site over-fetching
  data", or "audit site performance".
user-invocable: true
argument-hint: "[optional: --review <out-dir>]"
allowed-tools: Read, Write, Edit, Bash, Glob, Grep, AskUserQuestion, TaskCreate, TaskUpdate, TaskList, mcp__plugin_power-pages_microsoft-learn__microsoft_docs_search, mcp__plugin_power-pages_microsoft-learn__microsoft_docs_fetch
model: opus
---

> **Plugin check**: Run `node "${PLUGIN_ROOT}/scripts/check-version.js"` — if it outputs a message, show it to the user before proceeding.

# analyze-performance

Statically analyzes the **entire local Power Pages codebase** for known performance anti-patterns, enriches the static findings with **AI-driven, code-aware suggestions and mitigations**, presents them by severity in an HTML report + plain-language summary, and offers **safe auto-fixes with per-fix approval**. Never applies a fix without explicit consent.

This skill reads local source only — it does not call the deployed site. For a live security/vulnerability scan use `/scan-site`.

**Initial request:** $ARGUMENTS

## Prerequisites

- An existing local **non-SPA** Power Pages project or PAC CLI site download.
  `.powerpages-site/`, root-level `.portalconfig/`, `website.yml`, and portal
  content folders are useful discovery markers, but they are not all required
  when the user supplies an existing site folder.
- SPA websites are not supported yet. `powerpages.config.json` is the
  authoritative local SPA marker; if it exists at the selected project root,
  tell the user this skill currently supports non-SPA websites only and stop.
- Node.js (bundled scripts run under `node`).

No sign-in, PAC CLI, or Azure CLI is required — the analysis is fully offline.

## What it detects

See `references/performance-reference.md` for the authoritative rule catalog (tags,
severities, detection, fixes, thresholds, and Microsoft Learn sources). The scan
must cover all of these categories:

- **List pagination** — Power Pages list definitions with no positive
  `adx_pagesize` / `pagesize`.
- **Webpages used as APIs** — FetchXML/entity-backed web templates or webpage
  content that emit JSON/XML instead of a normal HTML page.
- **FetchXML anti-patterns** — `all-attributes`, no explicit columns, too many
  columns, no paging, oversized `count`/`top`, N+1 queries inside Liquid loops,
  unnecessary `returntotalrecordcount`, leading-wildcard `like` filters, and
  related-table ordering.
- **FetchXML query controls** — advanced query hints (`options`,
  `latematerialize`, `no-lock`, `useraworderby`, filter `hint`) and request-time
  values or explicit settings that bypass server-side query caching.
- **Web API anti-patterns** — `$select=*`, missing `$select`, no page bound
  (`$top` safety cap or `Prefer: odata.maxpagesize=N` cursor paging),
  too many selected columns, oversized `$top`, `$count=true`, `$expand` without
  a nested `$select`, `contains`/`endswith` filters, request-time date filters,
  related-table ordering, request-per-item/N+1 loops, and short-interval polling.
- **Rendering and caching** — disabled Header/Footer output caching,
  render-blocking `<head>` scripts, runtime CSS `@import`, synchronous XHR/jQuery,
  and `document.write`.
- **Tracking and volume** — sign-in/page/file tracking, excessive web-file or
  web-role counts, and oversized static assets.

## Phases

1. **Prerequisites** — locate the project, confirm the site exists, detect review mode
1.5. **Ground in current performance guidance** — optional Microsoft Learn cross-check (capped, offline-safe)
2. **Scan** — run the deterministic analyzer over the codebase
2.5. **AI mitigation pass** — inspect customer-code snippets behind each finding and add code-aware suggestions/mitigations
3. **Present findings** — severity table + coverage stats + AI suggestions
4. **Offer auto-fixes** — per-finding consent loop for the safely-automatable findings
5. **Verify** — re-run the analyzer to confirm fixes resolved their findings
6. **Report & next action** — render the HTML report, summarize, and route follow-ups

## Task Tracking

Create tasks in three groups. Mark each `in_progress` when starting, `completed` when done.

| Group | When to create | Tasks |
|-------|----------------|-------|
| 1 | At start | Verify prerequisites and locate project |
| 2 | After prerequisites pass | Scan codebase for anti-patterns · Add AI-driven suggestions and mitigations · Present findings |
| 3 | After findings presented (skip all three in review mode) | Offer auto-fixes (only if any `autoFixAvailable`) · Verify fixes · Render report and route follow-ups |

---

## Phase 1 — Verify Prerequisites and Locate Project

1. **Detect review mode first**: if `$ARGUMENTS` contains `--review <out-dir>`,
   remember `<REVIEW_DIR>`.
2. Resolve `<PROJECT_ROOT>` in this order:
   - If `<REVIEW_DIR>` itself contains recognizable Power Pages source, use it as
     both `<PROJECT_ROOT>` and `<REVIEW_DIR>`. This supports orchestrated reviews
     that pass the downloaded site folder directly.
   - Otherwise use an explicitly supplied project directory, then the current
     working directory. Use `Glob` to locate `**/powerpages.config.json`,
     `**/.powerpages-site`, `**/.portalconfig`, or `**/website.yml` when needed.
3. Treat any of these as recognizable Power Pages source:
   `.powerpages-site/`, root-level `.portalconfig/`, `website.yml`, or a
   characteristic portal export layout containing folders such as `web-pages/`,
   `web-templates/`, or `web-files/`. Do **not** reject an explicitly supplied
   existing site folder merely because it lacks `.powerpages-site/`.
4. If `<PROJECT_ROOT>/powerpages.config.json` exists, tell the user that the
   selected path is a SPA website and this skill currently supports non-SPA
   Power Pages websites only, then **stop**.
5. If no existing directory with recognizable non-SPA Power Pages source can be located,
   tell the user and recommend `/create-site`, then **stop**.
6. In review mode Phases 3, 4, and 6-presentation are skipped: Phase 2 runs,
   Step 6.2 writes JSON only, and the skill stops after writing it.

Report: "Found project: `<PROJECT_ROOT>`. Scanning for performance anti-patterns."

## Phase 1.5 — Ground in current performance guidance

> Skip in **review mode**. Cap this step at ~30 seconds. If MCP search / fetch errors out or is unavailable, log a one-line note and continue — this skill must remain runnable offline.

1. Run `microsoft_docs_search` with the query: `Power Pages Site Checker performance FetchXML output caching best practices`.
2. Optionally `microsoft_docs_fetch` `https://learn.microsoft.com/en-us/power-pages/admin/site-checker-performance`.
3. Extract a one-paragraph summary of what Microsoft Learn currently says. Compare it against the rule catalog in `references/performance-reference.md`. If Learn documents a performance pattern not covered by any analyzer rule, surface it to the user in Phase 6 as a **manual** follow-up — do not silently invent findings the analyzer did not produce.

## Phase 2 — Scan the codebase

Run the deterministic analyzer over the whole project:

```bash
node "${PLUGIN_ROOT}/skills/analyze-performance/scripts/analyze-performance.js" --projectRoot "<PROJECT_ROOT>"
```

The analyzer prints a single JSON object `{ status, findings, details, severityCounts }` to stdout. Parse it. Each finding has `id`, `tag`, `severity`, `title`, `location`, `details`, `fix`, `autoFixAvailable`, and (when auto-fixable) `fixAction`. See `references/performance-reference.md` for the finding envelope and every tag's meaning.

If the only finding is `PERF-NONE`, the codebase is clean — note this and skip Phase 4/5 (still render the report in Phase 6 so the user has a record).

## Phase 2.5 — Add AI-driven suggestions and mitigations

Run this after every deterministic scan result that will be presented or written
to `analyze-performance.json` (including **review mode**). Skip only `PERF-NONE`.

For each finding, inspect the relevant customer-code context before writing the
final JSON:

1. Read the file named by `finding.location` and capture a tight snippet around
   the line (about 20 lines before/after, capped so the report stays readable).
   If the file no longer exists or the finding has no location, use the finding's
   `details` and `fix` only.
2. Add these fields to the finding object:
   - `aiSuggestion`: one or two sentences explaining the best next change for
     this specific code path, grounded in the snippet and the rule catalog.
   - `mitigation`: a concrete mitigation plan that preserves behavior. Name the
     likely code/config edit, the safer alternative when there are tradeoffs, and
     anything the user must verify manually.
3. Keep the deterministic fields (`tag`, `severity`, `fix`, `fixAction`,
   `autoFixAvailable`) unchanged. Do **not** downgrade, suppress, or invent
   analyzer findings during this AI pass.
4. For heuristic findings (for example webpage-as-API, Web API N+1, cache
   bypassing, related-column ordering), say that the suggestion is conditional
   and name the observation that would confirm it.
5. For auto-fixable site-setting/tracking findings, keep `mitigation` aligned
   with the existing `fixAction` and repeat any important caveat, especially the
   Header/Footer output-cache substitution requirement.

The report renderer displays `aiSuggestion` and `mitigation` as separate fields,
so write them into the JSON rather than only mentioning them in chat. If the
current AI context cannot safely inspect a file because it is restricted or too
large, add a conservative mitigation based on `details`/`fix` and explicitly say
the source snippet was not inspected.

## Phase 3 — Present findings

> Skip in **review mode** (go straight to Step 5.1's JSON write).

Present all findings grouped by severity, highest first. Include the AI
suggestion and mitigation under each row (or immediately after the table for long
items) so the user sees both the static check and the code-aware recommendation:

| # | Severity | Tag | Issue | Location | Auto-fix? |
|---|----------|-----|-------|----------|-----------|
| 1 | high | PERF-FETCHXML-ALLATTR | FetchXML retrieves all attributes | `...:2` | No |
| 2 | warning | PERF-HEADER-OUTPUTCACHE | Header output caching disabled | `...sitesetting.yml` | Yes |

Then show the coverage stats from `details.entries` (FetchXML/Liquid, list,
Web API/script and CSS files scanned; web-file/web-role counts; total findings).
Keep the language plain; explain a tag only when asked. Make clear that AI
suggestions are grounded in the local snippet but still require developer
judgment for business-specific behavior.

## Phase 4 — Offer auto-fixes

> Skip in **review mode**. Skip entirely if no finding has `autoFixAvailable: true`.

Only the site-setting and tracking findings are safely automatable (`PERF-HEADER-OUTPUTCACHE`, `PERF-FOOTER-OUTPUTCACHE`, `PERF-SIGNIN-TRACKING`, `PERF-WEBPAGE-TRACKING`, `PERF-WEBFILE-TRACKING`). List pagination, webpage-as-API, FetchXML, Web API, query-hint, cache-bypass, and asset findings require human judgment — present those as manual fixes only.

For each finding with `autoFixAvailable: true`, in order:

<!-- gate: analyze-performance:4.auto-fix | category=consent | cancel-leaves=nothing -->
> 🚦 **Gate (consent · analyze-performance:4.auto-fix):** Per-finding consent before applying any auto-fix. **Loops once per `autoFixAvailable` finding** — each gets its own Yes / No / Skip-all `AskUserQuestion` naming the finding's tag and the exact change. **Never batch fixes** — three fixable findings = three separate prompts (unless the user picks "Skip all", which short-circuits the loop). Each fix has its own blast radius (a different site setting or YAML file), so approving one does not approve the next.
>
> **Trigger:** Phase 4, once per fixable finding.
> **Why we ask:** Enabling output caching alone can break header/footer rendering unless the web templates also use `{% substitution %}` (see caveat below); toggling tracking edits committed YAML. The user must consent to each concrete change.
> **Cancel leaves:** Nothing — declining a fix leaves that finding untouched and reported as manual.

For the approved finding, apply its `fixAction`:

- **`create-site-setting`** (setting is absent from a per-record `.powerpages-site`
  layout): create it with the shared helper —
  ```bash
  node "${PLUGIN_ROOT}/scripts/create-site-setting.js" --projectRoot "<PROJECT_ROOT>" --name "<fixAction.name>" --value "<fixAction.value>" --type boolean --description "<short why>"
  ```
  If it reports the setting already exists, treat it as already handled and switch to the `set-site-setting` path.
- **`set-site-setting`** (setting exists but is wrong): use `Edit` on the finding's `location` file to flip the `value:` line (`false` → `true`, or tracking `true` → `false`). Do **not** call `create-site-setting.js` — it refuses to overwrite.
- **`set-yaml-field`**: use `Edit` at the finding's precise `location` to set
  `<fixAction.field>: <fixAction.value>` (e.g., `adx_enabletracking: false`).
  For a non-SPA aggregate `sitesetting.yml`, `fixAction.recordName` identifies the
  setting record and the location points at its exact `adx_value` line. Do not
  replace another record's matching boolean.

> **Output-cache caveat (always surface this):** enabling `Header/Footer/OutputCache/Enabled` is **not** sufficient on its own — the Header, Footer, and Languages-Dropdown web templates must also use the `{% substitution %}` Liquid tag, or those regions stop rendering. After applying an output-cache fix, tell the user to update those templates and verify the site still renders.

Mark each finding **Fixed**, **Skipped**, or **Manual required** as you go.

## Phase 5 — Verify fixes

> Skip in **review mode**. Skip if no auto-fix was applied.

Re-run the analyzer to confirm the applied fixes resolved their findings:

```bash
node "${PLUGIN_ROOT}/skills/analyze-performance/scripts/analyze-performance.js" --projectRoot "<PROJECT_ROOT>"
```

Confirm each fixed finding's tag/location is gone (or downgraded from `warning` to `info` for the absent→present caching case). If a fix did not take, report it and offer to retry or hand it to the user. Use this re-scanned result set as the basis for the Phase 6 report so it reflects the post-fix state.

## Phase 6 — Report & next action

### 6.1 Review mode short-circuit

Handled at Step 6.2 below — review mode never reaches the HTML render or the follow-up walk-through.

### Step 6.2 — Write the review JSON

Write the enriched `{ status, findings, details }` object (the Phase 5 re-scan result if a re-scan ran, otherwise the Phase 2 result, with Phase 2.5 `aiSuggestion`/`mitigation` fields applied) to a JSON file:

- **Review mode**: write to `<REVIEW_DIR>/analyze-performance.json`, then **stop**. The orchestrating skill (e.g., `security-review`) handles presentation.
- **Interactive mode**: write to `<TEMP_DIR>/analyze-performance.json` where `<TEMP_DIR>` is a scratch directory containing only this file.

The filename **must** be `analyze-performance.json` — that is the key
`build-review-data.js` maps to the Performance section.

### Step 6.3 — Render the HTML report

Skip in **review mode**. Reuse the shared report pipeline (same template as the security review and site scan):

The final HTML report is a persistent website artifact under
`<PROJECT_ROOT>/docs/`, consistent with the other review reports. Only
`analyze-performance.json` and `data.json` are temporary scratch files; delete their
temporary directory after the HTML render succeeds.

```bash
node "${PLUGIN_ROOT}/scripts/build-review-data.js" \
  --reportName "Performance Analysis" \
  --inputDir "<TEMP_DIR>" \
  --siteName "<SITE_NAME>" \
  --goalLabel "Performance" \
  --scopeLabel "Local codebase" \
  --summary "<SUMMARY_TEXT>" \
  --output "<TEMP_DIR>/data.json"

node "${PLUGIN_ROOT}/scripts/render-review.js" \
  --data "<TEMP_DIR>/data.json" \
  --output "<PROJECT_ROOT>/docs/performance-analysis-<YYYY-MM-DD-HHMMSS>.html"

node "${PLUGIN_ROOT}/skills/analyze-performance/scripts/validate-analyze-performance.js" \
  --reportPath "<PROJECT_ROOT>/docs/performance-analysis-<YYYY-MM-DD-HHMMSS>.html"
```

`<SITE_NAME>` comes from the site's `website.yml`; fall back to the folder name.
The filename **must** include the local timestamp (e.g.,
`performance-analysis-2026-05-14-053805.html`). Delete `<TEMP_DIR>` after the
render and explicit validation succeed, then open the report in the browser.

### Step 6.4 — Summarize and route follow-ups

<!-- gate: analyze-performance:6.next-action | category=plan | cancel-leaves=nothing -->
> 🚦 **Gate (plan · analyze-performance:6.next-action):** After the report, recommend the single most useful next step and let the user accept or choose differently via `AskUserQuestion` — walk through the manual (non-auto-fixable) findings one at a time, re-scan, or finish. Reviewing findings and re-scanning are read-only; nothing is changed without a later Phase 4 consent.
>
> **Trigger:** Phase 6, after the report is rendered (interactive mode only).
> **Why we ask:** The manual list, webpage-as-API, FetchXML, Web API, query-hint,
> cache-bypass, and asset fixes need edits the user must drive; auto-walking every
> finding would be noisy if they only wanted the report.
> **Cancel leaves:** Nothing — the report is already written; declining ends the skill cleanly.

Give a plain-language summary: total findings, count by severity, and how many
were auto-fixed. For manual findings (list pagination, webpage-as-API patterns,
FetchXML/Web API anti-patterns, query hints, cache bypassing, volume counts, and
large assets), offer to walk through them one at a time with the concrete edit
each needs. If nothing meaningful remains, end the skill — do not ask just to ask.

### Record Skill Usage

> Reference: `${PLUGIN_ROOT}/references/skill-tracking-reference.md`
>
> Use `--skillName "AnalyzePerformance"`.

## Constraints

- **Read-only until consent.** The analyzer never mutates anything. The only writes are the HTML report, the scratch JSON, and auto-fixes the user explicitly approves in Phase 4.
- **High-signal findings.** Heuristics (Web API N+1, missing-but-defaultable caching) are intentionally conservative to avoid false positives. When a finding is a heuristic, say so.
- **Plain language.** Explain a tag only when asked; lead with the impact, not the internal name.
- **Offline-safe.** Phase 1.5 is best-effort; the skill must complete with no network access.

## References

- `references/performance-reference.md` — authoritative rule catalog: tags, severities, detection logic, fixes, auto-fix actions, thresholds, manual-only checks, key nuances, and Microsoft Learn sources. Read when explaining a finding or deciding whether a fix is safe.

## Progress Tracking Table

| Task subject | activeForm | Description |
|---|---|---|
| Verify prerequisites and locate project | Verifying prerequisites | Locate an explicit/current code-site or PAC-download folder, confirm recognizable Power Pages source, detect review mode |
| Scan codebase for anti-patterns | Scanning codebase | Run analyze-performance.js over the project, parse findings JSON |
| Present findings | Presenting findings | Show severity table and coverage stats |
| Offer auto-fixes | Applying auto-fixes | Per-finding consent loop; apply site-setting/tracking fixes, surface substitution caveat |
| Verify fixes | Verifying fixes | Re-run analyzer, confirm fixed findings are gone |
| Render report and route follow-ups | Rendering report | Build review JSON, render HTML, summarize, route manual follow-ups |

© Microsoft · MIT · microsoft/power-platform-skills

Similar skills

All skills for Code review and refactoring →

analyze-performance by other authors comes first.

analyze-performance Microsoft analyze-performance guides analysis of slow process activities, handoff delays, waiting times, and total workload without distorting statistical metrics. CX Codex +1 ★ 1,167repo stars MCP Dataverse codeurali Connects AI coding assistants directly to Microsoft Dataverse for live schema inspection, FetchXML queries, and batch record updates. CX Codex +1 ★ 18repo stars shopify-theme-optimization nexscope-ai shopify-theme-optimization — a skill that audits Shopify theme speed and UX: Core Web Vitals, Liquid, image loading, mobile layout. Returns a step-by-step plan. CX Codex +1 1,200installs fixing-motion-performance ibelick fixing-motion-performance is a Claude Code skill that finds and fixes FPS drops in animations, including scroll effects, blur, and layout repaints. It reduces UI stutter without changing the animation library. CX Codex +1 29,400installs react-performance affaan-m react-performance — a performance optimization skill for React 18/19 and Next.js. It helps coding agents spot network waterfalls, trim client bundle sizes, and tune Server Components during code review. CX Codex +1 6,700installs swiftui-performance dpearson2699 swiftui-performance — a skill for Claude Code, Cursor, Codex and other agents that takes a reproducible SwiftUI symptom through to a measured fix. CX Codex +1 5,000installs mapbox-web-performance-patterns mapbox mapbox-web-performance-patterns is a Claude Code skill that optimizes Mapbox GL JS by removing initialization waterfalls, shrinking style bundles, and moving markers to GPU layers. CX Codex +1 2,600installs

From the same set157

The whole set →
deploy Builds an Expo/React Native mobile app and pushes it to a Power Platform environment. First deployment requires two full build cycles. CX Codex +1 ★ 1,167repo stars generate-ppmplugin-manifest generate-ppmplugin-manifest is a Claude Code skill that validates and stages manifest.json for .ppmplugin bundles before packaging, checking names, prefixes, and entrypoints without build tools. CX Codex +1 ★ 1,167repo stars setup-datamodel setup-datamodel is a Claude Code skill that builds Dataverse tables, columns, and relationships for Power Pages. It runs when a site needs a data model from a diagram or source-code analysis. CX Codex +1 ★ 1,167repo stars activate-site activate-site — a skill that provisions a Power Pages website in a Power Platform environment through the REST API, with access checks, a confirmation step and status polling. CX Codex +1 ★ 1,167repo stars build-android-binary The build-android-binary skill turns a PAM control’s Android Kotlin module into a DEX file for a .ppmplugin. Run it after creating the manifest and before packaging the plugin. CX Codex +1 ★ 1,167repo stars migrate-webapi-selectall migrate-webapi-selectall replaces deprecated wildcard values in Power Pages Web API field settings with explicit Dataverse column lists following least-privilege principles. CX Codex +1 ★ 1,167repo stars genpage-customapi-builder genpage-customapi-builder discovers Dataverse Custom APIs and builds binding contracts for Power Apps generative pages. Runs headlessly under the genpage orchestrator. CX Codex ★ 1,167repo stars genpage-entity-builder genpage-entity-builder creates Dataverse entities from a plan for Power Apps generative pages. The genpage skill calls it; users do not invoke it directly. CX Codex ★ 1,167repo stars

Project sponsors

Companies that keep this analytics open