power-platform-standard

Centralizes authentication and environment configuration for Dataverse solution deployments.

Updated Apr 24, 2026
One-click install
npx skills add https://github.com/Kazuya0628/Quotation-Work-Automation-System --skill power-platform-standard
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: power-platform-standard
Source: https://github.com/Kazuya0628/Quotation-Work-Automation-System/tree/main/.github/skills/power-platform-standard
Command: npx skills add https://github.com/Kazuya0628/Quotation-Work-Automation-System --skill power-platform-standard

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill requires requests, python-dotenv, azure-identity, azure-core, Pillow, and includes scripts (resource) and references (resource) components.

What problem does it solve?

Centralizes authentication, environment configuration, and governance for Dataverse, Code Apps, Power Automate, and Copilot Studio into a single foundation skill.

Core Features & Use Cases

  • Provides a unified authentication workflow via a shared auth_helper.py and a standardized .env parameter set across all Power Platform phases.
  • Establishes a single SOLUTION_NAME and PUBLISHER_PREFIX convention to align deployments, with references to common docs and helpers for scalable environments.
  • Enables consistent provisioning and governance by codifying absolute rules, references, and reusable patterns for multi-skill deployments (Phase 1–3).
  • Example scenario: initialize a new solution by importing a Dataverse solution, configuring common credentials, and deploying initial components via the included scripts.

Quick Start

Create a .env with your Dataverse URL, tenant, and solution details, then run the sample scripts to verify authentication and solution provisioning.

Frequently Asked Questions about power-platform-standard

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I manage Dataverse authentication and environment configuration for Power Platform deployments?▼

Dataverse authentication and environment configuration are managed by setting standardized .env parameters and using a shared auth_helper.py to maintain consistent credentials across Power Platform deployment phases.

What is the best way to standardize solution naming conventions across Dataverse, Code Apps, and Copilot Studio?▼

Standardizing solution naming across Dataverse, Code Apps, and Copilot Studio requires establishing a unified SOLUTION_NAME and PUBLISHER_PREFIX convention to align cross-phase deployments within a single foundation.

How do I perform initial Dataverse solution provisioning and component deployment?▼

Initial Dataverse solution provisioning involves importing the solution, configuring common credentials in a .env file, and running included sample scripts to verify authentication and deploy initial components.

Does this approach support multi-phase governance for Power Automate and Copilot Studio agents?▼

Multi-phase governance for Power Automate and Copilot Studio agents is supported by codifying absolute rules, references, and reusable patterns for consistent provisioning across scalable environments.

Why do I need a shared authentication helper for Power Platform solution management?▼

A shared authentication helper is needed for Power Platform solution management to centralize cross-phase deployment workflows, ensuring consistent environment parameters and governance across all integrated components.