@ngxtm/devkit 3.15.0 → 3.16.0

package/merged-commands/vercel-automation.md

@@ -0,0 +1,231 @@
+---
+name: vercel-automation
+description: "Automate Vercel tasks via Rube MCP (Composio): manage deployments, domains, DNS, env vars, projects, and teams. Always search tools first for current schemas."
+requires:
+  mcp: [rube]
+risk: unknown
+source: community
+---
+
+# Vercel Automation via Rube MCP
+
+Automate Vercel platform operations through Composio's Vercel toolkit via Rube MCP.
+
+## Prerequisites
+
+- Rube MCP must be connected (RUBE_SEARCH_TOOLS available)
+- Active Vercel connection via `RUBE_MANAGE_CONNECTIONS` with toolkit `vercel`
+- Always call `RUBE_SEARCH_TOOLS` first to get current tool schemas
+
+## Setup
+
+**Get Rube MCP**: Add `https://rube.app/mcp` as an MCP server in your client configuration. No API keys needed — just add the endpoint and it works.
+
+
+1. Verify Rube MCP is available by confirming `RUBE_SEARCH_TOOLS` responds
+2. Call `RUBE_MANAGE_CONNECTIONS` with toolkit `vercel`
+3. If connection is not ACTIVE, follow the returned auth link to complete Vercel OAuth
+4. Confirm connection status shows ACTIVE before running any workflows
+
+## Core Workflows
+
+### 1. Monitor and Inspect Deployments
+
+**When to use**: User wants to list, inspect, or debug deployments
+
+**Tool sequence**:
+1. `VERCEL_LIST_ALL_DEPLOYMENTS` or `VERCEL_GET_DEPLOYMENTS` - List deployments with filters [Required]
+2. `VERCEL_GET_DEPLOYMENT` or `VERCEL_GET_DEPLOYMENT_DETAILS` - Get specific deployment info [Optional]
+3. `VERCEL_GET_DEPLOYMENT_LOGS` or `VERCEL_GET_RUNTIME_LOGS` - View build/runtime logs [Optional]
+4. `VERCEL_GET_DEPLOYMENT_EVENTS` - Get deployment event timeline [Optional]
+5. `VERCEL_LIST_DEPLOYMENT_CHECKS` - View deployment check results [Optional]
+
+**Key parameters**:
+- `projectId`: Filter deployments by project
+- `state`: Filter by deployment state (e.g., 'READY', 'ERROR', 'BUILDING')
+- `limit`: Number of deployments to return
+- `target`: Filter by environment ('production', 'preview')
+- `deploymentId` or `idOrUrl`: Specific deployment identifier
+
+**Pitfalls**:
+- Deployment IDs and URLs are both accepted as identifiers in most endpoints
+- Build logs and runtime logs are separate; use the appropriate tool
+- `VERCEL_GET_DEPLOYMENT_LOGS` returns build logs; `VERCEL_GET_RUNTIME_LOGS` returns serverless function logs
+- Deployment events include status transitions and are useful for debugging timing issues
+
+### 2. Create and Manage Deployments
+
+**When to use**: User wants to trigger a new deployment
+
+**Tool sequence**:
+1. `VERCEL_LIST_PROJECTS` - Find the target project [Prerequisite]
+2. `VERCEL_CREATE_NEW_DEPLOYMENT` - Trigger a new deployment [Required]
+3. `VERCEL_GET_DEPLOYMENT` - Monitor deployment progress [Optional]
+
+**Key parameters**:
+- `name`: Project name for the deployment
+- `target`: Deployment target ('production' or 'preview')
+- `gitSource`: Git repository source with ref/branch info
+- `files`: Array of file objects for file-based deployments
+
+**Pitfalls**:
+- Either `gitSource` or `files` must be provided, not both
+- Git-based deployments require proper repository integration
+- Production deployments update the production domain alias automatically
+- Deployment creation is asynchronous; poll with GET_DEPLOYMENT for status
+
+### 3. Manage Environment Variables
+
+**When to use**: User wants to add, list, or remove environment variables for a project
+
+**Tool sequence**:
+1. `VERCEL_LIST_PROJECTS` - Find the project ID [Prerequisite]
+2. `VERCEL_LIST_ENV_VARIABLES` - List existing env vars [Required]
+3. `VERCEL_ADD_ENVIRONMENT_VARIABLE` - Add a new env var [Optional]
+4. `VERCEL_DELETE_ENVIRONMENT_VARIABLE` - Remove an env var [Optional]
+
+**Key parameters**:
+- `projectId`: Target project identifier
+- `key`: Environment variable name
+- `value`: Environment variable value
+- `target`: Array of environments ('production', 'preview', 'development')
+- `type`: Variable type ('plain', 'secret', 'encrypted', 'sensitive')
+
+**Pitfalls**:
+- Environment variable names must be unique per target environment
+- `type: 'secret'` variables cannot be read back after creation; only the ID is returned
+- Deleting an env var requires both `projectId` and the env var `id` (not the key name)
+- Changes require a new deployment to take effect
+
+### 4. Manage Domains and DNS
+
+**When to use**: User wants to configure custom domains or manage DNS records
+
+**Tool sequence**:
+1. `VERCEL_GET_DOMAIN` - Check domain status and configuration [Required]
+2. `VERCEL_GET_DOMAIN_CONFIG` - Get DNS/SSL configuration details [Optional]
+3. `VERCEL_LIST_PROJECT_DOMAINS` - List domains attached to a project [Optional]
+4. `VERCEL_GET_DNS_RECORDS` - List DNS records for a domain [Optional]
+5. `VERCEL_CREATE_DNS_RECORD` - Add a new DNS record [Optional]
+6. `VERCEL_UPDATE_DNS_RECORD` - Modify an existing DNS record [Optional]
+
+**Key parameters**:
+- `domain`: Domain name (e.g., 'example.com')
+- `name`: DNS record name/subdomain
+- `type`: DNS record type ('A', 'AAAA', 'CNAME', 'MX', 'TXT', 'SRV')
+- `value`: DNS record value
+- `ttl`: Time-to-live in seconds
+
+**Pitfalls**:
+- Domain must be added to the Vercel account before DNS management
+- SSL certificates are auto-provisioned but may take time for new domains
+- CNAME records at the apex domain are not supported; use A records instead
+- MX records require priority values
+
+### 5. Manage Projects
+
+**When to use**: User wants to list, inspect, or update project settings
+
+**Tool sequence**:
+1. `VERCEL_LIST_PROJECTS` - List all projects [Required]
+2. `VERCEL_GET_PROJECT` - Get detailed project information [Optional]
+3. `VERCEL_UPDATE_PROJECT` - Modify project settings [Optional]
+
+**Key parameters**:
+- `idOrName`: Project ID or name for lookup
+- `name`: Project name for updates
+- `framework`: Framework preset (e.g., 'nextjs', 'vite', 'remix')
+- `buildCommand`: Custom build command override
+- `rootDirectory`: Root directory if not repo root
+
+**Pitfalls**:
+- Project names are globally unique within a team/account
+- Changing framework settings affects subsequent deployments
+- `rootDirectory` is relative to the repository root
+
+### 6. Team Management
+
+**When to use**: User wants to view team info or list team members
+
+**Tool sequence**:
+1. `VERCEL_LIST_TEAMS` - List all teams the user belongs to [Required]
+2. `VERCEL_GET_TEAM` - Get detailed team information [Optional]
+3. `VERCEL_GET_TEAM_MEMBERS` - List members of a specific team [Optional]
+
+**Key parameters**:
+- `teamId`: Team identifier
+- `limit`: Number of results per page
+- `role`: Filter members by role
+
+**Pitfalls**:
+- Team operations require appropriate team-level permissions
+- Personal accounts have no teams; team endpoints return empty results
+- Member roles include 'OWNER', 'MEMBER', 'DEVELOPER', 'VIEWER'
+
+## Common Patterns
+
+### ID Resolution
+
+**Project name -> Project ID**:
+```
+1. Call VERCEL_LIST_PROJECTS
+2. Find project by name in response
+3. Extract id field for subsequent operations
+```
+
+**Domain -> DNS Records**:
+```
+1. Call VERCEL_GET_DNS_RECORDS with domain name
+2. Extract record IDs for update/delete operations
+```
+
+### Pagination
+
+- Use `limit` parameter to control page size
+- Check response for pagination tokens or `next` fields
+- Continue fetching until no more pages are indicated
+
+## Known Pitfalls
+
+**Deployment States**:
+- States include: INITIALIZING, ANALYZING, BUILDING, DEPLOYING, READY, ERROR, CANCELED, QUEUED
+- Only READY deployments are live and serving traffic
+- ERROR deployments should be inspected via logs for failure details
+
+**Environment Variables**:
+- Secret type vars are write-only; values cannot be retrieved after creation
+- Env vars are scoped to environments (production, preview, development)
+- A redeployment is needed for env var changes to take effect
+
+**Rate Limits**:
+- Vercel API has rate limits per endpoint
+- Implement backoff on 429 responses
+- Batch operations where possible to reduce API calls
+
+## Quick Reference
+
+| Task | Tool Slug | Key Params |
+|------|-----------|------------|
+| List projects | VERCEL_LIST_PROJECTS | limit |
+| Get project details | VERCEL_GET_PROJECT | idOrName |
+| Update project | VERCEL_UPDATE_PROJECT | idOrName, name, framework |
+| List deployments | VERCEL_LIST_ALL_DEPLOYMENTS | projectId, state, limit |
+| Get deployment | VERCEL_GET_DEPLOYMENT | idOrUrl |
+| Create deployment | VERCEL_CREATE_NEW_DEPLOYMENT | name, target, gitSource |
+| Deployment logs | VERCEL_GET_DEPLOYMENT_LOGS | deploymentId |
+| Runtime logs | VERCEL_GET_RUNTIME_LOGS | deploymentId |
+| List env vars | VERCEL_LIST_ENV_VARIABLES | projectId |
+| Add env var | VERCEL_ADD_ENVIRONMENT_VARIABLE | projectId, key, value, target |
+| Delete env var | VERCEL_DELETE_ENVIRONMENT_VARIABLE | projectId, id |
+| Get domain | VERCEL_GET_DOMAIN | domain |
+| Get domain config | VERCEL_GET_DOMAIN_CONFIG | domain |
+| List DNS records | VERCEL_GET_DNS_RECORDS | domain |
+| Create DNS record | VERCEL_CREATE_DNS_RECORD | domain, name, type, value |
+| Update DNS record | VERCEL_UPDATE_DNS_RECORD | domain, recordId |
+| List project domains | VERCEL_LIST_PROJECT_DOMAINS | projectId |
+| List teams | VERCEL_LIST_TEAMS | (none) |
+| Get team | VERCEL_GET_TEAM | teamId |
+| Get team members | VERCEL_GET_TEAM_MEMBERS | teamId, limit |
+
+## When to Use
+This skill is applicable to execute the workflow or actions described in the overview.

