derive-metric

derive-metric is a skill for Claude Code from microsoft/power-platform-skills. It costs 29 tokens per session (877 once invoked), scanned A, original, MIT.

A method for finding or calculating a process measure when the needed metric is missing. It first checks for an existing measure or saved custom metric before using a temporary calculation.

In plain words
What is it for?
Use it to reuse saved metrics, apply native measures, or derive a temporary scalar for a defined business question in Process Mining.
Why use it?
It reduces incorrect results by requiring the measure's entity, meaning, units, time basis, and aggregation to be defined before calculation.

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 reuse saved metrics, apply native measures, or derive a temporary scalar for a defined business question in Process Mining.

Compare 6 skills from other repositories ↓
Install with agentmods
npx agentmods add skills/microsoft/power-platform-skills/derive-metric
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 derive-metric
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 derive-metric

README.md
[![agentmods](https://agentmods.dev/badge/skills/microsoft/power-platform-skills/derive-metric/github.svg)](https://agentmods.dev/skills/microsoft/power-platform-skills/derive-metric)
Your own site
<a href="https://agentmods.dev/skills/microsoft/power-platform-skills/derive-metric"><img src="https://agentmods.dev/badge/skills/microsoft/power-platform-skills/derive-metric/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 derive-metric

Your own site · 80×15
<a href="https://agentmods.dev/skills/microsoft/power-platform-skills/derive-metric"><img src="https://agentmods.dev/badge/skills/microsoft/power-platform-skills/derive-metric.svg" alt="Reviewed on agentmods" width="80" height="20"></a>
Per session 29 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.
When invoked 877 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.00029 $0.00877
Opus 5.5 $0.00012 $0.00351
Sonnet 5.5 $0.00006 $0.00175
Haiku 4.5 $0.00003 $0.00088

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

Security

Grade A, and why

derive-metric 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/derive-metric/SKILL.md · 57 lines

What it actually says

Resolve a metric gap without saving definitions

Use the shared contract and filters/units. Follow this order; stop at the first sufficient option.

For a business-derived measure, confirm case/event entity, outcome definition/provenance, units, time basis and aggregation. Are amounts incremental transactions or cumulative snapshots? Never assume sum, latest or maximum: nonmonotonic snapshots require authoritative ordering and refund/correction semantics. Missing definitions mean inconclusive; ask before computing. Do not infer formula grammar from an example name or business description.

  1. Native output first. Use the existing metric and its correct scope/aggregation. For cases over one day append {metric:"CaseDuration",comparisonOperator:"GreaterThan",values:["1.00:00:00"],isInclusive:true} to F's caseMetricConditionFilters, then get_cases_with_metrics_v2 {S,filterOptions:Fplus,itemsPerPage:5,itemsToSkip:0}. No formula is needed for ordinary duration/waiting/counts; use native grouped statistics instead of summing a truncated cases page.
  2. Enabled saved metric. Reuse fresh details' CustomMetrics ID/name/type/dataType. Details is not a generic metric catalog and contains no saved formula text. Match Case/Event/Edge scope and scalar type. For a Boolean Case metric C append {metric:"CustomMetric",customMetricId:C,comparisonOperator:"EqualTo",values:[true],isInclusive:true} to caseMetricConditionFilters; query get_process_overall_metrics_v2 {S,filterOptions:Fplus} for a count. An ID filter needs no formula validation. A saved-name output expression, e.g. synthetic EscalatedCase(), does require the validation/column path below; do not guess escaping or missing dependencies.
  3. Exact local scalar. Reuse complete, definition-compatible, same-scope totals with a nonzero denominator. Label the result derived, not saved. Never average averages or use overlapping groups/top-N samples as population totals.
  4. Ephemeral formula only if necessary. Load formula execution. Reuse PV/PMV from current details, not process/view IDs; refresh when stale. Fetch needed targeted reference pages without a lookup quota; then validate: validate_custom_metric_formula {processVersionId:PV,processExtendedMetadataVersionId:PMV,formula:Fexpr}. For a candidate and its repairs, allow three validation attempts total, not endless retries. Repair only from structured errors/definitions; stop early on an unavailable prerequisite. Require isValid:true, a compatible dataType and the exact target context in types. Validation alone neither executes nor saves anything.
  5. Execute the smallest matching filter/query or default page-five column query. For cases: get_cases_with_metrics_v2 {S,filterOptions:F,itemsPerPage:5,itemsToSkip:0,formulaMetricInput:{name:N,formula:Fexpr}}. N must not collide with returned built-ins. Never invent computedColumns or metrics.

Continue necessary pages or distinct evidence queries without ordinary-call or total-row quotas. Reuse completed results; stop when answered or no new evidence is available. Missing validator forbids unvalidated execution even if the output field is advertised. Column and formula-filter capabilities are independent; stop after an explicit gate rejection. No create/save metric tool exists. If a prerequisite cannot be inlined, explain creation/enablement outside MCP, then refresh metadata and revalidate after the user's action.

Report definition/formula, units/context, validation state, at most five headline rows and ephemeral/not saved. Retain definition provenance and scoped evidence/status using the investigation method.

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 · 57 lines · 29 tokens per session scan A fd11a95e78c4

Subscribe to this mod's changes

derive-metric is a skill published in the GitHub repository microsoft/power-platform-skills (1,016 stars, last pushed today), licensed MIT. It adds 29 tokens to every session and 877 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