Check how this producer repository lays out, installs, adopts, upgrades and reports on a room: the skills lane, support root, managed runtime tools, lifecycle classification, adoption, control fidelity, explicit upgrade and self-drift checks, plus the carrier line-landing, GitHub binding and socket contract checks. A…
Use when the user asks to find, create or update test cases in Allure TestOps, add steps and expected results, tag or link test cases, run a manual launch, or triage failed test results and defects. Triggers include "create a test case in Allure", "find test cases for this feature", "update the expected result", "what…
Interface with the Veris AI agent simulation and evaluation platform. Use this skill when you need to create AI agents, run simulations, generate scenarios, or evaluate agent performance. The Veris platform provides comprehensive tools for testing and validating AI agents through controlled simulation environments.
Develop, test, gate, and release the documentdb-mcp connector while preserving its SDK-owned client boundary, action-routed tools, knowledge graph ingestion, packaged resources, and shared publication contracts.
Use when a code change has multiple plausible implementation paths, high regression risk, uncertain root cause, or unclear tradeoffs. Creates isolated candidate implementations, runs comparable verification across each candidate, compares evidence, and applies the best proven approach while preserving user changes.
Unleash a mob of AI virtual users (impatient shoppers, confused seniors, keyboard-only users, chaos monkeys) on a website to stress-test its UX and hunt bugs. Use when the user asks to "crowd test", "mob test", "send virtual users", or wants persona-based UX/QA feedback on a URL before launch.
Lab playbook for the mcp-better server — claim equals wire; calls health and echo, and the optional confirmecho for MRTR. Use when connecting to mcp-better or testing its tools over protocol 2026-07-28.
Generate realistic synthetic test data — relational JSON/CSV/SQL fixtures, seed data, and QA datasets — via the MockHero MCP server or REST API. Use when a task needs mock users, orders, invoices, or multi-table seed data with valid foreign keys instead of hand-writing fixtures or faker scripts. Includes a free…
Behavioral verification intelligence for autonomous coding agents. Use this skill when the user asks "what could break in this PR?", "which workflows changed?", "what should I test before merging?", "is this change risky?", "what's the blast radius of removing this function?", or any question about understanding the…
Test, score, and inspect n8n workflows via MCP. Safe by design — no credential access, no destructive auto-repair. Use when testing workflows, debugging executions, searching nodes, or building workflows incrementally.
Generate persistent test cases from project analysis, or add individual test cases interactively. Supports full project analysis or adding single test cases via prompt description with browser exploration.
Toolkit for interacting with and testing local web applications using Playwright. Supports verifying frontend functionality, debugging UI behavior, capturing browser screenshots, and viewing browser logs.
Orchestrate test execution — run unit, integration, and E2E tests, collect coverage reports, and analyze failures. Use when running tests, checking coverage, debugging test failures, or validating code changes before merge.
Set up LLM workflow discipline for projects that use AI / LLM calls in production or eval suites. Authors an eval-cost-watcher agent that projects token cost BEFORE regression evals run, plus an AI-workflow-discipline rule covering mock-mode placement, fixture freshness, and multi-stage cost accumulation. Optionally a…
A workflow for comparing two versions of a prompt, skill, or piece of text without revealing which one is the new version. Separate agents create the versions, and a person scores them without seeing their labels.
Honest-completion ruleset for changes that touch tests or the code they cover. Use before deleting, skipping, renaming, or rewriting a test, before weakening an assertion, and before hardcoding or stubbing an implementation to make a test pass. Also covers what to do when a test looks genuinely wrong.
MSW (Mock Service Worker) v2 and v3 best practices, patterns, and API guidance for API mocking in JavaScript/TypeScript tests and development. Covers handler design, server setup, response construction, testing patterns, GraphQL, and v1-to-v2 and v2-to-v3 migration. Baseline: msw ^3.0.0. Triggers on: msw imports…
Execute an approved plan or specification with targeted implementation, tests, evidence, review, and independent verification. Use for “implement this”, “execute the plan”, “build this feature”, “write the code”, or “refactor without changing behavior”.
Use when doing non-trivial coding with Hermes, OpenClaw, Claude Code, Codex CLI, or similar autonomous coding agents. Orchestrates Karpathy-style minimal-change discipline, grill-plan intake, TDD, systematic debugging, subagent-driven implementation, spikes, and pre-commit review into one end-to-end workflow.
A coding workflow for planning changes, writing tests before or alongside code, and reviewing the result. TDD, or test-driven development, means using tests to guide the implementation.
Use when the user asks to check a repository's current branch, run its documented test command, and write a concise local test report.
★not rated 1 2mo agoA31 tokens
originalMIT
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: