analyze-performance

analyze-performance is a skill for Claude Code from microsoft/power-platform-skills. It costs 24 tokens per session (730 once invoked), scanned A, original, MIT.

A method for analysing process performance, including slow activities, waiting, handoffs, bottlenecks, and total activity time. It distinguishes average duration from the cumulative time spent across events.

In plain words
What is it for?
Use it to rank slow activities, measure cumulative activity duration, and gather targeted evidence about performance problems.
Why use it?
It prevents averages and totals from being treated as the same thing, which can hide activities with large overall impact.

Skill for Claude Code ✓ vendor

Written for Claude Code: allowed-tools in frontmatter. Also seen: names the AskUserQuestion tool.

Part of the process-intelligence plugin — 8 skills shipped together

Good fit Use it to rank slow activities, measure cumulative activity duration, and gather targeted evidence about performance problems.

Compare 6 skills from other repositories ↓
Install with agentmods
npx agentmods add skills/microsoft/power-platform-skills/analyze-performance
About the project

microsoft/power-platform-skills is a plugin marketplace containing reusable skills, agents, and commands for developing with Microsoft Power Platform. Developers use it to build and deploy Power Pages sites, model-driven Power Apps, and related solutions through Claude Code or GitHub Copilot. The catalogue entries are the marketplace's included skills, agents, plugins, and other agent components.

microsoft/power-platform-skills · 1,016 stars · on GitHub · aka.ms

Install

Getting it into your agent

One page per mod, every tool's command on it. A separate URL per tool would split the same page into five that compete with each other.

Any agent
npx skills add microsoft/power-platform-skills --skill analyze-performance
Clone the repo
git clone --depth 1 https://github.com/microsoft/power-platform-skills

Made for: Claude Code.

Or install process-intelligence, the plugin that ships this one along with the rest of its 8 skills.

Wrote this? Show the measurements

A badge with what this costs and how it scanned, read live from this page, so it follows the numbers instead of freezing them. Markdown for a README, HTML for a documentation site or a project page.

agentmods badge for analyze-performance

README.md
[![agentmods](https://agentmods.dev/badge/skills/microsoft/power-platform-skills/analyze-performance/github.svg)](https://agentmods.dev/skills/microsoft/power-platform-skills/analyze-performance)
Your own site
<a href="https://agentmods.dev/skills/microsoft/power-platform-skills/analyze-performance"><img src="https://agentmods.dev/badge/skills/microsoft/power-platform-skills/analyze-performance/github.svg" alt="Measured on agentmods" height="20"></a>

Or the 80×15 button, for a site that already has a row of RSS and ATOM ones. Only the verdict fits; the numbers stay here.

agentmods 80×15 button for analyze-performance

Your own site · 80×15
<a href="https://agentmods.dev/skills/microsoft/power-platform-skills/analyze-performance"><img src="https://agentmods.dev/badge/skills/microsoft/power-platform-skills/analyze-performance.svg" alt="Reviewed on agentmods" width="80" height="20"></a>
Per session 24 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.
When invoked 730 The whole file, excluding the scripts and references it only reads on demand.
Security scan A 0 findings. A grade says what 26 rules found in the file — not that it is safe.
Origin original No closer match found in the catalogue.
Token cost

What it costs to keep this loaded

Counted locally with the o200k_base tokenizer, which is exact for GPT models; Claude uses its own tokenizer and its counts differ. Treat this as one consistent yardstick across the catalogue rather than a bill. Prices are per million input tokens.

ModelPer sessionOnce invoked
Fable 5.1 $0.00024 $0.00730
Opus 5.5 $0.00010 $0.00292
Sonnet 5.5 $0.00005 $0.00146
Haiku 4.5 $0.00002 $0.00073

Measured 9d ago against content hash d2ed663934bc, method: parsed. Prices are Anthropic first-party input rates as of 2026-10-07, from the pricing page.

Security

Grade A, and why

analyze-performance scanned grade A with 0 findings against 26 rules in 11 categories — prompt injection, anti-refusal, data exfiltration, privilege escalation, supply chain, agent snooping, system-prompt leakage, SSRF and excessive agency — measured 9d ago.

A static scan of the body, not an audit. Every finding is printed with the line that produced it so you can judge whether it matters here. A mod is markdown that instructs an agent; that is exactly why what it instructs is worth reading.

Nothing flagged

None of the 26 patterns this scan looks for appear in this file: no shell pipes, no recursive deletes, no credential paths, no hidden text, no instruction-override or anti-refusal phrasing, no agent-config snooping. That is not a guarantee, it is the absence of the things that are checkable.

plugins/process-intelligence/skills/analyze-performance/SKILL.md · 54 lines

How it starts

The opening of the file, as written. The whole thing — 54 lines — stays where its author put it; the contents beside it link to each section on GitHub.

Performance: averages are not total impact

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.

Ordered recipe

Choose the smallest entry branch:

  1. Slow activities by mean: 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.
  2. Cumulative activity duration: skip step 1 if this alone was requested. From metadata take the exact Activity import attribute A; never assume its name is "Activity". If advertised, call 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.
  3. Only for unresolved evidence, choose a targeted drilldown: 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.

Boundaries and stopping

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.

Read the full file on GitHub · 54 lines

Changes

What this file has done since we first saw it

Hashed on every crawl. A supply-chain change to an agent config is a question of when, not whether, so the history is kept rather than the latest state alone.

  1. 9d ago First seen · 54 lines · 24 tokens per session scan A d2ed663934bc

Subscribe to this mod's changes

analyze-performance is a skill published in the GitHub repository microsoft/power-platform-skills (1,016 stars, last pushed today), licensed MIT. It adds 24 tokens to every session and 730 once invoked, about $0.0001 per session on Opus 5.5. A static security scan graded it A with 0 findings. No closer match exists in the catalogue, so it is treated as the original; first seen 2026-10-09.

Related

Other skills, from other repositories

canvas-apps-ui-gen

Generates paste-ready Power Apps Canvas App YAML. Invoke when the user wants to replicate a UI mockup, improve an existing Canvas app screen, or build a new screen from a text description. Also invoke when the user asks to "improve", "redesign", or "generate YAML" for a Canvas app screen.

ToluVictor/canvas-apps-tools · 71 tokens

top-design

Create award-winning, immersive web experiences at the level of Awwwards-featured agencies. Use when the user mentions "Awwwards quality", "make my site stunning", "scroll animations", "parallax storytelling", "cinematic web design", "portfolio site", or "brand experience". Also trigger when elevating a standard…

wondelai/skills · 113 tokens

ux-heuristics

Evaluate and improve interface usability using heuristic analysis. Use when the user mentions "usability audit", "users are confused", "form usability", "navigation problems", "Nielsen heuristics", "cognitive walkthrough", or "is this easy to use". Also trigger when reviewing a design for usability issues, improving…

wondelai/skills · 122 tokens

blue-ocean-strategy

Create uncontested market space using value innovation instead of competing head-to-head. Use when the user mentions "blue ocean", "red ocean", "strategy canvas", "ERRC framework", "value innovation", "non-customers", "buyer utility map", "the market is too crowded", "how do we stand out", or "escape the price war".…

wondelai/skills · 152 tokens

clean-code

Write readable, maintainable code through disciplined naming, small functions, and clean error handling. Use when the user mentions "clean up this code", "this function is too long", "code smells", "naming conventions", "boy scout rule", "single responsibility", or "unit test quality". Also trigger when reviewing a…

wondelai/skills · 126 tokens

session-scan

Compute metrics for Claude Code sessions. Discovers via ccrider, filters trivial, computes friction/opportunity/fingerprint scores. Use for broad session triage.

oliver-kriska/claude-elixir-phoenix · 36 tokens