Render end-to-end previews of what an alert notification will actually look like (plain-text email, HTML email, Slack attachment JSON, raw webhook JSON) by replaying a Prometheus unit-test file's expected alerts through a live Alertmanager. Effectively a "print preview" for alerts. Use to review notification…
Screenshot every page of the running localhost dev server and report which pages changed since the last snapshot. Use after editing anything users can see (pages, components, CSS/Tailwind, layouts, templates) to visually verify before saying you're done, and when the user says "check the UI", "does it look right"…
Use when working in a technical domain with no existing playbook, writing new coding guidelines / review criteria / checklists from scratch, judging whether a verification method actually proves a claim (test passed but does it count?), or when repeated fixes keep failing and the direction feels wrong. Domain-agnostic…
Run an isolated persona-based UX test through the real desktop or browser UI. Creates a precise non-developer user persona, gives the tester only an approved product introduction, prevents source-code and design-document leakage, and produces an evidence-based Chinese evaluation report. Use when the user asks for…
Spec-Build-Test loop — the user defines a spec, then three agents iterate (Builder implements, Tester validates, Supervisor monitors for freezes) until the result matches. Works for any digital function — UI, APIs, CLI tools, conversational AI, data pipelines, and more.
Capture screenshots, short recordings, and milestone evidence during long-running agent tasks. Use when an agent is asked to perform multi-step browser, desktop, QA, troubleshooting, deployment, or admin workflows where the user wants checkpoint artifacts, progress evidence, error snapshots, or a final timeline of…
Plan focused tests with CodeMeridian by finding relevant test shields, coverage gaps, impacted behavior, and the smallest useful test set before implementation.
Domain skill - run screenshot-light PIE playtest episodes with structured entity observations, bounded semantic actions, transition polling, and in-memory traces for QA and external policy or RL runners.
Operator guide for MCPLab config authoring, Test Case Assistant workflows, execution, and result analysis. Use when users need to create or refine test cases from runs/traces, suggest deterministic checks or value capture, write or debug MCPLab eval YAML, run or queue evaluations, troubleshoot failures, or compare…
Use when a Looper-managed GitHub repo needs scheduled pre-merge QA — a PR carries the looper:qa label, the spec stage reaches looper:spec-ready, or the Looper reviewer loop requests an independent second pass. Runs the full QA cycle (Looper state probe → PR checkout → ffs code review → language-specific test suite →…
Implement and verify CoCo features end-to-end (Telegram commands, callbacks, app-server transport, queueing, watchdogs, approvals, and tests). Use when changing this repository's bot behavior and needing repo-specific file targets, workflows, and validation commands. NOT for generic Python tasks outside CoCo.
Automated testing execution using OpenTester DSL. Use when the user wants to create tests, run tests, validate test syntax, or manage test projects. Supports CLI testing with a YAML-based DSL.
Use when reviewing a code change or diff for correctness, security, missing tests, and convention violations before opening or approving a PR. Review independently and adversarially, then fix high-confidence issues.
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".
Run the marketplace validation script to check plugin integrity. Use when finishing plugin work, after adding or modifying plugins, or before committing plugin changes.
Writes unit, widget, golden, and integration tests for Flutter projects, detecting whether BLoC, Riverpod, Provider, or GetX is in use from pubspec.yaml before writing any business-logic test. Use when the user asks to write Flutter tests, add test coverage to a widget/bloc/provider/repository, test a .dart file, or…
Test-driven bug fixing — reproduce before you fix. Use this skill whenever the user reports a bug, describes unexpected behavior, says something is broken, mentions a regression, or asks you to fix an error. This includes phrases like "this is broken", "X doesn't work", "there's a bug in", "getting an error when", "it…
Set up the skills-evals library in a repository — discover agent artifacts, interview the user about what to test, scaffold eval cases, and wire CI and local runners. Use when the user wants to set up skills-evals, test their agent skills, add evals for skills or custom agents, check why a skill isn't triggering, or…
Validate UIs by clicking through them like a real user — iOS Simulator, Android emulator, tvOS, desktop, and web. Detects the platform and picks the right tool — agent-device (Callstack) for mobile/TV/desktop, agent-browser (Vercel Labs) for web, Maestro + Maestro Viewer for declarative cross-platform flows; raw xcrun…
Run the pre-real-Serum-test checklist on one or more .SerumPreset files -- automated CBOR wire-type scan plus a human-readable summary -- then hand off to the user for the real load-it-in-Serum test. Use this after any generatepreset/editpreset call on serum-mcp, or whenever a preset file needs to be verified before…
Skill "docs" from SpecLeft/specleft, covering specleft cli reference, setup, workflow, quick checks and safety.
★not rated 3 4mo agoA0 tokens
originalApache-2.0
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: