Test Skill
Guides a maker through debugging a Power Automate cloud flow (workflow) behind their agent — exercising it, reading its per-action run history, localizing a fault to a specific action, and fixing the flow (or the template config it reads). Published by microsoft in Employee-Self-Service-Agent-Developer-Kit.
Decision snapshot
Is this a fit?
Testing, Deployment, Includes SKILL.md, Reusable instructions
Compatibility not yet detected.
Permission behavior not yet detected.
Copy skill directory
2 months ago · MIT license
No specific cautions were detected. Review the source and requested permissions before installing.
What is Test Skill?
Guides a maker through debugging a Power Automate cloud flow (workflow) behind their agent — exercising it, reading its per-action run history, localizing a fault to a specific action, and fixing the flow (or the template config it reads). Published by microsoft in Employee-Self-Service-Agent-Developer-Kit. This profile combines repository metadata with install, compatibility, and usage signals so developers can quickly decide whether it fits their agent workflow before opening the source repository.
Automated repository signals based on public metadata such as recency, license, installation evidence, and adoption. These are not a security audit or endorsement. See how SkillIndex evaluates profiles.
Key capabilities
- Includes SKILL.md support
- Reusable instructions support
- Testing
- Deployment
- Testing use cases
- Deployment use cases
Declared skill metadata
- Source file: solutions/ess-maker-skills/src/skills/workflows/test/SKILL.md
These fields retain source and confidence evidence from the indexed SKILL.md.
Compatibility and setup
- Install or run with Copy skill directory
When to use Test Skill
- Use it for testing.
- Use it for deployment.
Built with
Editorial notes
Source
- Creator: microsoft
- Repository: microsoft/Employee-Self-Service-Agent-Developer-Kit
- Skill file: solutions/ess-maker-skills/src/skills/workflows/test/SKILL.md
What it does
Guides a maker through debugging a Power Automate cloud flow (workflow) behind their agent — exercising it, reading its per-action run history, localizing a fault to a specific action, and fixing the flow (or the template config it reads).
Skill instructions
Test Workflow Skill Guides a maker through debugging a Power Automate cloud flow (workflow) behind their agent — exercising it, reading its per-action run history, localizing a fault to a specific action, and fixing the flow (or the template config it reads). You do not drive a flow directly from this skill. An ESS flow is triggered by Copilot Studio — a topic calls it — so you exercise it one of two ways (below) and then read the decisive surface: the run history, action by action. The bot reply tells you what the user saw; the flow source tells you what was authored; only the run-action view tells you what actually happened. The debug-and-validate loop Debugging a flow is one loop, repeated until the run is clean: 1. Identify the flow — the workflow folder and its workflowId (the flow GUID). 2. Exercise it — in isolation (Power Automate manual Test with direct inputs) or in context (drive the topic that calls it). Isolation tells you if the fault is in the flow itself; in-context tel
Verified compatibility and discovery
Frequently asked questions
What is Test?
Test is a open-source AI agent skill with Copy skill directory. Guides a maker through debugging a Power Automate cloud flow (workflow) behind their agent — exercising it, reading its per-action run history, localizing a fault to a specific action, and fixing the flow (or the.
Who is Test best for?
Test is best for reusing agent instructions, scripts, and references, testing workflows, deployment workflows.
How do I install Test?
Install or run Test using Copy skill directory. Check Test for the latest setup command.
Is Test actively maintained?
Test may need a closer maintenance check before production use.
Project health auto-fetched from the source repository.
Maintain this resource?
Review this source-backed profile, send a correction with evidence, or link to it from your documentation. Claims verify your relationship to the project; profile facts still require source evidence and editorial review.
