Posted Updated Agent Skills / Testing & Quality2 hours read (About 17397 words)

Testing & Quality | Agent Skills

Testing & Quality

Testing and quality skills focus on test design, automation, debugging, accessibility, and repeatable checks across software stacks.

Catalog snapshot: November 2, 2026

Category menu

Skills in this category

addyosmani/web-quality-audit

Catalog entry: Skills by - Google Chrome team - Addy Osmani (Web Quality)
Source documentation: https://github.com/addyosmani/web-quality-skills/blob/main/skills/web-quality-audit/SKILL.md

Function: Comprehensive quality review across performance, accessibility, SEO, and best practices categories

When to use it: Use when asked to “audit my site”, “review web quality”, “run lighthouse audit”, “check page quality”, or “optimize my website”.

Usage guidance is taken from the skill’s own trigger description or usage section.

Source skill menu:

  • Web quality audit
  • How it works
  • Tool routing
  • Audit categories
  • Performance
  • Accessibility
  • SEO
  • Best practices
  • Agentic browsing
  • Severity levels
  • Audit output format
  • Quick checklist
  • Before every deploy
  • Weekly review
  • Monthly deep dive
  • References

agiwhitelist/auteur

Catalog entry: Development and Testing
Source documentation: https://github.com/agiwhitelist/auteur/blob/main/SKILL.md

Function: Builds websites gated by an anti-slop linter and motion QA

When to use it: Use when a task needs the capability described in this catalog entry: Builds websites gated by an anti-slop linter and motion QA

The catalog does not state a separate trigger condition. This usage note is inferred from the published function description.

Source skill menu:

  • Use this when
  • What it actually does
  • Network access
  • Non-negotiables
  • Banned (rewrite, don’t tweak)
  • Critical numbers (memorize; full context in reference files)
  • Routing
  • The commit-sheet (before any code, both registers)
  • Phases at a glance
  • Reference files
  • Verification is part of the build
  • Working relationship with other skills
  • Weak-model note

anthropics/webapp-testing

Catalog entry: Official Claude Skills
Source documentation: https://github.com/anthropics/skills/blob/main/skills/webapp-testing/SKILL.md

Function: Test local web applications using Playwright

When to use it: Taking screenshots of a locally running React app to verify layout after a CSS change Clicking through a multi-step form to confirm all validation states render correctly Capturing browser console logs during a page load to catch JavaScript errors Testing a frontend against a running backend by managing both server processes simultaneously Discovering all interactive elements on a rendered page before writing targeted selectors

Usage guidance is taken from the skill’s own trigger description or usage section.

Source skill menu:

  • Web Application Testing
  • Decision Tree: Choosing Your Approach
  • Example: Using with_server.py
  • Reconnaissance-Then-Action Pattern
  • Common Pitfall
  • Best Practices
  • Reference Files

antonbabenko/terraform-skill

Catalog entry: Development and Testing
Source documentation: https://github.com/antonbabenko/terraform-skill/blob/master/skills/terraform-skill/SKILL.md

Function: Terraform and OpenTofu patterns: testing, modules, state, CI/CD.

When to use it: Use when writing, reviewing, or debugging Terraform/OpenTofu modules, tests, CI, scans, or state ops - diagnoses failure mode (identity churn, secrets, blast radius, CI drift, state corruption) with version-aware guards.

Usage guidance is taken from the skill’s own trigger description or usage section.

Source skill menu:

  • Terraform Skill for Claude
  • Response Contract
  • Workflow
  • Diagnose Before You Generate
  • When to Use This Skill
  • Core Principles
  • Module Hierarchy
  • Directory Layout
  • Naming Conventions (summary)
  • Block Ordering (summary)
  • Testing Strategy
  • Decision Matrix: Which Testing Approach?
  • Native Test Rules (1.6+)
  • Count vs For_Each — Quick Rule
  • Locals for Dependency Management
  • Module Development

browserbase/ui-test

Catalog entry: Skills by Browserbase
Source documentation: https://github.com/browserbase/skills/blob/main/skills/ui-test/SKILL.md

Function: Run adversarial UI tests by analyzing git diffs in a real browser

When to use it: Use when the user asks to test UI changes, QA a pull request, audit accessibility, or run exploratory testing. Supports local browser (localhost) and remote Browserbase (deployed sites).

Usage guidance is taken from the skill’s own trigger description or usage section.

Source skill menu:

  • UI Test — Agentic UI Testing Skill
  • How Testing Works
  • Planning: multiple angles, then execute once
  • Principles for splitting work
  • Giving sub-agents a step budget
  • Reporting
  • Testing Philosophy
  • Assertion Protocol
  • Step markers
  • Screenshot Capture for Failures
  • How to verify (in order of rigor)
  • Before/after comparison pattern
  • Setup
  • Avoid permission fatigue
  • Mode Selection
  • Local Mode (default for localhost)

callstackincubator/github

Catalog entry: Skills by CallStack
Source documentation: https://github.com/callstackincubator/agent-skills/blob/main/README.md

Function: GitHub workflow patterns for PRs, code review, branching

When to use it: Merging a chain of stacked PRs into main as individual squash commits Rebasing a dependent branch after its parent PR is merged Creating PRs with consistent title and body formats from the terminal Checking PR status and CI results without leaving the shell Updating a PR’s base branch after the target branch changes

Usage guidance is taken from the skill’s own trigger description or usage section.

Source skill menu:

  • Callstack Agent Skills
  • What’s included
  • Quick start
  • OpenAI Codex
  • Manual installation
  • Try it
  • Skills
  • Build and optimize
  • Test and verify
  • Migrate and modernize
  • Guides and related resources
  • Repository structure
  • Contributing
  • About Callstack

coderabbitai/code-review

Catalog entry: Skills by CodeRabbit
Source documentation: https://github.com/coderabbitai/skills/blob/main/skills/code-review/SKILL.md

Function: Run AI-powered code reviews through the CodeRabbit CLI

When to use it: Reviewing staged changes for security vulnerabilities before committing Comparing a feature branch against main to catch regressions Running a post-implementation review cycle that fixes its own findings Scanning uncommitted work for bugs during local development Getting severity-grouped feedback on a pull request without leaving the terminal

Usage guidance is taken from the skill’s own trigger description or usage section.

Source skill menu:

  • CodeRabbit Code Review
  • Capabilities
  • When to Use
  • How to Review
  • 1. Check CLI and Authentication
  • 2. Run Review
  • 3. Present Results
  • 4. Fix Issues (Autonomous Workflow)
  • 5. Review Specific Changes
  • Other CLI workflows
  • Security
  • Documentation

coderabbitai/skills

Catalog entry: Development and Testing
Source documentation: https://github.com/coderabbitai/skills/blob/main/README.md

Function: Code review and PR autofix workflows for coding agents

When to use it: Use when a task needs the capability described in this catalog entry: Code review and PR autofix workflows for coding agents

The catalog does not state a separate trigger condition. This usage note is inferred from the published function description.

Source skill menu:

  • CodeRabbit Skills and Plugins
  • Quickstart
  • Installation
  • 1. Install the CodeRabbit CLI
  • 2. Install the agent integration
  • What Lives Here
  • Usage
  • Supported Agents
  • Available Skills
  • code-review
  • autofix
  • Plugin Components
  • Claude Code
  • Cursor
  • Antigravity CLI
  • Gemini CLI

This catalog entry points to a collection. The scanned repository lists 2 distinct skill-file paths.

Sample members: autofix · code-review

cypress-io/cypress-author

Catalog entry: Skills by Cypress
Source documentation: https://github.com/cypress-io/ai-toolkit/blob/main/skills/cypress-author/SKILL.md

Function: Creates, updates, and fixes Cypress E2E and component tests.

When to use it: Use when the user asks to create tests, add tests, write tests, update tests, test this file/component, new spec, or fix a failing or flaky test. Apply even when the user does not say ‘Cypress’ (e.g. ‘create tests for this file’). Prefer cypress-explain when the user only wants to explain or review tests without changing code.

Usage guidance is taken from the skill’s own trigger description or usage section.

Source skill menu:

  • Cypress Author
  • Task
  • Mandatory flow (do not skip)
  • Conclusion

cypress-io/cypress-docs

Catalog entry: Skills by Cypress
Source documentation: https://github.com/cypress-io/ai-toolkit/blob/main/skills/cypress-docs/SKILL.md

Function: Search and extract Cypress information from official documentation.

When to use it: Use when a task needs the capability described in this catalog entry: Search and extract Cypress information from official documentation.

The catalog does not state a separate trigger condition. This usage note is inferred from the published function description.

Source skill menu:

  • Cypress Documentation
  • Purpose
  • When to use
  • Source Prioritization
  • Primary Sources (ALWAYS search first)
  • 🤖 LLM-Optimized Docs Strategy
  • Critical Rules
  • Never Assume Missing Features
  • Anti-Hallucination Guard
  • Search Strategy
  • 1. Classify the Query
  • 2. Search Flow
  • 3. Error-Aware Routing
  • Structured Extraction Rules
  • Commands
  • Concepts

cypress-io/cypress-explain

Catalog entry: Skills by Cypress
Source documentation: https://github.com/cypress-io/ai-toolkit/blob/main/skills/cypress-explain/SKILL.md

Function: Explains Cypress E2E and component tests, and answers questions about Cypress use and behavior.

When to use it: Use when the user asks to explain how a test works, explain how Cypress works, review or critique a test without writing code. Apply even when the user does not say ‘Cypress’ (e.g. ‘explain this test’). Prefer the cypress-author skill when the user wants to create, fix, or update tests.

Usage guidance is taken from the skill’s own trigger description or usage section.

Source skill menu:

  • Cypress Explain
  • Inputs
  • Mandatory flow (do not skip)

dembrandt/dembrandt-skills

Catalog entry: Development and Testing
Source documentation: https://github.com/dembrandt/dembrandt-skills/blob/main/README.md

Function: UX and design system skills: hierarchy, typography, accessibility, interactions

When to use it: Use when a task needs the capability described in this catalog entry: UX and design system skills: hierarchy, typography, accessibility, interactions

The catalog does not state a separate trigger condition. This usage note is inferred from the published function description.

Source skill menu:

  • dembrandt-skills
  • Quick start
  • Usage
  • Skills
  • The engine
  • Contributing
  • License

This catalog entry points to a collection. The scanned repository lists 45 distinct skill-file paths.

Sample members: algorithmic-color-palette · app-shell · authentic-product-representation · brand-visual-language · button-states · clone-website · color-mode-and-theme · component-family-consistency
More members are available in the source repository.

eduardo-sl/go-agent-skills

Catalog entry: Development and Testing
Source documentation: https://github.com/eduardo-sl/go-agent-skills/blob/main/README.md

Function: Curated Go skills for code review, concurrency, testing, and architecture

When to use it: Use when a task needs the capability described in this catalog entry: Curated Go skills for code review, concurrency, testing, and architecture

The catalog does not state a separate trigger condition. This usage note is inferred from the published function description.

Source skill menu:

  • Why
  • Highlights
  • 🚀 Quick start
  • 💬 Usage
  • 🧩 Skills
  • Code Quality
  • Architecture & Design
  • Data
  • Safety & Performance
  • Testing
  • Workflow
  • 🧠 How it works
  • 🧪 Evaluations
  • 🔐 Security
  • 🎚 Customizing
  • 🎯 Design principles

This catalog entry points to a collection. The scanned repository lists 35 distinct skill-file paths.

Sample members: go-api-design · go-architecture-review · go-cli · go-dependency-injection · go-design-patterns · go-graphql · go-grpc · go-interface-design
More members are available in the source repository.

expo/expo-dev-client

Catalog entry: Skills by Expo Team
Source documentation: https://github.com/expo/skills/blob/main/plugins/expo/skills/expo-dev-client/SKILL.md

Function: Build and distribute Expo dev clients locally or via TestFlight

When to use it: Building a dev client after adding a third-party native SDK that isn’t bundled in Expo Go Distributing a custom development build to QA testers via TestFlight Testing iOS widget or app clip extensions on a physical device Running a local build on an Android device with adb install during native module development Switching between multiple Metro bundler URLs on device using the dev client launcher UI

Usage guidance is taken from the skill’s own trigger description or usage section.

Source skill menu:

  • Important: When Development Clients Are Needed
  • EAS Configuration
  • Building for TestFlight
  • Building Locally
  • Installing Local Builds
  • Building for Specific Platform
  • Checking Build Status
  • Using the Dev Client
  • Troubleshooting
  • Submitting Feedback

fishzjp/qa-skills

Catalog entry: Development and Testing
Source documentation: https://github.com/fishzjp/qa-skills/blob/main/README.md

Function: QA engineering for AI coding agents: full lifecycle, measured gains

When to use it: Use when a task needs the capability described in this catalog entry: QA engineering for AI coding agents: full lifecycle, measured gains

The catalog does not state a separate trigger condition. This usage note is inferred from the published function description.

Source skill menu:

  • 快速开始
  • 1. 安装全部 skill
  • 2. 检查安装与装载
  • 3. 提供输入，开始测试
  • 选择 skill
  • 工作原理
  • 兼容性与边界
  • 实测效果
  • 文档导航
  • 贡献与反馈

This catalog entry points to a collection. The scanned repository lists 13 distinct skill-file paths.

Sample members: api-testing · automated-e2e-testing · bug-analysis · core · exploratory-testing · qa-memory · qa · regression-testing
More members are available in the source repository.

flutter/flutter-improving-accessibility

Catalog entry: Skills by Flutter
Source documentation: https://github.com/flutter/skills/blob/main/README.md

Function: Configure Flutter for screen readers and assistive tech

When to use it: Adding screen reader support to custom Flutter widgets Fixing contrast ratio failures flagged in accessibility audits Setting up ARIA role mapping for a Flutter web app Testing layouts with maximum OS font size settings enabled Wrapping decorative elements with ExcludeSemantics to clean up VoiceOver navigation

Usage guidance is taken from the skill’s own trigger description or usage section.

Source skill menu:

  • Flutter Agent Plugins
  • Installation
  • Available Skills
  • Contributing
  • Code of Conduct

flutter/flutter-testing-apps

Catalog entry: Skills by Flutter
Source documentation: https://github.com/flutter/skills/blob/main/README.md

Function: Implement unit, widget, and integration tests

When to use it: Writing unit tests for a ViewModel that depends on multiple repositories Testing a widget’s layout and tap interactions without launching the full app Running integration tests on Android emulators or Firebase Test Lab Adding platform-specific native tests for a Flutter plugin Setting up a test suite for a new feature with fakes instead of mocks

Usage guidance is taken from the skill’s own trigger description or usage section.

Source skill menu:

  • Flutter Agent Plugins
  • Installation
  • Available Skills
  • Contributing
  • Code of Conduct

forjd/better-writing

