Menu
Manages allocation of browser instances to agents for concurrent operations. Read this skill when spawning multiple agents that need independent browser sessions.
Installer avec Codex ou Claude Copiez ce prompt, collez-le dans Codex, Claude ou un autre assistant, puis laissez-le vérifier la page du skill et l'installer pour vous.
Basé sur la classification professionnelle SOC
| name | browser |
| description | Manages allocation of browser instances to agents for concurrent operations. Read this skill when spawning multiple agents that need independent browser sessions. |
This plugin provides 6 independent browser instances for concurrent operations. Each browser has its own profile directory.
| Browser | MCP Server | Tool Prefix |
|---|---|---|
| 1 | browser-1 | mcp__browser-1__browser_* |
| 2 | browser-2 | mcp__browser-2__browser_* |
| 3 | browser-3 | mcp__browser-3__browser_* |
| 4 | browser-4 | mcp__browser-4__browser_* |
| 5 | browser-5 | mcp__browser-5__browser_* |
| 6 | browser-6 | mcp__browser-6__browser_* |
Each browser has its own profile (.glide/browser-profile-1 through -6) to prevent conflicts.
Run /login once to:
browser-profile-1 to browser-profile-2 through browser-profile-6After login, all browsers share the same authenticated session (via copied profiles).
Re-sync profiles by running /login again if:
When spawning agents for parallel work, assign each a browser number:
"Build the Tasks screen using browser 1"
"Build the Projects screen using browser 2"
"Review the Employees screen design using browser 3"
Agents must use ONLY their assigned browser's tools:
mcp__browser-1__browser_navigate, mcp__browser-1__browser_snapshot, etc.mcp__browser-2__browser_navigate, mcp__browser-2__browser_snapshot, etc.If no browser is assigned, default to browser-1.
Parallel Screen Building
Build + Review
Build + Data Editing
Browsers are managed by Playwright MCP. They launch on first use and close when the Claude session ends. No manual cleanup needed.
.glide/browser-profile-1 - Primary profile (used for login).glide/browser-profile-2 through .glide/browser-profile-6 - Copies of primaryAudit Glide apps for performance issues and optimization opportunities. Use when analyzing app performance, identifying bottlenecks in data structure or layout, or providing recommendations for improving app speed and user experience. Automatically triggered when user provides a Glide app URL for audit, including read-only support-mode URLs of the form https://go.glideapps.com/support/{uuid}. Can also produce an optional plain-language, customer-facing version of the report on request, for sharing directly with the customer who reported the issue.
Get detailed explanations of Glide features - computed columns, workflows, components, data modeling, AI features, and more
Use the Glide API for programmatic data operations - REST API v2 and @glideapps/tables npm package. Use when importing data, bulk operations, automating data sync, or building integrations with Glide tables.
Create computed columns in Glide - Math, If-Then-Else, Relations, Rollups, Lookups, Templates. Use when adding calculations, formulas, lookups, or linking tables with relations.
Design Glide data models - tables, columns, column types, and calculation architecture. Use when creating tables, designing data structures, choosing column types, or planning relationships.
**The primary skill for building Glide apps.** Covers the full workflow, agent coordination, and browser automation. Use when building, creating, or modifying any Glide app. Read this first for any Glide project.