VividKit Crystal clear AI coding
VI
Choose Your Setup Get Started with AgentKit Continue with ClaudeKit Migrate from ClaudeKit to AgentKit Clean cutover from ClaudeKit What Is AgentKit? How AgentKit Works AgentKit Kits, Skills, Agents & Hooks AgentKit Runtime Support AgentKit Desktop App AgentKit Configuration AgentKit CLI Quick Reference AgentKit Skills Cheatsheet AgentKit Workflows AgentKit Statusline Update AgentKit CLI & Kits AgentKit Helper Clean reinstall of AgentKit AgentKit Troubleshooting What is ClaudeKit? ClaudeKit CLI Guide Command Finder Commands Cheat Sheet Workflow Recipes CLI Quick Reference Claude Mechanics Permission Modes ClaudeKit Hooks Coexistence ClaudeKit x Codex CK → Other coding tools How ClaudeKit Works Inside ClaudeKit Finding Your Unknowns Session Recovery Fix from Logs UI/UX Guide Accounts Switcher IDE Config Remote Control Codex App System Diagramming UI Review Gate Promotions Support VividKit

Quick Ref / Command

Engineer Kit

/ak:chrome-profile

Profile-aware Chrome automation

Profile-aware browser automation for real Chrome state: the right Google account, cookies, workspace, tenant, or deterministic profile target.

01

Decide need

02

Check mapping

03

Probe bridge

04

Guide setup

Rule 01

Real profile state is exceptional, not the default browser-testing path.

Rule 02

Static doctor output is not enough; live MCP reachability is the final check.

Rule 03

Bind by the returned cdp-open token, not by guessing the newest matching tab.

Rule 04

Protect account/profile metadata as local private information.

Execution Map

Core lanes from input to output, aligned with the command's real execution path.

01

Start

Input, scope, route

  1. 1 Decide need Use this skill only when real Chrome identity matters; otherwise use agent-browser, web-testing, Playwright, or ordinary DevTools navigation.
  2. 2 Check mapping Run profile discovery so the requested key resolves by account email or display-name substring, not by brittle Profile directories.
02

Work

Agent / skill execution

  1. 3 Probe bridge Use doctor as a heuristic, then make a live Chrome DevTools MCP page-list or snapshot probe before declaring the browser unreadable.
  2. 4 Guide setup If mapping or bridge is missing, explain the failing layer and give the next concrete setup command or browser action.
03

Verify

Gate, review, validation

  1. 5 Open exact tab Materialize the URL with chrome-profile open --json <key> <url> so the output includes an exact cdp-open binding marker.
  2. 6 Bind by token List pages, select the one containing the returned cdp-open token, and sanity-check the cdp-profile marker.
04

Close

Report, handoff, artifact

  1. 7 Operate safely Continue with snapshot, click, evaluate, screenshot, or extraction through the bound page; never navigate an arbitrary bridge tab for profile-scoped work.
  2. 8 Handle limits If SPAs strip hash markers, capture the page ID immediately and keep using that ID; if the bridge fails, follow the documented setup path.

Syntax, arguments, subcommands

How to invoke the skill: syntax, positional arguments, shared options, then each subcommand with its own syntax and outcome.

Syntax

/ak:chrome-profile "<profile-scoped browser task>"

Arguments

<profile-scoped browser task> Required

Browser task

Natural-language request that names the approved profile key, target URL, intended actions, forbidden changes, and required evidence.

/ak:chrome-profile "Use profile work to open https://github.com/example/repo/pulls, bind the exact opened tab, summarize failing checks, and do not comment, approve, merge, or change account settings"

Sample Prompt

Concrete invocations for each flag, subcommand, mode, or route available in the live workflow.

Open work profile Recommended 
/ak:chrome-profile "Use profile work to open https://github.com/org/repo/pulls, bind the exact opened tab, summarize failing checks, and do not comment, approve, merge, or change account settings"
Use when:
A task must use the user's signed-in work Chrome account.
Expected:
Checks profile mapping and live bridge reachability, opens with JSON binding data, selects the exact cdp-open tab, then performs only the requested browser work.
Setup help 
/ak:chrome-profile help me configure the profile bridge for my personal account
Use when:
The profile key or readable DevTools bridge is missing.
Expected:
Runs the documented checks, separates profile-mapping failures from browser-bridge failures, and gives the next concrete setup command or Chrome action.
Background open on macOS 
/ak:chrome-profile "Use profile work to open https://linear.app/acme/team/ENG without stealing focus if macOS supports it, bind the exact tab, and summarize open bugs"
Use when:
Real profile state is required but the user wants the current app focus preserved.
Expected:
Uses the documented background-open option where supported, still opens through chrome-profile open --json, captures the binding marker, and reports evidence without exposing profile metadata.
Handle conservative doctor 
/ak:chrome-profile "Doctor says the bridge is unavailable, but Chrome DevTools MCP tools are exposed; probe live pages first, then open https://example.com with profile work only if binding can be proven"
Use when:
Static doctor output disagrees with an apparently available Chrome DevTools MCP bridge.
Expected:
Treats doctor as a heuristic, performs the live page-list or read probe, uses --force only for the documented proven-bridge exception, and stops for setup if binding cannot be verified.

Handled Scope

  • Chrome profile mapping
  • DevTools MCP bridge probing
  • Exact URL-anchor tab binding
  • Real-account automation safety

Next