Agent skill / claude
Sync cookies from local Chrome to a Browserbase persistent context for authenticated browsing.
Core file
AI-first code editor with Composer
Before installing skills in Cursor, ensure your development environment meets these requirements:
node --versioncookie-syncExecute the skills CLI command in your project's root directory to begin installation:
Package manager
npx skills add https://github.com/browserbase/skills --skill cookie-syncFetches cookie-sync from claude/cookie-sync and configures it for Cursor.
The CLI shows a list of agents. Use arrow keys and space to select Cursor:
Confirm successful installation by checking the skill directory location:
Restart Cursor to activate cookie-sync. Access via /cookie-syncin your agent's command palette.
We perform automated surface-level scans (Gen AI Scanner, Socket, Snyk) during installation. These checks detect common vulnerabilities but do not guarantee complete security. Always review skill source code and verify the publisher's reputation before production use.
Skills execute code in your environment. Always review source, verify the publisher, and test in isolation before production.
Submit your Claude Code skill and start earning
Create detailed user stories, acceptance criteria, and feature specs
Example
Generate user stories for 'password reset feature' with acceptance criteria, edge cases, and test scenarios
Reduce spec writing time by 50%, ensure comprehensive coverage
Research competitors, compare features, identify gaps
Example
Analyze 5 competitor products, create feature comparison matrix, suggest differentiation opportunities
Complete competitive research in 2 hours instead of 2 days
Evaluate features using frameworks (RICE, ICE, Kano) and create prioritized backlogs
Example
Score 20 feature ideas using RICE framework, generate prioritized roadmap with rationale
Copy the command for your terminal
Package manager
npx skills add https://github.com/browserbase/skills --skill cookie-syncWorks with
| name | cookie-sync |
| description | Sync cookies from local Chrome to a Browserbase persistent context so the browse CLI can access authenticated sites. Use when the user wants to browse as themselves, sync cookies, or log into sites via Browserbase. |
Exports cookies from your local Chrome and saves them into a Browserbase persistent context. After syncing, use the browse CLI to open authenticated sessions with that context.
Supports domain filtering (only sync cookies you need) and context reuse (refresh cookies without creating a new context).
chrome://flags/#allow-remote-debugging, enable it and restart the browser--remote-debugging-port=9222 --user-data-dir=/tmp/chrome-debug and set CDP_URL=ws://127.0.0.1:9222BROWSERBASE_API_KEYInstall dependencies before first use:
cd .claude/skills/cookie-sync && npm install
node .claude/skills/cookie-sync/scripts/cookie-sync.mjs
Creates a persistent context with all your Chrome cookies. Outputs a context ID.
node .claude/skills/cookie-sync/scripts/cookie-sync.mjs --domains google.com,github.com
Matches the domain and all subdomains (e.g. google.com matches accounts.google.com, mail.google.com, etc.)
node .claude/skills/cookie-sync/scripts/cookie-sync.mjs --context ctx_abc123
Re-injects fresh cookies into a previously created context. Use this when cookies have expired.
node .claude/skills/cookie-sync/scripts/cookie-sync.mjs --stealth
Enables Browserbase's advanced stealth mode to reduce bot detection. Recommended for sites like Google that fingerprint browsers.
node .claude/skills/cookie-sync/scripts/cookie-sync.mjs --proxy "San Francisco,CA,US"
Routes through a residential proxy in the specified location. Format: "City,ST,Country" (state is 2-letter code). Helps match your local IP's geolocation so auth cookies aren't rejected.
node .claude/skills/cookie-sync/scripts/cookie-sync.mjs --domains github.com,google.com --stealth --proxy "San Francisco,CA,US"
After syncing, use the browse CLI with the context ID:
browse open https://mail.google.com --context-id <ctx-id> --persist
The --persist flag saves any new cookies or state changes back to the context, keeping the session fresh for next time.
Full workflow example:
# Step 1: Sync cookies for Twitter
node .claude/skills/cookie-sync/scripts/cookie-sync.mjs --domains x.com,twitter.com
# Output: Context ID: ctx_abc123
# Step 2: Browse authenticated Twitter
browse open https://x.com/messages --context-id ctx_abc123 --persist
browse snapshot
browse screenshot
browse stop
Contexts persist across sessions, making them ideal for scheduled/recurring tasks:
browse open <url> --context-id <ctx-id> --persist — no local Chrome needed--context <ctx-id> to refreshchrome://flags/#allow-remote-debugging if your browser build exposes it, or launch with --remote-debugging-port=9222 and set CDP_URL=ws://127.0.0.1:9222--context <id> to refresh--stealth and/or --proxy with a location near youMake data-driven prioritization decisions faster
Draft PRDs, status updates, and stakeholder presentations
Example
Create executive summary of Q3 roadmap, monthly progress report, feature launch announcement
Save 3-5 hours/week on communication overhead
Prerequisites
Time Estimate
30-60 minutes to see productivity improvements
Steps
Common Pitfalls
✓ Do
✗ Don't
💡 Pro Tips
✓ Use when
Use for user story writing, competitive research, roadmap prioritization, stakeholder communication, and PRD drafting. Best for reducing repetitive documentation and research work.
✗ Avoid when
Avoid for strategic product vision (requires deep customer empathy), pricing decisions (needs market and financial expertise), or when face-to-face customer discovery is more valuable than speed.
browserbasehq/browser-trace
joeseesun/qiaomu-anything-to-notebooklm
browserbasehq/cli
manaflow-ai/cmux
aj-geddes/useful-ai-prompts
mindrally/skills
Solid pick for teams standardizing on skills: cookie-sync is focused, and the summary matches what you get after install.
Keeps context tight: cookie-sync is the kind of skill you can hand to a new teammate without a long onboarding doc.
cookie-sync reduced setup friction for our internal harness; good balance of opinion and flexibility.
We added cookie-sync from the explainx registry; install was straightforward and the SKILL.md answered most questions upfront.
cookie-sync has been reliable in day-to-day use. Documentation quality is above average for community skills.
cookie-sync reduced setup friction for our internal harness; good balance of opinion and flexibility.
Registry listing for cookie-sync matched our evaluation — installs cleanly and behaves as described in the markdown.
cookie-sync is among the better-maintained entries we tried; worth keeping pinned for repeat workflows.
We added cookie-sync from the explainx registry; install was straightforward and the SKILL.md answered most questions upfront.
cookie-sync fits our agent workflows well — practical, well scoped, and easy to wire into existing repos.
showing 1-10 of 71