- 01
/plugin marketplace add microsoft/power-platform-skills - 02
/plugin install process-intelligence@power-platform-skills
Analyses object-centric processes in Power Automate Process Mining, where several kinds of business object interact, such as orders and invoices. It picks a leading object type, measures how its executions run and drills into executions, individual objects or the links between them.
WHEN TO USE
USE FOR
- See how long executions take for a chosen leading object type.
- Drill into specific executions, objects or the links between object types.
- Filter executions by the time between a first and a last activity.
NOT FOR
- Ordinary case-based processes: the other Process Mining skills cover those.
This is a saved copy of the skill's SKILL.md instructions. It may differ from the upstream file or the version you install.
Object-centric analysis, not relabeled cases
Use the shared contract. Require the needed
advertised OCPM tools; absence stops this workflow, never falls back to case analytics.
Keep separate object context and filters:Fobj; do not copy case filterOptions.
Ordered trace
- Only if unknown:
get_ocpm_processes {}-> select returned P ->get_process_details_v2 {processId:P}for missing metadata. Caseget_processesdoes not discover object-centric processes. - Unless cached:
get_ocpm_object_types {S,itemsPerPage:20,itemsToSkip:0}. Choose returned leading type O from the user's objective; ask if ambiguous. get_ocpm_process_execution_statistics {S,leadingObjectTypeName:O,filters:Fobj}.ProcessExecutionCountcounts executions;ProcessExecutionDurationis their mean.- Choose the requested evidence branch:
get_ocpm_process_executions {S,leadingObjectTypeName:O,filters:Fobj,itemsPerPage:5,itemsToSkip:0}, orget_ocpm_objects {S,objectTypeName:O,filters:Fobj,itemsPerPage:5,itemsToSkip:0}, orget_ocpm_edges {S,filters:Fobj,itemsPerPage:10,itemsToSkip:0}.
An exact object/execution request with cached type/scope can go directly to its drilldown; do not force a new summary. Continue needed pages or discriminating follow-ups without fixed call/row/drilldown quotas. Reuse complete results; stop when answered or no new evidence remains. No OCPM sort, generic metrics/grouping or formula-column inputs exist. Search is supported only on object types, objects and edges; aggregate statistics has no paging.
Filter construction
Use exact returned type names, attributes and object identifiers (objects expose Name, not invented GUIDs).
Declare leading type, propagation and date mode. For a selected-type-only timeframe:
objectTimeframeFilters:[{objectTypeName:O,startDate:START,endDate:END,
filteringType:"Contained",isInclusive:true,propagation:"SelectedObjectTypeOnly"}]SelectedObjectTypeOnly forbids propagationDepth. RelatedObjects defaults to depth 2; depth N means N-1 relation hops. Choose explicitly when ambiguity changes scope. OCPM timeframe requires start before end and describes an exclusive end; unlike case filters, its discovered modes can include Started, Completed, Intersecting and PassThrough.
For a first-to-last path threshold with known activity values FROM/TO:
processExecutionFilters:[{leadingObjectTypeName:O,
from:{selectionType:"First",value:FROM},to:{selectionType:"Last",value:TO},
timeBetweenEventsRelation:"GreaterThan",timeBetweenEventsSeconds:SECONDS,isInclusive:true}]Time relation and finite nonnegative seconds must be paired. Secondary object-metric Duration conditions instead use ticks; case duration filters use TimeSpan strings. Do not interchange them.
Report at most five headline rows with native units, leading type, filters and page coverage. Object-type counts are not additive unique executions. Execution Duration is not automatically the filtered path interval or invoice-to-order delay. A delay claim also needs a verified business definition/threshold. Mark unsupported interpretations inconclusive, not inferred from cases. Use the investigation method for evidence labels and compact references, counts, units, coverage and alternatives. Freeze baseline object filters separately from test filters; keep object context, leading type and propagation explicit. Stop on missing interval evidence or capability, never substitute a case-based model.
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 →