- Home
- Skills
- Robdtaylor
- Personal Ai Infrastructure
- Powerplatform
powerplatform_skill
- TypeScript
0
GitHub Stars
1
Bundled Files
2 months ago
Catalog Refreshed
4 months ago
First Indexed
Readme & install
Copy the install command, review bundled files from the catalogue, and read any extended description pulled from the listing source.
Installation
Preview and clipboard use veilstrat where the catalogue uses aiagentskills.
npx veilstrat add skill robdtaylor/personal-ai-infrastructure --skill powerplatform- SKILL.md6.9 KB
Overview
This skill generates Power Automate flows from plain-language requests and builds deployable solution packages ready to import into your Power Platform environment. It reads connector schemas exported in your work repo, maps triggers/actions, and emits flow JSON and a solution ZIP placed in the generated folder. Use it when you ask to create flows, automate workflows, or describe a business process to automate.
How this skill works
It inspects manifest.json and connector schema files in your work repo to determine available triggers, actions, and operation IDs. From the user request it extracts the trigger, actions, conditions, and data flow, then composes a Power Automate workflow JSON with connectionReferences and expression syntax. Finally it packages the workflow into the solution structure and writes the solution ZIP to the generated directory for import.
When to use it
- When you say “create flow”, “power automate”, or “automate workflow”
- When you describe a business process to automate (emails, approvals, file handling)
- When you need a deployable Flow JSON and solution package for import
- When you want a template-based or custom flow built from repo connector schemas
Best practices
- Keep the request explicit: name trigger, core actions, and any branching rules
- Mention connectors or systems involved (SharePoint, Teams, Office365) so correct schemas are selected
- Specify field mappings and important attributes (e.g., subject contains “urgent”, target folder name)
- Review generated connectionReferences before import and map to live connections in your environment
- Test flows in a sandbox before enabling in production
Example use cases
- Email notification: send a Teams message when an incoming email subject contains “urgent”
- Approval process: on SharePoint file creation, start approval and move file to approved/rejected folder
- Scheduled report: run a recurrence, query Dataverse, format results and email a report
- Webhook intake: When an HTTP request is received, parse payload, create SharePoint item and notify a channel
FAQ
No. It creates solution packages and Flow JSON. You must import the solution and map connection references in your environment.
What if connector schemas are missing or stale?
If manifest.json or connector schema files are missing or out of date, I will prompt you to run the export script at work and provide the updated files.