Root Cause Investigation
garrytan/gstack
Debugs in four phases (investigate, analyze, hypothesize, implement) under one rule: no fix is made until the root cause is found.
A skill your agent uses when investigating common or slow variants, repeated work, unusual paths, or a specific Process Mining case.
OfficialMITAuto-check passed
Install Analyze Variants
$ npx skills add microsoft/power-platform-skills --skill analyze-variants -a claude-codeProject install by default; add -g for ~/.claude/skills/.
$ gh skill install microsoft/power-platform-skills analyze-variants --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-variants .claude/skills/analyze-variants && 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-variants" agent skill from https://github.com/microsoft/power-platform-skills/tree/main/plugins/process-intelligence/skills/analyze-variants into .claude/skills/analyze-variants/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "analyze-variants", 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-variantsType 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-variants -a codexProject install goes to .agents/skills/; add -g for ~/.codex/skills/.
$ gh skill install microsoft/power-platform-skills analyze-variants --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-variants .agents/skills/analyze-variants && 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-variants" agent skill from https://github.com/microsoft/power-platform-skills/tree/main/plugins/process-intelligence/skills/analyze-variants into .agents/skills/analyze-variants/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "analyze-variants", 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-variants -a cursorProject install goes to .agents/skills/; add -g for ~/.cursor/skills/.
$ gh skill install microsoft/power-platform-skills analyze-variants --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-variants .cursor/skills/analyze-variants && 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-variants" agent skill from https://github.com/microsoft/power-platform-skills/tree/main/plugins/process-intelligence/skills/analyze-variants into .cursor/skills/analyze-variants/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "analyze-variants", 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-variants--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-variants -a gemini-cliProject install goes to .agents/skills/; add -g for ~/.gemini/skills/.
$ gh skill install microsoft/power-platform-skills analyze-variants --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-variants .gemini/skills/analyze-variants && 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-variants" agent skill from https://github.com/microsoft/power-platform-skills/tree/main/plugins/process-intelligence/skills/analyze-variants into .gemini/skills/analyze-variants/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "analyze-variants", 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-variantsInstalls 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-variants -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-variants .github/skills/analyze-variants && 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-variants" agent skill from https://github.com/microsoft/power-platform-skills/tree/main/plugins/process-intelligence/skills/analyze-variants into .github/skills/analyze-variants/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "analyze-variants", 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-variants -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-variants --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-variants .opencode/skills/analyze-variants && 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-variants" agent skill from https://github.com/microsoft/power-platform-skills/tree/main/plugins/process-intelligence/skills/analyze-variants into .opencode/skills/analyze-variants/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "analyze-variants", 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-variants- GitHub stars
- 984
- Token cost
- ~860 tokens
- SKILL.md length
- 342 words
- Files
- 1
- Skills in repo
- 93
- Repo updated
- First seen
- Licence
- MIT
At a glance
A skill your agent uses when investigating common or slow variants, repeated work, unusual paths, or a specific Process Mining case.
- Works in 2 steps: get_variants_with_metrics_v2… → Only if mean-case slowness still needs…
- Investigating common
- SKILL.md covers Ordered traces and Guardrails
- Instructions only: no scripts, shell commands, URLs or credentials in SKILL.md
What it does
Analyze Variants is an agent skill from microsoft/power-platform-skills, published by the product's own GitHub organization. Use when investigating common or slow variants, repeated work, unusual paths, or a specific Process Mining case.
Its SKILL.md is about 860 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
- Investigating common
- A specific Process Mining case
Example prompts
- “/analyze-variants”
Requirements
- Pre-approved tools (allowed-tools): Read, AskUserQuestion
Workflow steps
2 steps, taken from the first numbered list in SKILL.md.
- get_variants_with_metrics_v2 {S,filterOptions:F,itemsPerPage:5,itemsToSkip:0,metricToSortBy:"CaseCount",sortOrder:"Descending"}.
- Only if mean-case slowness still needs comparison, repeat with metricToSortBy:"CaseDuration".
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 Variants loads about 860 tokens when it runs. Until then it costs about 32 tokens; SKILL.md has 342 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). 342 words, ~860 tokens.
Download SKILL.mdSave it as
.claude/skills/analyze-variants/SKILL.md (or your agent's skills folder).- name
- analyze-variants
- description
- Use when investigating common or slow variants, repeated work, unusual paths, or a specific Process Mining case.
- allowed-tools
- Read, AskUserQuestion
Variants, rework and exact cases
Use the shared contract and filters/units. Choose the branch answering the question; do not run a variant overview before an exact-case or rework request.
Ordered traces
Common or slow variants
get_variants_with_metrics_v2 {S,filterOptions:F,itemsPerPage:5,itemsToSkip:0,metricToSortBy:"CaseCount",sortOrder:"Descending"}.- Only if mean-case slowness still needs comparison, repeat with
metricToSortBy:"CaseDuration". If the first complete result already answers it, stop.CaseDurationis a mean; variantDurationis not its substitute.
Cases with repeated work
- Copy F, appending to
caseMetricConditionFilters:{metric:"CaseReworkCount",comparisonOperator:"GreaterThan",values:[0],isInclusive:true}. get_cases_with_metrics_v2 {S,filterOptions:Fplus,itemsPerPage:5,itemsToSkip:0,metricToSortBy:"ReworkCount",sortOrder:"Descending"}. A native count suffices; no formula or saved metric is needed.- Only for unresolved transition evidence:
get_edges_with_metrics_v2 {S,filterOptions:Fplus,itemsPerPage:10,itemsToSkip:0}. No edge sort exists; mark incomplete evidence page-local.
A specific case
- Reuse details to identify the metadata-proven case-key attribute K and its type T.
Bind the exact user/returned value X, e.g. synthetic
"Demo-17". - Append
{attributeName:K,dataType:T,attributeValues:[X],isInclusive:true}to F'sattributeValueFilters; callget_cases_with_metrics_v2 {S,filterOptions:Fcase,itemsPerPage:5,itemsToSkip:0}. - An optional same-cohort bottleneck/edge query can summarize activities/handoffs.
If no exposed key expresses the case, stop; do not scan all cases or invent
caseId.
Guardrails
Continue relevant pages or drilldowns until the question is answered or evidence cannot discriminate;
no fixed call/total-row quota or automatic repeated queries. Show at most five headline rows by default.
Use filterOptions, itemsPerPage and itemsToSkip, not filters, metrics, limit or offset.
No variantId filter exists. For a user-specified sequence use only discovered attribute values
and the advertised sequence-filter schema; do not reconstruct unavailable variant Values.
No event-timeline or conformance-check tool exists. Rework/variation alone proves neither
event order nor a conformance violation. Retain scope, versions, metric units and partial coverage.
Activity occurrence is not full payment, successful dismissal, business closure or compliance. Check the business outcome definition and available attributes/measures; route missing measures to derive-metric, never infer success from an event name. Missing events or terminal-looking traces may be censored, ongoing, legitimately ended or incompletely recorded. Do not choose without closure, recording and observation-coverage evidence. Use the investigation method: distinguish observed presence/counts from tested outcomes; mark an unresolved outcome inconclusive and retain definition provenance, baseline/test filters, evidence references and the next discriminating check.
© 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-variants of microsoft/power-platform-skills.
Open the folder on GitHubat commit 7d6b845
Compare with similar skills
Analyze Variants 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 Variants this skillmicrosoft/power-platform-skills | 984 | — | ~860 | Automated safety check: Pass | MIT | |
| Root Cause Investigationgarrytan/gstack | 136k | — | ~12k | Automated safety check: Notes | MIT | |
| Osint Investigationaffaan-m/ECC | 276k | — | ~5.7k | Automated safety check: Pass | CC-BY-SA-4.0 | |
| Investigate Slow Upstream Responsesblotcms/blot | 2k | — | ~3.6k | Automated safety check: Pass | AGPL-3.0 | |
| Investigate CIClickHouse/ClickHouse | 50k | — | ~11k | Automated safety check: Notes | Apache-2.0 | |
| Investigate Issuevideojs/video.js | 40k | — | ~318 | Automated safety check: Pass | Custom licence |
Similar skills
Osint Investigation
affaan-m/ECC
Sparse-clue OSINT investigation methodology for extracting overlooked leads, connecting fragmented evidence, and testing explanations across sources.
Investigate Slow Upstream Responses
blotcms/blot
Scan the production openresty access log (/var/instance-ssd/logs/access.log) for requests with slow upstream response times (st=, the time the node containers took to answer), triage and rank them…
Investigate CI
ClickHouse/ClickHouse
Investigate a ClickHouse CI failure end-to-end from a PR or S3 report URL.
Investigate Issue
videojs/video.js
Investigate GitHub issues without changing code. An agent skill from videojs/video.js.
- Official
Investigating Replay
PostHog/posthog
Investigates a session recording by gathering metadata, person profile, same-session events, and linked error tracking issues in one pass.
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 Variants
What does Analyze Variants do?
A skill your agent uses when investigating common or slow variants, repeated work, unusual paths, or a specific Process Mining case. Analyze Variants is an agent skill from microsoft/power-platform-skills, published by the product's own GitHub organization. Use when investigating common or slow variants, repeated work, unusual paths, or a specific Process Mining case.
When should I use Analyze Variants?
Analyze Variants fits situations like: investigating common; A specific Process Mining case.
How do I install Analyze Variants in Claude Code?
Run `npx skills add microsoft/power-platform-skills --skill analyze-variants -a claude-code`. Or copy the skill folder (plugins/process-intelligence/skills/analyze-variants in microsoft/power-platform-skills) into .claude/skills/analyze-variants in your project. Claude Code loads it when a task matches its description.
How do I install Analyze Variants in Codex?
Run `npx skills add microsoft/power-platform-skills --skill analyze-variants -a codex`. Or copy the skill folder (plugins/process-intelligence/skills/analyze-variants in microsoft/power-platform-skills) into .agents/skills/analyze-variants in your project. Codex loads it when a task matches its description.
Can I use Analyze Variants 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-variants -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-variants, .gemini/skills/analyze-variants, .github/skills/analyze-variants and .opencode/skills/analyze-variants in your project.
What does Analyze Variants need to run?
SKILL.md names no scripts, command-line tools or credentials: Analyze Variants is instructions for the agent only. Its frontmatter pre-approves these tools: Read, AskUserQuestion.
Does Analyze Variants 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 Variants 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 Variants use?
Analyze Variants 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 Variants use?
About 860 tokens (SKILL.md is roughly 3.4k 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 Variants?
Skills that share tags, products or a category with Analyze Variants: Root Cause Investigation (garrytan/gstack, 136k stars), Osint Investigation (affaan-m/ECC, 276k stars), Investigate Slow Upstream Responses (blotcms/blot, 2k stars) and Investigate CI (ClickHouse/ClickHouse, 50k stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.
Who maintains Analyze Variants?
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.