Catalog entry: Productivity and Collaboration
Source documentation: https://github.com/forjd/better-writing/blob/main/skills/better-writing/SKILL.md

Function: Rewrites AI-sounding prose without inventing facts; eval-tested

When to use it: Use when improving emails, reports, documentation, marketing copy, UI text, or posts that sound generic, AI-written, verbose, salesy, or formulaic, and when the user asks to humanise/humanize, de-AI, fix text that sounds like ChatGPT, light edit, copy edit, proofread, or keep my voice. Covers voice calibration, anti-slop audits, and preflight checks.

Usage guidance is taken from the skill’s own trigger description or usage section.

Source skill menu:

  • Better Writing
  • Core workflow
  • Default output
  • Editing principles
  • Guardrails
  • References

foryourhealth111-pixel/Vibe-Skills

Catalog entry: Development and Testing
Source documentation: https://github.com/foryourhealth111-pixel/Vibe-Skills/blob/main/SKILL.md

Function: A skills governed plug-and-play harness for staged, test-driven skill orchestration

When to use it: Use when a task needs the capability described in this catalog entry: A skills governed plug-and-play harness for staged, test-driven skill orchestration

The catalog does not state a separate trigger condition. This usage note is inferred from the published function description.

Source skill menu:

  • Vibe Governed Runtime Entry
  • Trigger Contract
  • Canonical Bootstrap
  • Consensus And Task Evolution
  • Hard Stop And Re-entry
  • Unified Runtime Contract
  • Skill Execution
  • Quality Rules
  • User Delivery
  • Protocol Map
  • Maintenance

frmoretto/clarity-gate

Catalog entry: Specialized Domains
Source documentation: https://github.com/frmoretto/clarity-gate/blob/main/skills/clarity-gate/SKILL.md

Function: Epistemic quality verification for RAG systems

When to use it: Use when a task needs the capability described in this catalog entry: Epistemic quality verification for RAG systems

The catalog does not state a separate trigger condition. This usage note is inferred from the published function description.

Source skill menu:

  • agentskills.io compliant frontmatter
  • Clarity Gate v2.1
  • What’s New in v2.1
  • Specifications
  • Validation Codes
  • HITL Claim Validation (§1.3.2-1.3.3)
  • Body Structure (§1.2.1)
  • SOT Table Validation (§3.1)
  • Bundled Scripts
  • scripts/claim_id.py
  • scripts/document_hash.py
  • The Key Distinction
  • Critical Limitation
  • When to Use
  • The 9 Verification Points
  • Relationship to Spec Suite

fvadicamo/dev-agent-skills

Catalog entry: Development and Testing
Source documentation: https://github.com/fvadicamo/dev-agent-skills/blob/main/README.md

Function: Git and GitHub workflow skills for commits, PRs, and code reviews

When to use it: Use when a task needs the capability described in this catalog entry: Git and GitHub workflow skills for commits, PRs, and code reviews

The catalog does not state a separate trigger condition. This usage note is inferred from the published function description.

Source skill menu:

  • dev-agent-skills
  • Why these skills?
  • Quick install
  • How skills work
  • Plugin: github-workflow
  • git-commit
  • github-pr-creation
  • github-pr-merge
  • github-pr-review
  • Plugin: skill-authoring
  • creating-skills
  • Plugin: guardrails
  • guard-destructive
  • Plugin: privacy-guard
  • privacy-guard
  • Plugin: decision-records

This catalog entry points to a collection. The scanned repository lists 7 distinct skill-file paths.

Sample members: decision-records · git-commit · github-pr-creation · github-pr-merge · github-pr-review · privacy-guard · creating-skills

gal-a/qikly

Catalog entry: Development and Testing
Source documentation: https://github.com/gal-a/qikly/blob/main/.claude/skills/qikly/SKILL.md

Function: Writes pytest suites from criteria the coding agent never sees

When to use it: Use when someone does not trust a suite that passes. Use when they want tests written from a specification rather than from the code. Use when they ask whether a specification is testable, or want an existing suite scored by planting faults in the code. Python modules, through the qikly tool. Also use whenever qikly or spec-driven testing is mentioned.

Usage guidance is taken from the skill’s own trigger description or usage section.

Source skill menu:

  • qikly: tests written from a spec the coder never read
  • What this is for
  • The request this arrives as, and what to do with it
  • Ask economically, or you will lose them
  • Install
  • The one question that decides everything
  • Writing criteria that can be tested
  • The five steps, on the user’s own module
  • The free checks, and when to reach for each
  • When a run does not converge
  • What to tell the user honestly
  • References, and when to open them

garrytan/browse

Catalog entry: Skills by Garry Tan (gstack)
Source documentation: https://github.com/garrytan/gstack/blob/main/browse/SKILL.md

Function: Real Chromium browser for QA: real clicks, real screenshots, ~100ms per command

When to use it: Taking annotated screenshots of a broken UI state to attach to a bug report Verifying a login flow works end-to-end after a backend change Checking mobile, tablet, and desktop layouts in one command Comparing staging and production pages to catch unintended differences Testing file upload and dialog behavior without touching a real browser

Usage guidance is taken from the skill’s own trigger description or usage section.

Source skill menu:

  • Preamble (run first)
  • Plan Mode Safe Operations
  • Skill Invocation During Plan Mode
  • Artifacts Sync (skill start)
  • Model-Specific Behavioral Patch (claude)
  • Voice
  • Completion Status Protocol
  • Operational Self-Improvement
  • Telemetry (run last)
  • Plan Status Footer
  • browse: give the agent eyes
  • BROWSER SETUP (Aside — run this check BEFORE any browser step)
  • Rules for driving a real browser
  • Browser fallback: gstack’s own headless browser
  • Find the `$B` binary
  • Translate the Aside scripts step by step

garrytan/canary

Catalog entry: Skills by Garry Tan (gstack)
Source documentation: https://github.com/garrytan/gstack/blob/main/canary/SKILL.md

Function: SRE post-deploy monitoring: watches for console errors, performance regressions, and page failures

When to use it: Catching a missing env var that breaks the dashboard only in production Detecting a 3x load time regression introduced by a new database query Comparing homepage screenshots before and after a CSS deploy Running a quick post-deploy health check across all main nav pages Alerting on new JavaScript console errors that CI never caught

Usage guidance is taken from the skill’s own trigger description or usage section.

Source skill menu:

  • Shared preamble (load first)
  • Preamble (run first)
  • Question Tuning (skip entirely if `QUESTION_TUNING: false`)
  • Telemetry (run last)
  • BROWSER SETUP (Aside — run this check BEFORE any browser step)
  • Rules for driving a real browser
  • Browser fallback: gstack’s own headless browser
  • Find the `$B` binary
  • Translate the Aside scripts step by step
  • What changes without Aside
  • Step 0: Detect platform and base branch
  • /canary — Post-Deploy Visual Monitor
  • User-invocable
  • Arguments
  • Instructions
  • Phase 1: Setup

garrytan/freeze

Catalog entry: Skills by Garry Tan (gstack)
Source documentation: https://github.com/garrytan/gstack/blob/main/freeze/SKILL.md

Function: Edit Lock: restrict file edits to one directory while debugging

When to use it: Scoping a refactor to one module without risking changes to shared utilities Debugging a specific package while keeping the rest of the codebase untouched Reviewing a PR’s changed directory without accidentally editing unrelated files Onboarding to a codebase by limiting writes to a sandbox folder Isolating config changes to a single service directory during incident response

Usage guidance is taken from the skill’s own trigger description or usage section.

Source skill menu:

  • /freeze — Restrict Edits to a Directory
  • Setup
  • How it works
  • Notes

garrytan/gstack-upgrade

Catalog entry: Skills by Garry Tan (gstack)
Source documentation: https://github.com/garrytan/gstack/blob/main/gstack-upgrade/SKILL.md

Function: Self-Updater: upgrade gstack to latest version

When to use it: Upgrading gstack after a new release without manually running git commands Syncing a vendored local copy of gstack when the global install is already up to date Configuring auto-upgrades so gstack updates silently on future skill invocations Reviewing the changelog between your current version and the latest before deciding to upgrade Recovering a local vendored copy when it falls behind the global install version

Usage guidance is taken from the skill’s own trigger description or usage section.

Source skill menu:

  • /gstack-upgrade
  • Inline upgrade flow
  • Step 1: Ask the user (or auto-upgrade)
  • Step 2: Detect install type
  • Step 3: Save old version
  • Step 4: Upgrade
  • Step 4.5: Handle local vendored copy
  • Step 4.75: Run version migrations
  • Step 4.8: Stop any stale daemon (unconditional)
  • Step 5: Write marker + clear cache
  • Step 6: Show What’s New
  • Step 7: Continue
  • Standalone usage

garrytan/investigate

Catalog entry: Skills by Garry Tan (gstack)
Source documentation: https://github.com/garrytan/gstack/blob/main/investigate/SKILL.md

Function: Systematic root-cause debugging: no fixes without investigation, traces data flow, tests hypotheses

When to use it: Tracing why a regression appeared after a recent commit Debugging intermittent failures that only show up in staging Finding the root cause of a null reference before patching it Running a structured post-mortem on a bug that keeps coming back Diagnosing configuration drift between local and production environments

Usage guidance is taken from the skill’s own trigger description or usage section.

Source skill menu:

  • Shared preamble (load first)
  • Preamble (run first)
  • Question Tuning (skip entirely if `QUESTION_TUNING: false`)
  • Telemetry (run last)
  • Systematic Debugging
  • Iron Law
  • Arguments
  • Section index — Read each section when its situation applies
  • Phase 1: Root Cause Investigation
  • Prior Learnings
  • Refresh learnings for the hypothesis you just named
  • Scope Lock
  • Web research runs in Aside
  • Phase 2: Pattern Analysis
  • Recipes
  • Phase 3: Hypothesis Testing

garrytan/plan-eng-review

Catalog entry: Skills by Garry Tan (gstack)
Source documentation: https://github.com/garrytan/gstack/blob/main/plan-eng-review/SKILL.md

Function: Eng Manager review: lock in architecture, data flow, diagrams, edge cases, and tests

When to use it: Running an architecture review on a feature plan before any code is written Getting a test coverage diagram that maps every code path to existing or missing tests Reviewing data flow designs to catch N+1 queries and bottlenecks before implementation Walking through scope reduction when a plan touches too many files or introduces too many abstractions Locking in a ‘NOT in scope’ list with rationale before a coding sprint begins

Usage guidance is taken from the skill’s own trigger description or usage section.

Source skill menu:

  • Plan Review Mode
  • Scope gate (FIRST — overrides everything below). This is a hard STOP.
  • Shared preamble (load first)
  • Preamble (after scope gate)
  • Skill Invocation During Plan Mode
  • AskUserQuestion Format
  • Tool resolution (read first)
  • When AskUserQuestion is unavailable or a call fails
  • Format
  • Self-check before emitting
  • Question Tuning (skip entirely if `QUESTION_TUNING: false`)
  • Repo Ownership — See Something, Say Something
  • Search Before Building
  • Telemetry (run last)
  • Plan Status Footer
  • Priority hierarchy

garrytan/qa

Catalog entry: Skills by Garry Tan (gstack)
Source documentation: https://github.com/garrytan/gstack/blob/main/qa/SKILL.md

Function: QA Lead: test your app, find bugs, fix them with atomic commits, auto-generate regression tests

When to use it: Running Quick-tier checks before merging a feature branch Testing every form and interactive element on a Rails or Next.js app Getting a health score delta after a batch of bug fixes Verifying that a new checkout flow works end-to-end with screenshot evidence Automatically filing regression tests for each bug fixed during a QA session

Usage guidance is taken from the skill’s own trigger description or usage section.

Source skill menu:

  • Shared preamble (load first)
  • Preamble (run first)
  • Question Tuning (skip entirely if `QUESTION_TUNING: false`)
  • Repo Ownership — See Something, Say Something
  • Search Before Building
  • Telemetry (run last)
  • Step 0: Detect platform and base branch
  • /qa: Test → Fix → Verify
  • Section index — Read each section when its situation applies
  • Setup
  • Prior Learnings
  • Test Plan Context
  • Phases 1-6: QA Baseline
  • Output Structure
  • Phase 7: Triage
  • Refresh learnings for the component/page where the bug lives

garrytan/qa-only

Catalog entry: Skills by Garry Tan (gstack)
Source documentation: https://github.com/garrytan/gstack/blob/main/qa-only/SKILL.md

Function: QA Reporter: same methodology as /qa but report only, no code changes

When to use it: Getting a health score for a staging URL before a release review Auditing a feature branch for bugs without touching the code Documenting reproduction steps for issues to hand off to another developer Running a smoke test on a deployed app after a dependency update Building a baseline report to compare against after future changes

Usage guidance is taken from the skill’s own trigger description or usage section.

Source skill menu:

  • Shared preamble (load first)
  • Preamble (run first)
  • Question Tuning (skip entirely if `QUESTION_TUNING: false`)
  • Repo Ownership — See Something, Say Something
  • Search Before Building
  • Telemetry (run last)
  • /qa-only: Report-Only QA Testing
  • Section index — Read each section when its situation applies
  • Request Parameters
  • Test Plan Context
  • Prior Learnings
  • Select Surfaces and Isolation
  • Prepare Report Artifacts
  • Browser Setup (conditional)
  • Run the Selected Checks
  • Output

garrytan/review

Catalog entry: Skills by Garry Tan (gstack)
Source documentation: https://github.com/garrytan/gstack/blob/main/review/SKILL.md

Function: Staff Engineer code review: finds bugs that pass CI but blow up in production

When to use it: Catching SQL injection risks in a feature branch before it hits code review Auditing LLM output handling when writing AI-generated content to a database Verifying a branch covers every item in a plan file before opening a PR Running a multi-model adversarial pass on a large refactor to surface edge cases Spotting scope creep when a branch touches files outside its stated intent

Usage guidance is taken from the skill’s own trigger description or usage section.

Source skill menu:

  • Shared preamble (load first)
  • Preamble (run first)
  • Question Tuning (skip entirely if `QUESTION_TUNING: false`)
  • Repo Ownership — See Something, Say Something
  • Search Before Building
  • Telemetry (run last)
  • Step 0: Detect platform and base branch
  • Pre-Landing PR Review
  • Section index — Read each section when its situation applies
  • Step 1: Check branch
  • Step 1.5: Scope Drift Detection
  • Step 2: Read the checklist
  • Step 2.5: Check for Greptile review comments
  • Step 3: Get the diff
  • Step 3.4: Workspace-aware queue status (advisory)
  • Step 3.5: Diff scans

garrytan/ship

Catalog entry: Skills by Garry Tan (gstack)
Source documentation: https://github.com/garrytan/gstack/blob/main/ship/SKILL.md

