All directories
SkillEngineeringOperations

Chrome Relay

Drives your already-open Chrome session (cookies, SSO, extensions, localhost) via a local CLI bridge—real Chrome counterpart to Playwright fixtures.

Open sourceBrowse more skills
01

Overview

Chrome Relay is a Claude skill added to LimeDock Directories from recent community and vendor roundups. Drives your already-open Chrome session (cookies, SSO, extensions, localhost) via a local CLI bridge—real Chrome counterpart to Playwright fixtures. This page covers install, how to invoke it, example prompts, prerequisites, and concrete use cases.

SaaSOther

Work with LimeDock

Using this skill? LimeDock can wire it into a durable automation you own.

Skills show what's possible. LimeDock builds and runs the owned marketing, sales, and ops automations around them.

We sell owned automations for SaaS teams — live workflows that plug into Slack, CRM, and your internal platform — not just a skill list.

Book a workflow call
02

Link

https://chrome-relay.kushalsm.com/
03

Installation guide

npx skills add chrome-relay

Plus the Chrome Web Store extension (Chrome Relay).

04

How to use it

Use when you need the agent to operate in your authenticated browser—not a clean Playwright profile.

05

Example prompts

  • “Use the Chrome Relay skill for: Automate tasks in logged-in SaaS admin”
  • “Walk me through Chrome Relay step by step, then execute on my project.”
  • “Review my current approach and improve it using Chrome Relay.”
  • “Produce a reusable checklist for running Chrome Relay on similar work.”
06

Use cases and examples

  • Automate tasks in logged-in SaaS admin
  • Localhost app control with real session
  • SSO-protected workflows
  • Avoid re-auth in headless browsers
  • Team playbook trial of Chrome Relay on a real workflow
07

Prerequisites

  • Claude Code, Claude.ai (Skills enabled), or an Agent Skills–compatible host
  • Permission to install third-party skills — audit SKILL.md and scripts first
  • Project context (CLAUDE.md / product notes) for better outputs
08

Tips

  • Keep triggers specific so Chrome Relay only fires when relevant.
  • Audit SKILL.md and any bundled scripts before production use.
  • Pair with verification (tests, review, screenshots) before shipping.
  • Re-audit installed skills monthly to avoid context tax from unused packs.
09

Sources