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 seeking explanatory attributes or hypotheses for differences in process duration, waiting, utilization or rework.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
설치 방법 보기설치하기 전에 에이전트에게 전달되는 지시 내용을 확인할 수 있습니다.
Use the shared contract and filter/unit reference. Reuse metadata and frozen baseline scope; choose a specific defined outcome and relevant case-level attributes from the user's context, without a candidate quota. If none is known, ask; do not sweep. State a testable hypothesis, possible competing explanation and what would distinguish them. Load the investigation method for evidence/status tracking. For utilization, first check timestamp imports and the zero-duration convention in the unit reference. A cohort-mix convention is not resource efficiency or measured productive time.
Check A's metadata level before correlation. Reuse a cached signal instead of repeating it.
get_correlation_v2 {S,attributeName:A,influenceFormula:I,sortOrder:"Descending",filterOptions:F}.
| Outcome | I |
|---|---|
| Duration / waiting / active time | DurationInfluence / WaitingTimeInfluence / ActiveTimeInfluence |
| Utilization / event count | CaseUtilizationInfluence / EventCountInfluence |
| Rework / loops / self-loops | ReworkCountInfluence / LoopCountInfluence / SelfloopCountInfluence |
Use the advertised enum and exact spelling. There are no itemsPerPage, itemsToSkip,
top, metrics or limit arguments. The service ranks at most 20 groups.
Only if prevalence or mean evidence is needed and statistics is advertised:
get_attribute_statistics {S,attributeName:A,filterOptions:F,itemsPerPage:5,itemsToSkip:0,metricToSortBy:"CaseFrequency",sortOrder:"Descending"}.
Match returned values explicitly. Influence-ranked groups may differ from
frequency-ranked groups; an absent match is unknown, not zero.
For a remaining hypothesis, use a discriminating matched comparison via compare-cohorts, focused statistics/cases, or another relevant candidate. Derive each test from frozen F, never an outcome-only exploratory subset. A cached signal can go directly to its test. Continue needed checks/pages without fixed analytical-call or candidate quotas. If matched evidence contradicts the proposed direction, mark it contradicted within that scope; do not privilege the earlier influence score or claim it proves a cause.
An event-level Resource cannot be sent to correlation. If useful and advertised, use the statistics call above for that attribute, but describe grouped event duration/frequencies, not case-duration drivers. Otherwise ask for a case-level candidate or report the capability gap. Do not silently substitute a different causal analysis.
Influence is a prevalence-weighted descriptive score, not Pearson correlation, significance, causal effect or confidence. Its formula already scales by 100; do not multiply again. Return at most five useful signals with available counts/means, units, scope and partial coverage. Label explanations as hypotheses, note selection/confounding, and state one falsifiable evidence check. Record tested versus merely observed claims, alternatives and missing evidence; revise or stop when the next check cannot discriminate. No assumed outcome maturity or closure. Stop when no discriminating evidence remains; do not paginate correlations or invent sample sizes.
아직 리뷰가 없습니다. 사용해 본 소감을 남겨 주세요.
로그인 없이 쓸 수 있습니다. 사용 후기, 질문, 작동하지 않은 환경 등을 편하게 남겨 주세요.
아직 댓글이 없습니다. 첫 댓글을 남겨 보세요.
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.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Use when adding a Power Platform connector to an Expo/React Native Power Apps mobile app and no dedicated mobile connector skill exists.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.