{
  "name": "software-tester-skills",
  "repository": "https://github.com/mejbaurbahar/software-tester-skills",
  "homepage": "https://mejbaurbahar.github.io/software-tester-skills/",
  "skill_count": 97,
  "command_count": 21,
  "categories": [
    {
      "id": "strategy",
      "label": "Strategy, Planning & Metrics",
      "description": "Decide what to test, plan it, report on it."
    },
    {
      "id": "functional",
      "label": "Functional & Acceptance",
      "description": "Black-box, exploratory, regression and release-gate testing."
    },
    {
      "id": "code-level",
      "label": "Code-Level & White-Box",
      "description": "Unit, integration, property, fuzz, mutation and TDD."
    },
    {
      "id": "automation",
      "label": "Automation & CI",
      "description": "Frameworks, environments, flaky tests, coverage and pipelines."
    },
    {
      "id": "web",
      "label": "Web, UI & UX",
      "description": "Browsers, E2E, visual, accessibility, i18n, SEO and PWAs."
    },
    {
      "id": "api-backend",
      "label": "API, Backend & Messaging",
      "description": "REST, GraphQL, real-time, contracts, events and microservices."
    },
    {
      "id": "data",
      "label": "Data & Databases",
      "description": "Databases, ETL, migrations and test data."
    },
    {
      "id": "non-functional",
      "label": "Performance & Reliability",
      "description": "Load, scalability, chaos, recovery and compatibility."
    },
    {
      "id": "operations",
      "label": "Operations & Production",
      "description": "Observability, infrastructure and shift-right monitoring."
    },
    {
      "id": "security",
      "label": "Security & Privacy",
      "description": "Defensive security testing, auth, supply chain and IaC."
    },
    {
      "id": "compliance",
      "label": "Compliance",
      "description": "GDPR, HIPAA, PCI, SOC 2, audit evidence."
    },
    {
      "id": "ai",
      "label": "AI, ML & LLM",
      "description": "Models, LLM apps, RAG, agents, chatbots and MCP."
    },
    {
      "id": "platform",
      "label": "Platforms",
      "description": "Mobile, desktop, CLI, IoT, games, blockchain and serverless."
    },
    {
      "id": "domain",
      "label": "Domain-Specific",
      "description": "Payments, email, analytics and experimentation."
    }
  ],
  "skills": [
    {
      "name": "42crunch-api-security-testing",
      "description": "Use when auditing, scanning, or remediating OpenAPI/Swagger API definitions for security vulnerabilities \u2014 42Crunch audit scoring, OWASP API Security Top 10 compliance, BOLA/BFLA prevention, schema strictness, and shift-left API CI/CD testing.",
      "category": "security",
      "version": "2.0",
      "tags": [
        "openapi",
        "api-security",
        "owasp-api",
        "42crunch",
        "shift-left"
      ],
      "url": "https://mejbaurbahar.github.io/software-tester-skills/skills/42crunch-api-security-testing/",
      "source": "https://github.com/mejbaurbahar/software-tester-skills/tree/main/skills/42crunch-api-security-testing"
    },
    {
      "name": "a-b-testing",
      "description": "Use when designing or analysing controlled experiments \u2014 A/B and multivariate tests, hypotheses, sample size and power, statistical significance, SRM checks, feature-flag rollouts, guardrail metrics, and deciding whether a variant really won.",
      "category": "domain",
      "version": "2.0",
      "tags": [
        "ab-testing",
        "experimentation",
        "statistics",
        "feature-flags",
        "conversion"
      ],
      "url": "https://mejbaurbahar.github.io/software-tester-skills/skills/a-b-testing/",
      "source": "https://github.com/mejbaurbahar/software-tester-skills/tree/main/skills/a-b-testing"
    },
    {
      "name": "acceptance-testing",
      "description": "Use when validating a feature against business needs before release \u2014 user acceptance testing (UAT), alpha/beta programs, acceptance criteria, sign-off, contract/operational acceptance, and \"is this ready for the customer?\" decisions.",
      "category": "functional",
      "version": "2.0",
      "tags": [
        "uat",
        "acceptance-criteria",
        "sign-off",
        "beta",
        "alpha",
        "business-validation"
      ],
      "url": "https://mejbaurbahar.github.io/software-tester-skills/skills/acceptance-testing/",
      "source": "https://github.com/mejbaurbahar/software-tester-skills/tree/main/skills/acceptance-testing"
    },
    {
      "name": "accessibility-testing",
      "description": "Use when auditing a web app for accessibility (a11y) \u2014 WCAG compliance, screen reader compatibility, keyboard navigation, color contrast, and semantic HTML/ARIA correctness.",
      "category": "web",
      "version": "2.0",
      "tags": [
        "accessibility",
        "wcag",
        "axe-core",
        "screen-reader",
        "keyboard",
        "a11y"
      ],
      "url": "https://mejbaurbahar.github.io/software-tester-skills/skills/accessibility-testing/",
      "source": "https://github.com/mejbaurbahar/software-tester-skills/tree/main/skills/accessibility-testing"
    },
    {
      "name": "ai-agent-evaluation",
      "description": "Use when testing and evaluating AI agents and tool-using LLM systems \u2014 task-success and trajectory evaluation, tool-call correctness, LLM-as-judge calibration, regression datasets, non-determinism (pass@k), cost/latency budgets, and CI evals with DeepEval, promptfoo, LangSmith, Inspect or MLflow.",
      "category": "ai",
      "version": "2.0",
      "tags": [
        "agent-evaluation",
        "llm-evals",
        "tool-calling",
        "trajectory",
        "llm-as-judge",
        "promptfoo",
        "deepeval",
        "inspect",
        "non-determinism",
        "agents"
      ],
      "url": "https://mejbaurbahar.github.io/software-tester-skills/skills/ai-agent-evaluation/",
      "source": "https://github.com/mejbaurbahar/software-tester-skills/tree/main/skills/ai-agent-evaluation"
    },
    {
      "name": "ai-code-security",
      "description": "Use when reviewing AI-generated code or LLM-integrated applications for security flaws \u2014 OWASP Top 10 for LLMs, insecure generated patterns, secret and dependency hygiene, and secure-by-default coding guidance.",
      "category": "security",
      "version": "2.0",
      "tags": [
        "ai-generated-code",
        "llm-security",
        "secure-coding",
        "owasp-llm"
      ],
      "url": "https://mejbaurbahar.github.io/software-tester-skills/skills/ai-code-security/",
      "source": "https://github.com/mejbaurbahar/software-tester-skills/tree/main/skills/ai-code-security"
    },
    {
      "name": "ai-ml-testing",
      "description": "Use when testing a classical ML model or ML-powered feature \u2014 accuracy/precision/recall/F1 evaluation, model regression testing, bias/fairness testing, and ML pipeline robustness. For LLM/generative-AI-specific testing (prompts, hallucination, RAG), use llm-testing instead.",
      "category": "ai",
      "version": "2.0",
      "tags": [
        "machine-learning",
        "model-evaluation",
        "drift",
        "fairness",
        "data-quality"
      ],
      "url": "https://mejbaurbahar.github.io/software-tester-skills/skills/ai-ml-testing/",
      "source": "https://github.com/mejbaurbahar/software-tester-skills/tree/main/skills/ai-ml-testing"
    },
    {
      "name": "analytics-tracking-testing",
      "description": "Use when validating analytics and tracking \u2014 GA4/GTM dataLayer, Segment/Amplitude/Mixpanel events, pixels (Meta, TikTok), server-side tagging, consent mode, UTM/attribution, event schema/tracking plan conformance, and data parity with the backend.",
      "category": "domain",
      "version": "2.0",
      "tags": [
        "analytics",
        "ga4",
        "gtm",
        "datalayer",
        "segment",
        "tracking-plan",
        "consent",
        "utm",
        "attribution",
        "pixels"
      ],
      "url": "https://mejbaurbahar.github.io/software-tester-skills/skills/analytics-tracking-testing/",
      "source": "https://github.com/mejbaurbahar/software-tester-skills/tree/main/skills/analytics-tracking-testing"
    },
    {
      "name": "api-testing",
      "description": "Use when testing REST/GraphQL APIs directly \u2014 status codes, schema/contract validation, auth, pagination, rate limits, idempotency, and error responses. Use instead of driving the UI when the question is really about the API layer.",
      "category": "api-backend",
      "version": "2.0",
      "tags": [
        "rest",
        "api",
        "contract",
        "status-codes",
        "pagination",
        "idempotency"
      ],
      "url": "https://mejbaurbahar.github.io/software-tester-skills/skills/api-testing/",
      "source": "https://github.com/mejbaurbahar/software-tester-skills/tree/main/skills/api-testing"
    },
    {
      "name": "authn-authz-testing",
      "description": "Use when testing authentication and authorization \u2014 login, MFA, OAuth2/OIDC, SAML, JWT, sessions/cookies, password reset, RBAC/ABAC, IDOR/BOLA, privilege escalation, multi-tenant isolation, and account-takeover paths.",
      "category": "security",
      "version": "2.0",
      "tags": [
        "authentication",
        "authorization",
        "oauth2",
        "oidc",
        "jwt",
        "rbac",
        "idor",
        "bola",
        "mfa",
        "session",
        "multi-tenant"
      ],
      "url": "https://mejbaurbahar.github.io/software-tester-skills/skills/authn-authz-testing/",
      "source": "https://github.com/mejbaurbahar/software-tester-skills/tree/main/skills/authn-authz-testing"
    },
    {
      "name": "autonomous-qa-orchestration",
      "description": "Use when asked to autonomously test an application end-to-end with minimal hand-holding \u2014 discover, explore, plan, execute, investigate, report, and verify fixes as one continuous QA pass. The top-level playbook that pulls in the other testing skills as needed.",
      "category": "strategy",
      "version": "2.0",
      "tags": [
        "autonomous-testing",
        "qa-agent",
        "exploration",
        "triage",
        "orchestration"
      ],
      "url": "https://mejbaurbahar.github.io/software-tester-skills/skills/autonomous-qa-orchestration/",
      "source": "https://github.com/mejbaurbahar/software-tester-skills/tree/main/skills/autonomous-qa-orchestration"
    },
    {
      "name": "bdd-gherkin-testing",
      "description": "Use when writing or automating behavior-driven development (BDD) specs \u2014 Gherkin Given/When/Then, Cucumber, SpecFlow, Behave, pytest-bdd, Playwright-BDD, example mapping, living documentation, and fixing brittle or imperative feature files.",
      "category": "functional",
      "version": "2.0",
      "tags": [
        "bdd",
        "gherkin",
        "cucumber",
        "behave",
        "specflow",
        "example-mapping",
        "living-documentation"
      ],
      "url": "https://mejbaurbahar.github.io/software-tester-skills/skills/bdd-gherkin-testing/",
      "source": "https://github.com/mejbaurbahar/software-tester-skills/tree/main/skills/bdd-gherkin-testing"
    },
    {
      "name": "blockchain-smart-contract-testing",
      "description": "Use when testing smart contracts and dApps \u2014 Solidity/Foundry/Hardhat tests, fuzz and invariant testing, fork tests, gas profiling, reentrancy/overflow/access-control vulnerabilities, Slither/Echidna static and fuzz analysis, upgrade safety, oracle/MEV risks, and wallet UI flows.",
      "category": "platform",
      "version": "2.0",
      "tags": [
        "blockchain",
        "solidity",
        "smart-contracts",
        "foundry",
        "hardhat",
        "echidna",
        "slither",
        "reentrancy",
        "invariants",
        "web3"
      ],
      "url": "https://mejbaurbahar.github.io/software-tester-skills/skills/blockchain-smart-contract-testing/",
      "source": "https://github.com/mejbaurbahar/software-tester-skills/tree/main/skills/blockchain-smart-contract-testing"
    },
    {
      "name": "bug-reporting",
      "description": "Use whenever filing a defect found during any kind of testing \u2014 applies a standard severity scale, report template, and evidence requirements so bug reports are consistent, reproducible and actionable.",
      "category": "strategy",
      "version": "2.0",
      "tags": [
        "bug-report",
        "defect",
        "severity",
        "reproduction-steps",
        "evidence"
      ],
      "url": "https://mejbaurbahar.github.io/software-tester-skills/skills/bug-reporting/",
      "source": "https://github.com/mejbaurbahar/software-tester-skills/tree/main/skills/bug-reporting"
    },
    {
      "name": "chaos-resilience-testing",
      "description": "Use when deliberately injecting failure (network latency/loss, service/dependency crash, resource exhaustion) to verify a system degrades gracefully instead of cascading \u2014 retries, circuit breakers, timeouts, backpressure. Requires explicit authorization and a scoped blast radius; never run against unscoped production without sign-off.",
      "category": "non-functional",
      "version": "2.0",
      "tags": [
        "chaos-engineering",
        "resilience",
        "fault-injection",
        "circuit-breaker",
        "retries"
      ],
      "url": "https://mejbaurbahar.github.io/software-tester-skills/skills/chaos-resilience-testing/",
      "source": "https://github.com/mejbaurbahar/software-tester-skills/tree/main/skills/chaos-resilience-testing"
    },
    {
      "name": "chatbot-voice-agent-testing",
      "description": "Use when testing chatbots, voice assistants, or conversational AI agents specifically \u2014 multi-turn conversation flow, context/memory retention, intent recognition, STT/TTS accuracy, interrupt handling, and fallback behavior. Builds on llm-testing for the underlying model concerns.",
      "category": "ai",
      "version": "2.0",
      "tags": [
        "chatbot",
        "voice-agent",
        "conversation",
        "intent",
        "stt",
        "tts"
      ],
      "url": "https://mejbaurbahar.github.io/software-tester-skills/skills/chatbot-voice-agent-testing/",
      "source": "https://github.com/mejbaurbahar/software-tester-skills/tree/main/skills/chatbot-voice-agent-testing"
    },
    {
      "name": "cicd-testing",
      "description": "Use when designing or debugging test execution in CI/CD pipelines \u2014 PR gates, test tiering (smoke/regression/nightly), parallelization/sharding, quality gates, flaky-test tracking, and failure notification wiring. Covers GitHub Actions, GitLab CI, Jenkins and similar.",
      "category": "automation",
      "version": "2.0",
      "tags": [
        "ci-cd",
        "quality-gates",
        "test-sharding",
        "github-actions",
        "pipelines"
      ],
      "url": "https://mejbaurbahar.github.io/software-tester-skills/skills/cicd-testing/",
      "source": "https://github.com/mejbaurbahar/software-tester-skills/tree/main/skills/cicd-testing"
    },
    {
      "name": "cli-testing",
      "description": "Use when testing command-line tools and scripts \u2014 exit codes, stdout/stderr contracts, flags and argument parsing, help/version output, stdin/pipes, env/config precedence, cross-platform paths, signals, idempotency, and Bats/pytest/expect-based automation.",
      "category": "platform",
      "version": "2.0",
      "tags": [
        "cli",
        "command-line",
        "bats",
        "exit-codes",
        "stdout",
        "shell",
        "expect",
        "argparse",
        "cross-platform"
      ],
      "url": "https://mejbaurbahar.github.io/software-tester-skills/skills/cli-testing/",
      "source": "https://github.com/mejbaurbahar/software-tester-skills/tree/main/skills/cli-testing"
    },
    {
      "name": "cloud-infrastructure-testing",
      "description": "Use when testing cloud/infrastructure concerns \u2014 Docker/Kubernetes deployments, serverless functions, managed-service integration (S3, queues, API Gateway), disaster recovery/failover, and infra-as-code correctness on AWS/Azure/GCP.",
      "category": "operations",
      "version": "2.0",
      "tags": [
        "docker",
        "kubernetes",
        "cloud",
        "failover",
        "infrastructure"
      ],
      "url": "https://mejbaurbahar.github.io/software-tester-skills/skills/cloud-infrastructure-testing/",
      "source": "https://github.com/mejbaurbahar/software-tester-skills/tree/main/skills/cloud-infrastructure-testing"
    },
    {
      "name": "code-coverage-analysis",
      "description": "Use when measuring or improving test coverage \u2014 line, branch, function, condition/MC-DC and diff/patch coverage; coverage tools (coverage.py, Istanbul/c8, JaCoCo, gcov, go cover); setting sensible thresholds; and finding meaningful gaps rather than chasing 100%.",
      "category": "automation",
      "version": "2.0",
      "tags": [
        "code-coverage",
        "branch-coverage",
        "jacoco",
        "istanbul",
        "coverage-py",
        "diff-coverage",
        "mc-dc"
      ],
      "url": "https://mejbaurbahar.github.io/software-tester-skills/skills/code-coverage-analysis/",
      "source": "https://github.com/mejbaurbahar/software-tester-skills/tree/main/skills/code-coverage-analysis"
    },
    {
      "name": "compatibility-testing",
      "description": "Use when verifying software compatibility across environments, operating systems, database versions, backward/forward API compatibility, and migration rollback safety.",
      "category": "non-functional",
      "version": "2.0",
      "tags": [
        "compatibility",
        "backward-compatibility",
        "upgrades",
        "environments"
      ],
      "url": "https://mejbaurbahar.github.io/software-tester-skills/skills/compatibility-testing/",
      "source": "https://github.com/mejbaurbahar/software-tester-skills/tree/main/skills/compatibility-testing"
    },
    {
      "name": "compliance-testing",
      "description": "Use when testing for regulatory and standards compliance \u2014 GDPR/CCPA privacy rights, HIPAA, PCI-DSS, SOC 2, ISO 27001, WCAG/ADA/EAA, audit logging, data retention/deletion, consent, and generating verifiable audit evidence.",
      "category": "compliance",
      "version": "2.0",
      "tags": [
        "compliance",
        "gdpr",
        "hipaa",
        "pci-dss",
        "soc2",
        "iso27001",
        "privacy",
        "audit-trail",
        "consent",
        "retention",
        "ada"
      ],
      "url": "https://mejbaurbahar.github.io/software-tester-skills/skills/compliance-testing/",
      "source": "https://github.com/mejbaurbahar/software-tester-skills/tree/main/skills/compliance-testing"
    },
    {
      "name": "concurrency-race-condition-testing",
      "description": "Use when testing thread-safety, race conditions, deadlocks, double-submit, idempotency, optimistic/pessimistic locking, async ordering bugs, and flaky concurrency failures \u2014 with TSan, go -race, stress loops, barrier-based harnesses and parallel API calls.",
      "category": "code-level",
      "version": "2.0",
      "tags": [
        "concurrency",
        "race-condition",
        "deadlock",
        "idempotency",
        "thread-safety",
        "tsan",
        "locking"
      ],
      "url": "https://mejbaurbahar.github.io/software-tester-skills/skills/concurrency-race-condition-testing/",
      "source": "https://github.com/mejbaurbahar/software-tester-skills/tree/main/skills/concurrency-race-condition-testing"
    },
    {
      "name": "configuration-feature-flag-testing",
      "description": "Use when testing configuration, environment variables, secrets handling and feature flags \u2014 flag matrices, progressive rollouts, kill switches, targeting rules, stale flag cleanup, config drift between environments, and safe defaults (LaunchDarkly, Unleash, GrowthBook, OpenFeature).",
      "category": "non-functional",
      "version": "2.0",
      "tags": [
        "feature-flags",
        "configuration",
        "launchdarkly",
        "unleash",
        "openfeature",
        "rollout",
        "kill-switch",
        "config-drift",
        "twelve-factor"
      ],
      "url": "https://mejbaurbahar.github.io/software-tester-skills/skills/configuration-feature-flag-testing/",
      "source": "https://github.com/mejbaurbahar/software-tester-skills/tree/main/skills/configuration-feature-flag-testing"
    },
    {
      "name": "contract-testing",
      "description": "Use when testing integrations between services \u2014 consumer-driven contracts, microservice boundaries, event/message-queue testing (Kafka, webhooks), schema evolution, and backward compatibility between independently-deployed services.",
      "category": "api-backend",
      "version": "2.0",
      "tags": [
        "pact",
        "consumer-driven-contracts",
        "microservices",
        "schema"
      ],
      "url": "https://mejbaurbahar.github.io/software-tester-skills/skills/contract-testing/",
      "source": "https://github.com/mejbaurbahar/software-tester-skills/tree/main/skills/contract-testing"
    },
    {
      "name": "cross-browser-testing",
      "description": "Use when testing across multiple browser engines, operating systems, and viewport dimensions \u2014 Chromium, Gecko (Firefox), WebKit (Safari), responsive breakpoints, and engine-specific CSS/JS quirks.",
      "category": "web",
      "version": "2.0",
      "tags": [
        "cross-browser",
        "chromium",
        "firefox",
        "webkit",
        "responsive"
      ],
      "url": "https://mejbaurbahar.github.io/software-tester-skills/skills/cross-browser-testing/",
      "source": "https://github.com/mejbaurbahar/software-tester-skills/tree/main/skills/cross-browser-testing"
    },
    {
      "name": "data-migration-testing",
      "description": "Use when testing database schema migrations, system replatforming, or data migrations between systems \u2014 pre/post reconciliation, zero-downtime expand/contract, rollback rehearsal, cutover plans, performance of backfills, and data lineage validation.",
      "category": "data",
      "version": "2.0",
      "tags": [
        "data-migration",
        "schema-migration",
        "cutover",
        "rollback",
        "expand-contract",
        "reconciliation",
        "flyway",
        "liquibase"
      ],
      "url": "https://mejbaurbahar.github.io/software-tester-skills/skills/data-migration-testing/",
      "source": "https://github.com/mejbaurbahar/software-tester-skills/tree/main/skills/data-migration-testing"
    },
    {
      "name": "data-pipeline-etl-testing",
      "description": "Use when testing ETL/ELT pipelines, data warehouses, dbt models, Spark/Airflow jobs, and analytics data quality \u2014 schema, row-count and checksum reconciliation, null/uniqueness/referential rules, freshness, SCD logic, Great Expectations/dbt tests, and idempotent reruns.",
      "category": "data",
      "version": "2.0",
      "tags": [
        "etl",
        "elt",
        "data-quality",
        "dbt",
        "great-expectations",
        "airflow",
        "spark",
        "reconciliation",
        "data-warehouse"
      ],
      "url": "https://mejbaurbahar.github.io/software-tester-skills/skills/data-pipeline-etl-testing/",
      "source": "https://github.com/mejbaurbahar/software-tester-skills/tree/main/skills/data-pipeline-etl-testing"
    },
    {
      "name": "database-testing",
      "description": "Use when verifying data integrity, CRUD correctness at the persistence layer, migrations, transactions/concurrency, or query correctness/performance \u2014 SQL and NoSQL. Use whenever a bug claim needs to be confirmed against actual stored state, not just UI/API appearance.",
      "category": "data",
      "version": "2.0",
      "tags": [
        "database",
        "sql",
        "acid",
        "migrations",
        "transactions",
        "query-performance"
      ],
      "url": "https://mejbaurbahar.github.io/software-tester-skills/skills/database-testing/",
      "source": "https://github.com/mejbaurbahar/software-tester-skills/tree/main/skills/database-testing"
    },
    {
      "name": "date-time-timezone-testing",
      "description": "Use when testing anything involving dates, times, time zones, DST, leap years/seconds, scheduling, expiry, recurring events, cron jobs, or locale calendars \u2014 with frozen clocks, boundary calendars, and the classic time bugs checklist.",
      "category": "code-level",
      "version": "2.0",
      "tags": [
        "datetime",
        "timezone",
        "dst",
        "leap-year",
        "scheduling",
        "cron",
        "clock-mocking"
      ],
      "url": "https://mejbaurbahar.github.io/software-tester-skills/skills/date-time-timezone-testing/",
      "source": "https://github.com/mejbaurbahar/software-tester-skills/tree/main/skills/date-time-timezone-testing"
    },
    {
      "name": "desktop-app-testing",
      "description": "Use when testing desktop applications \u2014 Electron, Tauri, WPF/WinForms, Qt, macOS/Cocoa, GTK \u2014 covering UI automation (Playwright for Electron, WinAppDriver, pywinauto, Appium Mac2), installers/auto-update, OS integration, permissions, multi-monitor/DPI, and crash reporting.",
      "category": "platform",
      "version": "2.0",
      "tags": [
        "desktop",
        "electron",
        "tauri",
        "wpf",
        "qt",
        "macos",
        "windows",
        "installer",
        "auto-update",
        "ui-automation"
      ],
      "url": "https://mejbaurbahar.github.io/software-tester-skills/skills/desktop-app-testing/",
      "source": "https://github.com/mejbaurbahar/software-tester-skills/tree/main/skills/desktop-app-testing"
    },
    {
      "name": "disaster-recovery-backup-testing",
      "description": "Use when validating backup, restore, high availability and disaster recovery \u2014 RTO/RPO verification, restore drills, region failover, data corruption and ransomware recovery, runbooks, game days, and backup integrity checks for databases and storage.",
      "category": "non-functional",
      "version": "2.0",
      "tags": [
        "disaster-recovery",
        "backup",
        "restore",
        "rto",
        "rpo",
        "failover",
        "game-day",
        "business-continuity",
        "ransomware"
      ],
      "url": "https://mejbaurbahar.github.io/software-tester-skills/skills/disaster-recovery-backup-testing/",
      "source": "https://github.com/mejbaurbahar/software-tester-skills/tree/main/skills/disaster-recovery-backup-testing"
    },
    {
      "name": "e2e-testing",
      "description": "Use when automating end-to-end user journeys through the browser or UI \u2014 Playwright, Cypress, user critical paths, resilient locators, session storage, network stubbing, and visual artifacts.",
      "category": "web",
      "version": "2.0",
      "tags": [
        "e2e",
        "playwright",
        "cypress",
        "user-journeys",
        "locators"
      ],
      "url": "https://mejbaurbahar.github.io/software-tester-skills/skills/e2e-testing/",
      "source": "https://github.com/mejbaurbahar/software-tester-skills/tree/main/skills/e2e-testing"
    },
    {
      "name": "email-notification-testing",
      "description": "Use when testing transactional/marketing email, SMS, push and in-app notifications \u2014 capture inboxes (Mailpit, MailHog, Mailosaur), rendering across clients, links/tokens, SPF/DKIM/DMARC deliverability, unsubscribe/consent, timing, retries, and localization.",
      "category": "functional",
      "version": "2.0",
      "tags": [
        "email",
        "notifications",
        "sms",
        "push",
        "mailpit",
        "deliverability",
        "dkim",
        "spf",
        "dmarc",
        "unsubscribe"
      ],
      "url": "https://mejbaurbahar.github.io/software-tester-skills/skills/email-notification-testing/",
      "source": "https://github.com/mejbaurbahar/software-tester-skills/tree/main/skills/email-notification-testing"
    },
    {
      "name": "event-driven-messaging-testing",
      "description": "Use when testing message queues and event streams \u2014 Kafka, RabbitMQ, SQS/SNS, Pub/Sub, NATS, webhooks \u2014 covering schema evolution, ordering, at-least-once delivery, idempotent consumers, dead-letter queues, replay, and eventual consistency.",
      "category": "api-backend",
      "version": "2.0",
      "tags": [
        "kafka",
        "rabbitmq",
        "sqs",
        "event-driven",
        "dlq",
        "idempotency",
        "schema-registry",
        "webhooks",
        "outbox"
      ],
      "url": "https://mejbaurbahar.github.io/software-tester-skills/skills/event-driven-messaging-testing/",
      "source": "https://github.com/mejbaurbahar/software-tester-skills/tree/main/skills/event-driven-messaging-testing"
    },
    {
      "name": "exploratory-testing",
      "description": "Use when conducting exploratory testing, unscripted bug hunting, and session-based test management \u2014 test charters, heuristics (SFDIPOT, Tours), timeboxed sessions, and exploratory debriefing.",
      "category": "functional",
      "version": "2.0",
      "tags": [
        "exploratory",
        "sbtm",
        "heuristics",
        "tours",
        "charters"
      ],
      "url": "https://mejbaurbahar.github.io/software-tester-skills/skills/exploratory-testing/",
      "source": "https://github.com/mejbaurbahar/software-tester-skills/tree/main/skills/exploratory-testing"
    },
    {
      "name": "flaky-test-management",
      "description": "Use when tests pass and fail intermittently \u2014 detecting, quarantining, root-causing and eliminating flaky tests (async waits, shared state, order dependence, time, network, resource contention) with retries policy, flake dashboards and CI reruns.",
      "category": "automation",
      "version": "2.0",
      "tags": [
        "flaky-tests",
        "quarantine",
        "test-stability",
        "ci",
        "retries",
        "determinism"
      ],
      "url": "https://mejbaurbahar.github.io/software-tester-skills/skills/flaky-test-management/",
      "source": "https://github.com/mejbaurbahar/software-tester-skills/tree/main/skills/flaky-test-management"
    },
    {
      "name": "functional-testing",
      "description": "Use when verifying that a feature or user flow behaves according to requirements/specs \u2014 functional correctness testing of forms, workflows, business logic, and CRUD operations, whether done manually or via automation.",
      "category": "functional",
      "version": "2.0",
      "tags": [
        "functional",
        "forms",
        "workflows",
        "business-logic",
        "crud"
      ],
      "url": "https://mejbaurbahar.github.io/software-tester-skills/skills/functional-testing/",
      "source": "https://github.com/mejbaurbahar/software-tester-skills/tree/main/skills/functional-testing"
    },
    {
      "name": "fuzz-testing",
      "description": "Use when hunting crashes, hangs, memory bugs and parser/protocol vulnerabilities with random or coverage-guided inputs \u2014 fuzzing with AFL++, libFuzzer, Jazzer, Atheris, go-fuzz, cargo-fuzz, Schemathesis, and HTTP/API fuzzing, plus corpus and crash triage.",
      "category": "code-level",
      "version": "2.0",
      "tags": [
        "fuzzing",
        "afl",
        "libfuzzer",
        "atheris",
        "schemathesis",
        "crash-triage",
        "sanitizers",
        "security"
      ],
      "url": "https://mejbaurbahar.github.io/software-tester-skills/skills/fuzz-testing/",
      "source": "https://github.com/mejbaurbahar/software-tester-skills/tree/main/skills/fuzz-testing"
    },
    {
      "name": "game-testing",
      "description": "Use when testing video games \u2014 gameplay/balance, playtesting, performance (FPS, frame pacing, memory), input devices, save/load integrity, multiplayer/netcode, platform certification (TRC/TCR), localization, anti-cheat, monetization, and Unity/Unreal automation.",
      "category": "platform",
      "version": "2.0",
      "tags": [
        "game-testing",
        "gameplay",
        "playtesting",
        "fps",
        "netcode",
        "multiplayer",
        "unity",
        "unreal",
        "certification",
        "soak"
      ],
      "url": "https://mejbaurbahar.github.io/software-tester-skills/skills/game-testing/",
      "source": "https://github.com/mejbaurbahar/software-tester-skills/tree/main/skills/game-testing"
    },
    {
      "name": "graphql-testing",
      "description": "Use when testing GraphQL APIs \u2014 queries, mutations, subscriptions, schema validation and breaking-change detection, N+1 queries, depth/complexity limits, introspection exposure, authorization per field, batching abuse, and federation contracts.",
      "category": "api-backend",
      "version": "2.0",
      "tags": [
        "graphql",
        "apollo",
        "schema",
        "n+1",
        "federation",
        "introspection",
        "authorization",
        "subscriptions"
      ],
      "url": "https://mejbaurbahar.github.io/software-tester-skills/skills/graphql-testing/",
      "source": "https://github.com/mejbaurbahar/software-tester-skills/tree/main/skills/graphql-testing"
    },
    {
      "name": "iac-container-security-testing",
      "description": "Use when testing Infrastructure-as-Code and container configuration \u2014 Terraform/CloudFormation/Helm/Kubernetes scanning (Checkov, tfsec, KICS, kube-linter), policy-as-code (OPA/Conftest/Kyverno), Dockerfile lint (hadolint), image scanning (Trivy), CIS benchmarks, and drift detection.",
      "category": "security",
      "version": "2.0",
      "tags": [
        "iac",
        "terraform",
        "kubernetes",
        "docker",
        "helm",
        "opa",
        "conftest",
        "kyverno",
        "checkov",
        "trivy",
        "cis-benchmark",
        "policy-as-code"
      ],
      "url": "https://mejbaurbahar.github.io/software-tester-skills/skills/iac-container-security-testing/",
      "source": "https://github.com/mejbaurbahar/software-tester-skills/tree/main/skills/iac-container-security-testing"
    },
    {
      "name": "installation-upgrade-testing",
      "description": "Use when testing software installation, upgrade, downgrade, uninstall and packaging \u2014 installers (MSI/DMG/DEB/RPM/Docker/Helm/npm/pip), silent installs, permission and disk edge cases, data/config preservation across versions, rollback, and version-skew.",
      "category": "non-functional",
      "version": "2.0",
      "tags": [
        "installation",
        "upgrade",
        "uninstall",
        "packaging",
        "rollback",
        "docker",
        "helm",
        "msi",
        "deb",
        "version-skew"
      ],
      "url": "https://mejbaurbahar.github.io/software-tester-skills/skills/installation-upgrade-testing/",
      "source": "https://github.com/mejbaurbahar/software-tester-skills/tree/main/skills/installation-upgrade-testing"
    },
    {
      "name": "integration-testing",
      "description": "Use when verifying interactions between multiple components, modules, or services \u2014 API-to-database persistence, message queues, external service adapters, and Testcontainers.",
      "category": "code-level",
      "version": "2.0",
      "tags": [
        "integration",
        "testcontainers",
        "persistence",
        "queues",
        "adapters"
      ],
      "url": "https://mejbaurbahar.github.io/software-tester-skills/skills/integration-testing/",
      "source": "https://github.com/mejbaurbahar/software-tester-skills/tree/main/skills/integration-testing"
    },
    {
      "name": "iot-embedded-testing",
      "description": "Use when testing IoT devices, firmware and embedded systems \u2014 hardware-in-the-loop, simulators/emulators, MQTT/BLE/Zigbee/LoRa protocols, OTA updates, power/battery, sensor edge cases, constrained resources, connectivity loss, and device fleet security.",
      "category": "platform",
      "version": "2.0",
      "tags": [
        "iot",
        "embedded",
        "firmware",
        "hil",
        "mqtt",
        "ble",
        "ota",
        "edge",
        "fleet",
        "real-time"
      ],
      "url": "https://mejbaurbahar.github.io/software-tester-skills/skills/iot-embedded-testing/",
      "source": "https://github.com/mejbaurbahar/software-tester-skills/tree/main/skills/iot-embedded-testing"
    },
    {
      "name": "llm-security-audit",
      "description": "Use when auditing an LLM application's security posture \u2014 OWASP Top 10 for LLMs, threat modelling, data-leakage and prompt-handling review, and compliance mapping to NIST AI RMF and ISO 42001.",
      "category": "ai",
      "version": "2.0",
      "tags": [
        "llm-security",
        "owasp-llm",
        "prompt-injection",
        "nist-ai-rmf",
        "audit"
      ],
      "url": "https://mejbaurbahar.github.io/software-tester-skills/skills/llm-security-audit/",
      "source": "https://github.com/mejbaurbahar/software-tester-skills/tree/main/skills/llm-security-audit"
    },
    {
      "name": "llm-testing",
      "description": "Use when testing LLM-powered features \u2014 prompt testing, hallucination/faithfulness checks, RAG evaluation, agent/tool-use testing, prompt injection and LLM security, regression testing across model/prompt versions, and cost/latency/token budget testing.",
      "category": "ai",
      "version": "2.0",
      "tags": [
        "llm",
        "prompts",
        "hallucination",
        "rag",
        "evals",
        "token-budget"
      ],
      "url": "https://mejbaurbahar.github.io/software-tester-skills/skills/llm-testing/",
      "source": "https://github.com/mejbaurbahar/software-tester-skills/tree/main/skills/llm-testing"
    },
    {
      "name": "localization-testing",
      "description": "Use when verifying internationalization (i18n) and localization (l10n) \u2014 string truncation, pseudo-localization, Right-to-Left (RTL) layout rendering, date/time/currency formatting, and UTF-8 encoding.",
      "category": "web",
      "version": "2.0",
      "tags": [
        "i18n",
        "l10n",
        "rtl",
        "unicode",
        "pseudo-localization",
        "text-expansion"
      ],
      "url": "https://mejbaurbahar.github.io/software-tester-skills/skills/localization-testing/",
      "source": "https://github.com/mejbaurbahar/software-tester-skills/tree/main/skills/localization-testing"
    },
    {
      "name": "manual-testing",
      "description": "Use when designing test cases, doing exploratory testing, writing test plans/checklists, or manually verifying a feature before or instead of automating it. Covers test case design techniques, exploratory charters, and test plan structure.",
      "category": "functional",
      "version": "2.0",
      "tags": [
        "manual-testing",
        "test-cases",
        "boundary-value",
        "decision-tables",
        "checklists"
      ],
      "url": "https://mejbaurbahar.github.io/software-tester-skills/skills/manual-testing/",
      "source": "https://github.com/mejbaurbahar/software-tester-skills/tree/main/skills/manual-testing"
    },
    {
      "name": "mcp-testing",
      "description": "Use when testing Model Context Protocol (MCP) servers \u2014 unit and integration tests, tool/resource schema validation, JSON-RPC contract checks, MCP Inspector workflows, and security review of exposed tools.",
      "category": "ai",
      "version": "2.0",
      "tags": [
        "mcp",
        "model-context-protocol",
        "json-rpc",
        "tool-schemas",
        "inspector"
      ],
      "url": "https://mejbaurbahar.github.io/software-tester-skills/skills/mcp-testing/",
      "source": "https://github.com/mejbaurbahar/software-tester-skills/tree/main/skills/mcp-testing"
    },
    {
      "name": "memory-leak-resource-testing",
      "description": "Use when diagnosing or preventing memory leaks, unbounded growth, file-descriptor/connection/thread leaks, GC pressure, OOM kills, and slow degradation in long-running services, browsers, and mobile apps \u2014 heap snapshots, profilers, soak tests.",
      "category": "non-functional",
      "version": "2.0",
      "tags": [
        "memory-leak",
        "heap",
        "profiling",
        "soak",
        "gc",
        "file-descriptors",
        "oom",
        "resource-leak"
      ],
      "url": "https://mejbaurbahar.github.io/software-tester-skills/skills/memory-leak-resource-testing/",
      "source": "https://github.com/mejbaurbahar/software-tester-skills/tree/main/skills/memory-leak-resource-testing"
    },
    {
      "name": "microservices-testing",
      "description": "Use when designing a test strategy for microservices or distributed systems \u2014 service/component tests, consumer-driven contracts, service virtualization, testing in production, sagas and distributed transactions, cross-service E2E minimization, and the test honeycomb.",
      "category": "api-backend",
      "version": "2.0",
      "tags": [
        "microservices",
        "honeycomb",
        "service-virtualization",
        "saga",
        "distributed-systems",
        "testing-in-production"
      ],
      "url": "https://mejbaurbahar.github.io/software-tester-skills/skills/microservices-testing/",
      "source": "https://github.com/mejbaurbahar/software-tester-skills/tree/main/skills/microservices-testing"
    },
    {
      "name": "mobile-testing",
      "description": "Use when testing mobile apps (iOS/Android native, or responsive/mobile-web) \u2014 device/viewport matrices, touch gesture testing, mobile-specific network and lifecycle conditions, and app-store readiness checks.",
      "category": "platform",
      "version": "2.0",
      "tags": [
        "mobile",
        "ios",
        "android",
        "touch",
        "viewport",
        "responsive"
      ],
      "url": "https://mejbaurbahar.github.io/software-tester-skills/skills/mobile-testing/",
      "source": "https://github.com/mejbaurbahar/software-tester-skills/tree/main/skills/mobile-testing"
    },
    {
      "name": "mutation-testing",
      "description": "Use when measuring test suite quality, finding false positives, and eliminating blind spots \u2014 injecting code mutations (mutants), mutation score, Mutmut, Stryker, and kill rate analysis.",
      "category": "code-level",
      "version": "2.0",
      "tags": [
        "mutation-testing",
        "stryker",
        "mutmut",
        "test-quality",
        "kill-rate"
      ],
      "url": "https://mejbaurbahar.github.io/software-tester-skills/skills/mutation-testing/",
      "source": "https://github.com/mejbaurbahar/software-tester-skills/tree/main/skills/mutation-testing"
    },
    {
      "name": "observability-testing",
      "description": "Use when correlating a test failure or production issue across logs, metrics, and traces to find root cause; when verifying that a feature emits the logging/metrics/alerting it needs; or when doing shift-right testing via production monitoring.",
      "category": "operations",
      "version": "2.0",
      "tags": [
        "observability",
        "logs",
        "metrics",
        "traces",
        "opentelemetry",
        "monitoring"
      ],
      "url": "https://mejbaurbahar.github.io/software-tester-skills/skills/observability-testing/",
      "source": "https://github.com/mejbaurbahar/software-tester-skills/tree/main/skills/observability-testing"
    },
    {
      "name": "payment-ecommerce-testing",
      "description": "Use when testing checkout, payments, carts, coupons, taxes, inventory, orders, refunds, and subscriptions \u2014 Stripe/PayPal/Adyen sandboxes, test cards, 3-D Secure, webhooks, idempotency, rounding, PCI scope, and WooCommerce/Shopify flows.",
      "category": "domain",
      "version": "2.0",
      "tags": [
        "payments",
        "ecommerce",
        "checkout",
        "stripe",
        "paypal",
        "woocommerce",
        "shopify",
        "refunds",
        "subscriptions",
        "pci"
      ],
      "url": "https://mejbaurbahar.github.io/software-tester-skills/skills/payment-ecommerce-testing/",
      "source": "https://github.com/mejbaurbahar/software-tester-skills/tree/main/skills/payment-ecommerce-testing"
    },
    {
      "name": "performance-testing",
      "description": "Use for load/stress/soak/spike testing, Core Web Vitals audits, Lighthouse checks, API latency benchmarking, and diagnosing slow pages or endpoints. Covers both frontend perf and backend load testing.",
      "category": "non-functional",
      "version": "2.0",
      "tags": [
        "performance",
        "load-testing",
        "k6",
        "locust",
        "lighthouse",
        "web-vitals"
      ],
      "url": "https://mejbaurbahar.github.io/software-tester-skills/skills/performance-testing/",
      "source": "https://github.com/mejbaurbahar/software-tester-skills/tree/main/skills/performance-testing"
    },
    {
      "name": "production-monitoring-synthetic-testing",
      "description": "Use when testing in production safely (shift-right) \u2014 synthetic monitoring, canary checks, uptime probes, Playwright/Checkly/Datadog synthetics, real-user monitoring, SLO/SLI validation, alert testing, dark launches, traffic shadowing and observability-driven QA.",
      "category": "operations",
      "version": "2.0",
      "tags": [
        "synthetic-monitoring",
        "shift-right",
        "slo",
        "sli",
        "canary",
        "rum",
        "uptime",
        "checkly",
        "alerting",
        "testing-in-production"
      ],
      "url": "https://mejbaurbahar.github.io/software-tester-skills/skills/production-monitoring-synthetic-testing/",
      "source": "https://github.com/mejbaurbahar/software-tester-skills/tree/main/skills/production-monitoring-synthetic-testing"
    },
    {
      "name": "property-based-testing",
      "description": "Use when example-based tests miss edge cases \u2014 property-based testing with Hypothesis, fast-check, jqwik, QuickCheck, or proptest; invariants, round-trip, oracle and metamorphic properties, shrinking, stateful/model-based tests.",
      "category": "code-level",
      "version": "2.0",
      "tags": [
        "property-based",
        "hypothesis",
        "fast-check",
        "quickcheck",
        "invariants",
        "shrinking",
        "stateful-testing"
      ],
      "url": "https://mejbaurbahar.github.io/software-tester-skills/skills/property-based-testing/",
      "source": "https://github.com/mejbaurbahar/software-tester-skills/tree/main/skills/property-based-testing"
    },
    {
      "name": "pwa-offline-testing",
      "description": "Use when testing Progressive Web Apps and offline-first apps \u2014 service workers, caching strategies, manifest/installability, background sync, push notifications, storage quotas, update flows, and flaky-network behavior.",
      "category": "web",
      "version": "2.0",
      "tags": [
        "pwa",
        "service-worker",
        "offline",
        "workbox",
        "manifest",
        "background-sync",
        "web-push",
        "indexeddb"
      ],
      "url": "https://mejbaurbahar.github.io/software-tester-skills/skills/pwa-offline-testing/",
      "source": "https://github.com/mejbaurbahar/software-tester-skills/tree/main/skills/pwa-offline-testing"
    },
    {
      "name": "qa-code-intelligence",
      "description": "Use when reading source code to spot testability/risk issues before writing tests, generating test cases automatically from requirements/schemas/code, or doing root-cause/bug intelligence work \u2014 clustering failures, deduping reports, and reasoning from stack traces/logs to a likely cause.",
      "category": "strategy",
      "version": "2.0",
      "tags": [
        "static-analysis",
        "testability",
        "test-generation",
        "root-cause-analysis"
      ],
      "url": "https://mejbaurbahar.github.io/software-tester-skills/skills/qa-code-intelligence/",
      "source": "https://github.com/mejbaurbahar/software-tester-skills/tree/main/skills/qa-code-intelligence"
    },
    {
      "name": "qa-engineering",
      "description": "Use when setting up or improving end-to-end QA practice \u2014 systematic test design, automation strategy (Playwright/Cypress/Selenium), defect lifecycle, regression and flaky-test control, and QA mindset for catching bugs before users do.",
      "category": "strategy",
      "version": "2.0",
      "tags": [
        "qa",
        "test-automation",
        "defect-lifecycle",
        "test-strategy",
        "quality"
      ],
      "url": "https://mejbaurbahar.github.io/software-tester-skills/skills/qa-engineering/",
      "source": "https://github.com/mejbaurbahar/software-tester-skills/tree/main/skills/qa-engineering"
    },
    {
      "name": "qa-fundamentals",
      "description": "Use when scoping test strategy, writing a test plan, classifying testing types (QC vs QA, verification vs validation), applying risk-based prioritization, or navigating SDLC/STLC/Agile testing process questions. The conceptual root the other testing skills build on.",
      "category": "strategy",
      "version": "2.0",
      "tags": [
        "stlc",
        "test-levels",
        "verification",
        "validation",
        "quality-metrics"
      ],
      "url": "https://mejbaurbahar.github.io/software-tester-skills/skills/qa-fundamentals/",
      "source": "https://github.com/mejbaurbahar/software-tester-skills/tree/main/skills/qa-fundamentals"
    },
    {
      "name": "qa-skill-router",
      "description": "Use when the user asks what to test, which testing approach or skill to use, \"where do I start\", or describes a QA task without naming a skill \u2014 routes the request to the right software-testing skills and gives the order to apply them.",
      "category": "strategy",
      "version": "2.0",
      "tags": [
        "router",
        "index",
        "catalog",
        "qa-help",
        "skill-selection",
        "getting-started"
      ],
      "url": "https://mejbaurbahar.github.io/software-tester-skills/skills/qa-skill-router/",
      "source": "https://github.com/mejbaurbahar/software-tester-skills/tree/main/skills/qa-skill-router"
    },
    {
      "name": "qa-test-harness",
      "description": "Use when the user asks to test software end to end with a live browser \u2014 inspect web apps via Chrome DevTools MCP, automate browser actions, verify APIs, run test suites, capture console/network evidence, and file structured bug reports.",
      "category": "automation",
      "version": "2.0",
      "tags": [
        "chrome-devtools",
        "browser-automation",
        "dom",
        "network",
        "console"
      ],
      "url": "https://mejbaurbahar.github.io/software-tester-skills/skills/qa-test-harness/",
      "source": "https://github.com/mejbaurbahar/software-tester-skills/tree/main/skills/qa-test-harness"
    },
    {
      "name": "rag-evaluation-testing",
      "description": "Use when testing retrieval-augmented generation (RAG) \u2014 retrieval metrics (recall@k, MRR, nDCG), chunking and embedding evaluation, faithfulness/groundedness, answer relevancy, citation accuracy, abstention, freshness, access-control filtering, and Ragas/TruLens/DeepEval pipelines.",
      "category": "ai",
      "version": "2.0",
      "tags": [
        "rag",
        "retrieval",
        "embeddings",
        "ragas",
        "groundedness",
        "faithfulness",
        "chunking",
        "vector-search",
        "citations",
        "hallucination"
      ],
      "url": "https://mejbaurbahar.github.io/software-tester-skills/skills/rag-evaluation-testing/",
      "source": "https://github.com/mejbaurbahar/software-tester-skills/tree/main/skills/rag-evaluation-testing"
    },
    {
      "name": "regression-testing",
      "description": "Use when validating that recent changes haven't broken existing functionality \u2014 building/running regression suites, deciding regression scope for a release, and impact analysis from a diff/changelog.",
      "category": "functional",
      "version": "2.0",
      "tags": [
        "regression",
        "impact-analysis",
        "test-selection",
        "git-diff"
      ],
      "url": "https://mejbaurbahar.github.io/software-tester-skills/skills/regression-testing/",
      "source": "https://github.com/mejbaurbahar/software-tester-skills/tree/main/skills/regression-testing"
    },
    {
      "name": "release-readiness-testing",
      "description": "Use when deciding whether to ship \u2014 go/no-go criteria, release checklists, canary/blue-green/progressive rollout verification, post-deploy smoke, rollback rehearsal, DORA metrics, change-risk scoring, and release sign-off reports.",
      "category": "strategy",
      "version": "2.0",
      "tags": [
        "release",
        "go-no-go",
        "canary",
        "blue-green",
        "rollback",
        "dora",
        "deployment",
        "post-deploy",
        "change-risk"
      ],
      "url": "https://mejbaurbahar.github.io/software-tester-skills/skills/release-readiness-testing/",
      "source": "https://github.com/mejbaurbahar/software-tester-skills/tree/main/skills/release-readiness-testing"
    },
    {
      "name": "requirements-testing-review",
      "description": "Use when reviewing requirements, user stories, designs or specs before coding (shift-left static testing) \u2014 finding ambiguity, missing acceptance criteria, testability gaps, contradictory rules, and NFR omissions; INVEST checks, walkthroughs, and requirement-quality scoring.",
      "category": "strategy",
      "version": "2.0",
      "tags": [
        "shift-left",
        "static-testing",
        "requirements",
        "user-stories",
        "testability",
        "invest",
        "review"
      ],
      "url": "https://mejbaurbahar.github.io/software-tester-skills/skills/requirements-testing-review/",
      "source": "https://github.com/mejbaurbahar/software-tester-skills/tree/main/skills/requirements-testing-review"
    },
    {
      "name": "scalability-capacity-testing",
      "description": "Use when determining how a system scales and how much capacity it needs \u2014 load models, capacity planning, autoscaling validation, bottleneck identification (USE/RED), stress/spike/soak/breakpoint tests, and cost-per-request analysis with k6, Locust, JMeter, Gatling.",
      "category": "non-functional",
      "version": "2.0",
      "tags": [
        "scalability",
        "capacity-planning",
        "load-testing",
        "stress",
        "spike",
        "soak",
        "breakpoint",
        "autoscaling",
        "k6",
        "little's-law"
      ],
      "url": "https://mejbaurbahar.github.io/software-tester-skills/skills/scalability-capacity-testing/",
      "source": "https://github.com/mejbaurbahar/software-tester-skills/tree/main/skills/scalability-capacity-testing"
    },
    {
      "name": "security-hardening",
      "description": "Use when hardening an application's security \u2014 OWASP Top 10 mitigations, secure coding patterns, authentication and authorization, secret handling, input validation/output encoding, and lessons from real security incidents.",
      "category": "security",
      "version": "2.0",
      "tags": [
        "hardening",
        "owasp",
        "secure-coding",
        "secrets",
        "headers"
      ],
      "url": "https://mejbaurbahar.github.io/software-tester-skills/skills/security-hardening/",
      "source": "https://github.com/mejbaurbahar/software-tester-skills/tree/main/skills/security-hardening"
    },
    {
      "name": "security-owasp",
      "description": "Use when securing a web application against OWASP Top 10 risks \u2014 authentication, authorization, input validation, XSS and CSRF prevention, secure headers, and security test cases.",
      "category": "security",
      "version": "2.0",
      "tags": [
        "owasp-top-10",
        "xss",
        "csrf",
        "injection",
        "secure-headers"
      ],
      "url": "https://mejbaurbahar.github.io/software-tester-skills/skills/security-owasp/",
      "source": "https://github.com/mejbaurbahar/software-tester-skills/tree/main/skills/security-owasp"
    },
    {
      "name": "security-testing",
      "description": "Use for authorized security/penetration testing of web apps and APIs \u2014 OWASP Top 10 checks, auth/session testing, header/config audits, and vulnerability triage. Only for systems the user owns or has explicit authorization to test.",
      "category": "security",
      "version": "2.0",
      "tags": [
        "security-testing",
        "owasp",
        "session",
        "auth-bypass",
        "vulnerabilities"
      ],
      "url": "https://mejbaurbahar.github.io/software-tester-skills/skills/security-testing/",
      "source": "https://github.com/mejbaurbahar/software-tester-skills/tree/main/skills/security-testing"
    },
    {
      "name": "seo-testing",
      "description": "Use when auditing technical SEO and search visibility \u2014 crawlability, indexation, robots.txt, sitemaps, canonical/hreflang, meta and Open Graph tags, structured data (JSON-LD), Core Web Vitals, JS-rendering, redirects, and automating SEO regression checks in CI.",
      "category": "web",
      "version": "2.0",
      "tags": [
        "seo",
        "technical-seo",
        "structured-data",
        "sitemap",
        "robots",
        "canonical",
        "hreflang",
        "lighthouse",
        "indexing"
      ],
      "url": "https://mejbaurbahar.github.io/software-tester-skills/skills/seo-testing/",
      "source": "https://github.com/mejbaurbahar/software-tester-skills/tree/main/skills/seo-testing"
    },
    {
      "name": "serverless-testing",
      "description": "Use when testing serverless and cloud-function architectures \u2014 AWS Lambda, Azure Functions, Cloud Functions/Run, event sources, cold starts, timeouts and retries, IAM least privilege, idempotency, local emulation (SAM, LocalStack, Functions Core Tools), and testing in the cloud.",
      "category": "platform",
      "version": "2.0",
      "tags": [
        "serverless",
        "lambda",
        "azure-functions",
        "cloud-functions",
        "cold-start",
        "localstack",
        "sam",
        "idempotency",
        "event-sources",
        "iam"
      ],
      "url": "https://mejbaurbahar.github.io/software-tester-skills/skills/serverless-testing/",
      "source": "https://github.com/mejbaurbahar/software-tester-skills/tree/main/skills/serverless-testing"
    },
    {
      "name": "smoke-sanity-testing",
      "description": "Use when designing or executing smoke tests and sanity suites \u2014 Build Verification Testing (BVT), pre-flight deployment verification, critical-path health checks, and fast-fail gating.",
      "category": "functional",
      "version": "2.0",
      "tags": [
        "smoke",
        "sanity",
        "bvt",
        "health-check",
        "ci-gate"
      ],
      "url": "https://mejbaurbahar.github.io/software-tester-skills/skills/smoke-sanity-testing/",
      "source": "https://github.com/mejbaurbahar/software-tester-skills/tree/main/skills/smoke-sanity-testing"
    },
    {
      "name": "snapshot-golden-testing",
      "description": "Use when adding or reviewing snapshot, golden-file, approval, or characterization tests \u2014 Jest/Vitest snapshots, syrupy, ApprovalTests, insta, golden files for CLI/report/serializer output, and stopping snapshot rot and blind \"update all\" approvals.",
      "category": "code-level",
      "version": "2.0",
      "tags": [
        "snapshot",
        "golden-master",
        "approval-testing",
        "characterization",
        "jest",
        "syrupy",
        "insta"
      ],
      "url": "https://mejbaurbahar.github.io/software-tester-skills/skills/snapshot-golden-testing/",
      "source": "https://github.com/mejbaurbahar/software-tester-skills/tree/main/skills/snapshot-golden-testing"
    },
    {
      "name": "static-analysis-testing",
      "description": "Use when setting up or triaging static analysis as a quality gate \u2014 linters, type checkers, SAST (Semgrep, CodeQL, SonarQube, Bandit), complexity and duplication limits, dead-code detection, and configuring PR gates without drowning in false positives.",
      "category": "code-level",
      "version": "2.0",
      "tags": [
        "static-analysis",
        "sast",
        "semgrep",
        "codeql",
        "sonarqube",
        "eslint",
        "mypy",
        "linting",
        "quality-gate"
      ],
      "url": "https://mejbaurbahar.github.io/software-tester-skills/skills/static-analysis-testing/",
      "source": "https://github.com/mejbaurbahar/software-tester-skills/tree/main/skills/static-analysis-testing"
    },
    {
      "name": "supply-chain-dependency-testing",
      "description": "Use when testing software supply-chain and dependency risk \u2014 SCA/vulnerability scanning (Trivy, Grype, OSV, Dependabot, npm audit), SBOM (CycloneDX/SPDX), license compliance, lockfile integrity, reachability triage, secrets scanning, CI hardening, and SLSA provenance/signing.",
      "category": "security",
      "version": "2.0",
      "tags": [
        "sca",
        "sbom",
        "supply-chain",
        "dependencies",
        "cyclonedx",
        "spdx",
        "trivy",
        "grype",
        "osv",
        "licenses",
        "slsa",
        "sigstore",
        "secrets"
      ],
      "url": "https://mejbaurbahar.github.io/software-tester-skills/skills/supply-chain-dependency-testing/",
      "source": "https://github.com/mejbaurbahar/software-tester-skills/tree/main/skills/supply-chain-dependency-testing"
    },
    {
      "name": "system-testing",
      "description": "Use when verifying a fully integrated system against its specification \u2014 end-to-end functional and non-functional behavior in a production-like environment, system test planning, entry/exit criteria, and gap analysis between integration and acceptance testing.",
      "category": "functional",
      "version": "2.0",
      "tags": [
        "system-testing",
        "end-to-end",
        "black-box",
        "production-like",
        "nfr"
      ],
      "url": "https://mejbaurbahar.github.io/software-tester-skills/skills/system-testing/",
      "source": "https://github.com/mejbaurbahar/software-tester-skills/tree/main/skills/system-testing"
    },
    {
      "name": "tdd-workflow",
      "description": "Use when practicing or coaching test-driven development \u2014 red-green-refactor, outside-in vs inside-out (London vs Chicago), test lists, baby steps, TDD with AI coding agents, and legacy-code TDD (seams, characterization tests).",
      "category": "code-level",
      "version": "2.0",
      "tags": [
        "tdd",
        "red-green-refactor",
        "london-school",
        "chicago-school",
        "ai-pair",
        "refactoring"
      ],
      "url": "https://mejbaurbahar.github.io/software-tester-skills/skills/tdd-workflow/",
      "source": "https://github.com/mejbaurbahar/software-tester-skills/tree/main/skills/tdd-workflow"
    },
    {
      "name": "test-architect",
      "description": "Use when designing a test suite's architecture \u2014 test pyramid/trophy, test isolation, property-based testing, quality gates, and profiling slow or flaky suites.",
      "category": "strategy",
      "version": "2.0",
      "tags": [
        "test-pyramid",
        "isolation",
        "quality-gates",
        "test-suite-design"
      ],
      "url": "https://mejbaurbahar.github.io/software-tester-skills/skills/test-architect/",
      "source": "https://github.com/mejbaurbahar/software-tester-skills/tree/main/skills/test-architect"
    },
    {
      "name": "test-automation",
      "description": "Use when writing, structuring, or debugging automated tests \u2014 Playwright/Selenium E2E suites, pytest test design, page object models, CI test integration, and deciding what's worth automating.",
      "category": "automation",
      "version": "2.0",
      "tags": [
        "playwright",
        "selenium",
        "pytest",
        "page-object-model",
        "automation"
      ],
      "url": "https://mejbaurbahar.github.io/software-tester-skills/skills/test-automation/",
      "source": "https://github.com/mejbaurbahar/software-tester-skills/tree/main/skills/test-automation"
    },
    {
      "name": "test-data-engineering",
      "description": "Use when generating synthetic/realistic test data, seeding fixtures, masking PII for a test environment, or designing deterministic/reusable test datasets. Underpins reliable automation across all the other testing skills.",
      "category": "data",
      "version": "2.0",
      "tags": [
        "test-data",
        "fixtures",
        "data-masking",
        "seeding",
        "synthetic-data"
      ],
      "url": "https://mejbaurbahar.github.io/software-tester-skills/skills/test-data-engineering/",
      "source": "https://github.com/mejbaurbahar/software-tester-skills/tree/main/skills/test-data-engineering"
    },
    {
      "name": "test-design-techniques",
      "description": "Use when deriving test cases systematically \u2014 equivalence partitioning, boundary value analysis, decision tables, state transition testing, pairwise/combinatorial testing, use-case and classification-tree techniques, error guessing, and choosing which technique fits which requirement.",
      "category": "strategy",
      "version": "2.0",
      "tags": [
        "equivalence-partitioning",
        "boundary-value",
        "decision-table",
        "state-transition",
        "pairwise",
        "black-box-techniques"
      ],
      "url": "https://mejbaurbahar.github.io/software-tester-skills/skills/test-design-techniques/",
      "source": "https://github.com/mejbaurbahar/software-tester-skills/tree/main/skills/test-design-techniques"
    },
    {
      "name": "test-environment-management",
      "description": "Use when designing, stabilizing or scaling test environments \u2014 ephemeral preview environments, Docker Compose/Kubernetes/Testcontainers, environment parity, data seeding and reset, service virtualization, secrets, cost control and eliminating \"works on my machine\"/shared-staging contention.",
      "category": "automation",
      "version": "2.0",
      "tags": [
        "test-environments",
        "ephemeral",
        "testcontainers",
        "docker-compose",
        "kubernetes",
        "service-virtualization",
        "staging",
        "seeding",
        "parity"
      ],
      "url": "https://mejbaurbahar.github.io/software-tester-skills/skills/test-environment-management/",
      "source": "https://github.com/mejbaurbahar/software-tester-skills/tree/main/skills/test-environment-management"
    },
    {
      "name": "test-metrics-reporting",
      "description": "Use when measuring and communicating quality \u2014 test metrics and KPIs (defect escape rate, DDP, MTTR, flake rate, coverage, automation ROI), dashboards, Allure/ReportPortal reporting, trend analysis, quality gates, and executive-friendly QA status reports.",
      "category": "strategy",
      "version": "2.0",
      "tags": [
        "metrics",
        "kpi",
        "defect-density",
        "dora",
        "allure",
        "reportportal",
        "dashboard",
        "quality-gate",
        "automation-roi"
      ],
      "url": "https://mejbaurbahar.github.io/software-tester-skills/skills/test-metrics-reporting/",
      "source": "https://github.com/mejbaurbahar/software-tester-skills/tree/main/skills/test-metrics-reporting"
    },
    {
      "name": "test-planning-documentation",
      "description": "Use when producing test plans, test strategies, traceability matrices (RTM), entry/exit criteria, test summary reports, or IEEE 829/ISO 29119-style QA documentation \u2014 lightweight and agile-friendly formats included.",
      "category": "strategy",
      "version": "2.0",
      "tags": [
        "test-plan",
        "rtm",
        "traceability",
        "exit-criteria",
        "test-report",
        "iso-29119",
        "ieee-829"
      ],
      "url": "https://mejbaurbahar.github.io/software-tester-skills/skills/test-planning-documentation/",
      "source": "https://github.com/mejbaurbahar/software-tester-skills/tree/main/skills/test-planning-documentation"
    },
    {
      "name": "test-strategist",
      "description": "Use when deciding what to test and how \u2014 risk-based test planning, TDD vs test-after, the right level (unit/integration/E2E) for each behavior, and recognising when a test is not worth writing.",
      "category": "strategy",
      "version": "2.0",
      "tags": [
        "risk-based-testing",
        "test-strategy",
        "what-to-test",
        "automation-vs-manual"
      ],
      "url": "https://mejbaurbahar.github.io/software-tester-skills/skills/test-strategist/",
      "source": "https://github.com/mejbaurbahar/software-tester-skills/tree/main/skills/test-strategist"
    },
    {
      "name": "testing-strategies",
      "description": "Use when optimising a test suite for confidence and speed \u2014 the testing pyramid, mocking strategies, testing behavior instead of implementation, maintainable tests that survive refactoring, and modern tool choices (Jest, Vitest, Playwright, pytest).",
      "category": "strategy",
      "version": "2.0",
      "tags": [
        "testing-pyramid",
        "mocking",
        "maintainable-tests",
        "confidence"
      ],
      "url": "https://mejbaurbahar.github.io/software-tester-skills/skills/testing-strategies/",
      "source": "https://github.com/mejbaurbahar/software-tester-skills/tree/main/skills/testing-strategies"
    },
    {
      "name": "threat-modeling",
      "description": "Use when analyzing a design for security risks before or during build \u2014 STRIDE, data-flow diagrams, trust boundaries, LINDDUN privacy, abuse cases, risk ranking, mitigation mapping, and turning threats into security test cases.",
      "category": "security",
      "version": "2.0",
      "tags": [
        "threat-modeling",
        "stride",
        "dfd",
        "linddun",
        "abuse-cases",
        "security-design-review",
        "risk"
      ],
      "url": "https://mejbaurbahar.github.io/software-tester-skills/skills/threat-modeling/",
      "source": "https://github.com/mejbaurbahar/software-tester-skills/tree/main/skills/threat-modeling"
    },
    {
      "name": "unit-testing",
      "description": "Use when writing, refactoring, or auditing unit and component tests \u2014 isolated test doubles (mocks, stubs, spies), Arrange-Act-Assert (AAA) pattern, boundary value analysis, property-based testing, and code coverage.",
      "category": "code-level",
      "version": "2.0",
      "tags": [
        "unit-testing",
        "aaa",
        "mocks",
        "stubs",
        "boundary-value",
        "pytest",
        "jest"
      ],
      "url": "https://mejbaurbahar.github.io/software-tester-skills/skills/unit-testing/",
      "source": "https://github.com/mejbaurbahar/software-tester-skills/tree/main/skills/unit-testing"
    },
    {
      "name": "usability-testing",
      "description": "Use when evaluating usability, user friction, UI clarity, and workflow ergonomics \u2014 Nielsen Norman heuristics, form validation feedback, error recovery paths, cognitive load, and accessibility overlap.",
      "category": "web",
      "version": "2.0",
      "tags": [
        "usability",
        "nielsen-heuristics",
        "ux",
        "friction",
        "error-recovery"
      ],
      "url": "https://mejbaurbahar.github.io/software-tester-skills/skills/usability-testing/",
      "source": "https://github.com/mejbaurbahar/software-tester-skills/tree/main/skills/usability-testing"
    },
    {
      "name": "visual-testing",
      "description": "Use when checking visual/layout correctness \u2014 screenshot/visual regression testing, design-system and Figma-to-production validation, responsive layout, dark mode/theming, typography and spacing consistency. Distinct from functional correctness or accessibility (though related).",
      "category": "web",
      "version": "2.0",
      "tags": [
        "visual-regression",
        "screenshots",
        "responsive",
        "styling"
      ],
      "url": "https://mejbaurbahar.github.io/software-tester-skills/skills/visual-testing/",
      "source": "https://github.com/mejbaurbahar/software-tester-skills/tree/main/skills/visual-testing"
    },
    {
      "name": "web-performance-testing",
      "description": "Use when measuring or improving front-end and page-load performance \u2014 Core Web Vitals (LCP, INP, CLS), Lighthouse CI, WebPageTest, RUM vs lab data, performance budgets, bundle size, render-blocking resources, images/fonts, caching/CDN and third-party script impact.",
      "category": "non-functional",
      "version": "2.0",
      "tags": [
        "core-web-vitals",
        "lcp",
        "inp",
        "cls",
        "lighthouse",
        "webpagetest",
        "performance-budget",
        "rum",
        "bundle-size"
      ],
      "url": "https://mejbaurbahar.github.io/software-tester-skills/skills/web-performance-testing/",
      "source": "https://github.com/mejbaurbahar/software-tester-skills/tree/main/skills/web-performance-testing"
    },
    {
      "name": "webapp-testing",
      "description": "Use when testing local web applications with Python Playwright \u2014 verify frontend behavior, debug UI issues, capture screenshots and browser logs, and manage the app's server lifecycle with the bundled with_server.py helper.",
      "category": "automation",
      "version": "2.0",
      "tags": [
        "playwright",
        "python",
        "local-server",
        "screenshots",
        "browser-logs"
      ],
      "url": "https://mejbaurbahar.github.io/software-tester-skills/skills/webapp-testing/",
      "source": "https://github.com/mejbaurbahar/software-tester-skills/tree/main/skills/webapp-testing"
    },
    {
      "name": "websocket-realtime-testing",
      "description": "Use when testing WebSockets, Server-Sent Events, Socket.IO, WebRTC signaling, push/live-update features, chat, presence, and collaborative editing \u2014 connection lifecycle, reconnect, ordering, backpressure, auth, and scale.",
      "category": "api-backend",
      "version": "2.0",
      "tags": [
        "websocket",
        "sse",
        "socket.io",
        "realtime",
        "reconnect",
        "backpressure",
        "presence",
        "collaboration"
      ],
      "url": "https://mejbaurbahar.github.io/software-tester-skills/skills/websocket-realtime-testing/",
      "source": "https://github.com/mejbaurbahar/software-tester-skills/tree/main/skills/websocket-realtime-testing"
    }
  ],
  "commands": [
    {
      "name": "a11y-audit",
      "description": "Audit a page or component for WCAG 2.2 accessibility issues",
      "argument_hint": "[URL or component path]"
    },
    {
      "name": "api-tests",
      "description": "Build an API test suite from an endpoint, OpenAPI spec, or running service",
      "argument_hint": "[spec path, URL, or endpoint]"
    },
    {
      "name": "bug-report",
      "description": "Turn observations into a clear, reproducible bug report",
      "argument_hint": "[what went wrong]"
    },
    {
      "name": "coverage-gaps",
      "description": "Find meaningful test coverage gaps and write the missing tests",
      "argument_hint": "[path or module]"
    },
    {
      "name": "e2e-tests",
      "description": "Write resilient end-to-end browser tests for a user journey",
      "argument_hint": "[user journey or URL]"
    },
    {
      "name": "explore",
      "description": "Plan and run a time-boxed exploratory testing session",
      "argument_hint": "[area, feature, or URL]"
    },
    {
      "name": "flaky-triage",
      "description": "Investigate and fix intermittent (flaky) test failures",
      "argument_hint": "[test name or CI run]"
    },
    {
      "name": "perf-plan",
      "description": "Create a load/performance test plan and script with SLOs",
      "argument_hint": "[service, endpoint, or page]"
    },
    {
      "name": "qa-audit",
      "description": "Audit a repository's QA health and recommend which testing skills to apply",
      "argument_hint": "[repo path or blank for current]"
    },
    {
      "name": "qa-help",
      "description": "Find the right testing skill or command for your task",
      "argument_hint": "[what you want to test]"
    },
    {
      "name": "regression-scope",
      "description": "Pick the regression tests to run for a change, from the git diff",
      "argument_hint": "[branch, commit range, or PR]"
    },
    {
      "name": "release-check",
      "description": "Go/no-go release readiness assessment with evidence",
      "argument_hint": "[release, tag, or branch]"
    },
    {
      "name": "review-tests",
      "description": "Review test code for quality, brittleness, and false confidence",
      "argument_hint": "[test path or PR]"
    },
    {
      "name": "security-audit",
      "description": "Defensive security review of code or configuration (OWASP-focused)",
      "argument_hint": "[path, feature, or area]"
    },
    {
      "name": "smoke",
      "description": "Run a fast smoke check to see whether a build is testable",
      "argument_hint": "[URL or command]"
    },
    {
      "name": "tdd",
      "description": "Start a test-driven development session, one small cycle at a time",
      "argument_hint": "[behavior to build]"
    },
    {
      "name": "test-cases",
      "description": "Design test cases with formal techniques (EP, BVA, decision tables, state, pairwise)",
      "argument_hint": "[requirement, user story, or file]"
    },
    {
      "name": "test-plan",
      "description": "Create a risk-based test plan for a feature or release",
      "argument_hint": "[feature, ticket, or release]"
    },
    {
      "name": "test-strategy",
      "description": "Design an overall test strategy (levels, tools, automation, gates)",
      "argument_hint": "[product or repo]"
    },
    {
      "name": "threat-model",
      "description": "Build a STRIDE threat model and derive security test cases",
      "argument_hint": "[feature or system]"
    },
    {
      "name": "unit-tests",
      "description": "Generate high-quality unit tests for a file, function or module",
      "argument_hint": "[path or symbol]"
    }
  ]
}