Activates and provisions a Power Pages website in a Power Platform environment via the Power Platform REST API. Use when the user wants to activate, provision, turn on, or enable a Power Pages website or portal.
日本語の概要は準備中です。原文の説明を表示しています。
Use when comparing process cohorts, departments, periods or before-and-after results under matched definitions.
インストールする前に、エージェントに与えられる指示の中身を確認できます。
Use the shared contract and filters/units. Fix the outcome definition/provenance, metric, aggregation, units, timezone and one selector S. Freeze the user's agreed baseline F, separately from current exploratory filters. Reuse metadata versions and exact typed cohort values. Use the investigation method for findings/status.
{attributeName:A,dataType:T,attributeValues:[X],isInclusive:true} to
attributeValueFilters for A's cohort value, and the same shape with Y for B.
Preserve other agreed baseline conditions; retain rework restrictions only if part of that
baseline. Do not leak an exploratory/outcome-only subset into a full-population comparison.
Change only the intended cohort condition. If values are unknown, request
get_attribute_values_v2 {S,attributeName:A,itemsPerPage:20,itemsToSkip:0,filterOptions:F};
it returns values, not frequencies.get_process_overall_metrics_v2 {S,filterOptions:F_A} ->
get_process_overall_metrics_v2 {S,filterOptions:F_B}.
No metrics, groupBy or aggregation parameter exists. Use the same returned metric definitions;
native CaseDuration/CaseWaitingTime are means.get_attribute_statistics {S,attributeName:A,filterOptions:F_A,itemsPerPage:5,itemsToSkip:0,metricToSortBy:"TotalDuration",sortOrder:"Descending"},
then exactly the same call with F_B. Do not treat independent top-five pages as a complete aligned population.Continue relevant value/group pages or matched follow-ups when needed, without fixed call quotas. Stop at sufficient evidence, no new information or a capability/error boundary; no blind sweeps. Do not create views or use two inclusive timeframes in one query as an A/B comparison.
For periods, change only one explicit timeframeFilters start/end pair in each copied F.
Case windows mean Contained, not cases Started/Completed/Intersecting or all events during the period.
If completed-only membership including earlier starts is essential, stop/reframe or route
to derive-metric/a user-confirmed existing matching view. Never invent a date-mode field
or promise unknown end-boundary behavior.
If refresh is reported or reproducibility is at risk, recheck details. Changed PV/PMV invalidates the pair: mark inconclusive, stop or deliberately rerun both, not just the second. Process selection resolves latest; no direct version selector or atomic comparison snapshot exists. Views pin version context but their configuration is mutable/cached.
Report A/B counts, mean metrics, absolute delta and relative change only for a nonzero baseline. Empty cohorts mean insufficient evidence, not zero duration/infinite improvement. State scope/version and unmatched-group coverage; at most five headline rows. Recorded means do not establish closure, equal maturity or complete lifecycles. Report those as unknown unless supported; qualify the comparison, not an assumed causal improvement. Retain baseline/cohort filters, evidence references, status and alternatives. Overlapping groups cannot be added as unique-case totals. Object-centric comparisons belong in analyze-objects, not case-filter fallbacks.
まだレビューはありません。使ってみた感想をお寄せください。
概要と使いどころ
Activates and provisions a Power Pages website in a Power Platform environment via the Power Platform REST API. Use when the user wants to activate, provision, turn on, or enable a Power Pages website or portal.
日本語の概要は準備中です。原文の説明を表示しています。
Integrates Power Pages generative-AI summarization APIs (PREVIEW) into a Single Page Application (SPA) site — the Search Summary API and the Data Summarization API — on any record-detail or list page. Generates per-target service code (CSRF-handled) and AI site settings; delegates Web API settings, table permissions, and web roles to `/integrate-webapi` and `/create-webroles`. Use whenever a user wants AI/Copilot output that condenses Dataverse content on a Power Pages site — an AI summary, AI-generated overview or "key insights" across a record or list, a search-results summary, a case/incident summary, or recommendation-chip refinement — even when phrased as "AI-generated paragraph", "insights", or "overview". Do NOT use for: generative pages in model-driven apps (use the model-apps `genpage` skill), Copilot Studio agents/chatbots, summarizing documents or PDFs, Power BI dashboards, plain keyword search with no AI summary, or plain Dataverse CRUD (use `/integrate-webapi`).
日本語の概要は準備中です。原文の説明を表示しています。
Adds Azure DevOps connector to a Power Apps code app. Use when querying work items, creating bugs, managing pipelines, or making ADO API calls.
日本語の概要は準備中です。原文の説明を表示しています。
Internal implementation skill invoked by /add-native for camera, image picker, barcode scanner, QR scanner, and camera/gallery Dataverse artifact workflows.
日本語の概要は準備中です。原文の説明を表示しています。
Integrates Power Automate cloud flows into a Power Pages site. Lists available flows, suggests relevant ones based on intent, identifies scenarios and web roles, creates metadata files, and generates client-side code to call flows. Handles both new flow registration and adding already-registered flows to additional pages without re-creating metadata. Use when the user wants to add, connect, register, or link a Power Automate cloud flow to their site.
日本語の概要は準備中です。原文の説明を表示しています。
Adds any Power Platform connector to a Power Apps code app. Generic fallback for connectors not covered by a specific skill.
日本語の概要は準備中です。原文の説明を表示しています。