Compétences playwright-skill
🎭

playwright-skill

Risque faible ⚙️ Commandes externes🌐 Accès réseau📁 Accès au système de fichiers🔑 Variables d’environnement⚡ Contient des scripts

Automate browser tasks with Playwright

Également disponible depuis: lackeyjb

This skill enables Claude Code to automate browser interactions using Playwright, handling dev server detection, test script execution, and comprehensive web testing capabilities.

Prend en charge: Claude Codex Code(CC)
📊 71 Adéquat
1

Télécharger le ZIP du skill

2

Importer dans Claude

Allez dans Paramètres → Capacités → Skills → Importer un skill

3

Activez et commencez à utiliser

Tester

Utilisation de "playwright-skill". Test my local app at localhost:3000

Résultat attendu:

Auto-detected dev server on port 3000. Launching browser to test...

Page title: My Web App
Viewport: 1280x720
✓ Page loaded successfully
✓ No console errors detected
✓ Screenshot saved to /tmp/screenshot-2024-01-15.png

Utilisation de "playwright-skill". Check responsive design

Résultat attendu:

Testing across viewports:
- Mobile (375x667): ✓ No layout issues
- Tablet (768x1024): ✓ No layout issues
- Desktop (1280x720): ✓ No layout issues

All viewport tests passed. Screenshots saved to /tmp/

Audit de sécurité

Risque faible
v1 • 2/24/2026

This is a legitimate browser automation skill using the Playwright library. The static analyzer flagged many patterns but most are false positives: shell commands in documentation are usage examples, not dangerous execution; network access is required for browser automation; filesystem access is for writing test scripts to /tmp; environment variables are for configuration. No malicious intent detected.

5
Fichiers analysés
1,811
Lignes analysées
8
résultats
1
Total des audits
Problèmes à risque moyen (1)
SKILL.md:9-500API_REFERENCE.md:34-632
Shell Command Execution in Documentation
Documentation files contain shell command examples using backticks. These are usage examples for users, not dangerous code execution within the skill itself.
Problèmes à risque faible (2)
lib/helpers.js:15-46
Environment Variable Configuration
Skill reads configuration from environment variables (PW_HEADER_NAME, HEADLESS, etc.). This is legitimate configuration, not credential access.
run.js:209
Dynamic Script Loading
Skill uses require() to load Playwright and user test scripts. This is the expected mechanism for a scripting skill.

Facteurs de risque

⚙️ Commandes externes (1)
run.js:38-39
🌐 Accès réseau (1)
lib/helpers.js:391
📁 Accès au système de fichiers (1)
run.js:205
🔑 Variables d’environnement (1)
lib/helpers.js:15-16
⚡ Contient des scripts (1)
lib/helpers.js:174
Audité par: claude

Score de qualité

38
Architecture
100
Maintenabilité
87
Contenu
50
Communauté
81
Sécurité
91
Conformité aux spécifications

Ce que vous pouvez construire

Web Developer Testing

Test web applications locally by auto-detecting dev servers and running automated browser tests across multiple viewport sizes.

QA Automation

Create end-to-end tests for web applications, validate login flows, and check responsive design across different devices.

Web Scraping

Extract content from websites that require JavaScript rendering, including screenshots and structured data extraction.

Essayez ces prompts

Test Local Web App 
Test my local web application. First detect any running dev servers, then verify the main page loads correctly and check for console errors.
Responsive Design Check 
Check if my web application looks good on mobile, tablet, and desktop viewports. Take screenshots at each size and report any layout issues.
Login Flow Test 
Test the login flow on [URL]. Fill in the credentials, click login, and verify successful authentication by checking for dashboard or user menu.
Form Submission Test 
Fill out and submit the contact form on [URL] with test data. Verify the form submits successfully and check for any validation errors.

Bonnes pratiques

  • Always use parameterized URLs via constants or environment variables for maintainability
  • Write test scripts to /tmp to keep project directories clean
  • Use visible browser mode (headless: false) for debugging, switch to headless for CI
  • Handle async operations properly with waitForSelector and waitForNavigation

Éviter

  • Do not hardcode credentials in test scripts - use environment variables instead
  • Avoid testing against production websites without authorization
  • Do not rely solely on sleep/timers - use proper wait conditions for reliable tests
  • Avoid writing test files to the skill directory - always use /tmp

Foire aux questions

How do I set up Playwright?
Run 'npm run setup' in the skill directory, or the skill will prompt you to install on first use.
Can I test external websites?
Yes, but some sites may block automated browsers. Always respect robots.txt and website terms of service.
How do I pass custom headers?
Set PW_HEADER_NAME and PW_HEADER_VALUE environment variables, or PW_EXTRA_HEADERS for multiple headers in JSON format.
Can I run in headless mode?
Set HEADLESS=false environment variable for visible browser mode. Default is headless for CI environments.
Where do test scripts get saved?
Test scripts are written to /tmp/playwright-test-*.js to avoid cluttering your project directory.
Does this work with Firefox and WebKit?
Yes, the skill supports chromium, firefox, and webkit browsers. Install additional browsers with 'npx playwright install firefox'.

Détails du développeur

Auteur

sickn33

Licence

MIT

Dépôt

https://github.com/sickn33/antigravity-awesome-skills/tree/main/skills/playwright-skill

Réf

main

Structure de fichiers

📁 lib/

📄 helpers.js

📄 API_REFERENCE.md

📄 package.json

📄 run.js

📄 SKILL.md