Function: Release Engineer: sync main, run tests, audit coverage, push, open PR

When to use it: Shipping a feature branch to PR without writing changelog entries by hand Running tests against the merged base branch before pushing to catch merge-induced failures Separating pre-existing test failures from failures your branch actually introduced Getting an automated code review, version bump, and PR opened in a single command Auto-marking TODOS.md items as completed when their related code ships

Usage guidance is taken from the skill’s own trigger description or usage section.

Source skill menu:

  • Shared preamble (load first)
  • Preamble (run first)
  • Question Tuning (skip entirely if `QUESTION_TUNING: false`)
  • Repo Ownership — See Something, Say Something
  • Search Before Building
  • Telemetry (run last)
  • Third-Party Web Actions
  • Ship: Fully Automated Ship Workflow
  • Keep state between steps
  • Ship control flow
  • Section index — Read each section when its situation applies
  • Step 0: Detect platform and base branch
  • Step 0.9: Apple target detection
  • Step 1: Pre-flight
  • Review Readiness Dashboard
  • Step 2: Distribution Pipeline Check

getsentry/sentry-code-review

Catalog entry: Skills by Sentry team for their dev team.
Source documentation: https://github.com/getsentry/sentry-for-ai/blob/main/README.md

Function: Review code changes using Sentry issue and trace context

When to use it: Reviewing a PR for regressions flagged by Sentry issue history Addressing Sentry bot comments left on a PR Finding recent PRs that have open Sentry feedback to act on Using trace data to confirm whether a change fixes a live issue Spot-checking a PR against recent production errors in the touched files

Usage guidance is taken from the skill’s own trigger description or usage section.

Source skill menu:

  • Sentry for AI
  • What You Can Do
  • Distribution
  • Build it yourself
  • Skills
  • Core
  • Feature Setup
  • Reference Library
  • Prerequisites
  • Contributing
  • License

getsentry/sentry-pr-code-review

Catalog entry: Skills by Sentry team for their dev team.
Source documentation: https://github.com/getsentry/sentry-for-ai/blob/main/README.md

Function: Review PR comments from Seer Bug Prediction and Sentry feedback

When to use it: Addressing Seer Bug Prediction comments on an open PR Finding recent PRs with outstanding Sentry review feedback Responding to Sentry bot review comments across multiple PRs Triaging predicted bugs before merging a release branch Standardizing how PR feedback from Sentry is handled

Usage guidance is taken from the skill’s own trigger description or usage section.

Source skill menu:

  • Sentry for AI
  • What You Can Do
  • Distribution
  • Build it yourself
  • Skills
  • Core
  • Feature Setup
  • Reference Library
  • Prerequisites
  • Contributing
  • License

gokapso/observe-whatsapp

Catalog entry: Productivity and Collaboration
Source documentation: https://github.com/gokapso/agent-skills/blob/master/skills/observe-whatsapp/SKILL.md

Function: Debug WhatsApp delivery issues and run health checks

When to use it: Use when investigating production issues, message failures, workflow behavior, or webhook delivery problems.

Usage guidance is taken from the skill’s own trigger description or usage section.

Source skill menu:

  • Observe WhatsApp
  • When to use
  • Setup
  • How to
  • Search logs
  • Investigate message delivery
  • Triage errors
  • Run health checks
  • Scripts
  • Messages
  • Errors and logs
  • Health
  • OpenAPI
  • Notes
  • References
  • Related skills

half144/cutaway

Catalog entry: Development and Testing
Source documentation: https://github.com/half144/cutaway

Function: Record polished demo videos of web flows with Playwright

When to use it: Use when a task needs the capability described in this catalog entry: Record polished demo videos of web flows with Playwright

The catalog does not state a separate trigger condition. This usage note is inferred from the published function description.

No individual SKILL.md was retrieved; this entry is based on the catalog description and available repository README.

hermes-labs-ai/lintlang

Catalog entry: Development and Testing
Source documentation: https://github.com/hermes-labs-ai/lintlang/blob/main/.agents/skills/lintlang/SKILL.md

Function: Lint agent instructions for ambiguous tools and missing bounds

When to use it: Use when writing or reviewing AI agent configs, system prompts, or tool definitions (JSON/YAML/Python) and you need to catch ambiguous tool descriptions, missing stop conditions, schema/description mismatches, or embedded prompts before they reach runtime. Deterministic static analysis, no LLM or network calls.

Usage guidance is taken from the skill’s own trigger description or usage section.

Source skill menu:

  • LintLang
  • Use it for
  • Do not use it for
  • Quickstart
  • Output shape
  • Common gotchas
  • More

JasonColapietro/suede-creator-skills

Catalog entry: Development and Testing
Source documentation: https://github.com/JasonColapietro/suede-creator-skills/blob/main/README.md

Function: Design, UI polish, code review grading, AI evals, SEO audits.

When to use it: Use when a task needs the capability described in this catalog entry: Design, UI polish, code review grading, AI evals, SEO audits.

The catalog does not state a separate trigger condition. This usage note is inferred from the published function description.

Source skill menu:

  • Suede Awesome Everything
  • Recognition and discovery
  • Suede AI Skills for SEO and business growth
  • Install in 30 seconds
  • Find it on
  • Try it right now
  • Orchestration: broad outcomes, adversarial review
  • The A–F ship grade
  • The skills
  • Agent orchestration & workflows
  • Code quality & shipping
  • Design, copy & SEO
  • Mobile apps
  • Creator rights & release
  • Marketing & growth
  • From the blog

This catalog entry points to a collection. The scanned repository lists 67 distinct skill-file paths.

Sample members: android-app-factory · site-to-ios-app · suede-ab-testing · suede-ad-creative · suede-ads · suede-agent-teams · suede-ai-eval · suede-ai-seo
More members are available in the source repository.

kulchankas/paranoid

Catalog entry: Development and Testing
Source documentation: https://github.com/kulchankas/paranoid/blob/main/skills/paranoid/SKILL.md

Function: Pentests your running app: find, prove, patch, re-verify

When to use it: Use when a task needs the capability described in this catalog entry: Pentests your running app: find, prove, patch, re-verify

The catalog does not state a separate trigger condition. This usage note is inferred from the published function description.

Source skill menu:

  • paranoid
  • 1. Name the trust boundary (one line, out loud)
  • 2. Secure defaults per risk class
  • Hard “never introduce” list
  • 3. Try to break it before “done”
  • Scope & safety

lackeyjb/playwright-skill

Catalog entry: Development and Testing
Source documentation: https://github.com/lackeyjb/playwright-skill/blob/main/skills/playwright-skill/SKILL.md

Function: Browser automation with Playwright

When to use it: Use when the user wants to test a website, automate browser interactions, validate web functionality, or perform browser-based testing.

Usage guidance is taken from the skill’s own trigger description or usage section.

Source skill menu:

  • Playwright Browser Automation
  • Path resolution
  • Workflow
  • Setup
  • Minimal example
  • Current Playwright patterns
  • Common tasks
  • Responsive checks
  • Login flow
  • Save scripts and artifacts
  • Connect to an existing Chrome session
  • Helpers
  • Configuration

LambdaTest/agent-skills

Catalog entry: Development and Testing
Source documentation: https://github.com/LambdaTest/agent-skills/blob/main/README.md

Function: TestMu AI (Formerly LambdaTest) Skills is a curated collection of Agent Skills that teach AI coding assistants how to write production-grade test automation.

When to use it: Use when a task needs the capability described in this catalog entry: TestMu AI (Formerly LambdaTest) Skills is a curated collection of Agent Skills that teach AI coding assistants how to write production-grade test automation.

The catalog does not state a separate trigger condition. This usage note is inferred from the published function description.

Source skill menu:

  • TestMu AI (Formerly LambdaTest) Skills
  • Getting Started
  • Prerequisites
  • Setup
  • Run tests
  • Local testing with TestMu AI Tunnel
  • Rook: Skills for Testing AI Agents
  • Contributions
  • TestMu AI (Formerly LambdaTest) Community
  • TestMu AI (Formerly LambdaTest) Certifications
  • Learning Resources by TestMu AI (Formerly LambdaTest)
  • LambdaTest is Now TestMu AI
  • How LambdaTest Evolved into TestMu AI
  • Support

This catalog entry points to a collection. The scanned repository lists 74 distinct skill-file paths.

Sample members: accessibility-skill · ai-based-api · api-analyzer · api-compliance · api-designer · api-documentation · api-health-monitoring · api-inference-from-files
More members are available in the source repository.

laolaoshiren/zh-code-reviewer

Catalog entry: Development and Testing
Source documentation: https://github.com/laolaoshiren/claude-code-skills-zh/blob/main/skills/zh-code-reviewer/SKILL.md

Function: Chinese-output code review skill with structured findings and fix suggestions

When to use it: Use when a task needs the capability described in this catalog entry: Chinese-output code review skill with structured findings and fix suggestions

The catalog does not state a separate trigger condition. This usage note is inferred from the published function description.

Source skill menu:

  • 中文代码审查专家
  • 触发条件
  • 工作流程
  • 输出格式
  • 注意事项

mailtrap/mailtrap-skills

Catalog entry: Marketing
Source documentation: https://github.com/mailtrap/mailtrap-skills/blob/main/README.md

Function: Send emails via API/SMTP with sandbox testing

When to use it: Use when a task needs the capability described in this catalog entry: Send emails via API/SMTP with sandbox testing

The catalog does not state a separate trigger condition. This usage note is inferred from the published function description.

Source skill menu:

  • Mailtrap user skills
  • Standard
  • Install
  • Plugin
  • Manual install
  • Tokens and account_id
  • Contents
  • References

This catalog entry points to a collection. The scanned repository lists 7 distinct skill-file paths.

Sample members: authorizing-api-requests · converting-email-templates · managing-contacts · sending-emails · setting-up-sending-domain · testing-with-sandbox · using-email-templates

meodai/skill.color-expert

Catalog entry: Specialized Domains
Source documentation: https://github.com/meodai/skill.color-expert/blob/main/SKILL.md

Function: Color science expert skill with 286K words of reference material covering OKLCH/OKLAB, palette generation, accessibility/contrast, color naming, pigment mixing, and historical color theory

When to use it: Use when working with color naming, color theory, color spaces, color definitions, or any task involving color knowledge - palettes, ramps, gradients, conversions, accessibility, perceptual matching, pigment mixing, print-vs-screen color, CSS color syntax, or historical color terminology. Use this skill whenever the user is choosing, comparing, generating, naming, converting, or explaining colors, even if they do not explicitly ask for “color theory.“

Usage guidance is taken from the skill’s own trigger description or usage section.

Source skill menu:

  • Color Expert
  • How to Use This Skill
  • Color Spaces — What to Use When
  • Understanding HSL’s Limitations
  • Named Hue (HSL/HSV) Ranges
  • Key Distinctions
  • Gamut Mapping in Practice
  • Implementation Guidance — Code and CSS
  • CSS Color 4/5 — Syntax Cheat Sheet
  • Accessibility — Key Numbers
  • Color Harmony — What Actually Works
  • Hue-first harmony is a weak standalone heuristic
  • Character-first harmony works (Ellen Divers’ research)
  • Colour meaning in a story is per-story, not a symbolism table (Lewis Bond)
  • Legibility = lightness variation
  • The 60-30-10 rule

metalbear-co/skills

Catalog entry: Development and Testing
Source documentation: https://github.com/metalbear-co/skills/blob/main/README.md

Function: Skills that let agents code and test against your Kubernetes cluster using mirrord

When to use it: Use when a task needs the capability described in this catalog entry: Skills that let agents code and test against your Kubernetes cluster using mirrord

The catalog does not state a separate trigger condition. This usage note is inferred from the published function description.

Source skill menu:

  • mirrord Agent Skills
  • Installation
  • Claude Code
  • Codex
  • OpenCode
  • Cursor, Gemini, or any other Agent Skills-compatible agent
  • GitHub Copilot, Cline, and other rules-file agents
  • The twelve skills
  • Example prompts
  • Trusted by
  • Data and external services
  • Skill structure
  • Learn more
  • Contributing

This catalog entry points to a collection. The scanned repository lists 12 distinct skill-file paths.

Sample members: mirrord-chaos · mirrord-ci · mirrord-config · mirrord-db-branching · mirrord-header-propagation · mirrord-kafka · mirrord-operator · mirrord-prev-env
More members are available in the source repository.

microsoft/azure-microsoft-playwright-testing-ts

Catalog entry: Skills by Microsoft
Source documentation: https://github.com/microsoft/skills/blob/main/.github/plugins/azure-sdk-typescript/skills/azure-microsoft-playwright-testing-ts/SKILL.md

Function: Playwright tests at scale on Azure

When to use it: Use when scaling browser tests across cloud-hosted browsers, integrating with CI/CD pipelines, or publishing test results to the Azure portal.

Usage guidance is taken from the skill’s own trigger description or usage section.

Source skill menu:

  • Azure Playwright Workspaces SDK for TypeScript
  • Installation
  • Environment Variables
  • Authentication
  • Microsoft Entra Token Credential (Recommended)
  • Custom Credential
  • Core Workflow
  • Service Configuration
  • Run Tests
  • With Azure Reporter
  • Manual Browser Connection
  • Configuration Options
  • ServiceOS Enum
  • ServiceAuth Enum
  • CI/CD Integration
  • GitHub Actions

microsoft/azure-resource-manager-playwright-dotnet

Catalog entry: Skills by Microsoft
Source documentation: https://github.com/microsoft/skills/blob/main/.github/plugins/azure-sdk-dotnet/skills/azure-resource-manager-playwright-dotnet/SKILL.md

Function: Playwright Testing workspace management

When to use it: Creating a Playwright Testing workspace in a specific Azure region Checking whether a workspace name is available before provisioning Listing all Playwright workspaces across a subscription Retrieving subscription-level and workspace-level quota usage Deleting or updating an existing Playwright Testing workspace

Usage guidance is taken from the skill’s own trigger description or usage section.

Source skill menu:

  • Azure.ResourceManager.Playwright (.NET)
  • Installation
  • Environment Variables
  • Authentication
  • Resource Hierarchy
  • Core Workflow
  • 1. Create Playwright Workspace
  • 2. Get Existing Workspace
  • 3. List Workspaces
  • 4. Update Workspace
  • 5. Check Name Availability
  • 6. Get Quota Information
  • 7. Delete Workspace
  • Key Types Reference
  • Workspace Properties
  • Best Practices

MiniMax-AI/android-native-dev

Catalog entry: Skills by MiniMax Team
Source documentation: https://github.com/MiniMax-AI/skills/blob/main/skills/android-native-dev/SKILL.md

Function: Android native development with Kotlin/Jetpack Compose, Material Design 3, and accessibility

