원클릭으로 Manus에서 모든 스킬 실행

browser-mate

스타308

포크46

업데이트2026년 6월 3일 10:11

Use when automating a real, logged-in Chrome WITHOUT disturbing the user's open tabs — e.g. authenticated sessions like ChatGPT, LinkedIn, or any site needing a persistent login. Launches or reuses a dedicated debug Chrome instance per named profile that coexists with the user's main browser; it never quits or kills any browser (unlike real-browser, which closes Chrome Beta's tabs). Trigger on "automate this site without closing my tabs", "use my logged-in session", "open ChatGPT/LinkedIn in automation", or when a browser task must preserve the user's existing windows. macOS, requires the agent-browser CLI.

설치

Codex 또는 Claude로 설치 이 Prompt를 복사해 Codex, Claude 또는 다른 어시스턴트에 붙여 넣으면 Skill 페이지를 검토하고 설치를 진행할 수 있습니다.

Manus에서 실행

출처

glebis

glebis/claude-skills

GitHub 저장소 열기 Creator 저장소 보기

다운로드

Manus에서 실행

browser-mate

Non-destructive Chrome automation. The problem it solves: to attach a CDP/agent-browser session, Chrome must run with --remote-debugging-port. The real-browser skill achieves this by quitting Chrome Beta first, destroying the user's open tabs. browser-mate instead runs a dedicated debug Chrome instance (its own --user-data-dir + port) that coexists with the user's main browser — Chrome permits concurrent instances when the data dirs differ, so no quit is needed.

The one invariant (never violate)

Never quit, pkill, or osascript quit any browser. The skill only ever launches a new dedicated instance or reuses an existing one. The single stop path sends SIGTERM only to a process matched by BOTH our dedicated user_data_dir AND our debug port — never the user's browser.

Usage

# Ensure a profile's debug Chrome is up (launch or reuse); prints the PORT on stdout
PORT=$(python3 scripts/browser.py chatgpt)

# Then drive it with agent-browser (always pass --cdp $PORT). See references/agent-browser.md
SID=$(LC_ALL=C tr -dc 'a-z0-9' < /dev/urandom | head -c 6)
agent-browser --cdp $PORT --session $SID open "https://chatgpt.com/"
agent-browser --cdp $PORT --session $SID snapshot -i

Other subcommands:

python3 scripts/browser.py list              # configured profiles
python3 scripts/browser.py status [profile]  # up/down
python3 scripts/browser.py stop chatgpt      # SIGTERM OUR instance only (graceful)

For the full agent-browser command set (click, fill, upload, screenshot, reliability, upgrade gotchas), read references/agent-browser.md.

Profiles

Config: ~/.config/browser-mate/profiles.json (auto-created from assets/profiles.example.json on first run). Each profile:

{ "default": "automation",
  "profiles": {
    "automation": { "binary": "<chrome binary>", "user_data_dir": "~/.browser-mate/automation", "port": 9222 },
    "chatgpt":     { "binary": "<chrome binary>", "user_data_dir": "~/.browser-mate/chatgpt", "port": 9223, "default_url": "https://chatgpt.com/" }
  } }

Each profile keeps its own login state — log in once per profile, it persists.
Add a profile by editing the JSON: pick a unique port and a dedicated user_data_dir (the launcher validates uniqueness and refuses dirs that point at the user's real Chrome profile).

Authentication

Cannot enter passwords (and must not). For a first-time login, launch the profile, then ask the user to log in manually in that window once; the session persists in the profile's user_data_dir for all future runs.

Safety & limits

Loopback only. The debug port binds to 127.0.0.1 (Chrome default). CDP has no auth — anyone local can drive it. Use on trusted machines; never pass --remote-debugging-address.
Dedicated data dir. A profile's user_data_dir must never be the user's real Chrome profile (~/Library/Application Support/Google/Chrome*) — the launcher refuses these.
Locked dir. If a profile's dir is already open in a non-debug Chrome window, the launcher fails loudly rather than killing it.
Replaces real-browser's launch step; interaction still uses agent-browser.

이 저장소의 다른 Skills

같은 저장소

elimination-research

glebis/claude-skills

This skill should be used for elimination-style research where the user wants to choose from a shortlist of products, tools, services, vendors, or other options using explicit criteria, numeric evidence, tournament-style comparison, source/domain classification, image-supported consumer reports, raw data tables, and ownership-cost estimates for replaceable parts. Use this skill whenever the user asks to compare options, buy something, shortlist candidates, rank alternatives, generate a "don't make me think" report, or produce a full audit report with raw numeric data.

2026-07-06308

nielsen-heuristics

glebis/claude-skills

This skill should be used to run a formal heuristic evaluation of a design artifact against Jakob Nielsen's 10 usability heuristics, producing an evidence-backed, severity-scored report. Use it when the user wants a "heuristic evaluation", "usability review", "Nielsen heuristics check", "UX heuristic audit", or asks whether a screenshot, live URL, HTML page, codebase UI, interface description, or JTBD/spec document holds up against usability principles. Accepts five input types (screenshot/image, live URL, codebase/HTML, interface description, JTBD/spec doc) and adapts its rigor and output honestly to what is actually observable. Can render the report as plain markdown (default) or as a Tufte-style HTML report, and can export findings above a severity threshold as Linear or Beads (bd) tasks after confirmation.

2026-07-04308

i18n-studio

glebis/claude-skills

This skill should be used when editing, translating, or reviewing an Astro-style i18n string corpus (files of the form export default { en: {...}, ru: {...} } under src/i18n/strings), or when the user wants to fill in missing translations, audit coverage, accept/review translations, propagate an edit across duplicate strings, get translation candidates, bulk-edit UI microcopy, or open a visual/keyboard translation editor. Drives the standalone i18n Studio tool at ~/ai_projects/i18n-studio (AST-safe minimal-diff saves via ts-morph, acceptance review state, duplicate propagation, hot-reload, and Claude translation suggestions).

2026-07-03308

feature-factory

glebis/claude-skills

This skill should be used when taking a single software feature from intent to shipped as a solo developer — goal-first, TDD, deterministic verification, evidence only where it earns its keep, and human judgment at the two moments that matter (goal approval, merge). Trigger when the user says "let's build feature X", "ship this feature", "run this through the factory", "write a goal contract", "feature-factory", or wants a disciplined intent→merge loop that resists process bloat. NOT for whole-product planning, multi-feature roadmaps, or autonomous multi-agent swarms.

2026-07-01308

the-goal

glebis/claude-skills

A Theory-of-Constraints diagnostic for deciding what to automate with AI agents. Before building any automation, skill, Goal, loop, or schedule, it walks Goldratt's Five Focusing Steps over the user's work system to find the real bottleneck, then recommends the single highest-leverage automation aimed at the constraint plus a what-NOT-to-automate list. Use when the user asks "what should I automate", "where do I point my agents", "prioritize my automation backlog", "which workflow should I agentify", "is this worth building", "find my bottleneck", "what's the highest-leverage thing", when they are about to build a Claude Code skill/Goal/loop/schedule and aren't sure it matters, or during a review of their automations. Guards against the common failure of automating busywork (a local optimum) instead of the constraint.

2026-07-01308

design-tokens

glebis/claude-skills

This skill should be used to set up, validate, resolve, and export design tokens following the DTCG (Design Tokens Community Group) Format Module 2025.10 standard. Use when the user wants to define a design token set globally or per project, compile tokens to CSS variables, layer a project's tokens over a global brand base, or produce an on-brand context file for other generation skills. Triggers on "set up design tokens", "create a token set", "compile tokens to CSS", "design system variables", "brand tokens".

2026-07-01308

name

browser-mate

description

browser-mate

The one invariant (never violate)

Usage

# Ensure a profile's debug Chrome is up (launch or reuse); prints the PORT on stdout
PORT=$(python3 scripts/browser.py chatgpt)

# Then drive it with agent-browser (always pass --cdp $PORT). See references/agent-browser.md
SID=$(LC_ALL=C tr -dc 'a-z0-9' < /dev/urandom | head -c 6)
agent-browser --cdp $PORT --session $SID open "https://chatgpt.com/"
agent-browser --cdp $PORT --session $SID snapshot -i

Other subcommands:

python3 scripts/browser.py list              # configured profiles
python3 scripts/browser.py status [profile]  # up/down
python3 scripts/browser.py stop chatgpt      # SIGTERM OUR instance only (graceful)

For the full agent-browser command set (click, fill, upload, screenshot, reliability, upgrade gotchas), read references/agent-browser.md.

Profiles

Config: ~/.config/browser-mate/profiles.json (auto-created from assets/profiles.example.json on first run). Each profile:

{ "default": "automation",
  "profiles": {
    "automation": { "binary": "<chrome binary>", "user_data_dir": "~/.browser-mate/automation", "port": 9222 },
    "chatgpt":     { "binary": "<chrome binary>", "user_data_dir": "~/.browser-mate/chatgpt", "port": 9223, "default_url": "https://chatgpt.com/" }
  } }

Each profile keeps its own login state — log in once per profile, it persists.
Add a profile by editing the JSON: pick a unique port and a dedicated user_data_dir (the launcher validates uniqueness and refuses dirs that point at the user's real Chrome profile).

Authentication

Safety & limits

Loopback only. The debug port binds to 127.0.0.1 (Chrome default). CDP has no auth — anyone local can drive it. Use on trusted machines; never pass --remote-debugging-address.
Dedicated data dir. A profile's user_data_dir must never be the user's real Chrome profile (~/Library/Application Support/Google/Chrome*) — the launcher refuses these.
Locked dir. If a profile's dir is already open in a non-debug Chrome window, the launcher fails loudly rather than killing it.
Replaces real-browser's launch step; interaction still uses agent-browser.