Use when building, running, or testing an iOS app on a simulator — claims a leased simulator through simlease so parallel AI agents never collide, labels the simulator window with the task name, and releases it when done.
Hunt for bugs in distributed consensus protocol implementations using a 2-agent strategy+testgen pipeline. Use when targeting consensus protocols (Raft, PBFT, HotStuff, Tendermint, etc.) for automated vulnerability discovery.
Prepare dynobox packages for release to npm. Use this skill whenever the user asks to release, publish, ship, bump, or cut a version of any dynobox package — including dry runs, version bumps, changelog updates, and git tagging. Also trigger when the user asks about the release process or wants to verify publish…
Use when generating manual QA test cases from requirements, BRDs, user stories, acceptance criteria, spreadsheets, live mockup/prototype URLs, uploaded mockups, screenshots, wireframes, or existing test case templates; especially when coverage, deduplication, traceability, validations, permissions, workflows, or edge…
Test mobile apps with MobiLoop MCP, collect device evidence, and fix and retest confirmed failures within the user's scope. Use for Flutter, React Native, Android, or iOS QA on an emulator, simulator, or device, including relevant mobile security checks.
Check your work with a verification subagent that reviews diffs, runs builds and tests, and evaluates correctness. Read this file for instructions. Use when asked to "check work", "verify changes", "self-verify", "/check-work", "/check", "/verify", or "/self-verify".
Use 901 to run one feature end-to-end, headless, on its own git branch: high-level design, happy-path specs, test-driven build-out committed per module, cleanup, optional expanded coverage, and a merge back. Trigger it for prompts like "901", "feature loop", "master loop this feature", or "run the full pipeline for…
A testing workflow for y3 games, with three mandatory rules: review code before sending it, treat only [run-ok] as success, and ensure every run or Lua command reaches the command-ID success marker.
Generate, modify, validate, execute and triage Flow Forge API test cases. Use when the user wants to turn requirement documents, API documents, table structures or business rules into executable YAML/Excel test cases, revise existing cases after requirement/API changes, run cases with the Flow Forge executor and…
Adversarial verification agent that tests implementations by running builds, tests, and probing edge cases. Returns a structured VERDICT (PASS/FAIL/PARTIAL) with evidence.
Use when developing or testing Palm OS applications in the POSE64 emulator, including using MCP tools, automating emulator actions, or writing Palm app test scripts.
A batch verification process that checks proof-of-concept items against a list of assets. It runs the checks in parallel and produces a results matrix and Markdown report.
Samurai scoped testing framework for Go (github.com/zerosixty/samurai). MUST use when writing, modifying, reviewing, or debugging Go tests that import samurai, or reference samurai.Run, samurai.RunWith, samurai.Scope, samurai.TestScope, samurai.W, or samurai.BaseContext.
Guides agents through ISO validation and evidence collection. Use when running smoke tests, installer E2E tests, local ISO boots, or investigating validation artifacts.
This sop guides the implementation of code tasks using test-driven development principles, following a structured Explore, Plan, Code, Commit workflow. It balances automation with user collaboration while adhering to existing package patterns and prioritizing readability and extensibility. The agent acts as a…
A testing and quality-checking toolkit for running an application, finding bugs, and creating automated tests. It supports API tests and browser-based UI tests in Python or Java.
Verify a Memos-style MCP integration through GPTADMIN without duplicating the backend, leaking credentials, or confusing the native ShellMCP supervisor with legacy per-agent services.
Generates Behat tests for Drupal 10/11 using the Drupal Extension for Behat. Use this skill when the project already has Behat configured (look for behat.yml), when acceptance tests written in natural language (Gherkin) are needed, E2E flows, or when the client needs to read and validate test scenarios. Trigger…
At most 3 mods per repository are shown here, and a mod shipped inside a plugin is left to that plugin's page — the rest are on their repository pages: