Reach and see
The world. The browser, audio and video, the database, web search, Slack, the support desk, the SEO suite, and, with a deployment, logs and uptime.
Ask the agent to screenshot a page, transcribe a recording, query the database, search the web, summarize a Slack thread, or check how a page ranks. It answers from the system itself instead of guessing. Skills are named bare here; Skills shows how to run one on your host.
| Capability | What it does | Skills and tools |
|---|---|---|
| Browser | A bundled headless browser for screenshots, styled PDFs, page-to-Markdown, and recordings, plus scripted flows that sign in and click through real pages. | browser-flows tools: browser_flows, browser_screenshot, browser_pdf, browser_markdown, browser_record |
| Media | An audio or video file made readable: a timestamped transcript made on-device, screenshots at the moments that matter, a summary of what was said and shown, and repro steps from a bug-report video. | media tools: media_transcribe, video_frames |
| Logs and uptime with a deployment | Your telemetry, queried from the session: a request timeline by correlation ID, error rates, incidents, and the log lines behind a customer report. | betterstack |
| Database, read-only | Queries and schema against a production replica, or a fork you can break. | tools: database_query, database_schema, database_list, database_fork |
| Investigate with a deployment | A ticket, a production anomaly, or a bug traced across logs, the database, the codebase, and git history into a structured brief. Read-only. | investigate |
| Web search | Live search results with sources, from inside the session. | tools: web_search |
| Slack, read-only | Multi-channel summaries, thread pulls, workspace search, and what is waiting on you, over the channels the team works in. It never posts. | slack tools: slack_channels, slack_history, slack_thread, slack_search, slack_waiting |
| Support desk | A queue pulse, ticket deep-dives, account lookups, App Store reviews, and reply drafts left as private notes on the desk your support team runs. | helpdesk tools: helpdesk_tickets, helpdesk_ticket, helpdesk_stats, helpdesk_note, appstore_reviews |
| Search Console and PageSpeed | Queries, impressions, indexing, and Core Web Vitals for any site you own. | seo console seo speed tools: gsc_query, gsc_inspect, page_speed_audit |
| SERP and rank | Real Google results, AI overviews, and a domain-authority proxy for trend tracking. | seo serp seo rank tools: serpapi_search, open_page_rank |
| SEO audit and WordPress | A read-only audit across every SEO source, and WordPress content through its public API. | seo audit wordpress-rest |
Packs in the plugin switch on when you add a credential. See Packs.
What reads and what writes
Most of these only read:
- Database queries run in a read-only transaction, so Postgres itself rejects a write.
database_forkis the one exception: it clones a local database for risky schema work. - Slack is read with a token that has no write scope, so nothing posts.
- Search and SEO tools read. They never publish to a site or edit one.
Two can act on the system they reach:
- Browser flows drive a visible browser through real pages: they fill forms and click through steps, and you log in by hand when a flow needs it.
- The helpdesk pack can add a private note to a ticket and change its assignee. It asks first, unless a queue's own routine is written to go ahead, and it never replies to a customer.
With a deployment
Rows marked with a deployment are not in the open plugin. They come with a forward-deployed setup, because they need your own systems, such as telemetry, to exist. Slack and the support desk are not among them: the plugin's Slack and Helpdesk packs cover those.
investigate is one of the deployment rows. It traces a customer report into a brief: a timeline by correlation ID from the logs, the affected rows from the read-only replica, and the commit that introduced the change from git. It only reads. Without a deployment, the pieces the plugin ships work on their own: the database tools, the repo's git history, and the engineer skill, which reproduces a bug with a failing test before it drafts the fix.