Use when a Process Mining overview, initial process selection, or an analytical follow-up needs routing.
The English summary is being prepared. Showing the original description.
See how to installReview the instructions the agent will receive before you install.
Use the shared contract once per fresh analysis context. Recipes name native functions, not provider-prefixed host tools; bind them to discovered schemas.
get_processes {} ->
resolve the returned P (ask on duplicates) -> get_process_details_v2 {processId:P}
when metadata is missing. An empty process list stops analysis.get_process_overall_metrics_v2 {S,filterOptions:F}. Omit absent filters.
Report returned case/event/variant counts and mean CaseDuration/CaseWaitingTime;
preserve native units. Missing metrics are not zero.
For utilization with zero active time or start-only data, check the zero-duration convention
in filters and units; do not infer productive time.get_variants_with_metrics_v2 {S,filterOptions:F,itemsPerPage:5,itemsToSkip:0,metricToSortBy:"CaseCount",sortOrder:"Descending"}.Reuse completed evidence; continue necessary pages or checks without fixed analytical-call or total-row quotas. Stop at an answer, not an arbitrary count; do not sweep or repeat unchanged queries. Do not force an overview or investigation loop before a specialist's exact query. Broad business questions or competing explanations use investigate-process: establish only missing outcome definitions that change interpretation, then test the relevant claim.
| Follow-up | Load only this skill |
|---|---|
| Broad business question, observed pattern, competing explanations | investigate-process |
| Slow activities, waiting, handoffs, cumulative workload | analyze-performance |
| Common/slow variants, repeated work, a specific case | analyze-variants |
| Explanatory attributes, association hypotheses | analyze-drivers |
| Before/after or A/B cohorts | compare-cohorts |
| Missing metric, saved metric reuse, ephemeral formula | derive-metric |
| Interacting objects or leading-object executions | analyze-objects |
Stop when answered. Return a brief finding, at most five headline rows, scope/version, metric aggregation/units and coverage; retain compact context for the next question. Views, visualizations and saved metrics cannot be created through these tools.
No reviews yet. Tell others what you thought.
No login needed. Share how it worked for you, ask a question, or note where it did not run.
No comments yet. Be the first to write one.
Activates and provisions a Power Pages website in a Power Platform environment via the Power Platform REST API. Use when the user wants to activate, provision, turn on, or enable a Power Pages website or portal.
The English summary is being prepared. Showing the original description.
Integrates Power Pages generative-AI summarization APIs (PREVIEW) into a Single Page Application (SPA) site — the Search Summary API and the Data Summarization API — on any record-detail or list page. Generates per-target service code (CSRF-handled) and AI site settings; delegates Web API settings, table permissions, and web roles to `/integrate-webapi` and `/create-webroles`. Use whenever a user wants AI/Copilot output that condenses Dataverse content on a Power Pages site — an AI summary, AI-generated overview or "key insights" across a record or list, a search-results summary, a case/incident summary, or recommendation-chip refinement — even when phrased as "AI-generated paragraph", "insights", or "overview". Do NOT use for: generative pages in model-driven apps (use the model-apps `genpage` skill), Copilot Studio agents/chatbots, summarizing documents or PDFs, Power BI dashboards, plain keyword search with no AI summary, or plain Dataverse CRUD (use `/integrate-webapi`).
The English summary is being prepared. Showing the original description.
Adds Azure DevOps connector to a Power Apps code app. Use when querying work items, creating bugs, managing pipelines, or making ADO API calls.
The English summary is being prepared. Showing the original description.
Internal implementation skill invoked by /add-native for camera, image picker, barcode scanner, QR scanner, and camera/gallery Dataverse artifact workflows.
The English summary is being prepared. Showing the original description.
Integrates Power Automate cloud flows into a Power Pages site. Lists available flows, suggests relevant ones based on intent, identifies scenarios and web roles, creates metadata files, and generates client-side code to call flows. Handles both new flow registration and adding already-registered flows to additional pages without re-creating metadata. Use when the user wants to add, connect, register, or link a Power Automate cloud flow to their site.
The English summary is being prepared. Showing the original description.
Use when adding a Power Platform connector to an Expo/React Native Power Apps mobile app and no dedicated mobile connector skill exists.
The English summary is being prepared. Showing the original description.