dsh-plugin-t-expert 0.4.26 → 0.4.36

package/data/experts/design/user-experience-architect/skills/browser-use/SKILL.md

@@ -0,0 +1,253 @@
+---
+name: browser-use
+description: Automates browser interactions for web testing, form filling, screenshots, and data extraction. Use when the user needs to navigate websites, interact with web pages, fill forms, take screenshots,
+  or extract information from web pages.
+description_zh: 浏览器自动化（导航、点击、截图、数据提取、多会话、云浏览器）
+description_en: Automates browser interactions for web testing, form filling, screenshots, and d...
+version: 2.0.0
+allowed-tools: Bash(browser-use:*)
+metadata:
+  clawdbot:
+    emoji: 🌐
+    requires:
+      bins:
+      - browser-use
+    install:
+    - package-manager: curl
+      command: curl -fsSL https://browser-use.com/cli/install.sh | bash
+---
+
+# Browser Automation with browser-use CLI
+
+The `browser-use` command provides fast, persistent browser automation. A background daemon keeps the browser open across commands, giving ~50ms latency per call.
+
+## Prerequisites
+
+```bash
+browser-use doctor    # Verify installation
+```
+
+For setup details, see https://github.com/browser-use/browser-use/blob/main/browser_use/skill_cli/README.md
+
+## Core Workflow
+
+1. **Navigate**: `browser-use open <url>` — launches headless browser and opens page
+2. **Inspect**: `browser-use state` — returns clickable elements with indices
+3. **Interact**: use indices from state (`browser-use click 5`, `browser-use input 3 "text"`)
+4. **Verify**: `browser-use state` or `browser-use screenshot` to confirm
+5. **Repeat**: browser stays open between commands
+
+If a command fails, run `browser-use close` first to clear any broken session, then retry.
+
+To use the user's existing Chrome (preserves logins/cookies): run `browser-use connect` first.
+To use a cloud browser instead: run `browser-use cloud connect` first.
+After either, commands work the same way.
+
+### If `browser-use connect` fails
+
+When `browser-use connect` cannot find a running Chrome with remote debugging, prompt the user with two options:
+
+1. **Use their real Chrome browser** — they need to enable remote debugging first:
+   - Open `chrome://inspect/#remote-debugging` in Chrome, or relaunch Chrome with `--remote-debugging-port=9222`
+   - Then retry `browser-use connect`
+2. **Use managed Chromium with their Chrome profile** — no Chrome setup needed:
+   - Run `browser-use profile list` to show available profiles
+   - Ask which profile they want, then use `browser-use --profile "ProfileName" open <url>`
+   - This launches a separate Chromium instance with their profile data (cookies, logins, extensions)
+
+Let the user choose — don't assume one path over the other.
+
+## Browser Modes
+
+```bash
+browser-use open <url>                         # Default: headless Chromium (no setup needed)
+browser-use --headed open <url>                # Visible window (for debugging)
+browser-use connect                            # Connect to user's Chrome (preserves logins/cookies)
+browser-use cloud connect                      # Cloud browser (zero-config, requires API key)
+browser-use --profile "Default" open <url>     # Real Chrome with specific profile
+```
+
+After `connect` or `cloud connect`, all subsequent commands go to that browser — no extra flags needed.
+
+## Commands
+
+```bash
+# Navigation
+browser-use open <url>                    # Navigate to URL
+browser-use back                          # Go back in history
+browser-use scroll down                   # Scroll down (--amount N for pixels)
+browser-use scroll up                     # Scroll up
+browser-use tab list                      # List all tabs
+browser-use tab new [url]                 # Open a new tab (blank or with URL)
+browser-use tab switch <index>            # Switch to tab by index
+browser-use tab close <index> [index...]  # Close one or more tabs
+
+# Page State — always run state first to get element indices
+browser-use state                         # URL, title, clickable elements with indices
+browser-use screenshot [path.png]         # Screenshot (base64 if no path, --full for full page)
+
+# Interactions — use indices from state
+browser-use click <index>                 # Click element by index
+browser-use click <x> <y>                 # Click at pixel coordinates
+browser-use type "text"                   # Type into focused element
+browser-use input <index> "text"          # Click element, then type
+browser-use keys "Enter"                  # Send keyboard keys (also "Control+a", etc.)
+browser-use select <index> "option"       # Select dropdown option
+browser-use upload <index> <path>         # Upload file to file input
+browser-use hover <index>                 # Hover over element
+browser-use dblclick <index>              # Double-click element
+browser-use rightclick <index>            # Right-click element
+
+# Data Extraction
+browser-use eval "js code"                # Execute JavaScript, return result
+browser-use get title                     # Page title
+browser-use get html [--selector "h1"]    # Page HTML (or scoped to selector)
+browser-use get text <index>              # Element text content
+browser-use get value <index>             # Input/textarea value
+browser-use get attributes <index>        # Element attributes
+browser-use get bbox <index>              # Bounding box (x, y, width, height)
+
+# Wait
+browser-use wait selector "css"           # Wait for element (--state visible|hidden|attached|detached, --timeout ms)
+browser-use wait text "text"              # Wait for text to appear
+
+# Cookies
+browser-use cookies get [--url <url>]     # Get cookies (optionally filtered)
+browser-use cookies set <name> <value>    # Set cookie (--domain, --secure, --http-only, --same-site, --expires)
+browser-use cookies clear [--url <url>]   # Clear cookies
+browser-use cookies export <file>         # Export to JSON
+browser-use cookies import <file>         # Import from JSON
+
+# Session
+browser-use close                         # Close browser and stop daemon
+browser-use sessions                      # List active sessions
+browser-use close --all                   # Close all sessions
+```
+
+For advanced browser control (CDP, device emulation, tab activation), see `references/cdp-python.md`.
+
+## Cloud API
+
+```bash
+browser-use cloud connect                 # Provision cloud browser and connect (zero-config)
+browser-use cloud login <api-key>         # Save API key (or set BROWSER_USE_API_KEY)
+browser-use cloud logout                  # Remove API key
+browser-use cloud v2 GET /browsers        # REST passthrough (v2 or v3)
+browser-use cloud v2 POST /tasks '{"task":"...","url":"..."}'
+browser-use cloud v2 poll <task-id>       # Poll task until done
+browser-use cloud v2 --help               # Show API endpoints
+```
+
+`cloud connect` provisions a cloud browser with a persistent profile (auto-created on first use), connects via CDP, and prints a live URL. `browser-use close` disconnects AND stops the cloud browser. For custom browser settings (proxy, timeout, specific profile), use `cloud v2 POST /browsers` directly with the desired parameters.
+
+### Agent Self-Registration
+
+Only use this if you don't already have an API key (check `browser-use doctor` to see if api_key is set). If already logged in, skip this entirely.
+
+1. `browser-use cloud signup` — get a challenge
+2. Solve the challenge
+3. `browser-use cloud signup --verify <challenge-id> <answer>` — verify and save API key
+4. `browser-use cloud signup --claim` — generate URL for a human to claim the account
+
+## Tunnels
+
+```bash
+browser-use tunnel <port>                 # Start Cloudflare tunnel (idempotent)
+browser-use tunnel list                   # Show active tunnels
+browser-use tunnel stop <port>            # Stop tunnel
+browser-use tunnel stop --all             # Stop all tunnels
+```
+
+## Profile Management
+
+```bash
+browser-use profile list                  # List detected browsers and profiles
+browser-use profile sync --all            # Sync profiles to cloud
+browser-use profile update                # Download/update profile-use binary
+```
+
+## Command Chaining
+
+Commands can be chained with `&&`. The browser persists via the daemon, so chaining is safe and efficient.
+
+```bash
+browser-use open https://example.com && browser-use state
+browser-use input 5 "user@example.com" && browser-use input 6 "password" && browser-use click 7
+```
+
+Chain when you don't need intermediate output. Run separately when you need to parse `state` to discover indices first.
+
+## Common Workflows
+
+### Authenticated Browsing
+
+When a task requires an authenticated site (Gmail, GitHub, internal tools), use Chrome profiles:
+
+```bash
+browser-use profile list                           # Check available profiles
+# Ask the user which profile to use, then:
+browser-use --profile "Default" open https://github.com  # Already logged in
+```
+
+### Exposing Local Dev Servers
+
+```bash
+browser-use tunnel 3000                            # → https://abc.trycloudflare.com
+browser-use open https://abc.trycloudflare.com     # Browse the tunnel
+```
+
+## Multiple Browsers
+
+For subagent workflows or running multiple browsers in parallel, use `--session NAME`. Each session gets its own browser. See `references/multi-session.md`.
+
+## Configuration
+
+```bash
+browser-use config list                            # Show all config values
+browser-use config set cloud_connect_proxy jp      # Set a value
+browser-use config get cloud_connect_proxy         # Get a value
+browser-use config unset cloud_connect_timeout     # Remove a value
+browser-use doctor                                 # Shows config + diagnostics
+browser-use setup                                  # Interactive post-install setup
+```
+
+Config stored in `~/.browser-use/config.json`.
+
+## Global Options
+
+| Option | Description |
+|--------|-------------|
+| `--headed` | Show browser window |
+| `--profile [NAME]` | Use real Chrome (bare `--profile` uses "Default") |
+| `--cdp-url <url>` | Connect via CDP URL (`http://` or `ws://`) |
+| `--session NAME` | Target a named session (default: "default") |
+| `--json` | Output as JSON |
+| `--mcp` | Run as MCP server via stdin/stdout |
+
+## Tips
+
+1. **Always run `state` first** to see available elements and their indices
+2. **Use `--headed` for debugging** to see what the browser is doing
+3. **Sessions persist** — browser stays open between commands
+4. **CLI aliases**: `bu`, `browser`, and `browseruse` all work
+5. **If commands fail**, run `browser-use close` first, then retry
+
+## Troubleshooting
+
+- **Browser won't start?** `browser-use close` then `browser-use --headed open <url>`
+- **Element not found?** `browser-use scroll down` then `browser-use state`
+- **Run diagnostics:** `browser-use doctor`
+
+## Cleanup
+
+```bash
+browser-use close                         # Close browser session
+browser-use tunnel stop --all             # Stop tunnels (if any)
+```
+
+
+## 工具说明
+
+本技能使用以下工具：
+
+- **Bash(browser-use:*)**: 使用 Bash(browser-use:*) 工具

