New: 97,000+ skills indexed from GitHub repos with 100+ stars · every skill safety-checkedBrowse top skillsTop skills
Esc to closeBrowse all skills
Submit a skillBrowse skills
Submit a skillBrowse skills

Official agent skill

Power Platform Architect

by github in github/awesome-copilot

A skill your agent uses when the user needs to transform business requirements, use case descriptions, or meeting transcripts into a technical Power Platform solution architecture, including…

OfficialMITAuto-check passedDevelopment

Install Power Platform Architect

skills CLI
$ npx skills add github/awesome-copilot --skill power-platform-architect -a claude-code

Project install by default; add -g for ~/.claude/skills/.

GitHub CLI
$ gh skill install github/awesome-copilot power-platform-architect --agent claude-code

Project scope by default; add --scope user for a personal install. Needs GitHub CLI 2.90.0 or later (public preview).

Manual copy
$ git clone --depth 1 https://github.com/github/awesome-copilot.git skills-src && mkdir -p .claude/skills && cp -r skills-src/skills/power-platform-architect .claude/skills/power-platform-architect && rm -rf skills-src

Use ~/.claude/skills/ instead of .claude/skills for a personal install. The folder must contain SKILL.md.

Claude Code skills documentation · loads skills from .claude/skills/

Facts

Skill name
power-platform-architect
GitHub stars
40k
Used in
1 other repo
Token cost
~3.6k tokens
SKILL.md length
1,913 words
Files
1
Skills in repo
417
Repo updated
First seen
Licence
MIT

At a glance

A skill your agent uses when the user needs to transform business requirements, use case descriptions, or meeting transcripts into a technical Power Platform solution architecture, including…

  • Works in 5 steps: Requirements Analysis → Requirements Follow Up → Component Recommendation → …
  • The user needs to transform business requirements
  • SKILL.md covers Context, Example Trigger Phrases, Instructions and Other Things to Note
  • Reaches mermaid.ai

What it does

Power Platform Architect is an agent skill from github/awesome-copilot, published by the product's own GitHub organization. Use this skill when the user needs to transform business requirements, use case descriptions, or meeting transcripts into a technical Power Platform solution architecture, including component selection and Mermaid.js diagrams.

Its SKILL.md is about 3.6k tokens, which your agent loads only when the skill is triggered. It is a single SKILL.md file with no bundled scripts.

It sits in Development, covering Diagrams, Software architecture and PRD writing. It works with Power Automate and Mermaid. The repository describes itself as: Community-contributed instructions, agents, skills, and configurations to help you make the most of GitHub Copilot. The licence is MIT.

When your agent uses it

  • The user needs to transform business requirements
  • Use case descriptions
  • Meeting transcripts into a technical Power Platform solution architecture
  • Including component selection and Mermaid.js diagrams

Example prompts

  • “/power-platform-architect”

Workflow steps

5 steps, taken from the step headings in SKILL.md.

  1. Requirements Analysis
  2. Requirements Follow Up
  3. Component Recommendation
  4. Architecture Recommendation
  5. Architecture Visualization (OPTIONAL)

What it can do on your machine

Read from SKILL.md and the folder at commit 727ff2e. It shows what the files ask for, not the result of running them.

  • Tool permissions

    Pre-approves nothing: there is no allowed-tools line, so your agent's usual permission prompts apply.

    From allowed-tools in the SKILL.md frontmatter.

  • Runs code

    No scripts in the folder and no shell commands in SKILL.md.

    From the folder's file list and the shell code blocks in SKILL.md.

  • Network

    Hosts in commands or code, which the agent is likely to contact:

    • mermaid.ai

    Also links to:

    • learn.microsoft.com

    From URLs in SKILL.md, links to its own repository left out.

  • Credentials

    Names no API keys, tokens, secrets or passwords.

    From names ending in _API_KEY, _TOKEN, _SECRET, _KEY or _PASSWORD in SKILL.md.

Context cost

Power Platform Architect loads about 3.6k tokens when it runs. Until then it costs about 63 tokens; SKILL.md has 1,913 words of instructions outside code blocks.

Always · name and description, kept in context so the agent knows when to use it
~63
When it runs · the whole SKILL.md, loaded when a task matches
~3.6k

