ark-dashboard-and-ui-testing
Run Playwright tests against the Ark Dashboard and automatically generate screenshots for PR verification.
Install
mkdir -p .claude/skills/ark-dashboard-and-ui-testing && curl -L -o skill.zip "https://agentskills.codes/api/skills/download/2552" && unzip -o skill.zip -d .claude/skills/ark-dashboard-and-ui-testing && rm skill.zipInstalls to .claude/skills/ark-dashboard-and-ui-testing
Activation
This is the description your AI agent reads to decide when to run this skill — the better it matches your request, the more reliably it fires.
Test the Ark Dashboard and UI with Playwright and create PRs with screenshots. Use this skill when testing dashboard UI, taking screenshots for PRs, or validating dashboard changes.Key capabilities
- →Port forward dashboard services
- →Navigate browser UI elements
- →Capture UI screenshots
- →Upload screenshots to GitHub scratch repository
How it works
The skill connects to a live cluster via port-forwarding and uses Playwright to automate browser interactions, capturing and organizing screenshots for pull request documentation.
Inputs & outputs
When to use ark-dashboard-and-ui-testing
- →Run UI tests for dashboard changes
- →Capture screenshots for a pull request
- →Validate dashboard layout in a cluster
- →Verify dashboard navigation flows
About this skill
Ark Dashboard and UI
Test Ark Dashboard UI with Playwright and attach screenshots to PRs.
When to use this skill
Use this skill when:
- User wants to test the Ark dashboard
- User needs screenshots for a PR
- User asks to validate dashboard UI changes
Prerequisites
CRITICAL: Before proceeding, verify Kubernetes is available:
kubectl cluster-info
If this fails, STOP and inform the user:
Cannot continue without a Kubernetes environment. Please ensure Kind or another Kubernetes cluster is running and kubectl is configured.
Ark must be deployed first. Use the ark-setup skill if needed.
Setup
Port forward the dashboard and warm up:
kubectl port-forward svc/ark-dashboard 3000:3000 -n default &
curl http://localhost:3000
Test with Playwright
Use Playwright MCP tools to navigate and screenshot:
browser_navigate- Open pagesbrowser_wait_for- Wait for elementsbrowser_click- Click elementsbrowser_take_screenshot- Capture screenshots
Screenshots save to .playwright-mcp/screenshots/. Move to ./screenshots/ for organization.
Upload Screenshots for PRs
Check if user has a scratch repo:
gh repo view <USERNAME>/scratch
If not, suggest creating: scratch/pull-request-attachments/<org>_<repo>/
Upload screenshots:
cd /tmp && git clone [email protected]:<USERNAME>/scratch.git
mkdir -p scratch/pull-request-attachments/<org>_<repo>
cp ./screenshots/*.png scratch/pull-request-attachments/<org>_<repo>/
cd scratch && git add . && git commit -m "chore: screenshots for <org>/<repo> PR" && git push
Reference in PR body:
Update PR:
gh api repos/<org>/<repo>/pulls/<NUMBER> -X PATCH -f body="..."
When not to use it
- →Testing without a live Kubernetes cluster
Prerequisites
Limitations
- →Requires a running Kubernetes environment
- →Screenshots must be manually moved to organized directories
How it compares
It provides a structured workflow for capturing and attaching visual evidence to PRs, rather than manually taking and uploading screenshots.
Compared to similar skills
ark-dashboard-and-ui-testing side by side with the closest alternatives in the catalog.
| Skill | Installs | Updated | Safety | Difficulty |
|---|---|---|---|---|
| ark-dashboard-and-ui-testing (this skill) | 2 | 7mo | Review | Beginner |
| ark-chainsaw-testing | 1 | 4mo | Review | Intermediate |
| nx-run-tasks | 1 | 6mo | No flags | Intermediate |
| testing-load-balancers | 0 | 27d | Review | Advanced |
Try saying
Example prompts that trigger this skill in your AI assistant.
More by mckinsey
View all by mckinsey →You might also like
ark-chainsaw-testing
mckinsey
Run and write Ark Chainsaw tests with mock-llm. Use for running tests, debugging failures, or creating new e2e tests.
nx-run-tasks
nrwl
Helps with running tasks in an Nx workspace. USE WHEN the user wants to execute build, test, lint, serve, or run any other tasks defined in the workspace.
testing-load-balancers
jeremylongshore
Validate load balancer behavior, failover, and traffic distribution. Use when performing specialized testing. Trigger with phrases like "test load balancer", "validate failover", or "check traffic distribution".
chaos-scenario
petercort
Use when authoring, running, or reviewing chaos engineering experiments in this monorepo. Covers steady-state hypothesis, fault injection (service kill, latency, network partition, overload), result recording to CSV, and cleanup/restore. Triggers: "add chaos scenario", "new chaos test", "inject faul
webapp-testing
anthropics
Toolkit for interacting with and testing local web applications using Playwright. Supports verifying frontend functionality, debugging UI behavior, capturing browser screenshots, and viewing browser logs.
ui-ux-expert-skill
fercracix33
Technical workflow for implementing accessible React user interfaces with shadcn/ui, Tailwind CSS, and TanStack Query. Includes 6-phase process with mandatory Style Guide compliance, Context7 best practices consultation, Chrome DevTools validation, and WCAG 2.1 AA accessibility standards. Use after Test Agent, Implementer, and Supabase agents complete their work.