conducting-browser-compatibility-tests
tessl i github:jeremylongshore/claude-code-plugins-plus-skills --skill conducting-browser-compatibility-testsThis skill enables cross-browser compatibility testing for web applications using BrowserStack, Selenium Grid, or Playwright. It tests across Chrome, Firefox, Safari, and Edge, identifying browser-specific bugs and ensuring consistent functionality. It is used when a user requests to "test browser compatibility", "run cross-browser tests", or uses the `/browser-test` or `/bt` command to assess web application behavior across different browsers and devices. The skill generates a report detailing compatibility issues and screenshots for visual verification.
Validation
75%| Criteria | Description | Result |
|---|---|---|
description_trigger_hint | Description may be missing an explicit 'when to use' trigger hint (e.g., 'Use when...') | Warning |
metadata_version | 'metadata' field is not a dictionary | Warning |
license_field | 'license' field is missing | Warning |
body_output_format | No obvious output/return/format terms detected; consider specifying expected outputs | Warning |
Total | 12 / 16 Passed | |
Implementation
20%This skill content reads like marketing copy rather than actionable technical guidance. It describes what cross-browser testing does conceptually but provides zero executable code, configuration examples, or concrete commands. Claude would not be able to actually perform cross-browser testing based on this content alone.
Suggestions
Add executable code examples showing actual Playwright/Selenium test setup and browser matrix configuration (e.g., playwright.config.ts or BrowserStack capabilities JSON)
Include concrete CLI commands for running tests (e.g., 'npx playwright test --project=chromium firefox webkit')
Provide a sample browser matrix configuration file that can be copy-pasted and modified
Add validation steps: how to verify BrowserStack credentials are configured, how to check test results, what to do when specific browsers fail
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The content is verbose and explains concepts Claude already knows (what cross-browser testing is, what browsers exist). It describes rather than instructs, with padding like 'ensuring that web applications function correctly' that adds no value. | 1 / 3 |
Actionability | No concrete code, commands, or executable guidance provided. The skill describes what it will do abstractly ('Configure the browser matrix', 'Execute tests') but never shows how - no actual Playwright/Selenium code, no configuration examples, no CLI commands. | 1 / 3 |
Workflow Clarity | Steps are listed in sequence (configure, generate, execute, report) but lack any validation checkpoints, error handling, or feedback loops. No guidance on what to do if tests fail or how to verify the setup is correct before running. | 2 / 3 |
Progressive Disclosure | Content is organized into sections but everything is inline with no references to detailed configuration files, example test files, or separate documentation. The 'Integration' section mentions other tools vaguely without pointing to actual resources. | 2 / 3 |
Total | 6 / 12 Passed |
Activation
100%This is a well-crafted skill description that excels across all dimensions. It provides specific capabilities (testing across named browsers, generating reports with screenshots), includes natural trigger terms users would actually say, explicitly states when to use it with command shortcuts, and occupies a distinct niche that won't conflict with other skills.
| Dimension | Reasoning | Score |
|---|---|---|
Specificity | Lists multiple specific concrete actions: 'cross-browser compatibility testing', 'tests across Chrome, Firefox, Safari, and Edge', 'identifying browser-specific bugs', 'generates a report detailing compatibility issues and screenshots for visual verification'. | 3 / 3 |
Completeness | Clearly answers both what (cross-browser testing, identifying bugs, generating reports with screenshots) AND when ('used when a user requests to "test browser compatibility", "run cross-browser tests", or uses the `/browser-test` or `/bt` command'). | 3 / 3 |
Trigger Term Quality | Includes natural keywords users would say: 'test browser compatibility', 'run cross-browser tests', '/browser-test', '/bt', plus specific browser names (Chrome, Firefox, Safari, Edge) and tool names (BrowserStack, Selenium Grid, Playwright). | 3 / 3 |
Distinctiveness Conflict Risk | Clear niche focused specifically on cross-browser compatibility testing with distinct triggers like '/browser-test', '/bt', and specific tool/browser mentions that are unlikely to conflict with general testing or web development skills. | 3 / 3 |
Total | 12 / 12 Passed |
Reviewed
Table of Contents
Is this your skill?
If you maintain this skill, you can claim it as your own. Once claimed, you can manage eval scenarios, bundle related skills, attach documentation or rules, and ensure cross-agent compatibility.