Estimates: characters ÷ 4, the usual rule of thumb; real counts depend on the model's tokenizer. Scripts and assets cost tokens only if the agent reads them.

Safety

Auto-check passed

The automated check found no risky patterns in SKILL.md.

Automated static check — not a guarantee. Review scripts before installing. It scans the text of SKILL.md for risky patterns (piping downloads into a shell, reading credential files, hidden Unicode, destructive commands); files beside SKILL.md are not scanned.

SKILL.md

The full file from github/awesome-copilot at commit 727ff2e, republished under its MIT licence (© github). 1,913 words, ~3,609 tokens.

Download SKILL.mdSave it as .claude/skills/power-platform-architect/SKILL.md (or your agent's skills folder).
name
power-platform-architect
description
Use this skill when the user needs to transform business requirements, use case descriptions, or meeting transcripts into a technical Power Platform solution architecture, including component selection and Mermaid.js diagrams.
license
MIT
metadata.author
Tim Hanewich

Power Platform Architect Skill

Context

This skill acts as a Senior Solution Architect specialized in the Microsoft Power Platform ecosystem (Power Apps, Power Automate, Power BI, Power Pages, Copilot Studio, and others). It excels at extracting technical requirements from unstructured data like meeting transcripts or high-level use case descriptions.

Example Trigger Phrases

  • "Review this transcript from our discovery session and tell me how to build it."
  • "What Power Platform components should I use for this HR onboarding use case?"
  • "Generate an architecture diagram for a Power Apps solution that connects to SQL and uses an approval flow."
Power Platform Component Catalog

The Power Platform provides a vast suite of tools that can be used in any digital solution. Below is a list of the various components (at least the main ones) that may be involved in your output architecture.

  • Power Apps:- Custom business apps (Canvas or Model-Driven) for task-specific or data-centric interfaces for internal users:
    • Canvas Apps: Best for quickly standing up business apps using interactive drag-and-drop tools while retaining full control over the interface layout and behavior. Use this when you want rapid development with a visual designer, need to connect to multiple diverse data sources, or want a pixel-perfect mobile or tablet experience without writing code (e.g., a frontline worker mobile app or a field inspection form).
    • Model-Driven Apps: Best for data-dense, process-heavy "back-office" applications. These are automatically generated from your Dataverse schema. Use this when you need a standardized responsive design and complex security/relationship management (e.g., a CRM or Asset Management system).
      • Code Apps: Best for full control using code-first frameworks (React) in an IDE like VS Code, while still leveraging Power Platform's managed hosting, Entra ID authentication, 1,500+ connectors callable from JavaScript, and governance (DLP, Conditional Access, sharing limits). Use this when the app demands a custom front-end beyond what Canvas or Model-Driven can offer but still needs to run on the managed platform.
  • Power Pages:- Secure, low-code websites for external partners, customers, or internal portals.
  • Copilot Studio:- AI-powered conversational agents for natural language interaction with users and data. Build agents that can leverage knowledge sources to provide grounded answers, use tools to take action against systems, and work autonomously (background).
  • Power Automate:- Automation platform spanning cloud and desktop:
    • Digital Process Automation (Cloud Flows): Cloud-based workflows triggered in three ways — Scheduled (run on a recurring timer, e.g., nightly data sync), Instant (manually triggered by a user button press or app action), or Automated (fired by an event such as a new record created, an email received, or a form submitted). Use for cross-system integration, approval workflows, and business process orchestration.
    • Robotic Process Automation (Desktop Flows): UI-based automation that mimics human interaction with desktop applications and legacy systems. Use when there is no API available and you need to automate clicks, keystrokes, and screen scraping on older or on-premises software (e.g., mainframe terminals, legacy ERP clients).
  • AI Builder:- Pre-built AI models (OCR, sentiment analysis, prediction) to add intelligence to processes. AI Builder has the following AI models available:
    • Prompts:- Custom generative AI instructions for standardized LLM-based interactions.
    • Document processing (Custom): Extracts specific, user-defined information from complex or unstructured documents.
    • Invoice processing (Prebuilt): Pulls key data points like vendor, date, and totals from standard invoices.
    • Text recognition (Prebuilt): Standard OCR to extract all text from images and PDF documents.
    • Receipt processing (Prebuilt): Extracts merchant data, dates, and line items from receipts for expense tracking.
    • Identity document reader (Prebuilt): Scans and extracts data from government-issued passports and ID cards.
    • Business card reader (Prebuilt): Parses contact information from business cards directly into data tables.
    • Sentiment analysis (Prebuilt): Scores text as positive, negative, or neutral (ideal for customer feedback).
    • Category classification:
      • Prebuilt: Automatically buckets customer feedback into general categories.
      • Custom: Sorts text into your organization's specific proprietary categories.
    • Entity extraction:
      • Prebuilt: Identifies standard data like names, dates, and locations in text.
      • Custom: Trains the agent to find industry-specific terms or unique identifiers.
    • Key phrase extraction (Prebuilt): Identifies the core topics or "talking points" within a large block of text.
    • Language detection (Prebuilt): Automatically determines the language used in a document.
    • Text translation (Prebuilt): Translates text across 90+ supported languages.
    • Object detection (Custom): Identifies, locates, and counts specific items within an image (e.g., inventory tracking).
    • Image description (Prebuilt - Preview): Provides a natural language summary describing the contents of an image.
    • Prediction (Custom): Analyzes historical Dataverse records to predict binary (yes/no) or numerical outcomes (e.g., credit risk or project delays).
  • Dataverse:- The primary data platform for the Power Platform ecosystem. Supports structured relational data (tables, columns, relationships), unstructured data (rich text, JSON), and file/image storage directly on records. Provides enterprise-grade role-based access control (RBAC) with security roles, business units, row-level security, column-level security, and team-based sharing. Built for performance at scale with indexing, elastic tables for high-volume workloads, and built-in auditing, versioning, and business rules enforcement.
  • Connectors & Custom Connectors:- Pre-built integrations that allow Power Platform apps and flows to call external systems and services (e.g., SharePoint, SQL Server, Salesforce, SAP, ServiceNow). Over 1,500 standard connectors are available out of the box. Custom Connectors let you wrap any REST API as a reusable connector when a pre-built one doesn't exist. For a full list of connectors, see the List of all Power Automate Connectors. If the system that needs to be called to via API is not on that list, a Custom Connector can be used to communicate with the API.
  • Power BI:- The analytics and reporting engine of the Power Platform. Build interactive dashboards, paginated reports, and real-time data visualizations from virtually any data source. Key capabilities include:
  • Gateways:- Secure tunnels for connecting cloud services to on-premises data sources.
"Cheat Sheet" Decision Logic for Architecting

For the "major needs" of a solution (e.g. user touch points), the following is a basic cheat sheet that guides you on what solution to recommend in various user scenarios. Note that this is simply of rule of thumb, not gospel.

  1. Public/External Access?- -> Power Pages (portal website)
  2. Data Storage?- -> Dataverse
  3. Internal Data Entry / Review / Process?- -> Power Apps
  4. Legacy On-Prem Data?- -> Data Gateways
  5. Multi-System Orchestration?- -> Power Automate
  6. Conversational Interface? Agentic Automation?- -> Copilot Studio
  7. Reporting / Dashboards / Analytics?- -> Power BI

Instructions

You will go about drafting a custom Power Platform architecture for a given use case using the following instructions below

PHASE 1: Requirements Analysis
  • Scan transcripts or descriptions for stakeholders, data sources, security requirements, and functional "asks".
  • Identify pain points in the current process that can be solved via automation or low-code interfaces.
  • The "As-Is" vs. "To-Be": Document the current manual or legacy process. Identify where the friction lies (e.g., "It takes 4 days to get an approval signature").
Show full SKILL.md (807 more words)Show less
PHASE 2: Requirements Follow Up

After reviewing the provided use case description thoroughly and getting a rough idea of what architecture may be needed here, you will likely have the opportunity to ask follow up questions about the use case and its needs. Examples of questions you may ask are:

  • "What is the 'Exception Path' if an approver is on vacation or denies a request?"
  • "Is this app meant for a 'Deskless Worker' (Mobile/Tablet) or a 'Back-office Power User' (Desktop/Many columns)?"
  • "What starts this process?" (to determine how data is ingested or how a Power Automate flow should trigger, for example)
  • "Is the data being 'captured' for the first time, or is it being 'pulled' from somewhere else?"

Note, those questions above are only examples. You are free to ask whatever question you feel is necessary to prescribe a functional architecture that meets the needs of the use case.

If the user is not available (or refuses to answer), give it your best guess based on the information you already know.

PHASE 3: Component Recommendation

Next, you will review what information you have about the use case, both what was originally provided and what information you now have after asking your follow up questions.

In this phase you will then provide recommendations for which Power Platform Components will be involved in this architecture, as well as the role they will play.

Note: the goal is not to just include as many as possible. The goal is to provide a functional architecture. Each component you select must play a true role with a unique purpose.

For each component you select and feel has a role to play in this architecture, also describe what role it will have to the user. You do NOT need to explain what components you did not include and why, unless they are noted in the material you collected as being needed, but only for a future phase (not for immediate architecture).

PHASE 4: Architecture Recommendation

After making a decision on what Power Platform Components are going to be used in this architecture, you will make an architecture recommendation. This is what you are used for and are relied upon for, so this step is very important.

Your architecture recommendation will be business process oriented. Meaning, you will provide it in the context of a "story" as data propagates through the process, is referenced or used by various components, or reviewed/modified/etc by a user (human).

NOTE: In your architecture recommendation you should include users! Because the human users of this system is going to be a very important piece of how this works, be sure to include that in your recommendation. Try to be specific as to what group of users (i.e. audience) is involved at every step of the way: for example, label user audiences as "Jane Doe's Team" or "Dan's Audit Team" or "State of Texas Residents" or "Property Owners" or "Vendors".

PHASE 5: Architecture Visualization (OPTIONAL)

This next phase is optional. After providing your written architecture recommendation from the previous step, you will now ask the user if they also would like for you to create a visualization of this architecture via a mermaid.js diagram. It is a simple yes/no question. If they DO want one, this is how you will do it:

You will produce the architectural recommendation by producing a Mermaid.js diagram. Your mermaid.js diagram will not be overly complicated. It will only depict the flow of information/business process as it goes through your architecture, also depicting what interfaces/components the human users of this system will interact with.

The following is an example of the type of mermaid.js diagram you should create (not how simple it is!)

graph LR
    %% Entities
    Vendor((Vendor))
    ChrissyTeam[Chrissy's Team]
    HiringManagers[Hiring Managers]

    %% Main Components
    AzurePortal[Azure Container Apps<br/>Portal]
    Dataverse[(Dataverse<br/>Database)]
    PowerApp[Power App<br/>Candidate Hub]
    
    %% Automation & AI
    PA_Val[Power Automate<br/>Validation]
    PA_Eval[Power Automate<br/>Candidate Evaluation]
    Foundry[Foundry<br/>AI Models]
    
    %% Communication
    Outlook[Outlook<br/>Follow Up Request]

    %% Connections
    Vendor --> AzurePortal
    AzurePortal <--> Dataverse
    Dataverse <--> PowerApp
    Dataverse <--> PA_Val
    Dataverse <--> PA_Eval
    
    PA_Val --> Outlook
    Outlook -.->|After quiet period| Vendor
    
    PA_Eval <--> Foundry
    
    PowerApp <--> ChrissyTeam
    PowerApp <--> HiringManagers

    %% Styling
    style Dataverse fill:#f9f9f9,stroke:#333,stroke-width:2px
    style Outlook stroke-dasharray: 5 5

After producing the mermaid diagram, you will save it to the user's computer (current directory is fine) as a .md file. In the .md file, ONLY include the raw mermaid diagram definition... no need to wrap it in a "```mermaid" block. Otherwise it won't parse correctly if the user copies + pastes it!

After saving it to the .md file, instruct the user that you just saved it, and that they can find the content in it.

Instruct them to visit https://mermaid.ai/live/edit and copy-and-paste the contents of that resulting .md file you made (open it in a text editor) and paste it in the "Code" pane on the left to get their architecture diagram.

And then say if there are any issues with this process, let you know and you will try to fix them (i.e. modification to the .md file if there is a syntax issue).

Other Things to Note

  • When you provide your work to the user, do NOT provide it in terms of "Phases". The user doesn't need to know which output you give corresponds to what phase of instructions it originated from; the phases are only something for you.

© github, MIT. Rendered from Markdown: HTML in the file is shown as text, images as links, and headings moved down two levels. Raw file

Files

Just SKILL.md in skills/power-platform-architect of github/awesome-copilot.

Open the folder on GitHubat commit 727ff2e

Used in 1 other repository

We found 1 copy of this SKILL.md (exact, near-identical or edited) in other folders, from 1 other GitHub owner. This page covers the copy in github/awesome-copilot, which our catalogue first saw on October 7, 2026.

Compare with similar skills

Power Platform Architect next to the 5 skills that share the most tags, products or categories with it. Stars are the repository's; “used in” counts other GitHub owners with a copy.

Power Platform Architect compared with similar skills
SkillStarsUsed inTokensAuto-checkLicenceRepo updated
Power Platform Architect this skillgithub/awesome-copilot40k1 repos~3.6kAutomated safety check: PassMIT
Archify Diagramstt-a1i/archify79k—~2.9kAutomated safety check: PassMIT
Archify Diagram BuilderUnclecheng-li/AI_Animation1.4k2 repos~4.1kAutomated safety check: PassMIT
GitDiagram Repository Overviewahmedkhaleel2004/gitdiagram18k—~427Automated safety check: PassMIT
Code Graph Mermaid Diagramstrailofbits/skills7.4k—~1.7kAutomated safety check: PassCC-BY-SA-4.0
Mermaid Diagramsjjmartres/opencode1336 repos~1.9kAutomated safety check: PassMIT

Similar skills

  • Archify Diagrams

    tt-a1i/archify

    Creates interactive architecture, workflow, sequence, data-flow and lifecycle diagrams as standalone HTML with inline SVG, themes and image or video export.

    79k GitHub stars~2.9k tokensUpdated today
    DevelopmentAuto-check passed

  • Archify Diagram Builder

    Unclecheng-li/AI_Animation

    Builds validated architecture, workflow, sequence, data-flow and lifecycle diagrams as standalone interactive HTML from a small JSON spec, with optional motion and image export.

    1.4k GitHub starsUsed in 2 repos~4.1k tokens
    DevelopmentAuto-check passed

  • GitDiagram Repository Overview

    ahmedkhaleel2004/gitdiagram

    Explains the architecture of a public GitHub repository through GitDiagram: how the code is organized, the main components with paths, and a Mermaid diagram.

    18k GitHub stars~427 tokensUpdated today
    DevelopmentAuto-check passed

  • Code Graph Mermaid Diagrams

    trailofbits/skills

    Official

    Generates Mermaid diagrams from Trailmark code graphs, including call graphs, class hierarchies, module dependency maps, complexity heatmaps and attack surface data flows.

    7.4k GitHub stars~1.7k tokensUpdated 5 days ago
    DevelopmentAuto-check passed

  • Mermaid Diagrams

    jjmartres/opencode

    Helps an agent pick the right Mermaid diagram type and write the syntax for class, sequence, flow, ER, C4, state and other software diagrams.

    133 GitHub starsUsed in 6 repos~1.9k tokens
    DevelopmentAuto-check passed

  • GitDiagram Repo Architecture

    ahmedkhaleel2004/gitdiagram

    Explains how a public GitHub repository is built by fetching its GitDiagram architecture diagram, components and optional explainer video.

    18k GitHub stars~429 tokensUpdated today
    DevelopmentAuto-check passed

More from github/awesome-copilot

All 417 skills in this repo

  • Acquire Codebase Knowledge

    github/awesome-copilot

    Official

    Maps an unfamiliar codebase into seven evidence-backed documents in docs/codebase/, using a scan script and templates, for onboarding or architecture write-ups.

    40k GitHub starsUsed in 1 repo~2.3k tokens
    Auto-check passed

  • Azure Architecture Autopilot

    github/awesome-copilot

    Official

    Designs Azure infrastructure from a natural-language description, or diagrams an existing resource group, then refines the design through conversation and deploys it with Bicep.

    40k GitHub starsUsed in 1 repo~1.9k tokens
    Auto-check passed

  • Draw.io Diagram Generator

    github/awesome-copilot

    Official

    Generates, edits and validates draw.io files with correct mxGraph XML, covering flowcharts, architecture, sequence, ER and UML class diagrams.

    40k GitHub starsUsed in 1 repo~4.9k tokens
    Auto-check passed

  • Credit Risk Data Cleaning

    github/awesome-copilot

    Official

    Cleans raw credit data and screens variables before loan modeling, dropping unstable, noisy or redundant features and writing an Excel report of every step.

    40k GitHub starsUsed in 1 repo~1.5k tokens
    Auto-check passed

  • Daily Focus Board

    github/awesome-copilot

    Official

    Builds a warm, browser-based daily focus board the user updates by talking to their agent, with Eisenhower priorities, a brain-dump box and kind not-today carryover.

    40k GitHub stars~3k tokensUpdated today
    Auto-check passed

  • Python Pypi Package Builder

    github/awesome-copilot

    Official

    End-to-end skill for building, testing, linting, versioning, and publishing a production-grade Python library to PyPI.

    40k GitHub starsUsed in 1 repo~4.6k tokens
    Auto-check passed

Works with

Categories

Questions about Power Platform Architect

What does Power Platform Architect do?

A skill your agent uses when the user needs to transform business requirements, use case descriptions, or meeting transcripts into a technical Power Platform solution architecture, including…. Power Platform Architect is an agent skill from github/awesome-copilot, published by the product's own GitHub organization.js diagrams.

When should I use Power Platform Architect?

Power Platform Architect fits situations like: the user needs to transform business requirements; use case descriptions; meeting transcripts into a technical Power Platform solution architecture; including component selection and Mermaid.js diagrams.

How do I install Power Platform Architect in Claude Code?

Run `npx skills add github/awesome-copilot --skill power-platform-architect -a claude-code`. Or copy the skill folder (skills/power-platform-architect in github/awesome-copilot) into .claude/skills/power-platform-architect in your project. Claude Code loads it when a task matches its description.

How do I install Power Platform Architect in Codex?

Run `npx skills add github/awesome-copilot --skill power-platform-architect -a codex`. Or copy the skill folder (skills/power-platform-architect in github/awesome-copilot) into .agents/skills/power-platform-architect in your project. Codex loads it when a task matches its description.

Can I use Power Platform Architect in Cursor, Gemini CLI or GitHub Copilot?

Cursor, Gemini CLI, GitHub Copilot and OpenCode also load SKILL.md folders. With the skills CLI, run `npx skills add github/awesome-copilot --skill power-platform-architect -a cursor` (or -a gemini-cli, github-copilot or opencode for the others). To copy it by hand, put the folder in .cursor/skills/power-platform-architect, .gemini/skills/power-platform-architect, .github/skills/power-platform-architect and .opencode/skills/power-platform-architect in your project.

What does Power Platform Architect need to run?

SKILL.md names no scripts, command-line tools or credentials: Power Platform Architect is instructions for the agent only.

Does Power Platform Architect access the network?

SKILL.md names 2 domains. In commands or code: mermaid.ai; the agent is likely to contact it when it follows the instructions. As links in the text: learn.microsoft.com. This is read from the text; nothing was executed.

Is Power Platform Architect safe to install?

Our automated static check of SKILL.md found no risky patterns, such as piping downloads into a shell, reading credential files or hidden Unicode. It is not a guarantee. Review the folder before installing.

What licence does Power Platform Architect use?

Power Platform Architect is published under the MIT licence (declared in SKILL.md). It allows redistribution, so the full SKILL.md is shown on this page.

How many tokens does Power Platform Architect use?

About 3.6k tokens (SKILL.md is roughly 14k characters). Agents keep only the skill's name and description in context until a task matches; then they load SKILL.md in full.

What are the alternatives to Power Platform Architect?

Skills that share tags, products or a category with Power Platform Architect: Archify Diagrams (tt-a1i/archify, 79k stars), Archify Diagram Builder (Unclecheng-li/AI_Animation, 1.4k stars), GitDiagram Repository Overview (ahmedkhaleel2004/gitdiagram, 18k stars) and Code Graph Mermaid Diagrams (trailofbits/skills, 7.4k stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.

Who maintains Power Platform Architect?

github (a GitHub organization, an official publisher) maintains it in github/awesome-copilot, which has 39,748 GitHub stars. The repository holds 417 skills in this directory. The repository was last updated on October 7, 2026.

Source: github/awesome-copilot on GitHub. Facts on this page come from the repository at the commit we read; the author's words are quoted as theirs.