with one click
Power-App-Dataverse-Codex-Plugin
Power-App-Dataverse-Codex-Plugin contains 24 collected skills from rweisssieker-xp, with repository-level occupation coverage and site-owned skill detail pages.
Skills in this repository
Use when the user wants to inspect or operate a real Microsoft Dataverse environment through the plugin MCP server with OAuth2 client credentials. Supports metadata, query, retrieve, create, update, delete, action execution, and simulation tools.
Use when applying the monetizable enterprise USP pack for Dataverse and Power Platform: compliance evidence automation, ROI and process value scoring, autonomous remediation playbooks, tenant-specific AI skill generation, governed cross-tenant rollout, business capability mapping, trust scoring for AI actions, autonomous exception management, enterprise change impact AI, and AI-controlled operating cadence.
Use when applying the advanced AI USP expansion for Dataverse and Power Platform: organizational cognitive graph, autonomous reasoning, self-optimization, process discovery, semantic search, predictive intelligence, decision simulation, digital twin, generated business processes, autonomous governance, enterprise memory, data stewardship, personalized UX, natural-language enterprise programming, runtime security, continuous learning, executive intelligence, cross-system cognition, autonomous agents, and intent-driven enterprise computing.
Use when designing extensible Dataverse action packs, AI skills, workflow agents, industry modules, or reusable Dataverse skills. Produces marketplace architecture guidance only.
Use when planning dynamic task-specific forms, dashboards, tables, wizards, approval dialogs, or input masks generated for Dataverse and Power Apps scenarios. Produces UI plans only and generates no live UI.
Use when designing organizational memory for Dataverse AI actions, including user behavior, processes, preferences, common actions, approval patterns, and company language. Produces memory design guidance only.
Use when designing Dataverse AI behavior that adapts to user role, department, permissions, language, preferences, data context, relationships, business logic, policies, and organizational rules. Produces design guidance only and performs no live tenant inspection.
Use when designing a dialog-first ERP or CRM operating layer over Dataverse, Dynamics, or Power Platform apps. Produces architecture and interaction guidance only; it does not replace or control live applications.
Use when designing zero-technical-knowledge Dataverse AI experiences where users do not need table, form, flow, or solution knowledge. Produces UX guidance only.
Use when designing explanations for Dataverse AI actions, including why an action is recommended, what data was used, which rules applied, dependencies, and expected impact. Produces explanation guidance only.
Use when shaping the long-term vision of Dataverse as a semantic enterprise graph, AI operating system, and enterprise memory layer moving from app-centric software to intent-centric enterprise control. Produces strategy guidance only.
Use when designing specialized Dataverse AI agents for sales, operations, compliance, data stewardship, ALM, or other enterprise action domains. Produces an operating model only and does not run agents.
Use when designing proactive Dataverse recommendations such as churn risk, follow-up needs, API limit risks, compliance violations, pipeline risk, or next-best actions. Produces analysis design only.
Use when expressing the PRD's core USP: not AI for Power Apps, but a conversational enterprise execution platform that abstracts UI, processes, systems, and data models into intent, language, AI orchestration, and autonomous execution. Produces messaging guidance only.
Use when positioning the Dataverse AI Action Platform against classic Power Apps, Copilot-style assistance, or app-centric software. Produces strategy, USP, and messaging guidance only.
Use when designing the central runtime concept that interprets natural language, business intent, context, roles, and history into Dataverse operations, Power Automate flows, APIs, plugins, business processes, and multi-step workflows. Produces architecture guidance only.
Use when designing a global natural-language command bar for Dataverse, Dynamics, Power Apps, or Power Platform actions. Produces command taxonomy and UX guidance only.
Use when designing voice-first Dataverse and Power Platform operations for mobile, Teams calls, headsets, or Copilot-style interfaces. Produces interaction and safety guidance only.
Use when reviewing Dataverse AI actions for permissions, policy validation, risk assessment, approval routing, auditability, and explainability. Produces governance guidance only; it does not enforce policies in a live tenant.
Use when reviewing Power Apps, Dataverse, Dynamics, or Power Platform solution readiness for ALM, dependencies, environment variables, connection references, flows, security, and deployment planning. Produces review guidance only.
Use when a user wants to turn a business request into a Dataverse or Power Platform AI action design. Produces guidance, action plans, checks, and implementation prompts only; it does not connect to or execute against live Dataverse.
Use when planning Dataverse data quality, duplicate detection, ownership repair, migration, classification, normalization, or bulk data operations. Produces safe operation plans only and performs no data changes.
Use when mapping a natural-language Dataverse or Power Apps request to CRUD, workflow, approval, reporting, analysis, escalation, migration, or bulk-operation behavior. Produces plans only and performs no live execution.
Use when designing multi-step Dataverse, Dynamics, Power Apps, or Power Automate workflows controlled through natural language. Produces orchestration plans only and does not run workflows.