505 skills · sorted by relevance
Test Omnigent’s native Pi integration using the real terminal interface and a local server. Verify messages sent through the web or API, recorded replies, interruption, session resumption, authentication, and model settings to investigate integration problems.
Plan tests for APIs, interfaces, data pipelines, and infrastructure. Choose suitable test types, prioritize critical behavior, and produce a plan with coverage targets and example cases while balancing thoroughness, execution speed, and maintenance effort.
Document and validate Daytona interface workflows with labeled screenshots in a browsable HTML page. Add short videos when motion matters, check that evidence shows the claimed behavior, and share it for pull request review.
Test a real Electron app against a Den server in two separate Daytona environments. Check cloud sign-in, marketplace changes, organization policies, provider synchronization, and worker recovery, then collect evidence from the interface, APIs, logs, screenshots, and optional recordings.
Set up the iPolloWork server in Daytona, connect an Electron desktop client through public preview URLs, and check service health and logs. Supports cloud feature validation with separate server and desktop test environments.
Verify app changes through real user journeys and produce a single HTML demonstration. Each step connects a claim, user action, observable check, narration, and validated screenshot so reviewers can inspect evidence that the experience works.
Inspect and control live Chrome pages to investigate display problems, console errors, failed requests, and slow loading. Capture screenshots, automate page interactions, and record performance traces to identify where delays or layout shifts occur.
Prepare a branch for a pull request by running local tests, checking types for Node projects, pushing commits, and showing the CI pipeline link. Failed checks stop the workflow before the push.
Validate changes to Squad coordinator and agent templates through real sessions using a locally built CLI. Check generated files, agent behavior, and saved state, then record evidence, scenario verdicts, and progress for pull request reviews.
Check a Kiln branch or pull request through real browser interactions. Multiple agents test separate feature areas in isolated environments, then combine findings into a severity-ranked Markdown report with reproduction steps and expected versus actual behavior.
Write and improve Playwright tests for browser workflows, APIs, components, visual changes, and accessibility. Provides TypeScript and JavaScript patterns for selecting elements, waiting reliably, managing authentication and test data, and investigating intermittent failures.
Create Playwright tests for user workflows, APIs, and visual changes. Use TypeScript or JavaScript examples to choose reliable page elements, manage login state, diagnose intermittent failures, and configure automated test runs in CI.
Use when verifying OpenClaw gateway fixes end-to-end, testing skill loading after restart, or running integration tests against the local Nexu+OpenClaw stack. Triggers on "e2e test", "verify fix", "test gateway", "test skills loading".
The English summary is being prepared. Showing the original description.
Playwright E2E 测试模式、页面对象模型（POM）、配置、CI/CD 集成、产物管理以及不稳定测试（flaky test）策略。
The English summary is being prepared. Showing the original description.
Playwright E2E 测试模式、页面对象模型、配置、CI/CD 集成、工件管理和不稳定测试策略。
The English summary is being prepared. Showing the original description.
Playwright E2E 测试模式、页面对象模型 (Page Object Model)、配置、CI/CD 集成、产物管理以及不稳定测试 (Flaky Test) 策略。
The English summary is being prepared. Showing the original description.
Set up E2E test harness for CLI applications with process spawning and assertions.
The English summary is being prepared. Showing the original description.
Master end-to-end testing with Playwright and Cypress to build reliable test suites that catch bugs, improve confidence, and enable fast deployment. Use when implementing E2E tests, debugging flaky tests, or establishing testing standards.
The English summary is being prepared. Showing the original description.
This skill should be used when the user asks to "dev-webtest-plan", "Webテスト計画を生成", "テスト計画を作成", "webtest plan", "E2Eテスト計画", "画面テスト計画", "generate webtest plan", "create test plan from requirements", "webtest計画を更新", "テスト計画の差分更新", "update webtest plan", "画面仕様からテスト更新". dev-planの出力からPlaywright用のWebテスト計画ファイルを自動生成する。画面仕様の変更差分からテスト計画を更新する差分更新モードも対応。
The English summary is being prepared. Showing the original description.
This skill should be used when the user asks to "dev-webtest", "Webテスト", "画面の動作確認", "E2Eテスト", "web test", "visual check", "モンキーテスト", "アクセシビリティチェック", "レスポンシブテスト", "フォームテスト". Playwright CLIを使ってWebアプリの動作確認・視覚テスト・アクセシビリティ・レスポンシブ・フォームバリデーションを実行し、問題を検出・記録する。
The English summary is being prepared. Showing the original description.
Reference for the `odu` runner — how to invoke a full pipeline, a single recipe, or a platform-pinned node, and how to attach to a live run, from a project whose CI odu runs. Trigger when the user asks to "run CI", "run the pipeline", "re-run a check", to run named lanes or recipes (e.g. "run fmt and nix", "just the e2e lane", bare selectors like `fmt`/`nix`/`e2e`), or names a recipe by `<recipe>@<platform>`. This skill — not a repo's local `just ci` / `just <recipe>` — is how an odu-run request is served.
The English summary is being prepared. Showing the original description.
End-to-end testing with Playwright: test generation, page objects, locator strategy, flaky- test diagnosis, visual regression, and CI integration. Use when writing E2E tests, fixing flaky tests, or migrating from Cypress/Selenium.
The English summary is being prepared. Showing the original description.
Use when a completed phase needs unit or E2E tests, or the user asks to add tests for phase N. Classifies implementation files into TDD, E2E, or skip, gets plan approval, then generates RED-GREEN tests from SUMMARY.md and UAT criteria.
The English summary is being prepared. Showing the original description.
Use when writing E2E/integration tests, testing native interactions like permissions or system dialogs, capturing UI regressions, or validating cross-platform behavior (Patrol 4.x).
The English summary is being prepared. Showing the original description.