When to use it: Setting up Gradle build variants for dev, staging, and prod environments Fixing build errors like Unresolved reference or AAPT resource conflicts Writing coroutine-safe ViewModel code that avoids ANR and UI thread violations Configuring multi-resolution adaptive app icons for all screen densities Adding layered tests with JUnit, Robolectric, and Espresso without version conflicts

Usage guidance is taken from the skill’s own trigger description or usage section.

Source skill menu:

  • 1. Project Scenario Assessment
  • 1.1 Required Files Checklist
  • 2. Project Configuration
  • 2.1 gradle.properties
  • 2.2 Dependency Declaration Standards
  • 2.3 Build Variants & Product Flavors
  • 3. Kotlin Development Standards
  • 3.1 Naming Conventions
  • 3.2 Code Standards (Important)
  • 3.3 Threading & Coroutines (Critical)
  • 3.4 Visibility Rules
  • 3.5 Common Syntax Pitfalls
  • 3.6 Server Response Data Class Fields Must Be Nullable
  • 3.7 Lifecycle Resource Management
  • 3.8 Logging Level Usage
  • 4. Jetpack Compose Standards

MohamedAbdallah-14/unslop

Catalog entry: Marketing
Source documentation: https://github.com/MohamedAbdallah-14/unslop/blob/main/unslop/SKILL.md

Function: Removes named AI writing tells (tricolons, em-dash pileups, hedging stacks, sycophancy openers, stock vocab like “delve”/“crucial”). Split lint/rewrite modes for auditing your own text without auto-rewriting. Five intensity levels, MIT

When to use it: Use when a task needs the capability described in this catalog entry: Removes named AI writing tells (tricolons, em-dash pileups, hedging stacks, sycophancy openers, stock vocab like “delve”/“crucial”). Split lint/rewrite modes for auditing your own text without auto-rewriting. Five intensity levels, MIT

The catalog does not state a separate trigger condition. This usage note is inferred from the published function description.

Source skill menu:

  • Unslop Humanize
  • Purpose
  • Intensity levels (`--mode`)
  • Two-pass audit
  • Trigger
  • Process
  • Humanization Rules
  • Remove (canonical AI-isms)
  • Tighten
  • Preserve EXACTLY (never modify)
  • Preserve structure
  • CRITICAL RULE
  • Pattern (before → after)
  • At `--mode full`, additionally:
  • Reference
  • Boundaries

mongodb/atlas-stream-processing

Catalog entry: Skills by MongoDB
Source documentation: https://github.com/mongodb/agent-skills/blob/main/README.md

Function: Build, operate, and debug Atlas Stream Processing pipelines with Kafka, S3, and Lambda integrations

When to use it: Rolling up Kafka event streams into Atlas collections with tumbling windows Streaming change events from an Atlas cluster to an S3 archive bucket Debugging a FAILED processor stuck in restart loops with diagnose-processor Chaining processors to fan out one source to both Atlas and Kafka sinks Enriching events mid-pipeline with AWS Lambda via $externalFunction

Usage guidance is taken from the skill’s own trigger description or usage section.

Source skill menu:

  • MongoDB Agent Skills
  • Installation
  • Claude
  • Cursor
  • Codex
  • GitHub Copilot CLI
  • VS Code
  • Grok
  • Authentication
  • Installing the skills directly
  • Vercel’s Agent Skills Directory
  • Local install from repository

NeoLabHQ/sadd

Catalog entry: Development and Testing
Source documentation: https://github.com/NeoLabHQ/context-engineering-kit/blob/master/plugins/sadd/README.md

Function: Dispatches independent subagents for individual tasks with code review checkpoints between iterations for rapid, controlled development.

When to use it: Use when a task needs the capability described in this catalog entry: Dispatches independent subagents for individual tasks with code review checkpoints between iterations for rapid, controlled development.

The catalog does not state a separate trigger condition. This usage note is inferred from the published function description.

Source skill menu:

  • SADD Plugin (Subagent-Driven Development)
  • Plugin Target
  • Overview
  • Quick Start
  • New in v2.2 Release
  • Commands Overview
  • Skills Overview
  • Agents Overview
  • Theoretical Foundation
  • Agent Skills for Context Engineering
  • Research Papers
  • Engineering Methodologies

This catalog entry points to a collection. The scanned repository lists 10 distinct skill-file paths.

Sample members: do-and-judge · do-competitively · do-in-parallel · do-in-steps · judge-with-debate · judge · launch-sub-agent · multi-agent-patterns
More members are available in the source repository.

NeoLabHQ/sdd

Catalog entry: Development and Testing
Source documentation: https://github.com/NeoLabHQ/context-engineering-kit/blob/master/plugins/sdd/README.md

Function: Spec-driven development workflow that transforms prompts into production-ready implementations through structured planning, architecture design, and LLM-as-a-Judge based quality gates.

When to use it: Use when a task needs the capability described in this catalog entry: Spec-driven development workflow that transforms prompts into production-ready implementations through structured planning, architecture design, and LLM-as-a-Judge based quality gates.

The catalog does not state a separate trigger condition. This usage note is inferred from the published function description.

Source skill menu:

  • Spec-Driven Development (SDD) Plugin: Continuous Learning + LLM-as-Judge + Agent Swarm
  • Key Features
  • Quick Start
  • Overall Flow
  • Planning Pipeline
  • Sub-Task File Layout
  • Commands
  • Available Agents
  • Patterns
  • Vibe Coding vs. Specification-Driven Development
  • FAQ
  • Theoretical Foundation
  • Core Methodologies
  • Supporting Research

This catalog entry points to a collection. The scanned repository lists 5 distinct skill-file paths.

Sample members: add-task · brainstorm · create-ideas · implement-task · plan-task

obra/receiving-code-review

Catalog entry: Development and Testing
Source documentation: https://github.com/obra/superpowers/blob/main/skills/receiving-code-review/SKILL.md

Function: Process and incorporate code feedback

When to use it: Use when receiving code review feedback, before implementing suggestions, especially if feedback seems unclear or technically questionable - requires technical rigor and verification, not performative agreement or blind implementation

Usage guidance is taken from the skill’s own trigger description or usage section.

Source skill menu:

  • Code Review Reception
  • Overview
  • The Response Pattern
  • Forbidden Responses
  • Handling Unclear Feedback
  • Source-Specific Handling
  • From your human partner
  • From External Reviewers
  • YAGNI Check for “Professional” Features
  • Implementation Order
  • When To Push Back
  • Acknowledging Correct Feedback
  • Gracefully Correcting Your Pushback
  • Common Mistakes
  • Real Examples
  • GitHub Thread Replies

obra/requesting-code-review

Catalog entry: Development and Testing
Source documentation: https://github.com/obra/superpowers/blob/main/skills/requesting-code-review/SKILL.md

Function: Initiate code review processes

When to use it: Use when completing tasks, implementing major features, or before merging to verify work meets requirements

Usage guidance is taken from the skill’s own trigger description or usage section.

Source skill menu:

  • Requesting Code Review
  • When to Request Review
  • How to Request
  • Example
  • Common Rationalizations
  • Red Flags

obra/systematic-debugging

Catalog entry: Development and Testing
Source documentation: https://github.com/obra/superpowers/blob/main/skills/systematic-debugging/SKILL.md

Function: Methodical problem-solving in code

When to use it: Use when encountering any bug, test failure, or unexpected behavior, before proposing fixes

Usage guidance is taken from the skill’s own trigger description or usage section.

Source skill menu:

  • Systematic Debugging
  • Overview
  • The Iron Law
  • When to Use
  • The Four Phases
  • Phase 1: Root Cause Investigation
  • Phase 2: Pattern Analysis
  • Phase 3: Hypothesis and Testing
  • Phase 4: Implementation
  • Red Flags - STOP and Follow Process
  • your human partner’s Signals You’re Doing It Wrong
  • Common Rationalizations
  • Quick Reference
  • When Process Reveals “No Root Cause”
  • Supporting Techniques

obra/test-driven-development

Catalog entry: Development and Testing
Source documentation: https://github.com/obra/superpowers/blob/main/skills/test-driven-development/SKILL.md

Function: Write tests before implementing code

When to use it: Use when implementing any feature or bugfix, before writing implementation code

Usage guidance is taken from the skill’s own trigger description or usage section.

Source skill menu:

  • Test-Driven Development (TDD)
  • Overview
  • When to Use
  • The Iron Law
  • Red-Green-Refactor
  • RED - Write Failing Test
  • Verify RED - Watch It Fail
  • GREEN - Minimal Code
  • Verify GREEN - Watch It Pass
  • REFACTOR - Clean Up
  • Repeat
  • Good Tests
  • Common Rationalizations
  • Red Flags - STOP and Start Over
  • Example: Bug Fix
  • Verification Checklist

omkamal/pypict-skill

Catalog entry: Development and Testing
Source documentation: https://github.com/omkamal/pypict-claude-skill/blob/main/SKILL.md

Function: Pairwise test generation

When to use it: Use when a task needs the capability described in this catalog entry: Pairwise test generation

The catalog does not state a separate trigger condition. This usage note is inferred from the published function description.

Source skill menu:

  • PICT Test Designer
  • When to Use This Skill
  • Workflow
  • 1. Analyze Requirements or Code
  • 2. Generate PICT Model
  • 3. Execute PICT Model
  • 4. Determine Expected Outputs
  • 5. Format Complete Test Suite
  • Output Format
  • Parameters
  • Constraints
  • Best Practices
  • Parameter Identification
  • Constraint Writing
  • Expected Output Definition
  • Scalability

openai/develop-web-game

Catalog entry: Skills by OpenAI
Source documentation: https://github.com/openai/skills/blob/main/README.md

Function: Build and test web games iteratively using Playwright with time-stepping

When to use it: Building a browser-based platformer with automated input testing Debugging sprite collision logic by stepping frames deterministically Validating score and health state changes after each code iteration Resuming a half-finished game build where a previous agent left off Testing keyboard controls like jump, shoot, and pause through scripted action payloads

Usage guidance is taken from the skill’s own trigger description or usage section.

Source skill menu:

  • Agent Skills
  • Installing a skill
  • License

openai/gh-fix-ci

Catalog entry: Skills by OpenAI
Source documentation: https://github.com/openai/skills/blob/main/skills/.curated/gh-fix-ci/SKILL.md

Function: Debug and fix failing GitHub Actions PR checks using log inspection

When to use it: Use when a user asks to debug or fix failing GitHub PR checks that run in GitHub Actions; use `gh` to inspect checks and logs, summarize failure context, draft a fix plan, and implement only after explicit approval. Treat external providers (for example Buildkite) as out of scope and report only the details URL.

Usage guidance is taken from the skill’s own trigger description or usage section.

Source skill menu:

  • Gh Pr Checks Plan Fix
  • Overview
  • Inputs
  • Quick start
  • Workflow
  • Bundled Resources
  • scripts/inspect_pr_checks.py

openai/playwright

Catalog entry: Skills by OpenAI
Source documentation: https://github.com/openai/skills/blob/main/skills/.curated/playwright/SKILL.md

Function: Automate real browser interactions for navigation, forms, and scraping

When to use it: Use when the task requires automating a real browser from the terminal (navigation, form filling, snapshots, screenshots, data extraction, UI-flow debugging) via `playwright-cli` or the bundled wrapper script.

Usage guidance is taken from the skill’s own trigger description or usage section.

Source skill menu:

  • Playwright CLI Skill
  • Prerequisite check (required)
  • Skill path (set once)
  • Quick start
  • Core workflow
  • When to snapshot again
  • Recommended patterns
  • Form fill and submit
  • Debug a UI flow with traces
  • Multi-tab work
  • Wrapper script
  • References
  • Guardrails

openai/playwright-interactive

Catalog entry: Skills by OpenAI
Source documentation: https://github.com/openai/skills/blob/main/skills/.curated/playwright-interactive/SKILL.md

Function: Persistent browser and Electron interaction via js_repl for iterative UI debugging

When to use it: Debugging a local Vite app by reloading only the renderer after a CSS change Testing an Electron desktop app window layout without relaunching the full process each time Running mobile viewport QA on a responsive page at 390x844 alongside a desktop pass Capturing CSS-scaled screenshots for model-assisted coordinate clicking in a running app Checking viewport fit and visible clipping in the initial load state before signoff

Usage guidance is taken from the skill’s own trigger description or usage section.

Source skill menu:

  • Playwright Interactive Skill
  • Preconditions
  • One-time setup
  • Core Workflow
  • Bootstrap (Run Once)
  • Choose Session Mode
  • Start or Reuse Web Session
  • Desktop Web Context
  • Mobile Web Context
  • Native-Window Web Pass
  • Start or Reuse Electron Session
  • Reuse Sessions During Iteration
  • Checklists
  • Session Loop
  • Reload Decision
  • Functional QA

qdrant/skills

Catalog entry: Vector Databases
Source documentation: https://github.com/qdrant/skills/blob/main/README.md

Function: Agent skills for Qdrant vector search, covering scaling, performance optimization, search quality, monitoring, deployment, model migration, version upgrades, and SDK usage across Python, TypeScript, Rust, Go, .NET, and Java

When to use it: Use when a task needs the capability described in this catalog entry: Agent skills for Qdrant vector search, covering scaling, performance optimization, search quality, monitoring, deployment, model migration, version upgrades, and SDK usage across Python, TypeScript, Rust, Go, .NET, and Java

The catalog does not state a separate trigger condition. This usage note is inferred from the published function description.

Source skill menu:

  • Qdrant Skills - Agent Skills for Qdrant Vector Search
  • Philosophy
  • Disclaimer
  • Usage
  • Recommended: install the Qdrant Advisor
  • Alternative: pass the URL directly
  • Offline: install the full skill set
  • Quick Start
  • Skills
  • Installation
  • Qdrant Advisor (recommended)
  • npx skills
  • Claude Code
  • Cursor
  • Clone / Copy
  • MCP Servers

This catalog entry points to a collection. The scanned repository lists 34 distinct skill-file paths.

Sample members: qdrant-advisor · qdrant-clients-sdk · qdrant-deployment-options · qdrant-edge · qdrant-hybrid-cloud-setup · qdrant-managed-cloud-quickstart · qdrant-migration-tool · qdrant-model-migration
More members are available in the source repository.

ramzesenok/iOS-Accessibility-Audit-Skill

Catalog entry: Development and Testing
Source documentation: https://github.com/ramzesenok/iOS-Accessibility-Audit-Skill/blob/main/swiftui-wcag-accessibility-auditor/SKILL.md

Function: Audit iOS App against Accessibility norms

When to use it: Use when reviewing SwiftUI views/screens (including auth, forms, settings, and custom controls) and you need both standards traceability (WCAG + WCAG2Mobile interpretation) and practical, minimal code changes in a concise priority-grouped Markdown format with user follow-up checks for code-indeterminate behavior.

Usage guidance is taken from the skill’s own trigger description or usage section.

