pp-diagnose Skill
Slash command — diagnose a failing Power Platform Playwright test. Maps errors against CLAUDE.md anti-patterns, walks the trace zip, and explains the root cause + fix. Wraps the pp-playwright-diagnose agent. Published by microsoft in power-platform-playwright-samples.
Decision snapshot
Is this a fit?
Browser automation, Testing, Includes SKILL.md, Reusable instructions
Compatibility not yet detected.
Permission behavior not yet detected.
Copy skill directory
2 months ago · NOASSERTION license
No specific cautions were detected. Review the source and requested permissions before installing.
What is pp-diagnose Skill?
Slash command — diagnose a failing Power Platform Playwright test. Maps errors against CLAUDE.md anti-patterns, walks the trace zip, and explains the root cause + fix. Wraps the pp-playwright-diagnose agent. Published by microsoft in power-platform-playwright-samples. 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
- Browser automation
- Testing
- Browser automation use cases
- Testing use cases
Declared skill metadata
- Source file: .claude/skills/pp-diagnose/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 pp-diagnose Skill
- Use it for browser automation.
- Use it for testing.
Built with
Editorial notes
Source
- Creator: microsoft
- Repository: microsoft/power-platform-playwright-samples
- Skill file: .claude/skills/pp-diagnose/SKILL.md
What it does
Slash command — diagnose a failing Power Platform Playwright test. Maps errors against CLAUDE.md anti-patterns, walks the trace zip, and explains the root cause + fix. Wraps the pp-playwright-diagnose agent.
Skill instructions
/pp-diagnose — diagnose a failed Playwright test When the user types /pp-diagnose, invoke the pp-playwright-diagnose agent and pass any arguments through. Argument forms accepted | Form | What the agent does | | ------------------------------------------------------- | ---------------------------------------------------------------------------- | | /pp-diagnose | Asks the user for the failing test name, error text, or trace path | | /pp-diagnose tests/northwind/mda/form-context.test.ts | Reads the test, opens the most recent matching test-results/ folder | | /pp-diagnose test-results/canvas-app-update/trace.zip | Walks the trace, reports last action + DOM + network | | /pp-diagnose "TimeoutError: locator.click 30000ms" | Triages from the error fragment alone — fastest path for known anti-patterns | Behaviour 1. Spawn the pp-playwright-diagnose agent. 2. Pass the argument as the agent's evidence input. 3. The agent owns Steps 1–4 (anti-pattern triage → trace investigation → toolkit cros
Verified compatibility and discovery
Frequently asked questions
What is pp-diagnose?
pp-diagnose is a open-source AI agent skill with Copy skill directory. Slash command — diagnose a failing Power Platform Playwright test. Maps errors against CLAUDE.md anti-patterns, walks the trace zip, and explains the root cause + fix. Wraps the pp-playwright-diagnose agent.
Who is pp-diagnose best for?
pp-diagnose is best for reusing agent instructions, scripts, and references, browser automation workflows, testing workflows.
How do I install pp-diagnose?
Install or run pp-diagnose using Copy skill directory. Check pp-diagnose for the latest setup command.
Is pp-diagnose actively maintained?
pp-diagnose 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.
