Skip to main content
skill CX Codex

setup · microsoft, process-intelligence — Claude Code skill: configure Process Intelligence

setup guides the agent through Process Intelligence configuration: dependency checks, cloud and environment selection, az login binding, then profile activation.

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 process-intelligence@power-platform-skills
Open on GitHub

What setup does

The skill walks the agent through connecting Process Intelligence: Node.js 22/24 LTS and Azure CLI 2.54+ get checked, the cloud and environment ID are settled, the open az login session is bound, and profile work is switched on with pi_activate_profile. A pi_connection_status call confirms it.

Commands run from the installed plugin directory; the scripts live in server/mcp.mjs (resolve-environment, config, login, diagnostics). Nothing connects until a privacy notice is shown and the user explicitly names both the environment and the host. Saved profiles are plain JSON, with no application-level encryption.

GCC, GCC High, DoD and Mooncake are unsupported for now. Public is the commercial cloud setting, and the skill stops rather than quietly substituting it. Without Node.js 22/24 LTS and Azure CLI 2.54+ step one fails outright, so install those beforehand. The user runs az login --allow-no-subscriptions themselves, because Azure CLI owns shared credentials and a sign-in can reach other tools.

What it helps with

  • bind an existing az login session to the plugin profile
  • resolve the tenant and environment ID for the Public cloud
  • recover after a Conditional Access claims challenge
  • compare Node.js and Azure CLI versions before the first run
  • switch accounts or environments without replaying a broken call

Example prompts for the agent

  • Set up Process Intelligence for the Public cloud with the environment ID I confirmed.
  • Run diagnostics for profile work and tell me whether MCP discovery succeeded.
  • Sign-in failed with an authentication error, recover the work profile in this session.

How to install setup

1Plugin marketplace

/plugin marketplace add microsoft/power-platform-skills
/plugin install process-intelligence@power-platform-skills

This installs the whole process-intelligence plugin with all its skills

2Skills CLI (Vercel)

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

3Manually: put the files in place

~/.claude/skills/setup/SKILL.md

Copy the whole skill folder; for one project use .claude/skills/setup/

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

Questions about setup

How do I install setup in Claude Code?

Add the marketplace with /plugin marketplace add microsoft/power-platform-skills, then install the plugin: /plugin install process-intelligence@power-platform-skills. The plugin's MCP server loads before setup runs.

What does the setup skill do?

It handles Process Intelligence configuration end to end: dependency checks, picking the cloud and environment, binding the az login session, diagnostics, and activating profile work.

Which clouds does it support?

Public is the commercial configuration, and it is the only one with automatic environment discovery via resolve-environment. GCC, GCC High, DoD and Mooncake are not supported, and the skill will not swap in Public for them.

Source text

SKILL.md · MIT
---
name: setup
description: Use when Process Intelligence needs building, explicit cloud/account/environment configuration, sign-in, connection diagnostics, or recovery from an authentication error.
allowed-tools: Read, Bash, AskUserQuestion
---

# Set up Process Intelligence

Read the bundled [README](../../README.md) first. Use the absolute installed plugin directory
containing this skill for shell commands; host-provided `PLUGIN_ROOT`/`CLAUDE_PLUGIN_ROOT` can
identify it. Do not assume the agent shell starts there. All scripts are inside this plugin.

**GCC, GCC High, DoD and Mooncake are not supported yet.**
`Public` is the commercial cloud configuration.
The CLI accepts five cloud values; configuration support does
not make an unsupported cloud available.

Confirm the user-approved cloud and environment ID. Do not ask for a tenant GUID up front for Public.
Resolve it from the selected environment; never infer it from `Default-<guid>`, access private
credential caches or guess the working environment.
Use `node server/mcp.mjs --help` for exact syntax and
[connection patterns](../../references/connection-patterns.md) for cloud/claims details.
Stop if the cloud is not one of the listed values; do not substitute Public or an arbitrary audience.

**Before connection or analytical use, show this privacy notice:** analytical results may contain
personal and business data, forwarded unredacted to the customer-selected host. Model routing,
history, retention, possible training use and geography depend on the customer's host/provider
settings and contracts. Review those settings and organizational requirements; do not certify
an arbitrary host/provider. Optional installation is not permission to disclose data.

