analyze-drivers
This skill helps the agent identify explanatory attributes and test hypotheses for differences in process metrics like duration, waiting time, utilization, or…
Identity proven by GitHub's verified organisation badge (microsoft)
- Agents
- Claude Code, Codex, Cursor, Gemini CLI, GitHub Copilot, OpenCode, claude.ai and API
- License
- MIT (permissive)
- Pin
- ca144d2pinned Oct 9, 2026
- Context cost
- about 860 tokenswhen the skill loads
- GitHub stars
- 978on microsoft/power-platform-skills
- Scripts
- None found
What it does
“Use when seeking explanatory attributes or hypotheses for differences in process duration, waiting, utilization or rework.”
Generated summary from the skill's own text
This skill helps the agent identify explanatory attributes and test hypotheses for differences in process metrics like duration, waiting time, utilization, or rework. It uses correlation analysis and statistical methods to rank candidate drivers, then conducts focused comparisons to distinguish between competing explanations with tracked evidence.
When to use it
- Investigating why process cases vary in duration or waiting time
- Testing hypotheses about resource utilization or event frequency differences
- Analyzing potential causes of rework or loop patterns in processes
- Validating candidate explanatory attributes before claiming causation
When not to
- When seeking statistical significance or confidence intervals rather than descriptive influence
- Analyzing event-level attributes without case-level context available
- Situations requiring exploratory fishing without frozen hypothesis or scope
Install
These commands install from the publisher's repository and need no account.
skills CLI
npx skills add microsoft/power-platform-skills --skill analyze-driversInstalls from the repository's default branch, which may have changed since the commit we checked.
GitHub CLI 2.90 or later
gh skill install microsoft/power-platform-skills analyze-drivers@ca144d29c1665a329ab4b8e14946b2105e7622faInstalls the commit we checked (ca144d2).
Copy by hand
Download the folder at ca144d2 and put it in .claude/skills/analyze-drivers for Claude Code and in .agents/skills/analyze-drivers for Codex, Cursor, Gemini CLI, GitHub Copilot and OpenCode.
Claude Code plugin
/plugin install azure-cosmos-db-assistant@claude-plugins-officialThe publisher's plugin in Claude's official marketplace. It may hold more than this skill, and we have not pinned it.
Claude Code plugin
/plugin install azure@claude-plugins-officialThe publisher's plugin in Claude's official marketplace. It may hold more than this skill, and we have not pinned it.
Claude Code plugin
/plugin install azure-sql-developer@claude-plugins-officialThe publisher's plugin in Claude's official marketplace. It may hold more than this skill, and we have not pinned it.
Copy for your agent
A prompt for any coding agent. It installs this skill from GitHub at the pinned commit, copies the files as they are, and runs nothing unless you ask.
Prompt
Install the agent skill "analyze-drivers" by Microsoft. Source, pinned to commit ca144d29c1665a329ab4b8e14946b2105e7622fa: https://github.com/microsoft/power-platform-skills/tree/ca144d29c1665a329ab4b8e14946b2105e7622fa/plugins/process-intelligence/skills/analyze-drivers 1. Download that folder at exactly this commit. Do not use the default branch. 2. Copy every file unchanged, keeping the folder structure, into .claude/skills/analyze-drivers/ for Claude Code and .agents/skills/analyze-drivers/ for Codex, Cursor, Gemini CLI, GitHub Copilot and OpenCode. Create the folders if they do not exist. 3. Do not edit the files, and do not run any script in the folder unless I ask you to. 4. When you are done, list the files you copied and where you put them. Listing and checks: https://www.agentnative.dev/skills/microsoft/analyze-drivers
SKILL.md at the pin
---
name: analyze-drivers
description: Use when seeking explanatory attributes or hypotheses for differences in process duration, waiting, utilization or rework.
allowed-tools: Read, AskUserQuestion
---
# Drivers: association before explanation
Use the [shared contract](../../references/analysis-contract.md) and
[filter/unit reference](../../references/filters-and-units.md).
Reuse metadata and frozen baseline scope; choose a specific defined outcome and relevant case-level
attributes from the user's context, without a candidate quota. If none is known, ask; do not sweep.
State a testable hypothesis, possible competing explanation and what would distinguish them.
Load the [investigation method](../../references/investigation-method.md) for evidence/status tracking.
For utilization, first check timestamp imports and the zero-duration convention in the unit
reference. A cohort-mix convention is not resource efficiency or measured productive time.
## Ordered trace
1. Check A's metadata level before correlation. Reuse a cached signal instead of repeating it.
`get_correlation_v2 {S,attributeName:A,influenceFormula:I,sortOrder:"Descending",filterOptions:F}`.
| Outcome | I |
|---|---|
| Duration / waiting / active time | DurationInfluence / WaitingTimeInfluence / ActiveTimeInfluence |
| Utilization / event count | CaseUtilizationInfluence / EventCountInfluence |
| Rework / loops / self-loops | ReworkCountInfluence / LoopCountInfluence / SelfloopCountInfluence |
Use the advertised enum and exact spelling. There are **no** `itemsPerPage`, `itemsToSkip`,
`top`, `metrics` or `limit` arguments. The service ranks at most 20 groups.
2. Only if prevalence or mean evidence is needed and statistics is advertised:
`get_attribute_statistics {S,attributeName:A,filterOptions:F,itemsPerPage:5,itemsToSkip:0,metricToSortBy:"CaseFrequency",sortOrder:"Descending"}`.
Match returned values explicitly. Influence-ranked groups may differ from
frequency-ranked groups; an absent match is unknown, not zero.
3. For a remaining hypothesis, use a discriminating matched comparison via compare-cohorts,
focused statistics/cases, or another relevant candidate. Derive each test from frozen F,
never an outcome-only exploratory subset. A cached signal can go directly to its test.
Continue needed checks/pages without fixed analytical-call or candidate quotas.
If matched evidence contradicts the proposed direction, mark it **contradicted** within that
scope; do not privilege the earlier influence score or claim it proves a cause.
## Non-case branch
An event-level Resource cannot be sent to correlation. If useful and advertised, use the
statistics call above for that attribute, but describe grouped **event** duration/frequencies,
not case-duration drivers. Otherwise ask for a case-level candidate or report the capability gap.
Do not silently substitute a different causal analysis.
## Report and stop
Influence is a prevalence-weighted descriptive score, **not Pearson correlation, significance,
causal effect or confidence**. Its formula already scales by 100; do not multiply again.
Return at most five useful signals with available counts/means, units, scope and partial coverage.
Label explanations as hypotheses, note selection/confounding, and state one falsifiable evidence check.
Record tested versus merely observed claims, alternatives and missing evidence; revise or stop
when the next check cannot discriminate. No assumed outcome maturity or closure.
Stop when no discriminating evidence remains; do not paginate correlations or invent sample sizes.
From microsoft/power-platform-skills at ca144d2, shown as plain text under its license: MIT (permissive). The license text is in LICENSE.
View SKILL.md on GitHub at ca144d2Files
- SKILL.md3.6 KB · 296d49b11900
1 file, 3.6 KB in total. Each file has a sha256 in the pin's manifest; the first 12 characters are shown.
Skill folder on GitHub at ca144d2More from Microsoft
pull-requests
This skill guides the agent in writing high-quality pull request descriptions following the Agent Framework repository template and in systematically handling…
Claude Code, Codex, Cursor +4 · about 1.5K tokens · pinned 6 days ago
appinsights-instrumentation
This skill provides guidance and reference materials for instrumenting webapps with Azure Application Insights across ASP.NET Core, Node.js, Python, and…
Contains scripts
Claude Code, Codex, Cursor +3 · about 840 tokens · pinned 6 days ago
azure-ai
This skill enables agents to use Azure AI services including Search for full-text and vector queries, Speech for transcription and synthesis, OpenAI for…
Claude Code, Codex, Cursor +4 · about 750 tokens · pinned 6 days ago
azure-diagnostics
The skill diagnoses Azure production issues across App Service, Functions, Container Apps, AKS, VMs, and Messaging services using AppLens, Azure Monitor…
Contains scripts
Claude Code, Codex, Cursor +3 · about 1.6K tokens · pinned 6 days ago
add-camera
This skill generates typed TypeScript wrappers for camera capture and image gallery selection in Power Apps mobile apps using Expo libraries.
Claude Code · about 5.2K tokens · pinned 6 days ago
add-connector
This skill adds Power Platform connectors to Expo/React Native mobile apps by discovering the connector, establishing a connection, generating service files…
Claude Code · about 3.8K tokens · pinned 6 days ago
Related in Data and databases
data-table-manager
This skill manages n8n Data Tables through creation, import, querying, and mutation operations.
by n8nOfficial publisher
Claude Code, Codex, Cursor +3 · about 2.1K tokens · pinned 6 days ago
algolia-automation
This skill automates Algolia search and indexing operations through the Rube MCP interface.
by ComposioOfficial publisher
Claude Code, Codex, Cursor +3 · about 690 tokens · pinned 6 days ago
expo-sqlite
This skill enables SQLite database operations in Expo and React Native apps for structured data storage, offline queues, and persistent caches.
by ExpoOfficial publisher
Claude Code, Codex, Cursor +4 · about 2.6K tokens · pinned 6 days ago
prisma-8
This skill helps agents work with Prisma 8, a contract-first data layer for TypeScript projects.
by PrismaOfficial publisher
Contains scripts
Claude Code, Codex, Cursor +3 · about 3.5K tokens · pinned 6 days ago
analyzing-experiment-session-replays
This skill enables agents to analyze session recordings from experiment variants to identify behavioral differences between control and test groups.
by PostHogOfficial publisher
Claude Code, Codex, Cursor +4 · about 2.3K tokens · pinned 6 days ago
auditing-warehouse-view-health
Audits materialized views in a PostHog data warehouse to identify failed views and flag unused ones that waste compute resources.
by PostHogOfficial publisher
Claude Code, Codex, Cursor +4 · about 1.4K tokens · pinned 6 days ago