Source skill menu:

  • SwiftUI WCAG Accessibility Auditor
  • Overview
  • When to Use This Skill vs Nearby Skills
  • Load Order
  • Scope Rules
  • Audit Execution (Merged Workflow)
  • Output Format (Strict, Concise)
  • Practical Search Guidance (SwiftUI-first)
  • Example Requests
  • Resources

realkimbarrett/ad-angle-multiplier

Catalog entry: Advertising Skills by Kim Barrett
Source documentation: https://github.com/realkimbarrett/advertising-skills/blob/main/skills/operator-os/ad-angle-multiplier/SKILL.md

Function: Expand a core idea into multiple distinct ad angles for creative testing

When to use it: Trigger on “more ads”, “creative testing”, “scale campaigns”.

Usage guidance is taken from the skill’s own trigger description or usage section.

Source skill menu:

  • Role
  • Process
  • Output
  • Rules
  • Avoid

sanity-io/content-experimentation-best-practices

Catalog entry: Skills by Sanity Team
Source documentation: https://github.com/sanity-io/agent-toolkit/blob/main/skills/content-experimentation-best-practices/SKILL.md

Function: Content A/B testing and experimentation workflows

When to use it: Use this skill when planning experiments, setting up variants, choosing success metrics, interpreting statistical results, or building experimentation workflows in a CMS or frontend stack.

Usage guidance is taken from the skill’s own trigger description or usage section.

Source skill menu:

  • Content Experimentation Best Practices
  • When to Apply
  • Core Concepts
  • A/B Testing
  • Multivariate Testing
  • Statistical Significance
  • Experimentation Culture
  • References

serpapi/agent-usability-test

Catalog entry: Skills by SerpApi
Source documentation: https://github.com/serpapi/skills/blob/master/skills/agent-usability-test/SKILL.md

Function: Test whether agents can discover and use your tool — the subject under test is the interface, not the agent

When to use it: Measuring whether agents find and call your MCP tool or CLI without coaching Scoring which tool agents pick when competing tools are all available Testing if agents recover from 401s, rate limits, timeouts, and malformed responses Validating documentation changes with old-docs versus new-docs control runs Avoiding false negatives from stale ground truths and leaky test isolation

Usage guidance is taken from the skill’s own trigger description or usage section.

Source skill menu:

  • Failure modes
  • Discovery by integration level
  • Protocol
  • Adversarial conditions (tests your error messages, not agent intelligence)
  • Don’t
  • Sample size
  • Pre-flight checklist (run before committing to full matrix)
  • Not this

shalintripathi/saas-marketing-agents

Catalog entry: Marketing
Source documentation: https://github.com/shalintripathi/saas-marketing-agents/blob/main/README.md

Function: B2B SaaS marketing team: 90 agents, one orchestrator

When to use it: Use when a task needs the capability described in this catalog entry: B2B SaaS marketing team: 90 agents, one orchestrator

The catalog does not state a separate trigger condition. This usage note is inferred from the published function description.

Source skill menu:

  • SaaS Marketing Agents
  • What this is
  • ⚡ Quick start
  • Install as a Claude Code plugin (recommended)
  • Watch it work: the campaign board
  • Then: tell it who you are (15 minutes, biggest quality jump)
  • Or install via the skills CLI (Claude Code, Codex, Cursor & more)
  • Or use the files directly
  • 📋 The team (91 specialist agents)
  • 🧩 Skills
  • 🎛️ CATALYST orchestrator
  • 🔁 Marketing loops
  • 📚 Example workflows
  • 🔎 Built for AI search (AEO/GEO)
  • 🤝 Contributing
  • 📄 License

This catalog entry points to a collection. The scanned repository lists 19 distinct skill-file paths.

Sample members: abm-ops · catalyst-orchestrator · client-operations · comms-ops · content-marketing · design-ops · developer-marketing-ops · email-marketing-ops
More members are available in the source repository.

siril9/presentation-skill

Catalog entry: Productivity and Collaboration
Source documentation: https://github.com/siril9/presentation-skill/blob/main/SKILL.md

Function: Generate editable PowerPoint decks from source with visual QA.

When to use it: Use when a task needs the capability described in this catalog entry: Generate editable PowerPoint decks from source with visual QA.

The catalog does not state a separate trigger condition. This usage note is inferred from the published function description.

Source skill menu:

  • Presentation Skill
  • Core Contract
  • Choose A Route
  • Clarify Only What Matters
  • Quick Deck
  • Saved Workspace
  • Existing PPTX
  • Model Profiles
  • Design Decisions
  • Data And Figures
  • QA And Delivery
  • Progressive References
  • Development

supercorp-ai/supercov

Catalog entry: Development and Testing
Source documentation: https://github.com/supercorp-ai/supercov/blob/main/plugins/supercov/skills/supercov/SKILL.md

Function: Measure test coverage and write tests for untested code

When to use it: Use when the user asks to add or improve tests, find untested code or raise coverage, or find what to refactor. Works with JavaScript, TypeScript, Python, Ruby, Rust, Go, Java and Kotlin projects.

Usage guidance is taken from the skill’s own trigger description or usage section.

Source skill menu:

  • Supercov
  • Add a test
  • Quality

talkstream/ru-text

Catalog entry: Specialized Domains
Source documentation: https://github.com/talkstream/ru-text/blob/main/skills/ru-text/SKILL.md

Function: Russian text quality: ~1,040 rules for typography, info-style, editorial, UX writing, business correspondence. Cross-platform: Claude Code, Codex CLI, Gemini CLI, Cursor.

When to use it: Use when a task needs the capability described in this catalog entry: Russian text quality: ~1,040 rules for typography, info-style, editorial, UX writing, business correspondence. Cross-platform: Claude Code, Codex CLI, Gemini CLI, Cursor.

The catalog does not state a separate trigger condition. This usage note is inferred from the published function description.

Source skill menu:

  • ru-text — Russian Text Quality
  • Always-On: Typography
  • Top Stop-Words (when writing or editing on request)
  • When to Load Reference Files
  • Quality Checklist

testdino-hq/playwright-skill

Catalog entry: Development and Testing
Source documentation: https://github.com/testdino-hq/playwright-skill/blob/main/SKILL.md

Function: 70+ production-tested Playwright automation testing patterns: E2E, POM, CI/CD, migrations, CLI

When to use it: Use when a task needs the capability described in this catalog entry: 70+ production-tested Playwright automation testing patterns: E2E, POM, CI/CD, migrations, CLI

The catalog does not state a separate trigger condition. This usage note is inferred from the published function description.

Source skill menu:

  • Playwright Skill
  • Newer APIs (1.59–1.64) You May Not Know
  • Security Trust Boundary
  • Golden Rules
  • Guide Index
  • Writing Tests
  • Authoring Locatable Markup (Frontend)
  • QA Workflows
  • Debugging & Fixing
  • Framework Recipes
  • Migration Guides
  • Architecture Decisions
  • CI/CD & Infrastructure
  • Specialized Topics
  • CLI Browser Automation
  • Language Note

testmu-ai/api-skill

Catalog entry: Skills by TestMu AI
Source documentation: https://github.com/LambdaTest/agent-skills/blob/main/api-skill/README.md

Function: Suite of API skills for designing, mocking, documenting, securing, and generating tests for REST/GraphQL/gRPC APIs

When to use it: Use when a task needs the capability described in this catalog entry: Suite of API skills for designing, mocking, documenting, securing, and generating tests for REST/GraphQL/gRPC APIs

The catalog does not state a separate trigger condition. This usage note is inferred from the published function description.

Source skill menu:

  • api-skills
  • What is this?
  • Repository Structure
  • Getting Started
  • Skill Format
  • Contributing
  • Why This Exists
  • License

This catalog entry points to a collection. The scanned repository lists 24 distinct skill-file paths.

Sample members: ai-based-api · api-analyzer · api-compliance · api-designer · api-documentation · api-health-monitoring · api-inference-from-files · api-integration-helper
More members are available in the source repository.

testmu-ai/appium-skill

Catalog entry: Skills by TestMu AI
Source documentation: https://github.com/LambdaTest/agent-skills/blob/main/appium-skill/SKILL.md

Function: Generate Appium mobile automation for Android and iOS in Java, Python, or JS

When to use it: Use when the user asks to automate mobile apps, test on Android/iOS, write Appium tests, or mentions “Appium”, “mobile testing”, “real device”, “app automation”. Triggers on: “Appium”, “mobile test”, “Android test”, “iOS test”, “real device”, “app automation”, “UiAutomator”, “XCUITest driver”, “TestMu”, “LambdaTest”.

Usage guidance is taken from the skill’s own trigger description or usage section.

Source skill menu:

  • Appium Automation Skill
  • Step 1 — Execution Target
  • Step 2 — Platform Detection
  • Step 3 — Language Detection
  • Core Patterns — Java (Default)
  • Desired Capabilities — Android
  • Desired Capabilities — iOS
  • Locator Strategy Priority
  • Wait Strategy
  • Gestures
  • Anti-Patterns
  • Test Structure (JUnit 5)
  • TestMu AI Cloud — Quick Setup
  • Test Status Reporting
  • Validation Workflow
  • Quick Reference

testmu-ai/behat-skill

Catalog entry: Skills by TestMu AI
Source documentation: https://github.com/LambdaTest/agent-skills/blob/main/behat-skill/SKILL.md

Function: Generate Behat BDD tests for PHP with Gherkin and Mink

When to use it: Use when user mentions “Behat”, “PHP BDD”, “Mink”, “behat.yml”. Triggers on: “Behat”, “PHP BDD”, “Mink”, “behat.yml”, “FeatureContext PHP”.

Usage guidance is taken from the skill’s own trigger description or usage section.

Source skill menu:

  • Behat BDD Skill
  • Core Patterns
  • Feature File (features/login.feature)
  • Custom Context (features/bootstrap/LoginContext.php)
  • Built-in MinkContext Steps
  • behat.yml
  • Tags
  • Setup: `composer require --dev behat/behat behat/mink-extension behat/mink-selenium2-driver`
  • Init: `./vendor/bin/behat --init`
  • Cloud Execution on TestMu AI
  • Run: `./vendor/bin/behat` or `./vendor/bin/behat features/login.feature`
  • Deep Patterns

testmu-ai/behave-skill

Catalog entry: Skills by TestMu AI
Source documentation: https://github.com/LambdaTest/agent-skills/blob/main/behave-skill/SKILL.md

Function: Generate Behave BDD tests for Python with Gherkin and step implementations

When to use it: Use when user mentions “Behave”, “Python BDD”, “Python Gherkin”. Triggers on: “Behave”, “Python BDD”, “behave test”, “Python feature file”.

Usage guidance is taken from the skill’s own trigger description or usage section.

Source skill menu:

  • Behave BDD Skill
  • Core Patterns
  • Feature File (features/login.feature)
  • Step Definitions (features/steps/login_steps.py)
  • Environment Hooks (features/environment.py)
  • Tags
  • Setup: `pip install behave selenium`
  • Run: `behave` or `behave features/login.feature`
  • Cloud Execution on TestMu AI
  • Report: `behave --format json -o report.json`
  • Deep Patterns

testmu-ai/capybara-skill

Catalog entry: Skills by TestMu AI
Source documentation: https://github.com/LambdaTest/agent-skills/blob/main/capybara-skill/SKILL.md

Function: Generate Capybara E2E tests in Ruby with RSpec integration

When to use it: Use when user mentions “Capybara”, “visit”, “fill_in”, “click_button”, “Ruby E2E”. Triggers on: “Capybara”, “Ruby acceptance test”, “fill_in”, “click_button”, “have_content”.

Usage guidance is taken from the skill’s own trigger description or usage section.

Source skill menu:

  • Capybara Automation Skill
  • Core Patterns
  • Basic Test (RSpec)
  • DSL
  • Within Scope
  • TestMu AI Cloud
  • Setup: `gem ‘capybara’` + `gem ‘selenium-webdriver’` in Gemfile
  • Run: `bundle exec rspec spec/features/`
  • Cloud (TestMu AI)
  • Deep Patterns

testmu-ai/codeception-skill

Catalog entry: Skills by TestMu AI
Source documentation: https://github.com/LambdaTest/agent-skills/blob/main/codeception-skill/SKILL.md

Function: Generate Codeception acceptance, functional, and unit tests in PHP

When to use it: Use when user mentions “Codeception”, “$I->amOnPage”, “$I->see”, “Cest”. Triggers on: “Codeception”, “$I->amOnPage”, “AcceptanceTester”, “Codeception PHP”, “Cest”.

Usage guidance is taken from the skill’s own trigger description or usage section.

Source skill menu:

  • Codeception Testing Skill
  • Core Patterns
  • Acceptance Test (Cest)
  • Actor Methods (AcceptanceTester $I)
  • Page Objects (Step Objects)
  • Cloud (TestMu AI)
  • Cloud Config (acceptance.suite.yml)
  • Setup: `composer require --dev codeception/codeception codeception/module-webdriver`
  • Init: `php vendor/bin/codecept bootstrap`
  • Run: `php vendor/bin/codecept run acceptance`
  • Deep Patterns

testmu-ai/cucumber-skill

Catalog entry: Skills by TestMu AI
Source documentation: https://github.com/LambdaTest/agent-skills/blob/main/cucumber-skill/SKILL.md

Function: Generate Cucumber BDD tests with Gherkin and step definitions in Java, JS, or Ruby

When to use it: Use when user mentions “Cucumber”, “Gherkin”, “Feature/Scenario”, “Given/When/Then”, “BDD”. Triggers on: “Cucumber”, “Gherkin”, “BDD”, “Feature file”, “Given/When/Then”, “step definitions”.

Usage guidance is taken from the skill’s own trigger description or usage section.

Source skill menu:

  • Cucumber BDD Skill
  • Core Patterns
  • Feature File (Gherkin)
  • Step Definitions — Java
  • Step Definitions — JavaScript
  • Hooks
  • Tags
  • Anti-Patterns
  • Cloud Execution on TestMu AI
  • Quick Reference
  • Deep Patterns → `reference/playbook.md`

testmu-ai/cypress-skill

Catalog entry: Skills by TestMu AI
Source documentation: https://github.com/LambdaTest/agent-skills/blob/main/cypress-skill/SKILL.md

Function: Generate Cypress E2E and component tests in JavaScript or TypeScript

When to use it: Use when the user asks to write Cypress tests, set up Cypress, test with cy commands, or mentions “Cypress”, “cy.visit”, “cy.get”, “cy.intercept”. Triggers on: “Cypress”, “cy.“, “component test”, “E2E test”, “TestMu”, “LambdaTest”.

Usage guidance is taken from the skill’s own trigger description or usage section.

