Use when a requested measure is missing, a saved custom metric needs reuse, or an ephemeral formula or derived scalar is needed.
日本語の概要は準備中です。原文の説明を表示しています。
上記に当てはまらないスキル(1.5万 件)
Use when a requested measure is missing, a saved custom metric needs reuse, or an ephemeral formula or derived scalar is needed.
日本語の概要は準備中です。原文の説明を表示しています。
Use when seeking explanatory attributes or hypotheses for differences in process duration, waiting, utilization or rework.
日本語の概要は準備中です。原文の説明を表示しています。
Use when investigating slow activities, waiting, handoff duration, bottlenecks or cumulative activity workload.
日本語の概要は準備中です。原文の説明を表示しています。
Use when the user wants a Process Intelligence bug-report draft or support summary for a failed operation.
日本語の概要は準備中です。原文の説明を表示しています。
Use when analyzing interacting object types, object-centric processes, leading-object executions or cross-object delay.
日本語の概要は準備中です。原文の説明を表示しています。
Internal implementation skill invoked by /add-native for native background GPS tracking with durable storage and Dataverse sync using @microsoft/power-apps-native-bglocation.
日本語の概要は準備中です。原文の説明を表示しています。
Browse Power Automate environments and flows interactively. Use when the user wants to browse, list, or explore their flows and environments.
日本語の概要は準備中です。原文の説明を表示しています。
Assemble the final `.ppmplugin` binary bundle for a PAM native extension and verify its contents. First **reconciles** the manifest's declared `entrypoints` against the binaries actually staged — if the manifest declares a platform with no built binary it gates (build it / ship without it / stop) rather than shipping a broken bundle. Then re-runs the plugin's upload-compatibility checks on the reconciled manifest, zips the manifest plus whichever of `android/<PascalName>Plugin.dex` and `ios/<PascalName>Plugin.framework/` are present into `ppmplugin/<name>.ppmplugin`, and verifies the archive layout with `jar tf` (exactly the manifest + the shipped binaries — nothing missing, nothing extra). Output: a statically verified `.ppmplugin` file on disk. Prereqs: `jar` (JDK). Run after /generate-ppmplugin-manifest and the build skill(s).
日本語の概要は準備中です。原文の説明を表示しています。
Deep autonomous diagnosis of a failed flow run. Provide environment, flow, and run IDs. Use when the user asks to diagnose or deeply investigate a specific failed flow run.
日本語の概要は準備中です。原文の説明を表示しています。
Inspects and configures the web application firewall (WAF) in front of a Power Pages production site. Lists the current state, recommends enabling protection when it is off, and walks the user through adding, updating, or removing custom rules — IP blocks, country blocks, path blocks, and rate limits. Use when the user wants to turn on WAF, block traffic by IP or country, rate-limit login or signup pages, protect pages from brute-force attempts, restrict access to specific paths, review the current firewall configuration, or asks "is my site protected against bots / common web attacks?" — even if they say "add rate limit" or "protect login page" without mentioning "firewall" or "WAF".
日本語の概要は準備中です。原文の説明を表示しています。
Validate, reconcile to the chosen target(s), and stage the `manifest.json` for a `.ppmplugin` bundle. In the normal flow the committed `./manifest.json` already exists (authored by /generate-native-extension), so this stage reads it, runs the plugin's upload-compatibility checks locally as a pre-flight gate (name regex, canonical prefix, known incompatible names, method and identifier shapes), reconciles `entrypoints` down to the platform(s) you ship, and writes the gitignored staged copy `ppmplugin/staging/manifest.json` that /assemble-ppmplugin zips. If no committed manifest exists (a hand-authored module) it falls back to deriving every field from the class name and Android module source, writing both the committed file and the staged copy. No toolchain — pure read, validate, write. Target-aware. Run after the native module exists, before the build skills.
日本語の概要は準備中です。原文の説明を表示しています。
Check Power Platform environment routing status and understand default environment resolution. Use when the user asks about environment routing, developer environments, or new maker landing. Routing is configured in the admin center, not here. NOT for listing flows or managing connections.
日本語の概要は準備中です。原文の説明を表示しています。
Manage and run Power Automate Desktop (RPA) flows and machine groups. Use when the user asks about desktop flows, RPA, or machine groups.
日本語の概要は準備中です。原文の説明を表示しています。
Guided flow creation wizard. Use when the user wants to create a new flow interactively.
日本語の概要は準備中です。原文の説明を表示しています。
Autonomously build a complete Power Automate flow from a description. Use when you need to generate a full flow definition and create it.
日本語の概要は準備中です。原文の説明を表示しています。
Use when the user wants to preview generated screens in a browser without starting Metro / a simulator — for example after /create-mobile-app finishes or after /edit-app regenerates a screen.
日本語の概要は準備中です。原文の説明を表示しています。
Use when the user wants to read or write SharePoint lists, manage documents in a SharePoint document library, or create a new SharePoint list from a Power Apps mobile app.
日本語の概要は準備中です。原文の説明を表示しています。
Use when the user wants to discover and verify available Entra ID app registrations, wire one to a Power Apps Wrap mobile app, or create one through the Wrap page and update auth.config.json.
日本語の概要は準備中です。原文の説明を表示しています。
Use when the user wants to estimate the download size + sync frequency cost of an offline profile BEFORE pushing to users. Read-only. Wraps verify-offline-profile.js with per-table row-count estimates.
日本語の概要は準備中です。原文の説明を表示しています。
Use when the user needs to bind users or teams to a Mobile Offline Profile so they actually receive offline sync on their devices. Without this, the profile exists in Dataverse but no one's app uses it.
日本語の概要は準備中です。原文の説明を表示しています。
Use when the user wants to open the Power Apps Wrap page for an app ID in the active environment.
日本語の概要は準備中です。原文の説明を表示しています。
Use when the user wants to report a bug, file an issue, submit a bug report, or report any problem with the mobile-app plugin.
日本語の概要は準備中です。原文の説明を表示しています。
在 FanBox 终端里指挥兄弟终端窗口(列出/读取/发指令/新开/等待),以及设定时任务(每天/每周/固定时间/cron 自动开窗跑 agent)。用户说「开个窗口跑 X」「让 N 号窗口执行…」「每天 X 点自动…」「定时/定期跑…」时使用。仅当 FANBOX_CTL 环境变量存在时可用。
日本語の概要は準備中です。原文の説明を表示しています。
Only to be triggered by explicit super-swarm-spark commands.
日本語の概要は準備中です。原文の説明を表示しています。