package/merged-commands/vercel-deploy-claimable.md

@@ -1,6 +1,6 @@
 ---
 name: vercel-deploy-claimable
-description: Deploy applications and websites to Vercel. Use when user requests deployment actions such as Deploy my app, Deploy this to production, Create a preview deployment. No authentication required - returns preview URL and claimable deployment link.
+description: "Deploy applications and websites to Vercel. Use this skill when the user requests deployment actions such as 'Deploy my app', 'Deploy this to production', 'Create a preview deployment', 'Deploy and..."
 source: "https://github.com/vercel-labs/agent-skills/tree/main/skills/claude.ai/vercel-deploy-claimable"
 risk: safe
 ---
@@ -12,6 +12,7 @@ Deploy any project to Vercel instantly. No authentication required.
 ## When to Use This Skill
 
 Use this skill when:
+
 - User requests deployment actions like "Deploy my app"
 - Deploying to production
 - Creating preview deployments
@@ -32,6 +33,7 @@ bash /mnt/skills/user/vercel-deploy/scripts/deploy.sh [path]
 ```
 
 **Arguments:**
+
 - `path` - Directory to deploy, or a `.tgz` file (defaults to current directory)
 
 **Examples:**
@@ -88,6 +90,7 @@ For static HTML projects (no `package.json`), framework is set to `null`.
 ## Static HTML Projects
 
 For projects without a `package.json`:
+
 - If there's a single `.html` file not named `index.html`, it gets renamed automatically
 - This ensures the page is served at the root URL (`/`)
 

package/merged-commands/verification-before-completion.md

@@ -1,6 +1,8 @@
 ---
 name: verification-before-completion
-description: Use when about to claim work is complete, fixed, or passing, before committing or creating PRs - requires running verification commands and confirming output before making any success claims; evidence before assertions always
+description: "Use when about to claim work is complete, fixed, or passing, before committing or creating PRs - requires running verification commands and confirming output before making any success claims; evide..."
+risk: unknown
+source: community
 ---
 
 # Verification Before Completion
@@ -137,3 +139,6 @@ From 24 failure memories:
 Run the command. Read the output. THEN claim the result.
 
 This is non-negotiable.
+
+## When to Use
+This skill is applicable to execute the workflow or actions described in the overview.

package/merged-commands/viral-generator-builder.md

@@ -1,7 +1,8 @@
 ---
 name: viral-generator-builder
-description: "Expert in building shareable generator tools that go viral - name generators, quiz makers, avatar creators, personality tests, and calculator tools. Covers the psychology of sharing, viral mechanics, and building tools people can't resist sharing with friends. Use when: generator tool, quiz maker, name generator, avatar creator, viral tool."
+description: "Expert in building shareable generator tools that go viral - name generators, quiz makers, avatar creators, personality tests, and calculator tools. Covers the psychology of sharing, viral mechanic..."
 source: vibeship-spawner-skills (Apache 2.0)
+risk: unknown
 ---
 
 # Viral Generator Builder
@@ -197,3 +198,6 @@ Your branding subtle but present.
 ## Related Skills
 
 Works well with: `viral-hooks`, `landing-page-design`, `seo`, `frontend`
+
+## When to Use
+This skill is applicable to execute the workflow or actions described in the overview.

package/merged-commands/voice-agents.md

@@ -1,7 +1,8 @@
 ---
 name: voice-agents
-description: "Voice agents represent the frontier of AI interaction - humans speaking naturally with AI systems. The challenge isn't just speech recognition and synthesis, it's achieving natural conversation flow with sub-800ms latency while handling interruptions, background noise, and emotional nuance.  This skill covers two architectures: speech-to-speech (OpenAI Realtime API, lowest latency, most natural) and pipeline (STT→LLM→TTS, more control, easier to debug). Key insight: latency is the constraint. Hu"
+description: "Voice agents represent the frontier of AI interaction - humans speaking naturally with AI systems. The challenge isn't just speech recognition and synthesis, it's achieving natural conversation flo..."
 source: vibeship-spawner-skills (Apache 2.0)
+risk: unknown
 ---
 
 # Voice Agents
@@ -66,3 +67,6 @@ Detect when user starts/stops speaking
 ## Related Skills
 
 Works well with: `agent-tool-builder`, `multi-agent-orchestration`, `llm-architect`, `backend`
+
+## When to Use
+This skill is applicable to execute the workflow or actions described in the overview.

package/merged-commands/voice-ai-development.md

@@ -1,7 +1,8 @@
 ---
 name: voice-ai-development
-description: "Expert in building voice AI applications - from real-time voice agents to voice-enabled apps. Covers OpenAI Realtime API, Vapi for voice agents, Deepgram for transcription, ElevenLabs for synthesis, LiveKit for real-time infrastructure, and WebRTC fundamentals. Knows how to build low-latency, production-ready voice experiences. Use when: voice ai, voice agent, speech to text, text to speech, realtime voice."
+description: "Expert in building voice AI applications - from real-time voice agents to voice-enabled apps. Covers OpenAI Realtime API, Vapi for voice agents, Deepgram for transcription, ElevenLabs for synthesis..."
 source: vibeship-spawner-skills (Apache 2.0)
+risk: unknown
 ---
 
 # Voice AI Development
@@ -300,3 +301,6 @@ Harder to optimize.
 ## Related Skills
 
 Works well with: `langgraph`, `structured-output`, `langfuse`
+
+## When to Use
+This skill is applicable to execute the workflow or actions described in the overview.

package/merged-commands/voice-ai-engine-development.md

@@ -1,6 +1,8 @@
 ---
 name: voice-ai-engine-development
 description: "Build real-time conversational AI voice engines using async worker pipelines, streaming transcription, LLM agents, and TTS synthesis with interrupt handling and multi-provider support"
+risk: unknown
+source: community
 ---
 
 # Voice AI Engine Development

package/merged-commands/vulnerability-scanner.md

@@ -14,7 +14,7 @@ allowed-tools: Read, Glob, Grep, Bash
 
 | Script | Purpose | Usage |
 |--------|---------|-------|
-| `scripts/security_scan.py` | Validate security principles applied | `python scripts/security_scan.py <project_path>` |
+| `scripts/security_scan.py` | Validate security principles applied | `python3 ~/.{TOOL}/skills/vulnerability-scanner/scripts/security_scan.py <project_path>` |
 
 ## 📋 Reference Files
 

package/merged-commands/wcag-audit-patterns.md

@@ -1,6 +1,8 @@
 ---
 name: wcag-audit-patterns
-description: Conduct WCAG 2.2 accessibility audits with automated testing, manual verification, and remediation guidance. Use when auditing websites for accessibility, fixing WCAG violations, or implementing accessible design patterns.
+description: "Conduct WCAG 2.2 accessibility audits with automated testing, manual verification, and remediation guidance. Use when auditing websites for accessibility, fixing WCAG violations, or implementing ac..."
+risk: unknown
+source: community
 ---
 
 # WCAG Audit Patterns

package/merged-commands/web-artifacts-builder.md

@@ -1,7 +1,9 @@
 ---
 name: web-artifacts-builder
-description: Suite of tools for creating elaborate, multi-component claude.ai HTML artifacts using modern frontend web technologies (React, Tailwind CSS, shadcn/ui). Use for complex artifacts requiring state management, routing, or shadcn/ui components - not for simple single-file HTML/JSX artifacts.
+description: "Suite of tools for creating elaborate, multi-component claude.ai HTML artifacts using modern frontend web technologies (React, Tailwind CSS, shadcn/ui). Use for complex artifacts requiring state ma..."
 license: Complete terms in LICENSE.txt
+risk: unknown
+source: community
 ---
 
 # Web Artifacts Builder
@@ -71,4 +73,7 @@ To test/visualize the artifact, use available tools (including other Skills or b
 
 ## Reference
 
-- **shadcn/ui components**: https://ui.shadcn.com/docs/components
+- **shadcn/ui components**: https://ui.shadcn.com/docs/components
+
+## When to Use
+This skill is applicable to execute the workflow or actions described in the overview.

package/merged-commands/web-design-guidelines.md

@@ -1,7 +1,10 @@
 ---
 name: web-design-guidelines
 description: Review UI code for Web Interface Guidelines compliance. Use when asked to "review my UI", "check accessibility", "audit design", "review UX", or "check my site against best practices".
-argument-hint: <file-or-pattern>
+metadata:
+  author: vercel
+  version: "1.0.0"
+  argument-hint: <file-or-pattern>
 ---
 
 # Web Interface Guidelines

package/merged-commands/web-performance-optimization.md

@@ -1,6 +1,8 @@
 ---
 name: web-performance-optimization
 description: "Optimize website and web application performance including loading speed, Core Web Vitals, bundle size, caching strategies, and runtime performance"
+risk: unknown
+source: community
 ---
 
 # Web Performance Optimization

package/merged-commands/web-security-testing.md

@@ -0,0 +1,184 @@
+---
+name: web-security-testing
+description: "Web application security testing workflow for OWASP Top 10 vulnerabilities including injection, XSS, authentication flaws, and access control issues."
+source: personal
+risk: safe
+domain: security
+category: granular-workflow-bundle
+version: 1.0.0
+---
+
+# Web Security Testing Workflow
+
+## Overview
+
+Specialized workflow for testing web applications against OWASP Top 10 vulnerabilities including injection attacks, XSS, broken authentication, and access control issues.
+
+## When to Use This Workflow
+
+Use this workflow when:
+- Testing web application security
+- Performing OWASP Top 10 assessment
+- Conducting penetration tests
+- Validating security controls
+- Bug bounty hunting
+
+## Workflow Phases
+
+### Phase 1: Reconnaissance
+
+#### Skills to Invoke
+- `scanning-tools` - Security scanning
+- `top-web-vulnerabilities` - OWASP knowledge
+
+#### Actions
+1. Map application surface
+2. Identify technologies
+3. Discover endpoints
+4. Find subdomains
+5. Document findings
+
+#### Copy-Paste Prompts
+```
+Use @scanning-tools to perform web application reconnaissance
+```
+
+### Phase 2: Injection Testing
+
+#### Skills to Invoke
+- `sql-injection-testing` - SQL injection
+- `sqlmap-database-pentesting` - SQLMap
+
+#### Actions
+1. Test SQL injection
+2. Test NoSQL injection
+3. Test command injection
+4. Test LDAP injection
+5. Document vulnerabilities
+
+#### Copy-Paste Prompts
+```
+Use @sql-injection-testing to test for SQL injection
+```
+
+```
+Use @sqlmap-database-pentesting to automate SQL injection testing
+```
+
+### Phase 3: XSS Testing
+
+#### Skills to Invoke
+- `xss-html-injection` - XSS testing
+- `html-injection-testing` - HTML injection
+
+#### Actions
+1. Test reflected XSS
+2. Test stored XSS
+3. Test DOM-based XSS
+4. Test XSS filters
+5. Document findings
+
+#### Copy-Paste Prompts
+```
+Use @xss-html-injection to test for cross-site scripting
+```
+
+### Phase 4: Authentication Testing
+
+#### Skills to Invoke
+- `broken-authentication` - Authentication testing
+
+#### Actions
+1. Test credential stuffing
+2. Test brute force protection
+3. Test session management
+4. Test password policies
+5. Test MFA implementation
+
+#### Copy-Paste Prompts
+```
+Use @broken-authentication to test authentication security
+```
+
+### Phase 5: Access Control Testing
+
+#### Skills to Invoke
+- `idor-testing` - IDOR testing
+- `file-path-traversal` - Path traversal
+
+#### Actions
+1. Test vertical privilege escalation
+2. Test horizontal privilege escalation
+3. Test IDOR vulnerabilities
+4. Test directory traversal
+5. Test unauthorized access
+
+#### Copy-Paste Prompts
+```
+Use @idor-testing to test for insecure direct object references
+```
+
+```
+Use @file-path-traversal to test for path traversal
+```
+
+### Phase 6: Security Headers
+
+#### Skills to Invoke
+- `api-security-best-practices` - Security headers
+
+#### Actions
+1. Check CSP implementation
+2. Verify HSTS configuration
+3. Test X-Frame-Options
+4. Check X-Content-Type-Options
+5. Verify referrer policy
+
+#### Copy-Paste Prompts
+```
+Use @api-security-best-practices to audit security headers
+```
+
+### Phase 7: Reporting
+
+#### Skills to Invoke
+- `reporting-standards` - Security reporting
+
+#### Actions
+1. Document vulnerabilities
+2. Assess risk levels
+3. Provide remediation
+4. Create proof of concept
+5. Generate report
+
+#### Copy-Paste Prompts
+```
+Use @reporting-standards to create security report
+```
+
+## OWASP Top 10 Checklist
+
+- [ ] A01: Broken Access Control
+- [ ] A02: Cryptographic Failures
+- [ ] A03: Injection
+- [ ] A04: Insecure Design
+- [ ] A05: Security Misconfiguration
+- [ ] A06: Vulnerable Components
+- [ ] A07: Authentication Failures
+- [ ] A08: Software/Data Integrity
+- [ ] A09: Logging/Monitoring
+- [ ] A10: SSRF
+
+## Quality Gates
+
+- [ ] All OWASP Top 10 tested
+- [ ] Vulnerabilities documented
+- [ ] Proof of concepts captured
+- [ ] Remediation provided
+- [ ] Report generated
+
+## Related Workflow Bundles
+
+- `security-audit` - Security auditing
+- `api-security-testing` - API security
+- `wordpress-security` - WordPress security

package/merged-commands/web3-testing.md

@@ -1,6 +1,8 @@
 ---
 name: web3-testing
-description: Test smart contracts comprehensively using Hardhat and Foundry with unit tests, integration tests, and mainnet forking. Use when testing Solidity contracts, setting up blockchain test suites, or validating DeFi protocols.
+description: "Test smart contracts comprehensively using Hardhat and Foundry with unit tests, integration tests, and mainnet forking. Use when testing Solidity contracts, setting up blockchain test suites, or va..."
+risk: unknown
+source: community
 ---
 
 # Web3 Smart Contract Testing

package/merged-commands/webapp-testing.md

@@ -1,7 +1,9 @@
 ---
 name: webapp-testing
-description: Toolkit for interacting with and testing local web applications using Playwright. Supports verifying frontend functionality, debugging UI behavior, capturing browser screenshots, and viewing browser logs.
+description: "Toolkit for interacting with and testing local web applications using Playwright. Supports verifying frontend functionality, debugging UI behavior, capturing browser screenshots, and viewing browse..."
 license: Complete terms in LICENSE.txt
+risk: unknown
+source: community
 ---
 
 # Web Application Testing
@@ -93,4 +95,7 @@ with sync_playwright() as p:
 - **examples/** - Examples showing common patterns:
   - `element_discovery.py` - Discovering buttons, links, and inputs on a page
   - `static_html_automation.py` - Using file:// URLs for local HTML
-  - `console_logging.py` - Capturing console logs during automation
+  - `console_logging.py` - Capturing console logs during automation
+
+## When to Use
+This skill is applicable to execute the workflow or actions described in the overview.