Trellis Session Insight
mindfold-ai/Trellis
Reach into past AI conversation history through the trellis mem CLI.
One-time setup for a persistent debug browser on 127.0.0.1:9222 for dev-browser --connect.
Install Browser Debug Setup
$ npx skills add udecode/plate-playground-template --skill browser-debug-setup -a claude-codeProject install by default; add -g for ~/.claude/skills/.
$ gh skill install udecode/plate-playground-template browser-debug-setup --agent claude-codeProject scope by default; add --scope user for a personal install. Needs GitHub CLI 2.90.0 or later (public preview).
$ git clone --depth 1 https://github.com/udecode/plate-playground-template.git skills-src && mkdir -p .claude/skills && cp -r skills-src/.agents/skills/browser-debug-setup .claude/skills/browser-debug-setup && rm -rf skills-srcUse ~/.claude/skills/ instead of .claude/skills for a personal install. The folder must contain SKILL.md.
Claude Code skills documentation · loads skills from .claude/skills/
Install the "browser-debug-setup" agent skill from https://github.com/udecode/plate-playground-template/tree/main/.agents/skills/browser-debug-setup into .claude/skills/browser-debug-setup/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "browser-debug-setup", then confirm the skill loads.Claude Code copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$skill-installer install https://github.com/udecode/plate-playground-template/tree/main/.agents/skills/browser-debug-setupType this inside Codex. $skill-installer <name> installs a curated skill from openai/skills. The installer writes to $CODEX_HOME/skills (default ~/.codex/skills). Restart Codex if the skill does not show up.
$ npx skills add udecode/plate-playground-template --skill browser-debug-setup -a codexProject install goes to .agents/skills/; add -g for ~/.codex/skills/.
$ gh skill install udecode/plate-playground-template browser-debug-setup --agent codexProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/udecode/plate-playground-template.git skills-src && mkdir -p .agents/skills && cp -r skills-src/.agents/skills/browser-debug-setup .agents/skills/browser-debug-setup && rm -rf skills-srcUse ~/.agents/skills/ instead of .agents/skills for a personal install.
Codex skills documentation · loads skills from .agents/skills/
Install the "browser-debug-setup" agent skill from https://github.com/udecode/plate-playground-template/tree/main/.agents/skills/browser-debug-setup into .agents/skills/browser-debug-setup/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "browser-debug-setup", then confirm the skill loads.Codex copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ npx skills add udecode/plate-playground-template --skill browser-debug-setup -a cursorProject install goes to .agents/skills/; add -g for ~/.cursor/skills/.
$ gh skill install udecode/plate-playground-template browser-debug-setup --agent cursorProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/udecode/plate-playground-template.git skills-src && mkdir -p .cursor/skills && cp -r skills-src/.agents/skills/browser-debug-setup .cursor/skills/browser-debug-setup && rm -rf skills-srcUse ~/.cursor/skills/ instead of .cursor/skills for a personal install.
Cursor skills documentation · loads skills from .cursor/skills/, .agents/skills/, .claude/skills/, .codex/skills/
Install the "browser-debug-setup" agent skill from https://github.com/udecode/plate-playground-template/tree/main/.agents/skills/browser-debug-setup into .cursor/skills/browser-debug-setup/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "browser-debug-setup", then confirm the skill loads.Cursor copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ gemini skills install https://github.com/udecode/plate-playground-template.git --path .agents/skills/browser-debug-setup--scope user (default) or --scope workspace; --path is the subfolder of the repo that holds the skill; --consent skips the security confirmation prompt.
$ npx skills add udecode/plate-playground-template --skill browser-debug-setup -a gemini-cliProject install goes to .agents/skills/; add -g for ~/.gemini/skills/.
$ gh skill install udecode/plate-playground-template browser-debug-setup --agent gemini-cliProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/udecode/plate-playground-template.git skills-src && mkdir -p .gemini/skills && cp -r skills-src/.agents/skills/browser-debug-setup .gemini/skills/browser-debug-setup && rm -rf skills-srcUse ~/.gemini/skills/ instead of .gemini/skills for a personal install, then run /skills reload.
Gemini CLI skills documentation · loads skills from .gemini/skills/, .agents/skills/
Install the "browser-debug-setup" agent skill from https://github.com/udecode/plate-playground-template/tree/main/.agents/skills/browser-debug-setup into .gemini/skills/browser-debug-setup/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "browser-debug-setup", then confirm the skill loads.Gemini CLI copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ gh skill install udecode/plate-playground-template browser-debug-setupInstalls for Copilot at project scope by default; add --scope user for a personal install. Preview a skill first with gh skill preview. Needs GitHub CLI 2.90.0 or later (public preview).
$ npx skills add udecode/plate-playground-template --skill browser-debug-setup -a github-copilotProject install goes to .agents/skills/; add -g for ~/.copilot/skills/.
$ git clone --depth 1 https://github.com/udecode/plate-playground-template.git skills-src && mkdir -p .github/skills && cp -r skills-src/.agents/skills/browser-debug-setup .github/skills/browser-debug-setup && rm -rf skills-srcUse ~/.copilot/skills/ instead of .github/skills for a personal install. Commit .github/skills so cloud agent and code review can use it.
GitHub Copilot skills documentation · loads skills from .github/skills/, .claude/skills/, .agents/skills/
Install the "browser-debug-setup" agent skill from https://github.com/udecode/plate-playground-template/tree/main/.agents/skills/browser-debug-setup into .github/skills/browser-debug-setup/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "browser-debug-setup", then confirm the skill loads.GitHub Copilot copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ npx skills add udecode/plate-playground-template --skill browser-debug-setup -a opencodeOpenCode documents no install command of its own. Project install goes to .agents/skills/; add -g for ~/.config/opencode/skills/.
$ gh skill install udecode/plate-playground-template browser-debug-setup --agent opencodeProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/udecode/plate-playground-template.git skills-src && mkdir -p .opencode/skills && cp -r skills-src/.agents/skills/browser-debug-setup .opencode/skills/browser-debug-setup && rm -rf skills-srcUse ~/.config/opencode/skills/ instead of .opencode/skills for a personal install.
OpenCode skills documentation · loads skills from .opencode/skills/, .claude/skills/, .agents/skills/
Install the "browser-debug-setup" agent skill from https://github.com/udecode/plate-playground-template/tree/main/.agents/skills/browser-debug-setup into .opencode/skills/browser-debug-setup/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "browser-debug-setup", then confirm the skill loads.OpenCode copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
Facts
- Skill name
browser-debug-setup- GitHub stars
- 240
- Token cost
- ~1.1k tokens
- SKILL.md length
- 395 words
- Files
- 1
- Skills in repo
- 4
- Repo updated
- First seen
- Licence
- MIT
At a glance
One-time setup for a persistent debug browser on 127.0.0.1:9222 for dev-browser --connect.
- Works in 5 steps: Pick a separate signed-in Chrome profile… → Map that human-facing Chrome profile… → Clone that profile into the dedicated… → …
- Browser work is needed but no reusable debug browser is running yet
- SKILL.md covers Goal, Rules, Preferred Shape and Google Chrome Path, plus 1 more section
- Calls curl, jq and python3
What it does
Browser Debug Setup is an agent skill from udecode/plate-playground-template. One-time setup for a persistent debug browser on 127.0.0.1:9222 for dev-browser --connect. Use when browser work is needed but no reusable debug browser is running yet.
Its SKILL.md is about 1.1k tokens, which your agent loads only when the skill is triggered. It is a single SKILL.md file with no bundled scripts.
It sits in Development, covering Debugging. The repository describes itself as: Plate AI template with React 19, Next 16, Tailwind 4, MCP. The licence is MIT.
When your agent uses it
- Browser work is needed but no reusable debug browser is running yet
- Tasks that involve Debugging
Example prompts
- “/browser-debug-setup”
Requirements
- Python 3
Workflow steps
5 steps, taken from the first numbered list in SKILL.md.
- Pick a separate signed-in Chrome profile for agent work, like dev, not
- Map that human-facing Chrome profile name to the real folder in Local State.
- Clone that profile into the dedicated debug dir.
- Launch a separate Chrome instance on 9222.
- Leave that debug window open and reuse it.
What it can do on your machine
Read from SKILL.md and the folder at commit 324070e. It shows what the files ask for, not the result of running them.
Tool permissions
Pre-approves nothing: there is no allowed-tools line, so your agent's usual permission prompts apply.
From allowed-tools in the SKILL.md frontmatter.
Runs code
Shell commands in SKILL.md call:
curljqpython3rsync
From the folder's file list and the shell code blocks in SKILL.md.
Network
No URLs in SKILL.md. Its commands use curl and rsync, which can reach the network depending on how they are called.
From URLs in SKILL.md, links to its own repository left out.
Credentials
Names no API keys, tokens, secrets or passwords.
From names ending in _API_KEY, _TOKEN, _SECRET, _KEY or _PASSWORD in SKILL.md.
Context cost
Browser Debug Setup loads about 1.1k tokens when it runs. Until then it costs about 48 tokens; SKILL.md has 395 words of instructions outside code blocks.
Estimates: characters ÷ 4, the usual rule of thumb; real counts depend on the model's tokenizer. Scripts and assets cost tokens only if the agent reads them.
Safety
Auto-check passed
The automated check found no risky patterns in SKILL.md.
Automated static check — not a guarantee. Review scripts before installing. It scans the text of SKILL.md for risky patterns (piping downloads into a shell, reading credential files, hidden Unicode, destructive commands); files beside SKILL.md are not scanned.
SKILL.md
The full file from udecode/plate-playground-template at commit 324070e, republished under its MIT licence (© udecode). 395 words, ~1,138 tokens.
Download SKILL.mdSave it as
.claude/skills/browser-debug-setup/SKILL.md (or your agent's skills folder).- name
- browser-debug-setup
- description
- One-time setup for a persistent debug browser on `127.0.0.1:9222` for `dev-browser --connect`. Use when browser work is needed but no reusable debug browser is running yet.
Browser Debug Setup
Use this skill when dev-browser --connect http://127.0.0.1:9222 fails because
no persistent debug browser is running yet.
Goal
Get the user onto one persistent browser/profile that both the human and the
agent reuse. Minimize the Allow remote debugging? popup by keeping one
dedicated debug browser/profile alive.
Rules
- Prefer one permanent debug browser/profile over disposable automation browsers.
- Treat a custom
--user-data-diras mandatory, not optional. Chrome 136+ basically wants remote debugging to happen from a dedicated profile. - Keep auth in that profile. Do not fall back to cookie dumps or state files unless the user asks.
- Use a separate signed-in Chrome profile for browser work, like
dev. Do not use the user's normal dailyDefaultprofile as the source profile. - Clone that separate signed-in Chrome profile into the dedicated debug
--user-data-dir; do not point9222straight at the user's daily Chrome data dir. - On macOS, use
open -na "Google Chrome" --args ...for the debug browser. That starts a separate Chrome instance with the dedicated debug profile without touching the user's normal Chrome window.
Preferred Shape
Use a dedicated browser/profile with:
--remote-debugging-address=127.0.0.1--remote-debugging-port=9222- a persistent
--user-data-dir=<debug-profile-dir>
Sign in once in that dedicated browser and keep reusing it for agent work.
Quick sanity check:
curl -sS http://127.0.0.1:9222/json/versionHealthy output includes a JSON object with webSocketDebuggerUrl. Empty output
or 404 means the wrong process owns 9222.
Then verify dev-browser:
dev-browser --connect http://127.0.0.1:9222 <<'EOF'
const page = await browser.getPage("persistent-main");
console.log(await page.title());
EOFIf dev-browser --connect http://127.0.0.1:9222 still cannot resolve CDP even
though /json/version is healthy, connect with the exact websocket URL:
WS=$(curl -sS http://127.0.0.1:9222/json/version | jq -r '.webSocketDebuggerUrl')
dev-browser --connect "$WS" <<'EOF'
const page = await browser.getPage("persistent-main");
console.log(await page.title());
EOFShow full SKILL.md (152 more words)Show less
Google Chrome Path
Default setup on macOS:
- Pick a separate signed-in Chrome profile for agent work, like
dev, not the dailyDefaultprofile. - Map that human-facing Chrome profile name to the real folder in
Local State. - Clone that profile into the dedicated debug dir.
- Launch a separate Chrome instance on
9222. - Leave that debug window open and reuse it.
python3 - <<'PY'
import json, pathlib
p = pathlib.Path('~/Library/Application Support/Google/Chrome/Local State').expanduser()
obj = json.loads(p.read_text())
for key, val in obj.get('profile', {}).get('info_cache', {}).items():
print(f"{key}\tname={val.get('name')}\tgaia_name={val.get('gaia_name')}")
PY
# Example: if `dev` maps to `Profile 1`, clone `Profile 1`.
mkdir -p "$HOME/.config/google-chrome-debug-profile/Default"
rsync -a --delete \
--exclude='Singleton*' \
--exclude='DevToolsActivePort' \
--exclude='lockfile' \
"$HOME/Library/Application Support/Google/Chrome/Profile 1/" \
"$HOME/.config/google-chrome-debug-profile/Default/"
cp "$HOME/Library/Application Support/Google/Chrome/Local State" \
"$HOME/.config/google-chrome-debug-profile/Local State"
open -na "Google Chrome" --args \
--user-data-dir="$HOME/.config/google-chrome-debug-profile" \
--profile-directory="Default" \
--remote-debugging-address=127.0.0.1 \
--remote-debugging-port=9222That keeps the signed-in identity while still satisfying Chrome's dedicated
--user-data-dir requirement.
Then keep reusing that exact debug browser. Do not point 9222 at your normal
daily Default Chrome profile.
After Setup
- Use
dev-browser --connect http://127.0.0.1:9222for browser work. - Reuse named pages like
persistent-main. - Do not stop the user's debug browser unless they ask.
- If the wrong Chrome steals
9222, identify it withlsof -nP -iTCP:9222 -sTCP:LISTEN, kill that listener, and relaunch the dedicated debug browser. Do not keep debugging against a stale404or empty/json/versionowner.
© udecode, MIT. Rendered from Markdown: HTML in the file is shown as text, images as links, and headings moved down two levels. Raw file
Files
Just SKILL.md in .agents/skills/browser-debug-setup of udecode/plate-playground-template.
Open the folder on GitHubat commit 324070e
Compare with similar skills
Browser Debug Setup next to the 5 skills that share the most tags, products or categories with it. Stars are the repository's; “used in” counts other GitHub owners with a copy.
| Skill | Stars | Used in | Tokens | Auto-check | Licence | Repo updated |
|---|---|---|---|---|---|---|
| Browser Debug Setup this skilludecode/plate-playground-template | 240 | — | ~1.1k | Automated safety check: Pass | MIT | |
| Trellis Session Insightmindfold-ai/Trellis | 15k | 4 repos | ~1.7k | Automated safety check: Pass | AGPL-3.0 | |
| Native Data FetchingCherryHQ/cherry-studio-app | 4k | 6 repos | ~2.9k | Automated safety check: Notes | MIT | |
| Debugging Executionsn8n-io/n8n | 207k | — | ~2.6k | Automated safety check: Pass | Custom licence | |
| Aoti Debugpytorch/pytorch | 104k | 1 repos | ~1.7k | Automated safety check: Pass | Custom licence | |
| Herdr Throwaway Reproductionherdrdev/herdr | 43k | — | ~2.4k | Automated safety check: Pass | Apache-2.0 |
Similar skills
Native Data Fetching
CherryHQ/cherry-studio-app
A skill your agent uses when implementing or debugging ANY network request, API call, or data fetching.
- Official
Debugging Executions
n8n-io/n8n
Debug failed or wrong-output workflow executions using executions tools.
Aoti Debug
pytorch/pytorch
Debug AOTInductor (AOTI) errors and crashes. An agent skill from pytorch/pytorch.
Herdr Throwaway Reproduction
herdrdev/herdr
Runs a disposable, uniquely named Herdr session inside an existing one so runtime, pane, terminal or API bugs can be reproduced without touching the main session.
Systematic Debugging
ultralisp/ultralisp
A skill your agent uses when encountering any bug, test failure, or unexpected behavior, before proposing fixes
More from udecode/plate-playground-template
Autoreview
udecode/plate-playground-template
Structured code review when explicitly requested, preferring OpenAI/Codex before Claude.
Video Transcripts
udecode/plate-playground-template
Transcribe a supplied local or linked video with Gemini Files API when its contents are needed as evidence.
Testing
udecode/plate-playground-template
Skill: testing
Related
Categories
Questions about Browser Debug Setup
What does Browser Debug Setup do?
One-time setup for a persistent debug browser on 127.0.0.1:9222 for dev-browser --connect. Browser Debug Setup is an agent skill from udecode/plate-playground-template.1:9222 for dev-browser --connect.
When should I use Browser Debug Setup?
Browser Debug Setup fits situations like: browser work is needed but no reusable debug browser is running yet; tasks that involve Debugging.
How do I install Browser Debug Setup in Claude Code?
Run `npx skills add udecode/plate-playground-template --skill browser-debug-setup -a claude-code`. Or copy the skill folder (.agents/skills/browser-debug-setup in udecode/plate-playground-template) into .claude/skills/browser-debug-setup in your project. Claude Code loads it when a task matches its description.
How do I install Browser Debug Setup in Codex?
Run `npx skills add udecode/plate-playground-template --skill browser-debug-setup -a codex`. Or copy the skill folder (.agents/skills/browser-debug-setup in udecode/plate-playground-template) into .agents/skills/browser-debug-setup in your project. Codex loads it when a task matches its description.
Can I use Browser Debug Setup in Cursor, Gemini CLI or GitHub Copilot?
Cursor, Gemini CLI, GitHub Copilot and OpenCode also load SKILL.md folders. With the skills CLI, run `npx skills add udecode/plate-playground-template --skill browser-debug-setup -a cursor` (or -a gemini-cli, github-copilot or opencode for the others). To copy it by hand, put the folder in .cursor/skills/browser-debug-setup, .gemini/skills/browser-debug-setup, .github/skills/browser-debug-setup and .opencode/skills/browser-debug-setup in your project.
What does Browser Debug Setup need to run?
Going by SKILL.md and its folder, Browser Debug Setup needs the command-line tools its instructions call (curl, jq, python3 and rsync). Our summary lists: Python 3.
Does Browser Debug Setup access the network?
SKILL.md contains no URLs. Its commands use curl, which can reach the network depending on how they are called. This is read from the text; nothing was executed.
Is Browser Debug Setup safe to install?
Our automated static check of SKILL.md found no risky patterns, such as piping downloads into a shell, reading credential files or hidden Unicode. It is not a guarantee. Review the folder before installing.
What licence does Browser Debug Setup use?
Browser Debug Setup is published under the MIT licence (the repository's licence). It allows redistribution, so the full SKILL.md is shown on this page.
How many tokens does Browser Debug Setup use?
About 1.1k tokens (SKILL.md is roughly 4.6k characters). Agents keep only the skill's name and description in context until a task matches; then they load SKILL.md in full.
What are the alternatives to Browser Debug Setup?
Skills that share tags, products or a category with Browser Debug Setup: Trellis Session Insight (mindfold-ai/Trellis, 15k stars), Native Data Fetching (CherryHQ/cherry-studio-app, 4k stars), Debugging Executions (n8n-io/n8n, 207k stars) and Aoti Debug (pytorch/pytorch, 104k stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.
Who maintains Browser Debug Setup?
udecode (a GitHub organization) maintains it in udecode/plate-playground-template, which has 240 GitHub stars. The repository holds 4 skills in this directory. The repository was last updated on October 7, 2026.
Source: udecode/plate-playground-template on GitHub. Facts on this page come from the repository at the commit we read; the author's words are quoted as theirs.