Use when investigating slow activities, waiting, handoff duration, bottlenecks or cumulative activity workload.
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 and units/filter semantics. Reuse S, baseline F and metadata; do not request a baseline overview for an exact top-bottleneck question.
Choose the smallest entry branch:
get_bottleneck_analysis_v2 {S,itemsPerPage:5,itemsToSkip:0,mcpFilterOptions:F}.
Omit absent F. Duration is average activity duration, already ranked descending.
Do not pass attributeName, metrics, aggregation or limit.get_attribute_statistics {S,attributeName:A,filterOptions:F,itemsPerPage:5,itemsToSkip:0,metricToSortBy:"TotalDuration",sortOrder:"Descending"}.
There is no _v2 suffix. For an event-level Activity, TotalDuration sums matching
events; AvgDuration is their mean. Keep EventFrequency and CaseFrequency distinct.
RelativeCaseFrequency is a ratio; overlapping activity groups' case counts are not additive.get_edges_with_metrics_v2 {S,filterOptions:F,itemsPerPage:20,itemsToSkip:0} for handoffs,
or get_cases_with_metrics_v2 {S,filterOptions:F,itemsPerPage:5,itemsToSkip:0,metricToSortBy:"WaitingTime",sortOrder:"Descending"}.
Reuse earlier compatible results. Continue relevant drilldowns/pages without fixed call or
total-row ceilings; each query must resolve missing evidence, not repeat an answered question.Missing statistics: report the cumulative-measure gap, optionally average-only bottleneck evidence. Never derive population totals from top-five averages or call a hidden statistics tool. Edges expose no sort input: local ranking of one incomplete page is page-local, not global. Report the native edge Duration mean; do not relabel it as an independently established waiting metric. For a requested global edge ranking, retrieve necessary pages to complete coverage before ranking; if coverage is incomplete, explicitly leave the global result unresolved. Event/attribute filters retain whole cases, not just matching events. Check timestamp imports before interpreting utilization: zero-duration conventions with start-only data can produce nonzero ratios without measured active work. Keep raw values and use same-scope cohort evidence; see the unit reference.
Stop once answered or evidence/capability is exhausted. Show at most five headline rows with separate mean, total and frequency columns only when returned, scope/units and coverage. High duration is an investigation lead, not proof of cause or a guaranteed time saving. Mean activity duration times process case count is not total workload: cases are not activity occurrences. Even known workload is not an intervention's removable delay. Use the investigation method to label observations and tested findings, retain counterevidence and identify a discriminating next check.
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.