browser-control
Browser automation for authenticated web apps using Chrome DevTools MCP. Use when navigating PowerSchool, filling forms, downloading reports, or automating any browser task requiring login. Triggers on: browser control, navigate website, PowerSchool, fill form, download report, automate browser.
What this skill does
# Browser Control — Chrome DevTools MCP You automate browser interactions for authenticated web applications using Chrome DevTools Protocol. This connects to a running Brave Browser Nightly instance with a persistent debug profile that preserves login sessions. ## Setup — Launch Browser Before any browser interaction, ensure the debug browser is running: ```bash bash plugins/psd-productivity/skills/browser-control/scripts/launch-chrome.sh ``` If the script reports `already_running`, the browser is ready. If `started`, wait a moment for it to initialize. **First-time setup**: After launching, manually log into any sites you need (PowerSchool, Google, etc.). The persistent profile at `~/.psd-browser-automation` saves cookies and sessions across restarts. ## Core Workflow 1. **Check browser status** — run launch script with `--status` 2. **Launch if needed** — run launch script (no args for visible window) 3. **Navigate** — use `navigate_page` to go to URLs 4. **Interact** — use `click`, `fill`, `fill_form`, `type_text`, `press_key` 5. **Verify** — use `take_screenshot` or `take_snapshot` to confirm state 6. **Wait** — use `wait_for` when pages are loading or processing ## Tool Reference ### Navigation & Pages - `navigate_page` — go to a URL - `list_pages` — list open tabs - `select_page` — switch to a tab - `new_page` — open new tab - `close_page` — close a tab - `resize_page` — change viewport size - `handle_dialog` — accept/dismiss browser dialogs - `get_tab_id` — get current tab identifier ### Input - `click` — click an element by CSS selector or text - `click_at` — click at x,y coordinates - `hover` — hover over an element - `fill` — fill an input field (clears first) - `type_text` — type text character by character - `fill_form` — fill multiple form fields at once - `press_key` — press keyboard keys (Enter, Tab, Escape, etc.) - `upload_file` — upload a file to a file input - `drag` — drag from one element to another ### Observation - `take_screenshot` — capture visible page as image - `take_snapshot` — get accessibility tree (structured page content) - `wait_for` — wait for an element, text, or network idle - `evaluate_script` — run JavaScript in the page context ### Console & Network - `list_console_messages` — view browser console output - `get_console_message` — get details of a console message - `list_network_requests` — view network activity - `get_network_request` — get details of a network request ## Best Practices 1. **Always take_snapshot first** — before clicking or filling, get the page structure to identify correct selectors 2. **Use wait_for after navigation** — pages may not be fully loaded immediately 3. **Handle dialogs proactively** — PowerSchool shows confirm dialogs; use `handle_dialog` to accept/dismiss 4. **Use fill_form for multiple fields** — more efficient than individual fill calls 5. **Screenshot for verification** — take screenshots after important actions to confirm success 6. **Check for errors** — use `list_console_messages` if something seems wrong ## PowerSchool-Specific Knowledge When automating PowerSchool reports, run all browser automation directly in the main session — do not delegate to a subagent (subagents cannot access MCP tools). Key patterns: 1. Verify the correct school is selected (top banner) 2. Use the navigation paths from `plugins/psd-productivity/skills/enrollment/references/` 3. Elementary uses 1-Day FTE window; Middle/High use 5-Day window 4. Save reports with consistent naming: `[SchoolAbbr]_[ReportName]_[CountDate]` ## Troubleshooting - **"Browser not running"** — Run the launch script - **"Connection refused on 9222"** — Browser crashed; kill orphan processes and relaunch - **"Login required"** — Open the browser window, log in manually, then retry - **"Element not found"** — Take a snapshot to see current page structure, adjust selector - **Page loads slowly** — Use `wait_for` with appropriate timeout before interacting
Related in AI Agents
skill-development
IncludedComprehensive meta-skill for creating, managing, validating, auditing, and distributing Claude Code skills and slash commands (unified in v2.1.3+). Provides skill templates, creation workflows, validation patterns, audit checklists, naming conventions, YAML frontmatter guidance, progressive disclosure examples, and best practices lookup. Use when creating new skills, validating existing skills, auditing skill quality, understanding skill architecture, needing skill templates, learning about YAML frontmatter requirements, progressive disclosure patterns, tool restrictions (allowed-tools), skill composition, skill naming conventions, troubleshooting skill activation issues, creating custom slash commands, configuring command frontmatter, using command arguments ($ARGUMENTS, $1, $2), bash execution in commands, file references in commands, command namespacing, plugin commands, MCP slash commands, Skill tool configuration, or deciding between skills vs slash commands. Delegates to docs-management skill for official documentation.
reprompter
IncludedTransform messy prompts into well-structured, effective prompts — single or multi-agent. Use when: "reprompt", "reprompt this", "clean up this prompt", "structure my prompt", rough text needing XML tags and best practices, "reprompter teams", "repromptception", "run with quality", "smart run", "smart agents", multi-agent tasks, audits, parallel work, anything going to agent teams. Don't use when: simple Q&A, pure chat, immediate execution-only tasks. See "Don't Use When" section for details. Outputs: Structured XML/Markdown prompt, quality score (before/after), optional team brief + per-agent sub-prompts, agent team output files. Success criteria: Single mode quality score ≥ 7/10; Repromptception per-agent prompt quality score 8+/10; all required sections present, actionable and specific.
adaptive-compaction
IncludedAdaptive add-on policy and recovery layer that decides WHEN to compact, prune, snapshot, or fork -- replacing fixed-percent auto-compaction across Claude Code, Codex, and MCP-capable hosts. Trigger on auto-compact timing or damage: "when should I compact", "is it safe to compact now or start a fresh session", "auto-compact fires too early/mid-task", "switching to an unrelated task but the window still has space", "context rot", "answers get worse the longer the session runs", "the agent forgot the plan or my decisions after it summarized", "add a layer on top that manages context without changing the agent", raising autoCompactWindow to give the policy room, or installing/tuning a cross-tool compaction policy or PreCompact hook -- even when "compaction" is never said but the problem is context-window pressure or post-summarization memory loss. Do NOT use to summarize a conversation, build RAG, write a summarization prompt (decides WHEN not HOW), or answer max-context-length trivia.
agent-skill-creator
IncludedCreate cross-platform agent skills from workflow descriptions. Activates when users ask to create an agent, automate a repetitive workflow, create a custom skill, or need advanced agent creation. Triggers on phrases like create agent for, automate workflow, create skill for, every day I have to, daily I need to, turn process into agent, need to automate, create a cross-platform skill, validate this skill, export this skill, migrate this skill. Supports single skills, multi-agent suites, transcript processing, template-based creation, interactive configuration, cross-platform export, and spec validation.
llm-wiki
IncludedUse when building or maintaining a persistent personal knowledge base (second brain) in Obsidian where an LLM incrementally ingests sources, updates entity/concept pages, maintains cross-references, and keeps a synthesis current. Triggers include "second brain", "Obsidian wiki", "personal knowledge management", "ingest this paper/article/book", "build a research wiki", "compound knowledge", "Memex", or whenever the user wants knowledge to accumulate across sessions instead of being re-derived by RAG on every query.
skill-master
IncludedAgent Skills authoring, evaluation, and optimization. Create, edit, validate, benchmark, and improve skills following the agentskills.io specification. Use when designing SKILL.md files, structuring skill folders (references, scripts, assets), ingesting external documentation into skills, running trigger evals, benchmarking skill quality, optimizing descriptions, or performing blind A/B comparisons. Keywords: agentskills.io, SKILL.md, skill authoring, eval, benchmark, trigger optimization.