[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M699WP9SDG5ZR12P8VYNXKTN":3,"skill-same:01M699WP9SDG5ZR12P8VYNXKTN":59},{"skillNo":4,"name":5,"nameZh":6,"description":7,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":16,"categories":17,"keywords":18,"publishedAt":29,"linkOnly":30,"markdownContent":31,"markdownBody":32,"frontMatter":33,"refName":35,"commitSha":36,"skillDirectory":37,"forksCount":38,"repositoryHtmlUrl":39,"repositoryHomepageUrl":40,"ownerHtmlUrl":41,"ownerBlogUrl":42,"ownerDescription":43,"updatedAt":44,"install":45,"resources":58},"01M699WP9SDG5ZR12P8VYNXKTN","derive-metric",null,"Use when a requested measure is missing, a saved custom metric needs reuse, or an ephemeral formula or derived scalar is needed.","microsoft\u002Fpower-platform-skills","microsoft","https:\u002F\u002Favatars.githubusercontent.com\u002Fu\u002F6154722?v=4","01M698VYDXZ6JW5WH3CRV650R8","Microsoft","01M699JVYJFB75D9JM70BN4H0Q",1149,"MIT","https:\u002F\u002Fgithub.com\u002Fmicrosoft\u002Fpower-platform-skills\u002Fblob\u002Fmain\u002Fplugins\u002Fprocess-intelligence\u002Fskills\u002Fderive-metric\u002FSKILL.md",[],[19,20,21,22,23,24,25,26,27,28],"derive metric","metric","read","use","formula","missing","reuse","saved","custom","when","2026-11-10 10:12:30",false,"---\nname: derive-metric\ndescription: Use when a requested measure is missing, a saved custom metric needs reuse, or an ephemeral formula or derived scalar is needed.\nallowed-tools: Read, AskUserQuestion\n---\n\n# Resolve a metric gap without saving definitions\n\nUse the [shared contract](..\u002F..\u002Freferences\u002Fanalysis-contract.md) and\n[filters\u002Funits](..\u002F..\u002Freferences\u002Ffilters-and-units.md). Follow this order; stop at the first sufficient option.\n\nFor a business-derived measure, confirm case\u002Fevent entity, outcome definition\u002Fprovenance,\nunits, time basis and aggregation. Are amounts incremental transactions or cumulative snapshots?\nNever assume sum, latest or maximum: nonmonotonic snapshots require authoritative ordering and\nrefund\u002Fcorrection semantics. Missing definitions mean **inconclusive**; ask before computing.\nDo not infer formula grammar from an example name or business description.\n\n1. **Native output first.** Use the existing metric and its correct scope\u002Faggregation.\n   For cases over one day append\n   `{metric:\"CaseDuration\",comparisonOperator:\"GreaterThan\",values:[\"1.00:00:00\"],isInclusive:true}`\n   to F's `caseMetricConditionFilters`, then\n   `get_cases_with_metrics_v2 {S,filterOptions:Fplus,itemsPerPage:5,itemsToSkip:0}`.\n   No formula is needed for ordinary duration\u002Fwaiting\u002Fcounts; use native grouped statistics\n   instead of summing a truncated cases page.\n2. **Enabled saved metric.** Reuse fresh details' `CustomMetrics` ID\u002Fname\u002Ftype\u002FdataType.\n   Details is not a generic metric catalog and contains no saved formula text.\n   Match Case\u002FEvent\u002FEdge scope and scalar type. For a Boolean Case metric C append\n   `{metric:\"CustomMetric\",customMetricId:C,comparisonOperator:\"EqualTo\",values:[true],isInclusive:true}`\n   to `caseMetricConditionFilters`; query `get_process_overall_metrics_v2 {S,filterOptions:Fplus}`\n   for a count. An ID filter needs no formula validation.\n   A saved-name output expression, e.g. synthetic `EscalatedCase()`, **does** require\n   the validation\u002Fcolumn path below; do not guess escaping or missing dependencies.\n3. **Exact local scalar.** Reuse complete, definition-compatible, same-scope totals with a nonzero\n   denominator. Label the result derived, not saved. Never average averages or use overlapping\n   groups\u002Ftop-N samples as population totals.\n4. **Ephemeral formula only if necessary.** Load [formula execution](..\u002F..\u002Freferences\u002Fformulas.md).\n   Reuse PV\u002FPMV from current details, not process\u002Fview IDs; refresh when stale.\n   Fetch needed targeted reference pages without a lookup quota; then validate:\n   `validate_custom_metric_formula {processVersionId:PV,processExtendedMetadataVersionId:PMV,formula:Fexpr}`.\n   For a candidate and its repairs, allow **three validation attempts total**, not endless retries.\n   Repair only from structured errors\u002Fdefinitions; stop early on an unavailable prerequisite.\n   Require `isValid:true`, a compatible `dataType` and the **exact target context in types**.\n   Validation alone neither executes nor saves anything.\n5. Execute the smallest matching filter\u002Fquery or default page-five column query.\n   For cases: `get_cases_with_metrics_v2 {S,filterOptions:F,itemsPerPage:5,itemsToSkip:0,formulaMetricInput:{name:N,formula:Fexpr}}`.\n   N must not collide with returned built-ins. Never invent `computedColumns` or `metrics`.\n\nContinue necessary pages or distinct evidence queries without ordinary-call or total-row quotas.\nReuse completed results; stop when answered or no new evidence is available.\nMissing validator forbids unvalidated execution even if the output field is advertised.\nColumn and formula-filter capabilities are independent; stop after an explicit gate rejection.\nNo create\u002Fsave metric tool exists. If a prerequisite cannot be inlined, explain creation\u002Fenablement\noutside MCP, then refresh metadata and revalidate after the user's action.\n\nReport definition\u002Fformula, units\u002Fcontext, validation state, at most five headline rows and **ephemeral\u002Fnot saved**.\nRetain definition provenance and scoped evidence\u002Fstatus using the [investigation method](..\u002F..\u002Freferences\u002Finvestigation-method.md).\n","# Resolve a metric gap without saving definitions\n\nUse the [shared contract](..\u002F..\u002Freferences\u002Fanalysis-contract.md) and\n[filters\u002Funits](..\u002F..\u002Freferences\u002Ffilters-and-units.md). Follow this order; stop at the first sufficient option.\n\nFor a business-derived measure, confirm case\u002Fevent entity, outcome definition\u002Fprovenance,\nunits, time basis and aggregation. Are amounts incremental transactions or cumulative snapshots?\nNever assume sum, latest or maximum: nonmonotonic snapshots require authoritative ordering and\nrefund\u002Fcorrection semantics. Missing definitions mean **inconclusive**; ask before computing.\nDo not infer formula grammar from an example name or business description.\n\n1. **Native output first.** Use the existing metric and its correct scope\u002Faggregation.\n   For cases over one day append\n   `{metric:\"CaseDuration\",comparisonOperator:\"GreaterThan\",values:[\"1.00:00:00\"],isInclusive:true}`\n   to F's `caseMetricConditionFilters`, then\n   `get_cases_with_metrics_v2 {S,filterOptions:Fplus,itemsPerPage:5,itemsToSkip:0}`.\n   No formula is needed for ordinary duration\u002Fwaiting\u002Fcounts; use native grouped statistics\n   instead of summing a truncated cases page.\n2. **Enabled saved metric.** Reuse fresh details' `CustomMetrics` ID\u002Fname\u002Ftype\u002FdataType.\n   Details is not a generic metric catalog and contains no saved formula text.\n   Match Case\u002FEvent\u002FEdge scope and scalar type. For a Boolean Case metric C append\n   `{metric:\"CustomMetric\",customMetricId:C,comparisonOperator:\"EqualTo\",values:[true],isInclusive:true}`\n   to `caseMetricConditionFilters`; query `get_process_overall_metrics_v2 {S,filterOptions:Fplus}`\n   for a count. An ID filter needs no formula validation.\n   A saved-name output expression, e.g. synthetic `EscalatedCase()`, **does** require\n   the validation\u002Fcolumn path below; do not guess escaping or missing dependencies.\n3. **Exact local scalar.** Reuse complete, definition-compatible, same-scope totals with a nonzero\n   denominator. Label the result derived, not saved. Never average averages or use overlapping\n   groups\u002Ftop-N samples as population totals.\n4. **Ephemeral formula only if necessary.** Load [formula execution](..\u002F..\u002Freferences\u002Fformulas.md).\n   Reuse PV\u002FPMV from current details, not process\u002Fview IDs; refresh when stale.\n   Fetch needed targeted reference pages without a lookup quota; then validate:\n   `validate_custom_metric_formula {processVersionId:PV,processExtendedMetadataVersionId:PMV,formula:Fexpr}`.\n   For a candidate and its repairs, allow **three validation attempts total**, not endless retries.\n   Repair only from structured errors\u002Fdefinitions; stop early on an unavailable prerequisite.\n   Require `isValid:true`, a compatible `dataType` and the **exact target context in types**.\n   Validation alone neither executes nor saves anything.\n5. Execute the smallest matching filter\u002Fquery or default page-five column query.\n   For cases: `get_cases_with_metrics_v2 {S,filterOptions:F,itemsPerPage:5,itemsToSkip:0,formulaMetricInput:{name:N,formula:Fexpr}}`.\n   N must not collide with returned built-ins. Never invent `computedColumns` or `metrics`.\n\nContinue necessary pages or distinct evidence queries without ordinary-call or total-row quotas.\nReuse completed results; stop when answered or no new evidence is available.\nMissing validator forbids unvalidated execution even if the output field is advertised.\nColumn and formula-filter capabilities are independent; stop after an explicit gate rejection.\nNo create\u002Fsave metric tool exists. If a prerequisite cannot be inlined, explain creation\u002Fenablement\noutside MCP, then refresh metadata and revalidate after the user's action.\n\nReport definition\u002Fformula, units\u002Fcontext, validation state, at most five headline rows and **ephemeral\u002Fnot saved**.\nRetain definition provenance and scoped evidence\u002Fstatus using the [investigation method](..\u002F..\u002Freferences\u002Finvestigation-method.md).\n",{"name":5,"description":7,"allowed-tools":34},"Read, AskUserQuestion","main","0a55a88fa2855404029d1e5450faf92878baf763","plugins\u002Fprocess-intelligence\u002Fskills\u002Fderive-metric",232,"https:\u002F\u002Fgithub.com\u002Fmicrosoft\u002Fpower-platform-skills","https:\u002F\u002Fmicrosoft.github.io\u002Fpower-platform-skills\u002F","https:\u002F\u002Fgithub.com\u002Fmicrosoft","https:\u002F\u002Fopensource.microsoft.com","Open source projects and samples from Microsoft","2026-11-14 21:46:39",{"source":8,"skillName":5,"commands":46,"prompt":56,"zipAvailable":57},[47,50,53],{"tool":48,"command":49},"npx","npx skills add microsoft\u002Fpower-platform-skills --skill derive-metric",{"tool":51,"command":52},"bunx","bunx skills add microsoft\u002Fpower-platform-skills --skill derive-metric",{"tool":54,"command":55},"pnpm","pnpm dlx skills add microsoft\u002Fpower-platform-skills --skill derive-metric","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002Fmicrosoft\u002Fpower-platform-skills\u002Fblob\u002Fmain\u002Fplugins\u002Fprocess-intelligence\u002Fskills\u002Fderive-metric\u002FSKILL.md",true,[],[60,68,87,110,128,138],{"skillNo":61,"name":62,"nameZh":6,"description":63,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":64,"categories":65,"keywords":66,"publishedAt":67},"01M78JN2BFRRV1J54Q6WKZQ08D","compare-site-configurations","Compare Power Pages site configurations between two environments, such as dev, test and production, or between a local download and the live site, and explain which differences change site behavior. Use when a site works in one environment but not another (for example, works in dev but fails in test), to check configuration drift before promoting or deploying, or to see what changed between two sites. Produces a shareable HTML report and a JSON file that VS Code can import.","https:\u002F\u002Fgithub.com\u002Fmicrosoft\u002Fpower-platform-skills\u002Fblob\u002Fmain\u002Fplugins\u002Fpower-pages\u002Fskills\u002Fcompare-site-configurations\u002FSKILL.md",[],[],"2026-11-15 14:19:17",{"skillNo":69,"name":70,"nameZh":6,"description":71,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":72,"categories":73,"keywords":74,"publishedAt":29},"01M699WVHX0XN59EPBTTPEKYPG","setup","Use when Process Intelligence needs building, explicit cloud\u002Faccount\u002Fenvironment configuration, sign-in, connection diagnostics, or recovery from an authentication error.","https:\u002F\u002Fgithub.com\u002Fmicrosoft\u002Fpower-platform-skills\u002Fblob\u002Fmain\u002Fplugins\u002Fprocess-intelligence\u002Fskills\u002Fsetup\u002FSKILL.md",[],[70,28,75,76,77,78,79,80,81,82,22,83,84,21,85,86],"sign","diagnostics","configuration","cloud","connection","error","environment","authentication","Bash","intelligence","recovery","process",{"skillNo":88,"name":89,"nameZh":6,"description":90,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":91,"categories":92,"keywords":98,"publishedAt":29},"01M699WSR9EX55YY1WD9J22FEG","report-issue","Use when the user wants a Process Intelligence bug-report draft or support summary for a failed operation.","https:\u002F\u002Fgithub.com\u002Fmicrosoft\u002Fpower-platform-skills\u002Fblob\u002Fmain\u002Fplugins\u002Fprocess-intelligence\u002Fskills\u002Freport-issue\u002FSKILL.md",[93],{"categoryNo":94,"categoryName":95,"taxonomyType":96,"taxonomyTypeDesc":97},"01JBSEEDCAT000000000000034","行政与办公人员","PROFESSION","适用职业",[99,100,101,102,103,104,22,28,105,106,86,107,84,108,109],"report","issue","report issue","user","for","bug-report","operation","draft","bug","summary","support",{"skillNo":111,"name":112,"nameZh":6,"description":113,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":114,"categories":115,"keywords":116,"publishedAt":29},"01M699WR26YQ9Q21KE6MJF5B2G","investigate-process","Use when a broad Process Mining business question, observed pattern or competing explanation needs investigation across analytical perspectives.","https:\u002F\u002Fgithub.com\u002Fmicrosoft\u002Fpower-platform-skills\u002Fblob\u002Fmain\u002Fplugins\u002Fprocess-intelligence\u002Fskills\u002Finvestigate-process\u002FSKILL.md",[],[86,117,118,119,22,120,121,28,122,123,124,21,125,126,127],"investigate","investigate process","question","process mining","business","across","perspectives","mining","pattern","investigation","analytical",{"skillNo":129,"name":130,"nameZh":6,"description":131,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":132,"categories":133,"keywords":134,"publishedAt":29},"01M699WMG5R8P6SMTDAS1TKF9E","compare-cohorts","Use when comparing process cohorts, departments, periods or before-and-after results under matched definitions.","https:\u002F\u002Fgithub.com\u002Fmicrosoft\u002Fpower-platform-skills\u002Fblob\u002Fmain\u002Fplugins\u002Fprocess-intelligence\u002Fskills\u002Fcompare-cohorts\u002FSKILL.md",[],[135,136,86,22,28,137,21],"compare","compare cohorts","results",{"skillNo":139,"name":140,"nameZh":6,"description":141,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":142,"categories":143,"keywords":144,"publishedAt":29},"01M699WJWNVTMP9XK3NCJHV14D","analyze-variants","Use when investigating common or slow variants, repeated work, unusual paths, or a specific Process Mining case.","https:\u002F\u002Fgithub.com\u002Fmicrosoft\u002Fpower-platform-skills\u002Fblob\u002Fmain\u002Fplugins\u002Fprocess-intelligence\u002Fskills\u002Fanalyze-variants\u002FSKILL.md",[],[145,146,147,22,120,28,148,149,150,124,86,21,151],"variants","analyze","analyze variants","common","case","work","paths"]