- 01
/plugin marketplace add microsoft/power-platform-skills - 02
/plugin install process-intelligence@power-platform-skills
Fills the gap when the measure you need in Power Automate Process Mining doesn't exist. It tries built-in measures first, then saved custom metrics, then a calculation from results already in hand, and only then a temporary formula it validates before running. Nothing is saved.
WHEN TO USE
USE FOR
- Count the cases that took more than a day.
- Reuse a saved custom metric someone already built.
- Run a one-off formula for a measure that doesn't exist yet.
NOT FOR
- Saving a new metric for others: there's no tool for that, so create it in Process Mining and refresh.
This is a saved copy of the skill's SKILL.md instructions. It may differ from the upstream file or the version you install.
Resolve a metric gap without saving definitions
Use the shared contract and filters/units. Follow this order; stop at the first sufficient option.
For a business-derived measure, confirm case/event entity, outcome definition/provenance, units, time basis and aggregation. Are amounts incremental transactions or cumulative snapshots? Never assume sum, latest or maximum: nonmonotonic snapshots require authoritative ordering and refund/correction semantics. Missing definitions mean inconclusive; ask before computing. Do not infer formula grammar from an example name or business description.
- Native output first. Use the existing metric and its correct scope/aggregation.
For cases over one day append
{metric:"CaseDuration",comparisonOperator:"GreaterThan",values:["1.00:00:00"],isInclusive:true}to F'scaseMetricConditionFilters, thenget_cases_with_metrics_v2 {S,filterOptions:Fplus,itemsPerPage:5,itemsToSkip:0}. No formula is needed for ordinary duration/waiting/counts; use native grouped statistics instead of summing a truncated cases page. - Enabled saved metric. Reuse fresh details'
CustomMetricsID/name/type/dataType. Details is not a generic metric catalog and contains no saved formula text. Match Case/Event/Edge scope and scalar type. For a Boolean Case metric C append{metric:"CustomMetric",customMetricId:C,comparisonOperator:"EqualTo",values:[true],isInclusive:true}tocaseMetricConditionFilters; queryget_process_overall_metrics_v2 {S,filterOptions:Fplus}for a count. An ID filter needs no formula validation. A saved-name output expression, e.g. syntheticEscalatedCase(), does require the validation/column path below; do not guess escaping or missing dependencies. - Exact local scalar. Reuse complete, definition-compatible, same-scope totals with a nonzero denominator. Label the result derived, not saved. Never average averages or use overlapping groups/top-N samples as population totals.
- Ephemeral formula only if necessary. Load formula execution.
Reuse PV/PMV from current details, not process/view IDs; refresh when stale.
Fetch needed targeted reference pages without a lookup quota; then validate:
validate_custom_metric_formula {processVersionId:PV,processExtendedMetadataVersionId:PMV,formula:Fexpr}. For a candidate and its repairs, allow three validation attempts total, not endless retries. Repair only from structured errors/definitions; stop early on an unavailable prerequisite. RequireisValid:true, a compatibledataTypeand the exact target context in types. Validation alone neither executes nor saves anything. - Execute the smallest matching filter/query or default page-five column query.
For cases:
get_cases_with_metrics_v2 {S,filterOptions:F,itemsPerPage:5,itemsToSkip:0,formulaMetricInput:{name:N,formula:Fexpr}}. N must not collide with returned built-ins. Never inventcomputedColumnsormetrics.
Continue necessary pages or distinct evidence queries without ordinary-call or total-row quotas. Reuse completed results; stop when answered or no new evidence is available. Missing validator forbids unvalidated execution even if the output field is advertised. Column and formula-filter capabilities are independent; stop after an explicit gate rejection. No create/save metric tool exists. If a prerequisite cannot be inlined, explain creation/enablement outside MCP, then refresh metadata and revalidate after the user's action.
Report definition/formula, units/context, validation state, at most five headline rows and ephemeral/not saved. Retain definition provenance and scoped evidence/status using the investigation method.
Account or credentials required
3 FOR YOUItems without a tag are required.
- 01Install with the process-intelligence plugin, then run setup
Install it with Microsoft's process-intelligence plugin. It works through the plugin's Process Mining MCP server and shared analysis guides, which come only with the plugin.
- 02Node.js 22 or 24, Azure CLI 2.54+, Process Mining access
Node.js 22 or 24, the Azure CLI 2.54 or later, and an authorised Power Automate Process Mining account and environment. GCC, GCC High, DoD and Mooncake clouds aren't supported yet.
- 03Note Results reach your AI assistant unredacted
Analysis results, which can include personal and business data, are passed unredacted to the AI assistant you use. Check your organisation's rules for that assistant before you connect.
This skill ships inside the Power Platform Skills plugin. Listed package contents include 25 agents, hooks and an MCP server. Installed components and skill versions may vary by AI tool.
Install as a Claude Code plugin
Typed inside the agent's own prompt, not in a terminal. This skill uses files kept elsewhere in its plugin, so install the whole plugin — on its own the skill would be missing them.
The repository is licensed under MIT — use, modification, and redistribution are allowed under that license’s terms.
View the repository’s license file on GitHub →