ark-dashboard-testing

Test Ark Dashboard with Playwright and create PRs with screenshots. Use when testing dashboard UI, taking screenshots for PRs, or reviewing dashboard changes.

16 stars

bydiegosouzapw

View on GitHub Installation ↓

Best use case

ark-dashboard-testing is best used when you need a repeatable AI agent workflow instead of a one-off prompt.

Test Ark Dashboard with Playwright and create PRs with screenshots. Use when testing dashboard UI, taking screenshots for PRs, or reviewing dashboard changes.

Teams using ark-dashboard-testing should expect a more consistent output, faster repeated execution, less prompt rewriting.

When to use this skill

You want a reusable workflow that can be run more than once with consistent structure.

When not to use this skill

You only need a quick one-off answer and do not need a reusable workflow.
You cannot install or maintain the underlying files, dependencies, or repository context.

Installation

Claude Code / Cursor / Codex

$curl -o ~/.claude/skills/ark-dashboard-testing/SKILL.md --create-dirs "https://raw.githubusercontent.com/diegosouzapw/awesome-omni-skill/main/skills/testing-security/ark-dashboard-testing/SKILL.md"

Manual Installation

Download SKILL.md from GitHub
Place it in .claude/skills/ark-dashboard-testing/SKILL.md inside your project
Restart your AI agent — it will auto-discover the skill

How ark-dashboard-testing Compares

Feature / Agent	ark-dashboard-testing	Standard Approach
Platform Support	Not specified	Limited / Varies
Context Awareness	High	Baseline
Installation Complexity	Unknown	N/A

Frequently Asked Questions

What does this skill do?

Test Ark Dashboard with Playwright and create PRs with screenshots. Use when testing dashboard UI, taking screenshots for PRs, or reviewing dashboard changes.

Where can I find the source code?

You can find the source code on GitHub using the link provided at the top of the page.

SKILL.md Source

# Ark Dashboard Testing

Test Ark Dashboard UI with Playwright and create PRs with embedded screenshots.

## Setup

```bash
kubectl port-forward svc/ark-dashboard 3000:3000 -n default &
curl http://localhost:3000  # warm up
```

## Test with Playwright

Use Playwright MCP tools: `browser_navigate`, `browser_wait_for`, `browser_click`, `browser_take_screenshot`.

Screenshots save to `.playwright-mcp/screenshots/` - move to `./screenshots/`.

## PR Screenshots

Check if user has a scratch repo:
```bash
gh repo view <USERNAME>/scratch
```

If not, suggest creating one with structure: `scratch/pull-request-attachments/<org>_<repo>/`

Upload:
```bash
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 #XXX" && git push
```

Reference in PR:
```markdown
![Alt](https://raw.githubusercontent.com/<USERNAME>/scratch/master/pull-request-attachments/<org>_<repo>/01-screenshot.png)
```

Update PR via API:
```bash
gh api repos/<org>/<repo>/pulls/XXX -X PATCH -f body="..."
```

---
[Claude Code Skills Documentation](https://docs.anthropic.com/en/docs/claude-code/skills)

Related Skills

Burp Suite Web Application Testing

from diegosouzapw/awesome-omni-skill

This skill should be used when the user asks to "intercept HTTP traffic", "modify web requests", "use Burp Suite for testing", "perform web vulnerability scanning", "test with Burp Repeater", "analyze HTTP history", or "configure proxy for web testing". It provides comprehensive guidance for using Burp Suite's core features for web application security testing.

burp-suite-testing

from diegosouzapw/awesome-omni-skill

This skill should be used when the user asks to "intercept HTTP traffic", "modify web requests", "use Burp Suite for testing", "perform web vulnerability scanning", "test with Burp ...

backtesting-frameworks

from diegosouzapw/awesome-omni-skill

Build robust backtesting systems for trading strategies with proper handling of look-ahead bias, survivorship bias, and transaction costs. Use when developing trading algorithms, validating strateg...

axiom-ios-testing

from diegosouzapw/awesome-omni-skill

Use when writing ANY test, debugging flaky tests, making tests faster, or asking about Swift Testing vs XCTest. Covers unit tests, UI tests, fast tests without simulator, async testing, test architecture.

asyncredux-testing-view-models

from diegosouzapw/awesome-omni-skill

Test StoreConnector view-models in isolation. Covers creating view-models with `Vm.createFrom()`, testing view-model properties, testing callbacks that dispatch actions, and verifying state changes from callbacks.

asyncredux-testing-basics

from diegosouzapw/awesome-omni-skill

Write unit tests for AsyncRedux actions using the Store directly. Covers creating test stores with initial state, using `dispatchAndWait()`, checking state after actions, verifying action errors via ActionStatus, and testing async actions.

astro-testing

from diegosouzapw/awesome-omni-skill

Testing and QA gate for Astro lead gen sites. Manual + E2E + A11y + Performance. FAIL = no deploy.

aspire-integration-testing

from diegosouzapw/awesome-omni-skill

Write integration tests using .NET Aspire's testing facilities with xUnit. Covers test fixtures, distributed application setup, endpoint discovery, and patterns for testing ASP.NET Core apps with real dependencies.