Source skill menu:

  • Cypress Automation Skill
  • Step 1 — Execution Target
  • Step 2 — Test Type
  • Core Patterns
  • Command Chaining — CRITICAL
  • Selector Priority
  • Anti-Patterns
  • Basic Test Structure
  • Network Interception
  • Custom Commands
  • TestMu AI Cloud
  • Validation Workflow
  • Quick Reference
  • Reference Files
  • Advanced Playbook

testmu-ai/detox-skill

Catalog entry: Skills by TestMu AI
Source documentation: https://github.com/LambdaTest/agent-skills/blob/main/detox-skill/SKILL.md

Function: Generate Detox gray-box E2E tests for React Native apps in JavaScript

When to use it: Use when user mentions “Detox”, “React Native test”, “element(by.id())“, “device.launchApp”. Triggers on: “Detox”, “React Native E2E”, “React Native test”, “element(by.id)“, “device.launchApp”.

Usage guidance is taken from the skill’s own trigger description or usage section.

Source skill menu:

  • Detox Automation Skill
  • Core Patterns
  • Basic Test
  • Matchers (Finding Elements)
  • Actions
  • Expectations
  • Device Control
  • Anti-Patterns
  • .detoxrc.js Configuration
  • Cloud Execution on TestMu AI
  • Android (Espresso) Cloud Run
  • iOS (XCUITest) Cloud Run
  • Quick Reference
  • Setup
  • React Native Component Setup
  • Deep Patterns

testmu-ai/espresso-skill

Catalog entry: Skills by TestMu AI
Source documentation: https://github.com/LambdaTest/agent-skills/blob/main/espresso-skill/SKILL.md

Function: Generate Espresso UI tests for Android apps in Kotlin or Java

When to use it: Use when user mentions “Espresso”, “onView”, “ViewMatchers”, “Android UI test”, or “instrumentation test”. Triggers on: “Espresso”, “onView”, “ViewMatchers”, “Android UI test”, “instrumentation”, “TestMu”.

Usage guidance is taken from the skill’s own trigger description or usage section.

Source skill menu:

  • Espresso Automation Skill
  • Step 1 — Execution Target
  • Core Patterns — Kotlin (Default)
  • Basic Test
  • ViewMatchers (Finding Elements)
  • ViewActions (Performing Actions)
  • ViewAssertions (Checking State)
  • Idling Resources (Async Operations)
  • Anti-Patterns
  • TestMu AI Cloud
  • build.gradle Setup
  • Quick Reference
  • Reference Files
  • Deep Patterns → `reference/playbook.md`

testmu-ai/flutter-testing-skill

Catalog entry: Skills by TestMu AI
Source documentation: https://github.com/LambdaTest/agent-skills/blob/main/flutter-testing-skill/SKILL.md

Function: Generate Flutter widget, integration, and golden tests in Dart

When to use it: Use when user mentions “Flutter”, “widget test”, “WidgetTester”, “testWidgets”, “flutter_test”, “integration_test”. Triggers on: “Flutter”, “widget test”, “Dart test”, “testWidgets”, “WidgetTester”, “golden test”.

Usage guidance is taken from the skill’s own trigger description or usage section.

Source skill menu:

  • Flutter Testing Skill
  • Step 1 — Test Type
  • Core Patterns — Dart
  • Widget Test (Most Common)
  • Finder Strategies
  • Actions
  • Integration Test
  • Golden Tests (Visual Regression)
  • Mocking Dependencies
  • Anti-Patterns
  • TestMu AI Cloud (Integration Tests)
  • Quick Reference
  • pubspec.yaml
  • Deep Patterns

testmu-ai/gauge-skill

Catalog entry: Skills by TestMu AI
Source documentation: https://github.com/LambdaTest/agent-skills/blob/main/gauge-skill/SKILL.md

Function: Generate Gauge specs in Markdown with steps in Java, Python, JS, or Ruby

When to use it: Use when user mentions “Gauge”, “spec file”, “## Scenario”, “step implementation”. Triggers on: “Gauge”, “Gauge spec”, “Gauge framework”, “ThoughtWorks test”.

Usage guidance is taken from the skill’s own trigger description or usage section.

Source skill menu:

  • Gauge Automation Skill
  • Core Patterns
  • Specification (specs/login.spec)
  • Step Implementation — Java
  • Step Implementation — Python
  • Concepts (Reusable Step Groups — specs/concepts/login.cpt)
  • Setup: `gauge install java` (or `python`, `js`, `ruby`)
  • Init: `gauge init java`
  • Run: `gauge run specs/` or `gauge run specs/login.spec`
  • Cloud Execution on TestMu AI
  • Tags: `gauge run --tags “smoke”` (use `Tags: smoke` in spec)
  • Deep Patterns

testmu-ai/geb-skill

Catalog entry: Skills by TestMu AI
Source documentation: https://github.com/LambdaTest/agent-skills/blob/main/geb-skill/SKILL.md

Function: Generate Geb browser automation in Groovy with Spock and page objects

When to use it: Use when user mentions “Geb”, “Groovy test”, “GebSpec”, “Browser.drive”. Triggers on: “Geb”, “GebSpec”, “Groovy browser test”, “Browser.drive”.

Usage guidance is taken from the skill’s own trigger description or usage section.

Source skill menu:

  • Geb Automation Skill
  • Core Patterns
  • Basic Test (Spock)
  • Page Objects
  • Navigator API
  • Cloud: `driver = new RemoteWebDriver(new URL(gridUrl), caps)`
  • Setup: Gradle with `geb-spock` and `selenium-support` dependencies
  • Cloud Execution on TestMu AI
  • Run: `./gradlew test`
  • Deep Patterns

testmu-ai/hyperexecute-skill

Catalog entry: Skills by TestMu AI
Source documentation: https://github.com/LambdaTest/agent-skills/blob/main/hyperexecute-skill/SKILL.md

Function: Operate TestMu AI HyperExecute end-to-end: YAML, CLI runs, debugging, and CI wiring

When to use it: Use when the user mentions HyperExecute, hyperexecute.yaml, HyperExecute CLI, autosplit, matrix execution, LambdaTest grid, cloud test runs, CI test orchestration, or migrating Playwright/Cypress/Selenium/Pytest/WebdriverIO tests to HyperExecute.

Usage guidance is taken from the skill’s own trigger description or usage section.

Source skill menu:

  • HyperExecute Operator
  • Quick Start
  • Operating Rules
  • Workflow
  • Helper Scripts
  • References

testmu-ai/jasmine-skill

Catalog entry: Skills by TestMu AI
Source documentation: https://github.com/LambdaTest/agent-skills/blob/main/jasmine-skill/SKILL.md

Function: Generate Jasmine BDD tests in JavaScript with spies and async support

When to use it: Use when user mentions “Jasmine”, “jasmine.createSpy”, “toHaveBeenCalled”. Triggers on: “Jasmine”, “jasmine test”, “createSpy”, “Jasmine spec”.

Usage guidance is taken from the skill’s own trigger description or usage section.

Source skill menu:

  • Jasmine Testing Skill
  • Core Patterns
  • Basic Test
  • Matchers
  • Spies
  • Async Testing
  • Setup: `npm install jasmine --save-dev && npx jasmine init`
  • Run: `npx jasmine` or `npx jasmine spec/calculatorSpec.js`
  • Deep Patterns

testmu-ai/jest-skill

Catalog entry: Skills by TestMu AI
Source documentation: https://github.com/LambdaTest/agent-skills/blob/main/jest-skill/SKILL.md

Function: Generate Jest unit and integration tests in JS/TS with mocking and snapshots

When to use it: Use when user mentions “Jest”, “describe/it/expect”, “jest.mock”, “toMatchSnapshot”. Triggers on: “Jest”, “expect().toBe()“, “jest.mock”, “snapshot test”, “JS test”, “React test”.

Usage guidance is taken from the skill’s own trigger description or usage section.

Source skill menu:

  • Jest Testing Skill
  • Core Patterns
  • Basic Test
  • Matchers
  • Mocking
  • Async Testing
  • React Component Testing (Testing Library)
  • Snapshot Testing
  • Anti-Patterns
  • Quick Reference
  • Deep Patterns

testmu-ai/junit-5-skill

Catalog entry: Skills by TestMu AI
Source documentation: https://github.com/LambdaTest/agent-skills/blob/main/junit-5-skill/SKILL.md

Function: Generate JUnit 5 unit and integration tests in Java with Mockito

When to use it: Use when user mentions “JUnit”, “JUnit 5”, “@Test”, “assertEquals”, “Assertions”, “Java unit test”. Triggers on: “JUnit”, “@Test”, “assertEquals”, “Java test”, “unit test Java”.

Usage guidance is taken from the skill’s own trigger description or usage section.

Source skill menu:

  • JUnit 5 Testing Skill
  • Step 1 — Test Type
  • Core Patterns
  • Basic Test
  • Assertions Reference
  • Parameterized Tests
  • Mocking with Mockito
  • Nested Tests
  • Anti-Patterns
  • Maven Dependencies
  • Quick Reference
  • Deep Patterns

testmu-ai/kanecli-skill

Catalog entry: Skills by TestMu AI
Source documentation: https://github.com/LambdaTest/agent-skills/blob/main/kanecli-skill/SKILL.md

Function: Generate and run browser tests from natural-language objectives via kane-cli

When to use it: Use when a task needs the capability described in this catalog entry: Generate and run browser tests from natural-language objectives via kane-cli

The catalog does not state a separate trigger condition. This usage note is inferred from the published function description.

Source skill menu:

  • Kane CLI — Browser Automation Skill
  • 1. Every session: ready check, launch, result card. READ THIS FIRST
  • 1.1 Start with the ready check
  • 1.2 How to launch kane-cli
  • 1.3 Before you launch
  • 1.4 After the run: summarize what happened
  • 1.5 The result card
  • 1.6 On failure
  • 1.7 After the first result: three choices, then save
  • 2. Decision tree
  • 3. Building a `run` command
  • Examples
  • 4. Writing objectives
  • Two rules that make an objective replayable
  • The “store as” rule (critical for extraction)
  • Calling APIs directly

testmu-ai/karma-skill

Catalog entry: Skills by TestMu AI
Source documentation: https://github.com/LambdaTest/agent-skills/blob/main/karma-skill/SKILL.md

Function: Generate Karma test-runner configs for browser-based JS testing

When to use it: Use when user mentions “Karma”, “karma.conf.js”, “browser test runner”. Triggers on: “Karma”, “karma.conf”, “karma test runner”, “browser-based JS test”.

Usage guidance is taken from the skill’s own trigger description or usage section.

Source skill menu:

  • Karma Testing Skill
  • Core Patterns
  • karma.conf.js
  • Test with Jasmine Framework
  • Angular Integration
  • Setup: `npm install karma karma-jasmine karma-chrome-launcher karma-coverage --save-dev`
  • Run: `npx karma start` or `npx karma start --single-run`
  • Init: `npx karma init karma.conf.js`
  • Deep Patterns

testmu-ai/laravel-dusk-skill

Catalog entry: Skills by TestMu AI
Source documentation: https://github.com/LambdaTest/agent-skills/blob/main/laravel-dusk-skill/SKILL.md

Function: Generate Laravel Dusk Chrome-based browser tests in PHP

When to use it: Use when user mentions “Dusk”, “Laravel Dusk”, “$browser->visit”, “DuskTestCase”. Triggers on: “Laravel Dusk”, “Dusk test”, “$browser->visit”, “DuskTestCase”.

Usage guidance is taken from the skill’s own trigger description or usage section.

Source skill menu:

  • Laravel Dusk Skill
  • Core Patterns
  • Basic Test
  • Browser Methods
  • Page Objects
  • Cloud: Override `DuskTestCase::driver()` to return `RemoteWebDriver` with LT caps
  • Setup: `composer require --dev laravel/dusk && php artisan dusk:install`
  • Cloud Execution on TestMu AI
  • Run: `php artisan dusk` or `php artisan dusk tests/Browser/LoginTest.php`
  • Deep Patterns

testmu-ai/lettuce-skill

Catalog entry: Skills by TestMu AI
Source documentation: https://github.com/LambdaTest/agent-skills/blob/main/lettuce-skill/SKILL.md

Function: Generate Lettuce BDD tests for Python (legacy; prefer Behave)

When to use it: Use when user specifically mentions “Lettuce”. Triggers on: “Lettuce”, “lettuce test”, “lettuce BDD”.

Usage guidance is taken from the skill’s own trigger description or usage section.

Source skill menu:

  • Lettuce BDD Skill (Legacy)
  • Core Patterns
  • Feature File (features/login.feature)
  • Step Definitions (features/steps.py)
  • Terrain (Setup/Teardown — terrain.py)
  • Setup: `pip install lettuce selenium`
  • Run: `lettuce` or `lettuce features/login.feature`
  • Cloud Execution on TestMu AI
  • Migration: Consider switching to `behave` for active maintenance
  • Deep Patterns

testmu-ai/mocha-skill

Catalog entry: Skills by TestMu AI
Source documentation: https://github.com/LambdaTest/agent-skills/blob/main/mocha-skill/SKILL.md

Function: Generate Mocha tests in JavaScript with Chai and Sinon

When to use it: Use when user mentions “Mocha”, “Chai”, “sinon”, “describe/it (not Jest)“. Triggers on: “Mocha”, “Chai”, “sinon”, “mocha test”.

Usage guidance is taken from the skill’s own trigger description or usage section.

Source skill menu:

  • Mocha Testing Skill
  • Core Patterns
  • Basic Test with Chai
  • Chai Assertions
  • Sinon Mocking
  • Async Testing
  • Anti-Patterns
  • Quick Reference
  • Setup: `npm install mocha chai sinon --save-dev`
  • Deep Patterns → `reference/playbook.md`

testmu-ai/mstest-skill

Catalog entry: Skills by TestMu AI
Source documentation: https://github.com/LambdaTest/agent-skills/blob/main/mstest-skill/SKILL.md

Function: Generate MSTest tests in C# for .NET

When to use it: Use when user mentions “MSTest”, “[TestMethod]“, “[TestClass]“, “Assert.AreEqual”. Triggers on: “MSTest”, “[TestMethod]“, “[TestClass]“, “Microsoft test framework”.

Usage guidance is taken from the skill’s own trigger description or usage section.

Source skill menu:

  • MSTest Testing Skill
  • Core Patterns
  • Basic Test
  • Data-Driven Tests
  • Assertions
  • Lifecycle
  • Categories
  • Setup: `dotnet add package MSTest.TestFramework MSTest.TestAdapter Microsoft.NET.Test.Sdk`
  • Run: `dotnet test` or `dotnet test --filter “TestCategory=Smoke”`
  • Deep Patterns

testmu-ai/nemojs-skill

Catalog entry: Skills by TestMu AI
Source documentation: https://github.com/LambdaTest/agent-skills/blob/main/nemojs-skill/SKILL.md

