上記に当てはまらないスキル（1.5万 件）
High-performance C JSON parsing, creation, and modification with yyjson. Use when working with yyjson documents, string copy-vs-borrow ownership, dangling c_str() bugs, yyjson_alc allocators, or writer output freeing.
日本語の概要は準備中です。原文の説明を表示しています。
clangd LSP over HTTP for C++ syntax checks and symbol navigation in LuisaCompute sources.
日本語の概要は準備中です。原文の説明を表示しています。
C++ naming, formatting, static analysis, and RTTI rules for LuisaCompute.
日本語の概要は準備中です。原文の説明を表示しています。
SPIRV-Tools optimizer pass development, IR manipulation, PassTest registration, and LuisaCompute spvtools::Optimizer integration (presets, LUISA_SPIRV_OPT_* env knobs).
日本語の概要は準備中です。原文の説明を表示しています。
Optimize LuisaCompute DSL kernels using warp/wave primitives, shared-memory aggregation, block-level collectives, thread-group (block) size / occupancy tuning, and C++ branch-prediction hints (`[[likely]]`/`[[unlikely]]`). Use when kernels bottleneck on atomics, reductions, inter-thread communication, or poor occupancy.
日本語の概要は準備中です。原文の説明を表示しています。
Manual AST construction with FunctionBuilder for kernels and callables without DSL sugar.
日本語の概要は準備中です。原文の説明を表示しています。
Enable, disable, or check usage telemetry transmission for Power Apps Mobile Extension skills. Use for 'turn off telemetry', 'opt out', 'enable telemetry', or 'telemetry status'. Opt-out stops transmission only; local diagnostic logs continue when the plugin is enabled.
日本語の概要は準備中です。原文の説明を表示しています。
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 a requested measure is missing, a saved custom metric needs reuse, or an ephemeral formula or derived scalar is needed.
日本語の概要は準備中です。原文の説明を表示しています。
Use when the user wants a Process Intelligence bug-report draft or support summary for a failed operation.
日本語の概要は準備中です。原文の説明を表示しています。
Use when investigating common or slow variants, repeated work, unusual paths, or a specific Process Mining case.
日本語の概要は準備中です。原文の説明を表示しています。
Use when comparing process cohorts, departments, periods or before-and-after results under matched definitions.
日本語の概要は準備中です。原文の説明を表示しています。
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.
日本語の概要は準備中です。原文の説明を表示しています。
Autonomously build a complete Power Automate flow from a description. Use when you need to generate a full flow definition and create it.
日本語の概要は準備中です。原文の説明を表示しています。
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.
日本語の概要は準備中です。原文の説明を表示しています。
Guided flow creation wizard. Use when the user wants to create a new flow interactively.
日本語の概要は準備中です。原文の説明を表示しています。
Creates and configures web roles for a Power Pages SPA site. Web roles control access and permissions for site users, including authenticated and anonymous roles. Use when the user wants to create, add, set up, or manage web roles for their site. Also supports PAC-downloaded non-SPA sites with nested or directly opened metadata roots.
日本語の概要は準備中です。原文の説明を表示しています。
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".
日本語の概要は準備中です。原文の説明を表示しています。
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).
日本語の概要は準備中です。原文の説明を表示しています。
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.
日本語の概要は準備中です。原文の説明を表示しています。
Browse Power Automate environments and flows interactively. Use when the user wants to browse, list, or explore their flows and environments.
日本語の概要は準備中です。原文の説明を表示しています。