← LeaderboardThe Skill Leaderboard

analytics

Use when a Process Mining overview, initial process selection, or an analytical follow-up needs routing.

Published by microsoft ↗microsoft/power-platform-skills

Try your first task

analytics

Start a fresh conversation. Replace the highlighted placeholders.

Use analytics to provide a concise process overview for [process], reporting available case, event, variant, duration, and waiting-time metrics with their native units and coverage.

Required inputs

  • [process]

User-approved starter prompt based on a pinned source version; check current skill requirements before running. Task evidence ↗

SKILL.md

name: analyticsdescription: Use when a Process Mining overview, initial process selection, or an analytical follow-up needs routing.allowed-tools: Read, AskUserQuestion

Process overview and routing

Use the shared contract once per fresh analysis context. Recipes name native functions, not provider-prefixed host tools; bind them to discovered schemas.

Shortest trace

  1. Reuse the selected process and fresh metadata. Otherwise 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.
  2. 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.
  3. Only for requested path concentration: 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-upLoad only this skill
Broad business question, observed pattern, competing explanationsinvestigate-process
Slow activities, waiting, handoffs, cumulative workloadanalyze-performance
Common/slow variants, repeated work, a specific caseanalyze-variants
Explanatory attributes, association hypothesesanalyze-drivers
Before/after or A/B cohortscompare-cohorts
Missing metric, saved metric reuse, ephemeral formuladerive-metric
Interacting objects or leading-object executionsanalyze-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.