Use AskUserQuestion to obtain explicit instruction or confirmation naming the selected environment
and host: "Do you instruct me to connect this selected environment to this selected host after
reviewing its data-handling settings?" Substitute the actual selections. Do not proceed to binding,
remote diagnostics or analytics until the user gives an explicit instruction covering both.
Environment-ID confirmation alone is insufficient. This is user-level integration instruction,
not tenant-admin consent or a plugin-enforced per-request gateway; existing authorization still applies.

1. Check Node.js 22/24 LTS and Azure CLI 2.54+ (`az version`).
   Use official installation guidance in the README; never install or change global settings automatically.
   The bundle is ready to run; source development uses `npm ci` then `npm run build`
   from this directory in a repository checkout, never during MCP launch.
   Profiles use `ProcessIntelligenceBridgeAzureCli` under the platform's per-user data directory.
2. Check the intended Azure CLI cloud and organizational account using supported read-only CLI commands.
   If sign-in is needed, have them run `az login --allow-no-subscriptions` themselves.
   Azure CLI owns shared credentials; login may affect other CLI consumers. The bridge never switches clouds/accounts.
3. For Public, run `node server/mcp.mjs resolve-environment --cloud Public --environment <environment-id>`.
   This explicit discovery step acquires a directory token and reads environment metadata. It needs
   directory-read access, creates no profile/cache, and returns a small JSON result on stderr.
   Confirm the returned target and the host-aware instruction above, then pass its `tenantId` and `environmentId` into
   `config --profile work --cloud Public --tenant <resolved-tenant-guid> --environment <environment-id>`.
   The config command remains offline. Discovery is Public-only: for another cloud or a lookup failure,
   preserve the error and use the manual path with an explicitly confirmed tenant GUID and selected cloud.
   Do not cycle tenants/resources, request extra consent or substitute the active CLI tenant.
   No `select`, custom client-id, browser/redirect flags, secrets or service-principal sessions.
4. The agent must run `node server/mcp.mjs login --profile work` using the absolute installed bundle
   path to bind the existing CLI session. This works without a TTY and opens no UI.
   Only `--sign-in true` requires a normal terminal; use direct terminal `az login` if device-code
   interaction is needed.
   Never collect tokens or raw auth output.
5. Run `diagnostics --profile work` for read-only CLI version/cloud/tenant/user-shape checks.
   Cold local diagnostics cannot verify the saved OID and report `boundAccountVerified: false`.
   Only with target authorization, use `--remote true` for token acquisition and MCP discovery.
   Confirm MCP discovery succeeds, not only token acquisition. No business tools are needed.
6. Call the discovered local `pi_activate_profile` with `{ "profile": "work", "remember": true }`.
   Confirm `pi_connection_status` is active, rediscover the analytical tools and use their actual
   schemas. Local activation notifies the host to refresh tools in this same session; do not restart
   Copilot, edit registrations or ask the user to set environment variables.
   The explicit choice is remembered for this client/installation, not machine-wide. Fresh server
   processes reuse it if the binding and Azure CLI session remain valid. Other active sessions keep
   their own selection. Explicit launch selection wins over the preference.

For repeated setup, check `pi_connection_status` first. If the intended profile is already active
and the integration instruction still applies, do not redo sign-in or config. Unchanged config and
silent binding preserve the revision. A stale/missing preference never selects another profile;
complete the indicated recovery and explicitly activate the intended name.
Marketplace loading supplies the MCP server before setup. Source development and `--plugin-dir`
examples are separate in the README; they are not steps for an already installed marketplace plugin.

Serve never opens UI. For a Conditional Access / CAE claims challenge, explain the policy failure
and ask the user to run `login --profile work --sign-in true` in a normal terminal, then call
`pi_activate_profile` in the existing session.
Do not store, decode or forward claims-challenge payloads. If the problem persists, ask the user's
administrator to review the policy; normal sign-in may not satisfy policies requiring specific claims.
Never change the client, resource or tenant as authentication recovery.
Account changes require explicit `login --profile work --switch-account true`; tenant/environment changes
require config, login and explicit activation. Revision/account changes cancel the stale remote
context but retain local recovery tools. Never replay interrupted business calls.
Logout invalidates only the plugin profile, never `az logout`.
Profiles are plaintext JSON without application-level encryption.
Account binding persists only the tenant-local OID alongside the tenant; usernames stay in RAM.
Use a non-personal profile label. Names can still contain identifying information.
For their exact fields, lifecycle and local export/removal, use connection patterns.