Function: Generate Nemo.js Selenium-based tests for Node.js

When to use it: Use when user mentions “Nemo.js”, “nemo automation”. Triggers on: “Nemo.js”, “nemo automation”, “nemo test”, “PayPal test framework”.

Usage guidance is taken from the skill’s own trigger description or usage section.

Source skill menu:

  • Nemo.js Automation Skill
  • Core Patterns
  • Basic Test (Mocha)
  • View Locators
  • Configuration (nemo.config.json)
  • Cloud Execution on TestMu AI
  • Setup: `npm install nemo nemo-view --save-dev`
  • Run: `npx mocha test/*.js --timeout 30000`
  • Deep Patterns

testmu-ai/nightwatchjs-skill

Catalog entry: Skills by TestMu AI
Source documentation: https://github.com/LambdaTest/agent-skills/blob/main/nightwatchjs-skill/SKILL.md

Function: Generate NightwatchJS E2E tests in JavaScript with Selenium WebDriver

When to use it: Use when user mentions “Nightwatch”, “NightwatchJS”, “nightwatch.conf.js”. Triggers on: “Nightwatch”, “NightwatchJS”, “nightwatch test”.

Usage guidance is taken from the skill’s own trigger description or usage section.

Source skill menu:

  • NightwatchJS Automation Skill
  • Step 1 — Execution Target
  • Core Patterns
  • Basic Test
  • Page Objects
  • Assertions
  • TestMu AI Cloud Config
  • Setup: `npm install nightwatch --save-dev`
  • Run: `npx nightwatch` or `npx nightwatch --env lambdatest`
  • Deep Patterns

testmu-ai/nunit-skill

Catalog entry: Skills by TestMu AI
Source documentation: https://github.com/LambdaTest/agent-skills/blob/main/nunit-skill/SKILL.md

Function: Generate NUnit 3 tests in C# with the constraint model and Moq

When to use it: Use when user mentions “NUnit”, “[TestFixture]“, “[Test]“, “Assert.That”, “C# unit test”. Triggers on: “NUnit”, “[Test]“, “Assert.That”, “C# test”, “NUnit3”.

Usage guidance is taken from the skill’s own trigger description or usage section.

Source skill menu:

  • NUnit 3 Testing Skill
  • Core Patterns
  • Basic Test
  • Constraint Model (Assert.That)
  • Parameterized Tests
  • Mocking with Moq
  • Lifecycle
  • Categories and Attributes
  • Anti-Patterns
  • Setup: `dotnet add package NUnit NUnit3TestAdapter Microsoft.NET.Test.Sdk`
  • Run: `dotnet test` or `dotnet test --filter TestCategory=Smoke`
  • Deep Patterns

testmu-ai/phpunit-skill

Catalog entry: Skills by TestMu AI
Source documentation: https://github.com/LambdaTest/agent-skills/blob/main/phpunit-skill/SKILL.md

Function: Generate PHPUnit tests in PHP with data providers and mocking

When to use it: Use when user mentions “PHPUnit”, “TestCase”, “assertEquals”, “PHP test”. Triggers on: “PHPUnit”, “TestCase PHP”, “assertEquals PHP”, “PHP unit test”.

Usage guidance is taken from the skill’s own trigger description or usage section.

Source skill menu:

  • PHPUnit Testing Skill
  • Core Patterns
  • Basic Test
  • Data Providers
  • Assertions
  • Mocking
  • Lifecycle
  • Anti-Patterns
  • Setup: `composer require --dev phpunit/phpunit`
  • Run: `./vendor/bin/phpunit` or `./vendor/bin/phpunit --group smoke`
  • Config: `phpunit.xml` with testsuites and coverage
  • Deep Patterns

testmu-ai/playwright-skill

Catalog entry: Skills by TestMu AI
Source documentation: https://github.com/LambdaTest/agent-skills/blob/main/playwright-skill/SKILL.md

Function: Generate Playwright E2E tests in TS, JS, Python, Java, or C#

When to use it: Use when the user asks to write Playwright tests, automate browsers, run cross-browser tests, test on real devices, debug flaky tests, mock APIs, or do visual regression. Triggers on: “Playwright”, “E2E test”, “browser test”, “run on cloud”, “cross-browser”, “TestMu”, “LambdaTest”, “test my app”, “test on mobile”, “real device”.

Usage guidance is taken from the skill’s own trigger description or usage section.

Source skill menu:

  • Playwright Test Automation
  • Step 1 — Determine Execution Target
  • Step 2 — Detect Language
  • Step 3 — Determine Scope
  • Core Patterns — TypeScript (Default)
  • Selector Priority
  • Assertions — Always Web-First
  • Anti-Patterns
  • Page Object Model
  • Configuration — Local
  • Cloud Execution on TestMu AI
  • Test Status Reporting (Cloud)
  • Validation Workflow
  • Quick Reference
  • Common Commands
  • Auth State Reuse

testmu-ai/protractor-skill

Catalog entry: Skills by TestMu AI
Source documentation: https://github.com/LambdaTest/agent-skills/blob/main/protractor-skill/SKILL.md

Function: Generate Protractor E2E tests for Angular in JS/TS (deprecated; prefer Playwright/Cypress)

When to use it: Use when user mentions “Protractor”, “element(by.model())“, “Angular E2E”. Triggers on: “Protractor”, “element(by.model)“, “Angular E2E test”, “protractor.conf”.

Usage guidance is taken from the skill’s own trigger description or usage section.

Source skill menu:

  • Protractor Automation Skill (Deprecated)
  • Core Patterns
  • Basic Test
  • Angular-Specific Locators
  • Page Objects
  • protractor.conf.js
  • Migration Guide
  • Cloud Execution on TestMu AI
  • Run: `npx protractor conf.js` (deprecated, use Playwright/Cypress instead)
  • Deep Patterns

testmu-ai/puppeteer-skill

Catalog entry: Skills by TestMu AI
Source documentation: https://github.com/LambdaTest/agent-skills/blob/main/puppeteer-skill/SKILL.md

Function: Generate Puppeteer scripts for browser automation, scraping, and PDF generation

When to use it: Triggers on: “Puppeteer”, “headless Chrome”, “page.goto”, “scrape”, “PDF generation”.

Usage guidance is taken from the skill’s own trigger description or usage section.

Source skill menu:

  • Puppeteer Automation Skill
  • Core Patterns
  • Basic Script
  • Wait Strategies
  • Screenshot & PDF
  • Network Interception
  • TestMu AI Cloud
  • Quick Reference
  • Deep Patterns → `reference/playbook.md`

testmu-ai/pytest-skill

Catalog entry: Skills by TestMu AI
Source documentation: https://github.com/LambdaTest/agent-skills/blob/main/pytest-skill/SKILL.md

Function: Generate pytest tests in Python with fixtures, parametrize, and mocking

When to use it: Use when user mentions “pytest”, “conftest”, “@pytest.fixture”, “@pytest.mark”, “Python test”. Triggers on: “pytest”, “conftest”, “Python test”, “parametrize”, “Python unit test”.

Usage guidance is taken from the skill’s own trigger description or usage section.

Source skill menu:

  • Pytest Testing Skill
  • Core Patterns
  • Basic Test
  • Fixtures
  • Parametrize
  • Markers
  • Mocking
  • Assertions
  • Anti-Patterns
  • Quick Reference
  • pyproject.toml
  • Deep Patterns

testmu-ai/reqnroll-skill

Catalog entry: Skills by TestMu AI
Source documentation: https://github.com/LambdaTest/agent-skills/blob/main/reqnroll-skill/SKILL.md

Function: Generate Reqnroll BDD tests for web and mobile in C#

When to use it: Use when the user asks to write BDD tests, automate with Reqnroll, create .feature files, write Gherkin scenarios, write step definitions, migrate from SpecFlow, or test on browsers/Android/iOS. Triggers on: “Reqnroll”, “BDD”, “Gherkin”, “.feature file”, “step definition”, “SpecFlow migration”, “Selenium C#“, “Appium C#“, “TestMu”, “LambdaTest”, “NUnit BDD”, “reqnroll.actions.json”.

Usage guidance is taken from the skill’s own trigger description or usage section.

Source skill menu:

  • Overview
  • Key Execution Pathways
  • Core Technical Patterns
  • Feature Files (Gherkin)
  • Step Definitions
  • Hooks
  • ScenarioContext Driver Sharing
  • Explicit Waits
  • Cloud Integration (TestMu / LambdaTest)
  • Web (Selenium 4)
  • Mobile (Appium 2)
  • Reporting Pass/Fail
  • Quality Checkpoints
  • Reference Structure

testmu-ai/robot-framework-skill

Catalog entry: Skills by TestMu AI
Source documentation: https://github.com/LambdaTest/agent-skills/blob/main/robot-framework-skill/SKILL.md

Function: Generate Robot Framework keyword-driven tests in Python

When to use it: Use when user mentions “Robot Framework”, “*** Test Cases ***“, “SeleniumLibrary”, “.robot file”. Triggers on: “Robot Framework”, “*** Test Cases ***“, “.robot”, “SeleniumLibrary”, “keyword-driven test”.

Usage guidance is taken from the skill’s own trigger description or usage section.

Source skill menu:

  • Robot Framework Skill
  • Core Patterns
  • Basic Test (tests/login.robot)
  • Custom Keywords
  • Data-Driven Tests (Template)
  • API Testing (RequestsLibrary)
  • Cloud Config
  • Setup: `pip install robotframework robotframework-seleniumlibrary robotframework-requests`
  • Run: `robot tests/` or `robot --include smoke tests/`
  • Report: `report.html` and `log.html` auto-generated
  • Deep Patterns

testmu-ai/rspec-skill

Catalog entry: Skills by TestMu AI
Source documentation: https://github.com/LambdaTest/agent-skills/blob/main/rspec-skill/SKILL.md

Function: Generate RSpec tests in Ruby with matchers, hooks, and mocking

When to use it: Use when user mentions “RSpec”, “describe do”, “expect().to”, “Ruby test”. Triggers on: “RSpec”, “expect().to eq()“, “describe do”, “Ruby test”, “spec file”.

Usage guidance is taken from the skill’s own trigger description or usage section.

Source skill menu:

  • RSpec Testing Skill
  • Core Patterns
  • Basic Test
  • Matchers
  • Hooks and Let
  • Mocking and Stubbing
  • Shared Examples
  • Anti-Patterns
  • Setup: `gem install rspec` then `rspec --init`
  • Run: `bundle exec rspec` or `rspec spec/models/user_spec.rb`
  • Config: `.rspec` file with `--format documentation --color`
  • Deep Patterns

testmu-ai/selenide-skill

Catalog entry: Skills by TestMu AI
Source documentation: https://github.com/LambdaTest/agent-skills/blob/main/selenide-skill/SKILL.md

Function: Generate Selenide UI tests in Java with auto-waits and a fluent API

When to use it: Use when user mentions “Selenide”, “$(selector)“, “shouldBe(visible)“, “Selenide Java”. Triggers on: “Selenide”, “$() selector”, “shouldBe”, “shouldHave”, “Selenide test”.

Usage guidance is taken from the skill’s own trigger description or usage section.

Source skill menu:

  • Selenide Automation Skill
  • Core Patterns
  • Basic Test
  • Selectors
  • Conditions
  • TestMu AI Cloud
  • Setup: Maven `com.codeborne:selenide:7.0.0`
  • Run: `mvn test` (auto-downloads browser driver)
  • Deep Patterns

testmu-ai/selenium-skill

Catalog entry: Skills by TestMu AI
Source documentation: https://github.com/LambdaTest/agent-skills/blob/main/selenium-skill/SKILL.md

Function: Generate Selenium WebDriver tests in Java, Python, JS, C#, Ruby, or PHP

When to use it: Use when the user asks to write Selenium tests, automate with WebDriver, run cross-browser tests on Selenium Grid, or mentions “Selenium”, “WebDriver”, “RemoteWebDriver”, “ChromeDriver”, “GeckoDriver”. Triggers on: “Selenium”, “WebDriver”, “browser automation”, “Selenium Grid”, “cross-browser”, “TestMu”, “LambdaTest”.

Usage guidance is taken from the skill’s own trigger description or usage section.

Source skill menu:

  • Selenium Automation Skill
  • Step 1 — Execution Target
  • Step 2 — Language Detection
  • Step 3 — Scope
  • Core Patterns — Java (Default)
  • Locator Priority
  • Wait Strategy — CRITICAL
  • Anti-Patterns
  • Basic Test Structure
  • Page Object Model — Quick Example
  • TestMu AI Cloud — Quick Setup
  • Test Status Reporting
  • Validation Workflow
  • Quick Reference
  • Reference Files
  • Advanced Playbook

testmu-ai/serenity-bdd-skill

Catalog entry: Skills by TestMu AI
Source documentation: https://github.com/LambdaTest/agent-skills/blob/main/serenity-bdd-skill/SKILL.md

Function: Generate Serenity BDD tests in Java with the Screenplay pattern and reporting

When to use it: Use when user mentions “Serenity”, “Screenplay”, “@Steps”, “Serenity BDD”. Triggers on: “Serenity BDD”, “Screenplay pattern”, “@Steps”, “Serenity report”.

Usage guidance is taken from the skill’s own trigger description or usage section.

Source skill menu:

  • Serenity BDD Skill
  • Core Patterns
  • Step Library Pattern
  • Test Class
  • Screenplay Pattern
  • Reporting
  • Cloud Execution on TestMu AI
  • Setup: Maven with `serenity-core`, `serenity-junit5`, `serenity-screenplay-webdriver`, `serenity-lambdatest`
  • Run: `mvn verify` (generates living documentation)
  • Deep Patterns

testmu-ai/smartui-skill

Catalog entry: Skills by TestMu AI
Source documentation: https://github.com/LambdaTest/agent-skills/blob/main/smartui-skill/SKILL.md

Function: Generate SmartUI visual regression configs for screenshot comparison

When to use it: Use when user mentions “SmartUI”, “visual regression”, “screenshot comparison”, “visual testing”. Triggers on: “SmartUI”, “visual regression”, “screenshot comparison”, “pixel diff”, “visual testing LambdaTest”.

Usage guidance is taken from the skill’s own trigger description or usage section.

Source skill menu:

  • SmartUI Visual Regression Skill
  • Core Patterns
  • Playwright + SmartUI SDK
  • Selenium + SmartUI
  • CLI Execution
  • smartui.config.json
  • SmartUI with Storybook
  • Approval Workflow
  • Anti-Patterns
  • Cloud Authentication
  • Quick Reference
  • Deep Patterns

testmu-ai/specflow-skill

Catalog entry: Skills by TestMu AI
Source documentation: https://github.com/LambdaTest/agent-skills/blob/main/specflow-skill/SKILL.md

