Skill

Ark Dashboard and UI Testing

From ark

Tests Ark Dashboard UI via Playwright on Kubernetes, captures screenshots, and uploads to GitHub scratch repo for PR attachments.

Playwright

Install

npx claudepluginhub mckinsey/agents-at-scale-ark --plugin ark

Tool Access

This skill uses the workspace's default tool permissions.

Preview

Test Ark Dashboard UI with Playwright and attach screenshots to PRs.

SKILL.md

Similar Skills

applying-brand-guidelines

3 files

Applies Acme Corporation brand guidelines including colors, fonts, layouts, and messaging to generated PowerPoint, Excel, and PDF documents.

anthropics-claude-cookbooks

41.6k

creating-financial-models

2 files

Builds DCF models with sensitivity analysis, Monte Carlo simulations, and scenario planning for investment valuation and risk assessment.

anthropics-claude-cookbooks

41.6k

analyzing-financial-statements

2 files

Calculates profitability (ROE, margins), liquidity (current ratio), leverage, efficiency, and valuation (P/E, EV/EBITDA) ratios from financial statements in CSV, JSON, text, or Excel for investment analysis.

anthropics-claude-cookbooks

41.6k

Stats

Parent Repo Stars364

Parent Repo Forks80

Last CommitJan 7, 2026

Used By2 plugins

Actions

View Source View Plugin View on GitHub View README

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 pages
browser_wait_for - Wait for elements
browser_click - Click elements
browser_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 git@github.com:<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:

![Screenshot](https://raw.githubusercontent.com/<USERNAME>/scratch/master/pull-request-attachments/<org>_<repo>/01-screenshot.png)

Update PR:

gh api repos/<org>/<repo>/pulls/<NUMBER> -X PATCH -f body="..."