Ark Dashboard and UI Testing
Skill439 starsChanged 7 months agoApache-2.0View on GitHub
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.
- Commits and pushes
In this repository29 other files it gives its agents.
- ark/CLAUDE.mdCLAUDE.md
- CLAUDE.mdCLAUDE.md
- tests/CLAUDE.mdCLAUDE.md
- a2a-protocolSkill
- Ark AnalysisSkill
- ark-architectureSkill
- ark-controller-developmentSkill
- ark-dependabot-managementSkill
- ark-sdk-developmentSkill
- ark-setup-clusterSkill
- ark-chainsaw-testingSkill
- ark-documentationSkill
- issue-creationSkill
- ark-issuesSkill
- multi-branch-cluster-setupSkill
- openspec-apply-changeSkill
- openspec-archive-changeSkill
- openspec-bulk-archive-changeSkill
- openspec-continue-changeSkill
- openspec-exploreSkill
- openspec-ff-changeSkill
- openspec-new-changeSkill
- openspec-onboardSkill
- openspec-sync-specsSkill
- openspec-verify-changeSkill
- ark-pentest-issue-resolverSkill
- ark-researchSkill
- slack-announcementSkill
- ark-vulnerability-fixerSkill
The file
We split this skill into the rules it gives an agent
7 rules. About 0 are common, 6 are distinctive, and 1 is very specific to this project.
≈0
Common · estimate
Many files like this have a rule of this kind.
≈6
Distinctive · estimate
This author's own choices. Worth a look.
1
Very specific
Tied to their project's names, files or tools. Probably skip.
- Common
- Distinctive
- Very specific
- Distinctive: line 8
Test Ark Dashboard UI with Playwright and attach screenshots to PRs.
- Distinctive: line 12
Use this skill when:
- Distinctive: line 19
CRITICAL: Before proceeding, verify Kubernetes is available:
- Distinctive: line 25
If this fails, STOP and inform the user:
- Distinctive: line 41
Use Playwright MCP tools to navigate and screenshot:
- Distinctive: line 51
Check if user has a scratch repo:
- Very specific: line 56
If not, suggest creating: scratch/pull-request-attachments/<org>_<repo>/
≈ “Common” is an estimate: at least 1 in 5 of the 364,980 skill files we read have a rule of the same kind, not the same words. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.
Files
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-infoIf 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:3000Test 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>/scratchIf 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 pushReference in PR body:
Update PR:
gh api repos/<org>/<repo>/pulls/<NUMBER> -X PATCH -f body="..."Does it work?
Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.
No reviews yet
People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.
- It worked
- Partly
- It didn't
Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.
Your trail
Files you open will collect here, so you can find them again.
Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.
Now do this for your own.
Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.

