Browse reusable Agent Skills, each with a clear purpose and practical guidance.
Stand up a local SQL Server 2022 backend, apply SQL fixtures, and run airbyte-ops protocol commands (spec / check / discover / read) against airbyte/source-mssql:<tag> for ad-hoc end-to-end testing. Use when you need a deterministic, throwaway local environment for any source-mssql test or repro that is not CDC-specific.
Validate branch readiness before push or PR using base-diff and local-change checks.
Work with CodeQL in Kibana — write, test, and debug custom queries locally, fetch scan results from GitHub, and validate inline suppression comments. Use when writing or debugging CodeQL queries, running CodeQL unit tests, analyzing SARIF results, fetching scan results, or checking codeql suppression justifications.
Migrate Kibana Cypress E2E tests (.cy.ts) to Scout (Playwright). Applies to any Kibana plugin or solution. Includes triage gates (duplicate detection, layer analysis, value assessment), Cypress-to-Scout pattern mapping, data cleanup audit, and PR workflow. Use when: (1) migrating a Cypress test to Scout, (2) converting .cy.ts to .spec.ts, (3) planning a Cypress-to-Scout migration batch, (4) rewriting Cypress screens/tasks as Scout page objects, (5) asked "how do I move this Cypress test to Scout/Playwright", (6) asked about differences between Cypress and Scout.
Use when debugging OpenAPI (OAS) issues for a specific API area in Kibana by scoping validation output with one or more --path filters, then separating structural invalid-OAS failures from quality or documentation gaps such as missing descriptions.
Migrate Enzyme tests to React Testing Library (RTL). Use when converting shallow/mount enzyme tests to RTL render, replacing enzyme selectors with RTL queries, updating snapshot tests, or when the user mentions enzyme migration, RTL migration, or react-testing-library.
Security Solution specific. Analyzes flaky, failing, or skipped Security Solution Cypress tests to determine root cause and recommend fixes. Use when: (1) a user shares a flaky or skipped Cypress test, (2) asked to fix a test that intermittently fails, (3) asked to unskip a test, (4) triaging a test stability GitHub issue, (5) asked "why is this test flaky/failing", (6) asked to analyze test failures in ESS/Serverless/MKI environments, (7) asked whether to fix, delete, or migrate a broken Cypress test.
Security Solution specific extensions for Cypress-to-Scout migration. Adds Security Solution conventions, paths, packages, roles, and API services on top of the general cypress-to-scout-migration skill. Use when: (1) migrating a Security Solution Cypress test (.cy.ts) to Scout, (2) working in x-pack/solutions/security/ and asked about Cypress-to-Scout migration, (3) need Security-specific Scout tags, roles, or API services for a migration, (4) asked about MKI pipelines for Security Solution.