smithery.ai

demo-test

Playwright-based testing for demo console errors and rendering

First seen Mar 31, 2026

Installation

$ npx skills add https://smithery.ai

Similar popular skills

Related neighbors and high-traction skills in the same topics — useful to compare before installing.

Also in this package

Other skills from smithery.ai · top by installs.

npx skills add https://smithery.ai

Browse all from smithery.ai

More details

Agent compatibility

Declared targets from SKILL.md / docs. Unmarked agents are not listed — the skill may still install via the CLI.

Claude Code Not declared
Cursor Not declared
Codex Not declared
GitHub Copilot Not declared
Windsurf Not declared
Gemini CLI Not declared
Cline Not declared
OpenCode Not declared

Skill metadata

Parsed from SKILL.md frontmatter.

Allowed toolsmcp__playwright__browser_navigate, mcp__playwright__browser_snapshot, mcp__playwright__browser_console_messages, mcp__playwright__browser_wait_for, mcp__playwright__browser_close, Bash(npm run dev:*)

Package contents

Files included with this skill beyond the listing page.

  • skill md SKILL.md 1,975 B
  • docs SUMMARY.md 79 B

History

  1. First seen on skills.sh
  2. First recorded snapshot · 1 installs

SKILL.md

Demo Test Skill

Automated testing of demo pages for console errors using Playwright MCP tools.

Workflow

1. Navigate to Demo

Use mcp__playwright__browser_navigate to open the demo URL.
Default: http://localhost:5173

2. Wait for Initialization

Use mcp__playwright__browser_wait_for with time: 3 (seconds)
This allows Three.js/WebGPU to initialize fully.

3. Capture Page State

Use mcp__playwright__browser_snapshot to capture current page accessibility tree.
Verify expected elements are present (canvas, controls, etc.).

4. Check Console Messages

Use mcp__playwright__browser_console_messages with level: "error"
Report any errors found.

5. Report Results

Summarize findings:

  • Page loaded successfully: yes/no
  • Console errors: count and details
  • Expected elements present: list
  • Recommendations for fixes

Testing Standards

Pass Criteria

  • Zero console errors
  • Canvas element present and rendering
  • No WebGL context loss warnings
  • Controls responsive (if applicable)

Common Issues to Check

  • Three.js initialization errors
  • Shader compilation failures
  • Resource loading failures (textures, models)
  • Memory/disposal warnings
  • Vue reactivity errors

Usage Notes

If no URL is provided, test the root development server at http://localhost:5173.

For specific demo routes, provide the full URL or just the path (will be appended to localhost:5173).

Always close the browser after testing with mcpplaywrightbrowser_close.