Use when KPIs need AI-assisted lifecycle governance across proposed, approved, certified, changed, deprecated, retired, and replaced states.
원문 언어: 영어
메뉴
이 저장소의 skills
SkillsMP는 rweisssieker-xp/PowerBi-Codex-Plugin에서 259개의 skill을 수집했습니다. skill을 열어 소스와 세부 정보를 확인하세요.
rweisssieker-xp/PowerBi-Codex-Plugin수집된 skill 259개 중 40개를 표시합니다.
Use when KPIs need AI-assisted lifecycle governance across proposed, approved, certified, changed, deprecated, retired, and replaced states.
원문 언어: 영어
Use when Power BI models have duplicated, near-duplicate, conflicting, unused, local, or uncertified DAX measures that need consolidation.
원문 언어: 영어
Use when complex Power BI delivery needs coordinated AI agents for source mapping, modelling, DAX, Power Query, UX, governance, testing, release, documentation, and adoption.
원문 언어: 영어
Use when Power BI process chains, KPIs, simulations, forecasts, events, and actions should be connected into an AI-assisted digital twin of enterprise operations.
원문 언어: 영어
Use when Power BI cockpits need AI-assisted role-based variants for CFO, COO, plant, sales, quality, supply chain, procurement, service, HR, IT, or executive users.
원문 언어: 영어
Use when Power BI reports should be assessed for retirement, consolidation, replacement, archive, or certification based on usage, ownership, overlap, risk, and business dependency.
원문 언어: 영어
Use when Power BI tests should be mined from historical edge cases, anomalies, complaints, postings, CAPAs, returns, failures, tickets, or business exceptions.
원문 언어: 영어
Use when each Power BI KPI needs AI-generated root-cause paths, drilldowns, hypotheses, driver trees, standard actions, and evidence requirements.
원문 언어: 영어
Use when Power BI planning, supply chain, finance, pricing, inventory, or capacity questions need AI-recommended what-if scenarios and decision options.
원문 언어: 영어
Use when source schema changes break or threaten Power Query, semantic models, DAX, refresh, data contracts, tests, or report visuals.
원문 언어: 영어
Use when Power BI security exposure must be analyzed across RLS, OLS, sharing, export, sensitivity labels, external guests, PII, groups, workspaces, and tenant settings.
원문 언어: 영어
Use when business self-service Power BI builders need AI guidance and guardrails for model design, DAX, sharing, exports, security, source use, and certification boundaries.
원문 언어: 영어
Use when Power BI semantic model, DAX, visuals, documentation, and validation must be checked against the approved KPI or data product contract.
원문 언어: 영어
Use when AI should identify weak Power BI semantic models, poor relationships, mixed grain, ambiguous measures, snowflaking, many-to-many risks, or refactor paths into governed star schemas.
원문 언어: 영어
Use when business terms must be mapped to Power BI source systems, tables, APIs, CDS views, fields, semantic model objects, and validation evidence.
원문 언어: 영어
Use when Power BI tenants need AI prediction of reports or datasets likely to break from refresh failures, owner gaps, gateway issues, capacity pressure, schema drift, or usage decay.
원문 언어: 영어
Use when Power BI KPI exceptions should automatically prepare Jira, ServiceNow, Planner, SAP Workflow, CRM, or operational tasks with owners, due dates, impact, and retest criteria.
원문 언어: 영어
Use when Power BI usage should automatically trigger recommendations for training, redesign, consolidation, retirement, communication, or owner follow-up.
원문 언어: 영어
Use when Power BI or Fabric capacity should automatically recommend refresh windows, aggregations, model size reduction, Direct Lake or Import choices, and load optimization.
원문 언어: 영어
Use when datasets, semantic models, reports, or data products need automated certification checks for KPI, DAX, RLS, performance, docs, owner acceptance, and release readiness.
원문 언어: 영어
Use when Power BI measures need automatically generated DAX test cases, edge cases, reconciliation checks, RLS contexts, and expected values.
원문 언어: 영어
Use when Power BI documentation should be regenerated from current models, measures, sources, RLS, lineage, report pages, quality gates, and release changes.
원문 언어: 영어
Use when CFO, COO, CEO, board, plant, sales, supply chain, or finance briefings should be automatically generated from Power BI KPIs, variances, risks, scenarios, and actions.
원문 언어: 영어
Use when new Power BI requests need automated classification into build, reuse, consolidate, reject, defer, escalate, migrate, certify, or route-to-expert paths.
원문 언어: 영어
Use when business questions or process scopes need automated KPI contracts with owner, definition, formula, grain, sources, validation, and certification path.
원문 언어: 영어
Use when Power Query/M needs automated review for folding, types, nulls, duplicates, pagination, incremental refresh, gateway, privacy, and error handling.
원문 언어: 영어
Use when Power BI refresh failures need automated classification, root-cause grouping, owner routing, fix plans, SLA impact, and communication.
원문 언어: 영어
Use when PBIP, TMDL, DAX, Power Query, semantic model, report layout, RLS, or documentation changes need automated release notes and impact summaries.
원문 언어: 영어
Use when Power BI report pages need automated UX review for visual choice, overload, drilldowns, KPI context, accessibility, actions, and misleading layouts.
원문 언어: 영어
Use when Power BI requirements are incomplete and need automated questions until KPI, source, grain, owner, RLS, audience, and target decisions are clear.
원문 언어: 영어
Use when source changes should automatically alert impacts on Power Query, semantic models, DAX, report visuals, data contracts, tests, and documentation.
원문 언어: 영어
Use when Power BI needs automated scanning for RLS, sharing, export, external guests, PII, sensitivity labels, groups, workspaces, and tenant security exposure.
원문 언어: 영어
Use when metadata, KPI contracts, or data contracts should automatically draft Power BI facts, dimensions, relationships, measures, roles, and model structure.
원문 언어: 영어
Use when Power BI, Fabric, SAP, Salesforce, SQL, Snowflake, Databricks, APIs, files, or semantic models need scheduled or repeatable metadata scans.
원문 언어: 영어
Use when Power BI tenants need automated identification of orphaned workspaces, stale reports, duplicate datasets, broken refreshes, risky sharing, and unused capacity.
원문 언어: 영어
Use when Power BI delivery needs automated UAT scenarios, expected values, source traces, owners, evidence fields, and sign-off checklists.
원문 언어: 영어
Use when Power BI reports, semantic models, data products, or migrations need UAT scenarios, expected values, owners, sign-off evidence, and acceptance criteria.
원문 언어: 영어
Use when AI-generated Power BI recommendations, insights, DAX, Power Query, KPI definitions, or process actions need auditable sources, assumptions, tests, approvals, confidence, and change history.
원문 언어: 영어
Use when a Power BI initiative needs source requirements, mandatory fields, keys, grain, history, freshness, quality thresholds, ownership, and blocking conditions generated from the business problem.
원문 언어: 영어
Use when Power BI reports, models, or dashboards need scored review rubrics for UX, semantic model, DAX, Power Query, performance, security, governance, adoption, and business value.
원문 언어: 영어