Function: Generate SpecFlow BDD tests for C#/.NET with Gherkin and step bindings

When to use it: Use when user mentions “SpecFlow”, “C# BDD”, “.NET Gherkin”, “[Binding]“, “[Given]/[When]/[Then]“. Triggers on: “SpecFlow”, “C# BDD”, “.NET BDD”, “step bindings”, “[Binding]“.

Usage guidance is taken from the skill’s own trigger description or usage section.

Source skill menu:

  • SpecFlow BDD Skill
  • Core Patterns
  • Feature File (Features/Login.feature)
  • Step Bindings
  • Hooks
  • Dependency Injection (Context Injection)
  • Setup: `dotnet add package SpecFlow.NUnit` or `SpecFlow.xUnit`
  • Run: `dotnet test`
  • Cloud Execution on TestMu AI
  • Report: SpecFlow+ LivingDoc extension for rich HTML reports
  • Deep Patterns

testmu-ai/test-framework-migration-skill

Catalog entry: Skills by TestMu AI
Source documentation: https://github.com/LambdaTest/agent-skills/blob/main/test-framework-migration-skill/SKILL.md

Function: Migrate tests between Selenium, Playwright, Puppeteer, and Cypress

When to use it: Use when the user asks to migrate, convert, or port tests from one framework to another; rewrite tests in a different framework; or switch from Selenium to Playwright, Playwright to Selenium, Puppeteer to Playwright, Cypress to Playwright, or vice versa. Triggers on: “migrate”, “convert”, “port”, “selenium to playwright”, “playwright to selenium”, “puppeteer to playwright”, “cypress to playwright”, “rewrite tests in”, “switch from [framework] to [framework]“.

Usage guidance is taken from the skill’s own trigger description or usage section.

Source skill menu:

  • Test Framework Migration Skill
  • Step 1 — Detect Source Framework
  • Step 2 — Detect Target Framework
  • Step 3 — Detect Language
  • Step 4 — Route to Reference
  • Step 5 — Apply Mappings
  • Cross-References for Deep Patterns
  • Validation Workflow
  • Reference Files Summary

testmu-ai/testcafe-skill

Catalog entry: Skills by TestMu AI
Source documentation: https://github.com/LambdaTest/agent-skills/blob/main/testcafe-skill/SKILL.md

Function: Generate TestCafe automation tests in JavaScript or TypeScript

When to use it: Triggers on: “TestCafe”, “test cafe”, “fixture/test”.

Usage guidance is taken from the skill’s own trigger description or usage section.

Source skill menu:

  • TestCafe Automation Skill
  • Core Patterns
  • Basic Test
  • Selectors
  • Page Model
  • TestMu AI Cloud
  • Anti-Patterns
  • Quick Reference
  • Deep Patterns

testmu-ai/testng-skill

Catalog entry: Skills by TestMu AI
Source documentation: https://github.com/LambdaTest/agent-skills/blob/main/testng-skill/SKILL.md

Function: Generate TestNG tests in Java with data providers and parallel execution

When to use it: Use when user mentions “TestNG”, “@DataProvider”, “testng.xml”, “groups”. Triggers on: “TestNG”, “@DataProvider”, “testng.xml”, “TestNG suite”, “parallel tests Java”.

Usage guidance is taken from the skill’s own trigger description or usage section.

Source skill menu:

  • TestNG Testing Skill
  • Core Patterns
  • Basic Test with Groups
  • Data Providers
  • TestNG XML Suite
  • Parallel Execution
  • Soft Assertions
  • Listeners
  • Lifecycle Annotations
  • Anti-Patterns
  • Quick Reference
  • Deep Patterns → `reference/playbook.md`

testmu-ai/testunit-skill

Catalog entry: Skills by TestMu AI
Source documentation: https://github.com/LambdaTest/agent-skills/blob/main/testunit-skill/SKILL.md

Function: Generate Test::Unit xUnit-style tests in Ruby

When to use it: Use when user mentions “Test::Unit”, “assert_equal Ruby”, “Ruby test-unit”. Triggers on: “Test::Unit”, “Ruby test-unit”, “assert_equal Ruby” (not RSpec).

Usage guidance is taken from the skill’s own trigger description or usage section.

Source skill menu:

  • Test::Unit Ruby Skill
  • Core Patterns
  • Basic Test
  • Assertions
  • Test Fixtures
  • Test Ordering and Naming
  • Setup: `gem install test-unit`
  • Run: `ruby test/test_calculator.rb` or `ruby -Itest -e “Dir.glob(‘test/**/test_*.rb’).each{|f| require f}“`
  • Autodiscovery: `testrb test/` (with test-unit gem)
  • Deep Patterns

testmu-ai/unittest-skill

Catalog entry: Skills by TestMu AI
Source documentation: https://github.com/LambdaTest/agent-skills/blob/main/unittest-skill/SKILL.md

Function: Generate Python unittest tests with TestCase and setUp/tearDown

When to use it: Use when user mentions “unittest”, “TestCase”, “self.assertEqual”, “Python unittest”. Triggers on: “unittest”, “TestCase”, “self.assertEqual”, “Python unittest” (not pytest).

Usage guidance is taken from the skill’s own trigger description or usage section.

Source skill menu:

  • Python unittest Skill
  • Core Patterns
  • Basic Test
  • Assertions
  • SubTest (Parameterized)
  • Mocking
  • Lifecycle
  • Run: `python -m unittest` or `python -m unittest test_module.TestClass.test_method`
  • Discover: `python -m unittest discover -s tests -p “test_*.py”`
  • Deep Patterns

testmu-ai/vitest-skill

Catalog entry: Skills by TestMu AI
Source documentation: https://github.com/LambdaTest/agent-skills/blob/main/vitest-skill/SKILL.md

Function: Generate Vitest tests in JS/TS with a Jest-compatible API and ESM

When to use it: Use when user mentions “Vitest”, “vi.mock”, “vitest.config”. Triggers on: “Vitest”, “vi.mock”, “vi.fn”, “Vite test”, “vitest config”.

Usage guidance is taken from the skill’s own trigger description or usage section.

Source skill menu:

  • Vitest Testing Skill
  • Core Patterns
  • Basic Test
  • Mocking (vi instead of jest)
  • In-Source Testing
  • Snapshot Testing
  • React Component Testing
  • Anti-Patterns
  • Quick Reference
  • vitest.config.ts
  • Deep Patterns → `reference/playbook.md`

testmu-ai/webdriverio-skill

Catalog entry: Skills by TestMu AI
Source documentation: https://github.com/LambdaTest/agent-skills/blob/main/webdriverio-skill/SKILL.md

Function: Generate WebdriverIO (WDIO) automation tests in JavaScript or TypeScript

When to use it: Use when user mentions “WebdriverIO”, “WDIO”, “wdio.conf”, “browser.url”, “$”, “$$”. Triggers on: “WebdriverIO”, “WDIO”, “wdio”, “browser.$”.

Usage guidance is taken from the skill’s own trigger description or usage section.

Source skill menu:

  • WebdriverIO Automation Skill
  • Step 1 — Execution Target
  • Step 2 — Framework
  • Core Patterns
  • Selectors
  • Basic Test (Mocha)
  • Page Object
  • TestMu AI Cloud Config
  • Wait Strategies
  • Quick Reference
  • Reference Files
  • Deep Patterns → `reference/playbook.md`

testmu-ai/xcuitest-skill

Catalog entry: Skills by TestMu AI
Source documentation: https://github.com/LambdaTest/agent-skills/blob/main/xcuitest-skill/SKILL.md

Function: Generate XCUITest UI tests for iOS/iPadOS apps in Swift

When to use it: Use when user mentions “XCUITest”, “XCTest”, “iOS UI test”, “Swift test”, “XCUIApplication”. Triggers on: “XCUITest”, “XCTest UI”, “iOS UI test”, “Swift UI test”, “XCUIApplication”, “TestMu”.

Usage guidance is taken from the skill’s own trigger description or usage section.

Source skill menu:

  • XCUITest Automation Skill
  • Step 1 — Execution Target
  • Core Patterns — Swift
  • Basic Test
  • Element Queries
  • Actions
  • Assertions
  • Handling System Alerts
  • Page Object Pattern
  • Anti-Patterns
  • TestMu AI Cloud
  • Quick Reference
  • Deep Patterns

testmu-ai/xunit-skill

Catalog entry: Skills by TestMu AI
Source documentation: https://github.com/LambdaTest/agent-skills/blob/main/xunit-skill/SKILL.md

Function: Generate xUnit.net tests in C# with Fact/Theory and FluentAssertions

When to use it: Use when user mentions “xUnit”, “[Fact]“, “[Theory]“, “Assert.Equal”, “C# xUnit”. Triggers on: “xUnit”, “[Fact]“, “[Theory]“, “Assert.Equal C#“, “xUnit.net”.

Usage guidance is taken from the skill’s own trigger description or usage section.

Source skill menu:

  • xUnit.net Testing Skill
  • Core Patterns
  • Basic Test
  • Theory (Parameterized)
  • Assertions
  • Shared Context (IClassFixture)
  • Constructor/Dispose (Per-Test Setup)
  • Anti-Patterns
  • Setup: `dotnet add package xunit xunit.runner.visualstudio Microsoft.NET.Test.Sdk`
  • Run: `dotnet test` or `dotnet test --filter “FullyQualifiedName~Calculator”`
  • Deep Patterns

tjboudreaux/cc-thinking-skills

Catalog entry: Productivity and Collaboration
Source documentation: https://github.com/tjboudreaux/cc-thinking-skills/blob/main/README.md

Function: 28 eval-informed mental models for decisions, debugging, systems, and strategy

When to use it: Use when a task needs the capability described in this catalog entry: 28 eval-informed mental models for decisions, debugging, systems, and strategy

The catalog does not state a separate trigger condition. This usage note is inferred from the published function description.

Source skill menu:

  • Claude Code thinking skills
  • Contents
  • Why use this catalog
  • Quick start
  • Skills CLI
  • Claude Code plugin
  • Copy from a clone
  • Use a skill
  • Skill catalog
  • Route and compose
  • Diagnose and understand
  • Decide and evaluate
  • Create and improve
  • Manage risk and execution
  • Evidence
  • Repository layout

This catalog entry points to a collection. The scanned repository lists 28 distinct skill-file paths.

Sample members: thinking-bounded-rationality · thinking-circle-of-competence · thinking-cynefin · thinking-effectuation · thinking-first-principles · thinking-five-whys-plus · thinking-jobs-to-be-done · thinking-kepner-tregoe
More members are available in the source repository.

wendylabsinc/claude-skills

Catalog entry: Development and Testing
Source documentation: https://github.com/wendylabsinc/claude-skills/blob/main/README.md

Function: Swift Server development guidance with linting tool for best practices

When to use it: Use when a task needs the capability described in this catalog entry: Swift Server development guidance with linting tool for best practices

The catalog does not state a separate trigger condition. This usage note is inferred from the published function description.

Source skill menu:

  • Swift Server Skills & Linting
  • The Technique
  • The solution
  • Overview
  • Setup with Claude Code
  • 1. Install Skills
  • 2. Build the Linter
  • 3. Auto-Lint with a Hook
  • 4. Allow the Linter in Permissions
  • IDE Integration

This catalog entry points to a collection. The scanned repository lists 26 distinct skill-file paths.

Sample members: database-driver-design · deckset · github-actions · hummingbird · linear · postgres-nio · pull-request · swift-concurrency
More members are available in the source repository.

wgwtest/novel-writing

Catalog entry: Productivity and Collaboration
Source documentation: https://github.com/wgwtest/novel-writing/blob/main/novel-writing/SKILL.md

Function: Plans and revises fiction with viewpoint, dialogue, and style checks.

When to use it: Use when setting up a fiction project, planning, drafting, revising, or reviewing fiction where chapter versions, author feedback, character knowledge, scene causality, dialogue, or style fidelity matter.

Usage guidance is taken from the skill’s own trigger description or usage section.

Source skill menu:

  • Novel Writing
  • Overview
  • When to Use
  • Stage Selection
  • 1. Planning
  • 2. Drafting or Continuing
  • 3. Reviewing
  • Long-Fiction Context Strategy
  • Load order
  • Manuscript and author-feedback stewardship
  • Hard Rules
  • Reader Knowledge Is Not Author Knowledge
  • Important Characters Cannot Enter Naked
  • Scene Information Must Obey Access Limits
  • Cognition Must Change Choice and Language
  • Viewpoint Does Not Own Every Decision

ZeKaiNie/universal-examprep-skill

Catalog entry: Specialized Domains
Source documentation: https://github.com/ZeKaiNie/universal-examprep-skill/blob/main/README.md

Function: Multimodal grounded active-learning tutor for college textbooks (PDF/PPTX/DOCX). Features native PDF vector diagram cropping (`pypdfium2`), real homework quiz banks, hard exit-code anti-hallucination, and persistent cross-session state. Tested on 1,000+ pages of real college courseware on small cheap models.

When to use it: Use when a task needs the capability described in this catalog entry: Multimodal grounded active-learning tutor for college textbooks (PDF/PPTX/DOCX). Features native PDF vector diagram cropping (`pypdfium2`), real homework quiz banks, hard exit-code anti-hallucination, and persistent cross-session state. Tested on 1,000+ pages of real college courseware on small cheap models.

The catalog does not state a separate trigger condition. This usage note is inferred from the published function description.

Source skill menu:

  • Exam Cram Coach · Flash
  • 🌟 Featured & Curated By
  • Two editions, pick one
  • Contents
  • Start studying in five minutes
  • Step 0 · What you need
  • Step 1 · Install the skill
  • Step 2 · Put your materials in one folder
  • Step 3 · Send the first message
  • Step 4 · Keep talking normally
  • What a study session looks like
  • Preparing your materials
  • Flash vs. the full edition
  • What ends up in the `exam-cram/` folder
  • Command reference
  • Measured results

This catalog entry points to a collection. The scanned repository lists 14 distinct skill-file paths.

Sample members: full · en · zh · confusion-tracker · exam-audit · exam-cheatsheet · exam-cram · exam-help
More members are available in the source repository.

Back to the category index

本分类中文版

Follow

Archives

Tags

AGI1
Agent Skills13
Alfred1
Automation3
Documentation4
Hexo2
Python_library1
Skills,Agent skills1
Software3
VoltAgent13
bibliography1
chart1
computational simulation1
condensed-matter physics1
data analysis1
data-science2
deep-learning1
encryptAsDiary2
fortran1
functional programming2
github1
machine-learning2
matplotlib1
multiprocessing1
neural-networks1
physics2
physics experiment3
plasma physics1
plugins1
poetry1
python16
python_configuration1
python_editors1
python_intermediate2
python_tools1
rust1
semiconductors1
superintelligence1
uv1
zotero1

follow.it

Recents

Latest Comments

×