Preserve the safe error. Do not request admin consent, edit identity registrations or imply every AADSTS
failure is licensing. Direct access or consent problems to the user's administrator.

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

Similar skills

All skills for Agent setup: memory, context, orchestration →

setup by other authors comes first.

setup official anthropics setup is a Claude Code skill that checks connected tools, learns your writing style from sent email, and builds a starter dashboard without a questionnaire. For first run. CX Codex +1 371installs setup Alireza Rezvani setup sets up an autoresearch experiment by collecting its target file, evaluation command, metric, and optimization direction. Use it before starting an optimization loop. CX Codex +1 1,480installs setup aws This skill kicks off the connection setup for AWS DevOps Agent and AWS Security Agent. Reach for it when MCP tools go missing or you are wiring the toolkit up for the first time. CX Codex +1 1,600installs setup marketcalls setup sets up a Python backtesting environment with VectorBT and OpenAlgo. It configures the virtual environment, installs dependencies, and prepares .env. CX Codex +1 2,100installs setup assistant-ui setup is a Claude Code skill that installs and configures assistant-ui through its CLI. It covers new projects, existing Next.js apps, and package updates. CX Codex +1 6,400installs auth-setup goldsky-io auth-setup sets up Goldsky CLI access and project selection for pipelines and subgraphs. It handles login checks plus not logged in and unauthorized errors. CX Codex +1 5,100installs gcp-setup Google The gcp-setup skill checks and aligns identities across gcloud, Application Default Credentials, and kubectl at the start of your session. Use it to ensure all three systems authenticate as the same user before you begin working with GCP. CX Codex +1 ★ 151repo stars clerk-setup clerk clerk-setup is a skill for Claude Code and other agents that adds Clerk authentication to a project through the Clerk CLI. CX Codex +1 59,700installs azure-identity-rust Microsoft azure-identity-rust — a skill that tells your agent how to wire Microsoft Entra ID into a Rust app: which credential fits local work and which one belongs in production. CX Codex +1 5installs azure-identity-py Microsoft The azure-identity-py skill guides Python authentication to Azure with Microsoft Entra ID. Use it for DefaultAzureCredential, managed identities, service principals, and token access. CX Codex +1 3installs cyrus-setup-claude-auth cyrusagents The cyrus-setup-claude-auth skill writes Claude credentials into ~/.cyrus/.env so Cyrus can start AI sessions. Handy on first run or when switching accounts. CX Codex +1 1,100installs

From the same set157

The whole set →
add-datasource The add-datasource skill identifies the data an Expo/React Native app needs and directs the request to the matching Power Platform skill. CX Codex +1 ★ 1,167repo stars canvas-create-discovery canvas-create-discovery — a subagent that scans Power Apps to map available controls, data sources, and APIs, then documents feasible design choices and constraints. Use it to validate your canvas app concept before implementation begins. CX Codex ★ 1,167repo stars check-updates check-updates is a Claude Code skill that sequentially checks and updates direct dependencies in Power Apps mobile projects, with type-checking, Expo validation, and rollback. CX Codex +1 ★ 1,167repo stars report-issue report-issue collects project details and diagnostics, then drafts a GitHub issue for the mobile-app plugin. Use it to document a bug, unexpected result, or documentation problem. CX Codex +1 ★ 1,167repo stars debug-flow debug-flow diagnoses failed Power Automate runs. It traces execution graphs, flags root causes, and prepares targeted flow fixes. CX Codex +1 ★ 1,167repo stars configure-canvas-mcp The configure-canvas-mcp skill connects Canvas Authoring MCP to an active Power Apps coauthoring session. Run it before editing a canvas app when the server is not connected yet. CX Codex +1 ★ 1,167repo stars add-sharepoint add-sharepoint connects SharePoint Online to Power Apps code apps: reads lists, manages documents, creates new lists via Graph API. CX Codex +1 ★ 1,167repo stars preview-offline-scope preview-offline-scope estimates download payload and sync frequency costs for a Power Platform offline profile before rollout. Runs strictly in read-only mode. CX Codex +1 ★ 1,167repo stars

Project sponsors

Companies that keep this analytics open