package/data/experts/design/user-experience-architect/skills/browser-use/references/cdp-python.md

@@ -0,0 +1,76 @@
+# Raw CDP & Python Session Reference
+
+The CLI commands handle most browser interactions. Use `browser-use python` with raw CDP when you need browser-level control the CLI doesn't expose — activating a tab so the user sees it, intercepting network requests, emulating devices, or working with Chrome target IDs directly.
+
+## How the Python session works
+
+`browser-use python "statement"` executes one Python statement per call. Variables persist across calls — set a value in one call, use it in the next.
+
+A `browser` object is pre-injected with sync wrappers for common operations (`browser.goto()`, `browser.click()`, etc.). For anything beyond those, two internals give you full access:
+
+- `browser._run(coroutine)` — run any async coroutine synchronously (60s timeout)
+- `browser._session` — the raw `BrowserSession` with full CDP client access
+
+## Getting a CDP client
+
+```bash
+browser-use python "cdp = browser._run(browser._session.get_or_create_cdp_session())"
+```
+
+After this, `cdp` persists across calls. Use `cdp.cdp_client.send.<Domain>.<method>()` for any CDP command and `cdp.session_id` for the session parameter.
+
+## Recipes
+
+### Activate a tab (make it visible to the user)
+
+The CLI's `tab switch` only changes the agent's internal focus — Chrome's visible tab doesn't change. To actually show the user a specific tab:
+
+```bash
+# Get all targets to find the target ID
+browser-use python "targets = browser._session.session_manager.get_all_page_targets()"
+browser-use python "print([(i, t.url) for i, t in enumerate(targets)])"
+
+# Activate target at index 1 so the user sees it
+browser-use python "cdp = browser._run(browser._session.get_or_create_cdp_session(target_id=None, focus=False))"
+browser-use python "browser._run(cdp.cdp_client.send.Target.activateTarget(params={'targetId': targets[1].target_id}))"
+```
+
+### List all tabs with target IDs
+
+```bash
+browser-use python "targets = browser._session.session_manager.get_all_page_targets()"
+browser-use python "
+for i, t in enumerate(targets):
+    print(f'{i}: {t.target_id[:12]}... {t.url}')
+"
+```
+
+### Run JavaScript and get the result
+
+```bash
+browser-use python "cdp = browser._run(browser._session.get_or_create_cdp_session())"
+browser-use python "result = browser._run(cdp.cdp_client.send.Runtime.evaluate(params={'expression': 'document.title', 'returnByValue': True}, session_id=cdp.session_id))"
+browser-use python "print(result['result']['value'])"
+```
+
+### Emulate a mobile device
+
+```bash
+browser-use python "cdp = browser._run(browser._session.get_or_create_cdp_session())"
+browser-use python "browser._run(cdp.cdp_client.send.Emulation.setDeviceMetricsOverride(params={'width': 375, 'height': 812, 'deviceScaleFactor': 3, 'mobile': True}, session_id=cdp.session_id))"
+```
+
+### Get cookies via CDP
+
+```bash
+browser-use python "cdp = browser._run(browser._session.get_or_create_cdp_session())"
+browser-use python "cookies = browser._run(cdp.cdp_client.send.Network.getCookies(params={}, session_id=cdp.session_id))"
+browser-use python "print(cookies)"
+```
+
+## Tips
+
+- Each `browser-use python` call is one statement. Multi-line strings work for `for` loops and `if` blocks, but you can't mix statements and expressions. Use multiple calls.
+- Variables persist: set `cdp = ...` in one call, use `cdp` in the next.
+- The `browser._run()` bridge has a 60-second timeout. For long operations, increase it or use the async internals directly.
+- All CDP domains are available via `cdp.cdp_client.send.<Domain>.<method>()`. See the [Chrome DevTools Protocol docs](https://chromedevtools.github.io/devtools-protocol/) for the full API.

package/data/experts/design/user-experience-architect/skills/browser-use/references/multi-session.md

@@ -0,0 +1,92 @@
+# Multiple Browser Sessions
+
+## Why use multiple sessions
+
+When you need more than one browser at a time:
+- Cloud browser for scraping + local Chrome for authenticated tasks
+- Two different Chrome profiles simultaneously
+- Isolated browser for testing that won't affect the user's browsing
+- Running a headed browser for debugging while headless runs in background
+
+## How sessions are isolated
+
+Each `--session NAME` gets:
+- Its own daemon process
+- Its own Unix socket (`~/.browser-use/{name}.sock`)
+- Its own PID file and state file
+- Its own browser instance (completely independent)
+- Its own tab ownership state (multi-agent locks don't cross sessions)
+
+## The `--session` flag
+
+Must be passed on every command targeting that session:
+
+```bash
+browser-use --session work open <url>      # goes to 'work' daemon
+browser-use --session work state           # reads from 'work' daemon
+browser-use state                          # goes to 'default' daemon (different browser)
+```
+
+If you forget `--session`, the command goes to the `default` session. This is the most common mistake — you'll interact with the wrong browser.
+
+## Combining sessions with browser modes
+
+```bash
+# Session 1: cloud browser
+browser-use --session cloud cloud connect
+
+# Session 2: connect to user's Chrome
+browser-use --session chrome connect
+
+# Session 3: headed Chromium for debugging
+browser-use --session debug --headed open <url>
+```
+
+Each session is fully independent. The cloud session talks to a remote browser, the chrome session talks to the user's Chrome, and the debug session manages its own Chromium — all running simultaneously.
+
+## Listing and managing sessions
+
+```bash
+browser-use sessions
+```
+
+Output:
+```
+SESSION          PHASE          PID      CONFIG
+cloud            running        12345    cloud
+chrome           running        12346    cdp
+debug            ready          12347    headed
+```
+
+PHASE shows the daemon lifecycle state: `initializing`, `ready`, `starting`, `running`, `shutting_down`, `stopped`, `failed`.
+
+```bash
+browser-use --session cloud close           # close one session
+browser-use close --all                     # close every session
+```
+
+## Common patterns
+
+**Cloud + local authenticated:**
+```bash
+browser-use --session scraper cloud connect
+browser-use --session scraper open https://example.com
+# ... scrape data ...
+
+browser-use --session auth --profile "Default" open https://github.com
+browser-use --session auth state
+# ... interact with authenticated site ...
+```
+
+**Throwaway test browser:**
+```bash
+browser-use --session test --headed open https://localhost:3000
+# ... test, debug, inspect ...
+browser-use --session test close    # done, clean up
+```
+
+**Environment variable:**
+```bash
+export BROWSER_USE_SESSION=work
+browser-use open <url>              # uses 'work' session without --session flag
+```

package/data/experts/design/user-experience-researcher/.codebuddy-plugin/plugin.json

@@ -0,0 +1,31 @@
+{
+  "name": "user-experience-researcher",
+  "version": "1.0.1",
+  "description": "Expert user experience researcher specializing in user behavior analysis, usability testing, and data-driven design insights",
+  "expertType": "agent",
+  "agentName": "user-experience-researcher",
+  "agents": ["./agents/user-experience-researcher.md"],
+  "skills": ["./skills/market-researcher", "./skills/browser-use", "./skills/minimax-docx"],
+  "displayName": { "en": "Zoe", "zh": "探真真" },
+  "profession": { "en": "User Experience Researcher", "zh": "用户体验研究员" },
+  "displayDescription": {
+    "en": "Validating design decisions with real data instead of assumptions, specializing in user behavior analysis and usability testing",
+    "zh": "用真实数据而非假设验证设计决策，专精用户行为分析和可用性测试"
+  },
+  "avatar": "avatars/expert.png",
+  "categoryId": "01-ProductDesign",
+  "defaultInitPrompt": {
+    "zh": "我们想深入了解用户需求和痛点,需要科学的用户研究方法,请用户体验研究员帮我制定用户研究计划并分析研究结果。",
+    "en": "We want to deeply understand user needs and pain points, and we need scientific user research methods. Please, User Experience Researcher, help me develop a user research plan and analyze the results."
+  },
+  "tags": [
+    { "en": "User Research", "zh": "用户研究" },
+    { "en": "Usability Testing", "zh": "可用性测试" },
+    { "en": "Data Insight", "zh": "数据洞察" }
+  ],
+  "quickPrompts": [
+    { "zh": "我们想深入了解用户需求和痛点,需要科学的用户研究方法,请用户体验研究员帮我制定用户研究计划并分析研究结果。", "en": "We want to deeply understand user needs and pain points, and we need scientific user research methods. Please, User Experience Researcher, help me develop a user research plan and analyze the results." },
+    { "zh": "进行用户行为分析和体验洞察", "en": "Conduct user behavior analysis and experience insights" },
+    { "zh": "输出可执行的用户研究报告和建议", "en": "Deliver actionable user research reports and recommendations" }
+  ]
+}

package/data/experts/design/user-experience-researcher/.downloaded_at

@@ -0,0 +1 @@
+2026-09-29T03:24:59.005760+00:00

package/data/experts/design/user-experience-researcher/.imported-from-workbuddy

@@ -0,0 +1,7 @@
+{
+  "plugin": "user-experience-researcher",
+  "division": "design",
+  "categoryId": "01-ProductDesign",
+  "importedAt": "2026-09-29T12:42:08",
+  "source": "workbuddy expert marketplace (COS)"
+}

package/data/experts/design/user-experience-researcher/README.md

@@ -0,0 +1,21 @@
+# 探真真 - 用户体验研究员
+
+深入洞察用户真实需求，用研究数据驱动产品体验决策
+
+## 功能特性
+
+- 深入洞察用户真实需求与行为
+- 用研究数据驱动产品体验决策
+- 设计用户访谈、问卷与可用性测试方案
+- 支持网络检索、市场调研与文档导出
+
+## 致谢
+
+本专家封装并引用了以下开源技能：
+
+- 本专家的 agent prompt 改编自 [agency-agents](https://github.com/msitarzewski/agency-agents)（MIT License），在此致谢。
+- `browser-use` 技能：封装引用 [browser-use](https://github.com/browser-use/browser-use)（MIT License）命令行工具。
+- `minimax-docx` 技能：遵循 MIT License（Copyright MiniMaxAI）。
+- `market-researcher` 技能：本仓原创。
+
+各许可证全文见 `license/` 目录。本专家在原始内容基础上进行了适配与修改。