Hypotheses
davepoon/buildwithclaude
Manages the project's testable hypotheses — surfacing new ones, refining existing ones, updating status, reviewing the full set, and assessing hypothesis state based on evidence gathered so far.
A skill your agent uses when seeking explanatory attributes or hypotheses for differences in process duration, waiting, utilization or rework.
OfficialMITAuto-check passed
Install Analyze Drivers
$ npx skills add microsoft/power-platform-skills --skill analyze-drivers -a claude-codeProject install by default; add -g for ~/.claude/skills/.
$ gh skill install microsoft/power-platform-skills analyze-drivers --agent claude-codeProject scope by default; add --scope user for a personal install. Needs GitHub CLI 2.90.0 or later (public preview).
$ git clone --depth 1 https://github.com/microsoft/power-platform-skills.git skills-src && mkdir -p .claude/skills && cp -r skills-src/plugins/process-intelligence/skills/analyze-drivers .claude/skills/analyze-drivers && rm -rf skills-srcUse ~/.claude/skills/ instead of .claude/skills for a personal install. The folder must contain SKILL.md.
Claude Code skills documentation · loads skills from .claude/skills/
Install the "analyze-drivers" agent skill from https://github.com/microsoft/power-platform-skills/tree/main/plugins/process-intelligence/skills/analyze-drivers into .claude/skills/analyze-drivers/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "analyze-drivers", then confirm the skill loads.Claude Code copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$skill-installer install https://github.com/microsoft/power-platform-skills/tree/main/plugins/process-intelligence/skills/analyze-driversType this inside Codex. $skill-installer <name> installs a curated skill from openai/skills. The installer writes to $CODEX_HOME/skills (default ~/.codex/skills). Restart Codex if the skill does not show up.
$ npx skills add microsoft/power-platform-skills --skill analyze-drivers -a codexProject install goes to .agents/skills/; add -g for ~/.codex/skills/.
$ gh skill install microsoft/power-platform-skills analyze-drivers --agent codexProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/microsoft/power-platform-skills.git skills-src && mkdir -p .agents/skills && cp -r skills-src/plugins/process-intelligence/skills/analyze-drivers .agents/skills/analyze-drivers && rm -rf skills-srcUse ~/.agents/skills/ instead of .agents/skills for a personal install.
Codex skills documentation · loads skills from .agents/skills/
Install the "analyze-drivers" agent skill from https://github.com/microsoft/power-platform-skills/tree/main/plugins/process-intelligence/skills/analyze-drivers into .agents/skills/analyze-drivers/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "analyze-drivers", then confirm the skill loads.Codex copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ npx skills add microsoft/power-platform-skills --skill analyze-drivers -a cursorProject install goes to .agents/skills/; add -g for ~/.cursor/skills/.
$ gh skill install microsoft/power-platform-skills analyze-drivers --agent cursorProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/microsoft/power-platform-skills.git skills-src && mkdir -p .cursor/skills && cp -r skills-src/plugins/process-intelligence/skills/analyze-drivers .cursor/skills/analyze-drivers && rm -rf skills-srcUse ~/.cursor/skills/ instead of .cursor/skills for a personal install.
Cursor skills documentation · loads skills from .cursor/skills/, .agents/skills/, .claude/skills/, .codex/skills/
Install the "analyze-drivers" agent skill from https://github.com/microsoft/power-platform-skills/tree/main/plugins/process-intelligence/skills/analyze-drivers into .cursor/skills/analyze-drivers/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "analyze-drivers", then confirm the skill loads.Cursor copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ gemini skills install https://github.com/microsoft/power-platform-skills.git --path plugins/process-intelligence/skills/analyze-drivers--scope user (default) or --scope workspace; --path is the subfolder of the repo that holds the skill; --consent skips the security confirmation prompt.
$ npx skills add microsoft/power-platform-skills --skill analyze-drivers -a gemini-cliProject install goes to .agents/skills/; add -g for ~/.gemini/skills/.
$ gh skill install microsoft/power-platform-skills analyze-drivers --agent gemini-cliProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/microsoft/power-platform-skills.git skills-src && mkdir -p .gemini/skills && cp -r skills-src/plugins/process-intelligence/skills/analyze-drivers .gemini/skills/analyze-drivers && rm -rf skills-srcUse ~/.gemini/skills/ instead of .gemini/skills for a personal install, then run /skills reload.
Gemini CLI skills documentation · loads skills from .gemini/skills/, .agents/skills/
Install the "analyze-drivers" agent skill from https://github.com/microsoft/power-platform-skills/tree/main/plugins/process-intelligence/skills/analyze-drivers into .gemini/skills/analyze-drivers/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "analyze-drivers", then confirm the skill loads.Gemini CLI copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ gh skill install microsoft/power-platform-skills analyze-driversInstalls for Copilot at project scope by default; add --scope user for a personal install. Preview a skill first with gh skill preview. Needs GitHub CLI 2.90.0 or later (public preview).
$ npx skills add microsoft/power-platform-skills --skill analyze-drivers -a github-copilotProject install goes to .agents/skills/; add -g for ~/.copilot/skills/.
$ git clone --depth 1 https://github.com/microsoft/power-platform-skills.git skills-src && mkdir -p .github/skills && cp -r skills-src/plugins/process-intelligence/skills/analyze-drivers .github/skills/analyze-drivers && rm -rf skills-srcUse ~/.copilot/skills/ instead of .github/skills for a personal install. Commit .github/skills so cloud agent and code review can use it.
GitHub Copilot skills documentation · loads skills from .github/skills/, .claude/skills/, .agents/skills/
Install the "analyze-drivers" agent skill from https://github.com/microsoft/power-platform-skills/tree/main/plugins/process-intelligence/skills/analyze-drivers into .github/skills/analyze-drivers/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "analyze-drivers", then confirm the skill loads.GitHub Copilot copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ npx skills add microsoft/power-platform-skills --skill analyze-drivers -a opencodeOpenCode documents no install command of its own. Project install goes to .agents/skills/; add -g for ~/.config/opencode/skills/.
$ gh skill install microsoft/power-platform-skills analyze-drivers --agent opencodeProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/microsoft/power-platform-skills.git skills-src && mkdir -p .opencode/skills && cp -r skills-src/plugins/process-intelligence/skills/analyze-drivers .opencode/skills/analyze-drivers && rm -rf skills-srcUse ~/.config/opencode/skills/ instead of .opencode/skills for a personal install.
OpenCode skills documentation · loads skills from .opencode/skills/, .claude/skills/, .agents/skills/
Install the "analyze-drivers" agent skill from https://github.com/microsoft/power-platform-skills/tree/main/plugins/process-intelligence/skills/analyze-drivers into .opencode/skills/analyze-drivers/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "analyze-drivers", then confirm the skill loads.OpenCode copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
Facts
- Skill name
analyze-drivers- GitHub stars
- 984
- Token cost
- ~907 tokens
- SKILL.md length
- 396 words
- Files
- 1
- Skills in repo
- 93
- Repo updated
- First seen
- Licence
- MIT
At a glance
A skill your agent uses when seeking explanatory attributes or hypotheses for differences in process duration, waiting, utilization or rework.
- Works in 3 steps: Check A's metadata level before… → Only if prevalence or mean evidence is… → For a remaining hypothesis, use a…
- Seeking explanatory attributes
- SKILL.md covers Ordered trace, Non-case branch and Report and stop
- Instructions only: no scripts, shell commands, URLs or credentials in SKILL.md
What it does
Analyze Drivers is an agent skill from microsoft/power-platform-skills, published by the product's own GitHub organization. Use when seeking explanatory attributes or hypotheses for differences in process duration, waiting, utilization or rework.
Its SKILL.md is about 910 tokens, which your agent loads only when the skill is triggered. It is a single SKILL.md file with no bundled scripts.
The repository describes itself as: A plugin marketplace for GitHub Copilot and other AI agents that provides Power Platform development plugins, including reusable skills, agents, and commands for building and… The licence is MIT.
When your agent uses it
- Seeking explanatory attributes
- Hypotheses for differences in process duration
Example prompts
- “/analyze-drivers”
Requirements
- Pre-approved tools (allowed-tools): Read, AskUserQuestion
Workflow steps
3 steps, taken from the first numbered list in SKILL.md.
- Check A's metadata level before correlation. Reuse a cached signal instead of repeating it.
- Only if prevalence or mean evidence is needed and statistics is advertised
- For a remaining hypothesis, use a discriminating matched comparison via compare-cohorts,
What it can do on your machine
Read from SKILL.md and the folder at commit 7d6b845. It shows what the files ask for, not the result of running them.
Tool permissions
Pre-approves these tools, so the agent can use them without asking each time:
ReadAskUserQuestion
From allowed-tools in the SKILL.md frontmatter.
Runs code
No scripts in the folder and no shell commands in SKILL.md.
From the folder's file list and the shell code blocks in SKILL.md.
Network
No URLs in SKILL.md.
From URLs in SKILL.md, links to its own repository left out.
Credentials
Names no API keys, tokens, secrets or passwords.
From names ending in _API_KEY, _TOKEN, _SECRET, _KEY or _PASSWORD in SKILL.md.
Context cost
Analyze Drivers loads about 907 tokens when it runs. Until then it costs about 35 tokens; SKILL.md has 396 words of instructions outside code blocks.
Estimates: characters ÷ 4, the usual rule of thumb; real counts depend on the model's tokenizer. Scripts and assets cost tokens only if the agent reads them.
Safety
Auto-check passed
The automated check found no risky patterns in SKILL.md.
Automated static check — not a guarantee. Review scripts before installing. It scans the text of SKILL.md for risky patterns (piping downloads into a shell, reading credential files, hidden Unicode, destructive commands); files beside SKILL.md are not scanned.
SKILL.md
The full file from microsoft/power-platform-skills at commit 7d6b845, republished under its MIT licence (© microsoft). 396 words, ~907 tokens.
Download SKILL.mdSave it as
.claude/skills/analyze-drivers/SKILL.md (or your agent's skills folder).- 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 and filter/unit reference. 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 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
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,metricsorlimitarguments. The service ranks at most 20 groups.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.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.
Show full SKILL.md (141 more words)Show less
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.
© microsoft, MIT. Rendered from Markdown: HTML in the file is shown as text, images as links, and headings moved down two levels. Raw file
Files
Just SKILL.md in plugins/process-intelligence/skills/analyze-drivers of microsoft/power-platform-skills.
Open the folder on GitHubat commit 7d6b845
Compare with similar skills
Analyze Drivers next to the 5 skills that share the most tags, products or categories with it. Stars are the repository's; “used in” counts other GitHub owners with a copy.
| Skill | Stars | Used in | Tokens | Auto-check | Licence | Repo updated |
|---|---|---|---|---|---|---|
| Analyze Drivers this skillmicrosoft/power-platform-skills | 984 | — | ~907 | Automated safety check: Pass | MIT | |
| Hypothesesdavepoon/buildwithclaude | 3.6k | — | ~2k | Automated safety check: Pass | MIT | |
| Performance AttributionHKUDS/Vibe-Trading | 35k | — | ~3.1k | Automated safety check: Pass | MIT | |
| Campaign Attribution Evidence Analysismukul975/Anthropic-Cybersecurity-Skills | 34k | — | ~2.3k | Automated safety check: Pass | Apache-2.0 | |
| Seek And Analyze Videosickn33/agentic-awesome-skills | 47k | 2 repos | ~997 | Automated safety check: Pass | MIT | |
| Direction Attributethedaviddias/Front-End-Checklist | 74k | — | ~534 | Automated safety check: Pass | MIT |
Similar skills
Performance Attribution
HKUDS/Vibe-Trading
Explains why a portfolio beat or lagged its benchmark with Brinson sector attribution, factor alpha and beta decomposition, timing evaluation and benchmark comparison.
Campaign Attribution Evidence Analysis
mukul975/Anthropic-Cybersecurity-Skills
Weighs infrastructure, TTP, malware code and timing evidence with the Diamond Model and competing hypotheses to reach a confidence-rated attribution.
Seek And Analyze Video
sickn33/agentic-awesome-skills
Seek and analyze video content using Memories.ai Large Visual Memory Model for persistent video intelligence
Direction Attribute
thedaviddias/Front-End-Checklist
A skill your agent uses when reviewing templates, rendered HTML, or shared components related to Set text direction for RTL languages.
Fetchpriority Attribute
thedaviddias/Front-End-Checklist
A skill your agent uses when optimising Largest Contentful Paint (LCP), reducing render-blocking resource contention, or fine-tuning resource loading order in the critical rendering path.
More from microsoft/power-platform-skills
All 93 skills in this repo- Official
Manage Firewall
microsoft/power-platform-skills
Inspects and configures the web application firewall (WAF) in front of a Power Pages production site.
- Official
Manage Headers
microsoft/power-platform-skills
Inspects and configures the security headers a Power Pages site sends to browsers — Content Security Policy, frame and clickjacking protection, cross-origin sharing, cookie behavior, and related…
- Official
Scan Code
microsoft/power-platform-skills
Scans a Power Pages site project for security issues in source code and dependencies.
- Official
Scan Site
microsoft/power-platform-skills
Runs a security scan on a deployed Power Pages site, fetches the latest scan report, and produces a plain-language summary.
- Official
Setup Datamodel
microsoft/power-platform-skills
Creates Dataverse tables, columns, and relationships for a Power Pages site based on a data model proposal.
- Official
Add Localization
microsoft/power-platform-skills
Adds or extends multilingual localization in a Power Pages code-site SPA.
Questions about Analyze Drivers
What does Analyze Drivers do?
A skill your agent uses when seeking explanatory attributes or hypotheses for differences in process duration, waiting, utilization or rework. Analyze Drivers is an agent skill from microsoft/power-platform-skills, published by the product's own GitHub organization. Use when seeking explanatory attributes or hypotheses for differences in process duration, waiting, utilization or rework.
When should I use Analyze Drivers?
Analyze Drivers fits situations like: seeking explanatory attributes; hypotheses for differences in process duration.
How do I install Analyze Drivers in Claude Code?
Run `npx skills add microsoft/power-platform-skills --skill analyze-drivers -a claude-code`. Or copy the skill folder (plugins/process-intelligence/skills/analyze-drivers in microsoft/power-platform-skills) into .claude/skills/analyze-drivers in your project. Claude Code loads it when a task matches its description.
How do I install Analyze Drivers in Codex?
Run `npx skills add microsoft/power-platform-skills --skill analyze-drivers -a codex`. Or copy the skill folder (plugins/process-intelligence/skills/analyze-drivers in microsoft/power-platform-skills) into .agents/skills/analyze-drivers in your project. Codex loads it when a task matches its description.
Can I use Analyze Drivers in Cursor, Gemini CLI or GitHub Copilot?
Cursor, Gemini CLI, GitHub Copilot and OpenCode also load SKILL.md folders. With the skills CLI, run `npx skills add microsoft/power-platform-skills --skill analyze-drivers -a cursor` (or -a gemini-cli, github-copilot or opencode for the others). To copy it by hand, put the folder in .cursor/skills/analyze-drivers, .gemini/skills/analyze-drivers, .github/skills/analyze-drivers and .opencode/skills/analyze-drivers in your project.
What does Analyze Drivers need to run?
SKILL.md names no scripts, command-line tools or credentials: Analyze Drivers is instructions for the agent only. Its frontmatter pre-approves these tools: Read, AskUserQuestion.
Does Analyze Drivers access the network?
SKILL.md contains no URLs. Any network use would come from the scripts or tools the agent runs. This is read from the text; nothing was executed.
Is Analyze Drivers safe to install?
Our automated static check of SKILL.md found no risky patterns, such as piping downloads into a shell, reading credential files or hidden Unicode. It is not a guarantee. Review the folder before installing.
What licence does Analyze Drivers use?
Analyze Drivers is published under the MIT licence (the repository's licence). It allows redistribution, so the full SKILL.md is shown on this page.
How many tokens does Analyze Drivers use?
About 907 tokens (SKILL.md is roughly 3.6k characters). Agents keep only the skill's name and description in context until a task matches; then they load SKILL.md in full.
What are the alternatives to Analyze Drivers?
Skills that share tags, products or a category with Analyze Drivers: Hypotheses (davepoon/buildwithclaude, 3.6k stars), Performance Attribution (HKUDS/Vibe-Trading, 35k stars), Campaign Attribution Evidence Analysis (mukul975/Anthropic-Cybersecurity-Skills, 34k stars) and Seek And Analyze Video (sickn33/agentic-awesome-skills, 47k stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.
Who maintains Analyze Drivers?
microsoft (a GitHub organization, an official publisher) maintains it in microsoft/power-platform-skills, which has 984 GitHub stars. The repository holds 93 skills in this directory. The repository was last updated on October 9, 2026.
Source: microsoft/power-platform-skills on GitHub. Facts on this page come from the repository at the commit we read; the author's words are quoted as theirs.