catalyst-smartbrowz
Catalyst SmartBrowz — browser automation and document generation service. Includes Headless (connect to remote Chrome/Firefox with Puppeteer/Playwright/Selenium), Browser Logic (serverless functions for browser tasks in Java/Node.js), PDF & Screenshot (generate visual documents from HTML/URL/Template), Templates (design dynamic content templates), Browser Grid (parallel headless browsers with auto-scaling, Early Access), and Dataverse (data scraping APIs). Trigger on 'SmartBrowz', 'headless browser', 'Headless Browser', 'Puppeteer', 'Selenium', 'Playwright', 'Browser Logic', 'PDF generation', 'screenshot', 'PDF/Screenshot generation', 'PDF & Screenshot', 'browser automation', 'Browser Grid', or 'web scraping'. Console + SDK (Java/Node.js/Python for PDF/Screenshot + Browser Grid) + CLI (for Browser Logic functions).
- Installs
- 947
- Last 24h
- +12
- Trending rank
- #7863
- Security
- Not audited
Install
Works with every agent the skills CLI supports.
npx skills add https://github.com/catalystbyzoho/agent-skills --skill catalyst-smartbrowz- 01
Install
Run the command in your project. The CLI asks which agents to install for.
- 02
Describe the task
Ask your agent for something this skill covers. It loads catalyst-smartbrowz automatically when relevant.
- 03
Review the result
The agent follows the SKILL.md steps, scripts and references bundled with the skill.
SKILL.md
The instructions your agent reads when the skill is triggered.
Prerequisites
Before using SmartBrowz, activate it once per project in the console:
Console → your project → SmartBrowz (left sidebar) → click "Start Exploring"
Skipping this step prevents access to Headless, Browser Logic, PDF & Screenshot, Templates, Browser Grid, and Dataverse components.
For Browser Logic functions: Requires Catalyst CLI installation. Initialize and deploy Browser Logic functions via CLI (cannot be created directly in console, but can be uploaded).
How It Works
-
Multi-component service — SmartBrowz offers 6 independent components in one unified platform:
- Headless: Connect to remote Chrome/Firefox in Catalyst cloud with automation libraries
- Browser Logic: Serverless functions (Java/Node.js) containing browser automation logic
- PDF & Screenshot: Generate visual documents programmatically
- Templates: Design and store templates for dynamic content
- Browser Grid (Early Access): Parallel headless browsers with auto-scaling
- Dataverse: Data scraping APIs
-
Choose your workflow:
- Headless mode: Copy console-provided endpoints and code snippets to connect with Puppeteer/Playwright/Selenium
- Browser Logic: Initialize via CLI, code in IDE, deploy to console — for persistent browser automation tasks
- PDF & Screenshot: Use console Playground, SDKs (Java/Node.js/Python), or API to generate documents
- Browser Grid: Configure node/browser count, connect via CDP/Webdriver endpoints, process requests in parallel
-
Load
references/smartbrowz-basics.md— for component details, automation library setup, Browser Logic structure, PDF/Screenshot SDK usage, Browser Grid configurations, and troubleshooting -
SDK-first rule — When writing implementation code, always prefer SDK methods over raw REST API calls:
- Node.js:
app.smartbrowz()(lowercase —app.SmartBrowz()is not a function) →smartbrowz.convertToPdf(),smartbrowz.generateFromTemplate(),app.smartbrowz().browserGrid()→grid.getGrid(),grid.stopGrid() - Python:
app.smart_browz()→smart_browz.convert_to_pdf(),smart_browz.generate_from_template(),app.smart_browz().browser_grid()→grid.get_all_grid() - Java:
ZCSmartBrowz.getInstance()→smartBrowz.convertToPdf(),smartBrowz.generateFromTemplate() - Use REST API only when no SDK equivalent exists (e.g., checking
free_sessionson Browser Grid live stats)
- Node.js:
-
Key concepts:
- Remote browsers run in Catalyst cloud — not local. Endpoints are auto-generated by console.
- No api-key in connection code — Puppeteer/Playwright/Selenium connect using only the endpoint URL. The
api-keyis only used for Browser Grid REST API calls (e.g., live stats). - Chrome browser only (currently) — Firefox support in Browser Grid (Early Access)
- Browser Logic functions = Serverless function type — created with CLI, not console UI
- Browser Grid = auto-scaling — nodes and browsers spawn on demand based on configuration
- Code Recipes available in console for testing automation library use cases
-
Security note — Any browser automation or web scraping is at your own risk. Only use on domains that permit such actions or with proper approval.
Security Checklist
- API Key protection: Endpoints for Headless and Browser Grid are secured with auto-generated API keys. Regenerate keys if compromised (note: this resets grid stats).
- Browser Logic logs: All function activity is logged in Console → DevOps → Logs. Review logs for debugging and security audits.
- Browser Grid queue limits: Selenium requests queue for 30 seconds, Puppeteer/Playwright for 5 minutes. After timeout, requests are killed.
- Browser Grid alerts: Monitor Dashboard for alerts (Browser Creation Rejected, 90% Disk Exhausted, 80% Memory/CPU Exhausted, Nodes Crashed).
- Default storage: Browser Grid nodes have 10GB disk limit. Monitor disk usage to prevent failures.
- Rate considerations: Browser automation can generate high network traffic. Be mindful of target website rate limits and terms of service.
Triggers
Use this skill for: "SmartBrowz", "headless browser", "Headless Browser", "remote browser", "Puppeteer", "Playwright", "Selenium", "browser automation", "Browser Logic", "PDF generation", "screenshot webpage", "HTML to PDF", "URL to PDF", "template PDF", "PDF/Screenshot generation", "PDF & Screenshot", "SmartBrowz templates", "Browser Grid", "parallel browsers", "web scraping", "Dataverse", "CDP endpoint", "Webdriver endpoint", "headless Chrome", "headless Firefox", "browser testing", or "automation library".
References
| Reference | Load when the query is about… |
|---|---|
references/smartbrowz-basics.md | Headless setup (Puppeteer/Playwright/Selenium code snippets), Browser Logic (CLI commands, function structure, deployment), PDF & Screenshot (console Playground, SDK usage in Java/Node.js/Python, API calls, input formats HTML/URL/Template), Templates (design, storage, dynamic content), Browser Grid (configurations Basic/Light/Moderate/Heavy, node/browser setup, CDP/Webdriver endpoints, workflow, alerts, states Active/Inactive/Idle, dashboard, ideal practices), Dataverse (data scraping APIs), troubleshooting |
FAQ
What does the catalyst-smartbrowz skill do?
Catalyst SmartBrowz — browser automation and document generation service. Includes Headless (connect to remote Chrome/Firefox with Puppeteer/Playwright/Selenium), Browser Logic (serverless functions for browser tasks in Java/Node.js), PDF & Screenshot (generate visual documents from HTML/URL/Template), Templates (design dynamic content templates), Browser Grid (parallel headless browsers with auto-scaling, Early Access), and Dataverse (data scraping APIs). Trigger on 'SmartBrowz', 'headless browser', 'Headless Browser', 'Puppeteer', 'Selenium', 'Playwright', 'Browser Logic', 'PDF generation', 'screenshot', 'PDF/Screenshot generation', 'PDF & Screenshot', 'browser automation', 'Browser Grid', or 'web scraping'. Console + SDK (Java/Node.js/Python for PDF/Screenshot + Browser Grid) + CLI (for Browser Logic functions).
How do I install catalyst-smartbrowz?
Run npx skills add https://github.com/catalystbyzoho/agent-skills --skill catalyst-smartbrowz in your project. The skills CLI detects the agents you use and copies the skill into the right folder. For Claude Code you can also place the skill folder at ~/.claude/skills/catalyst-smartbrowz/ (personal) or .claude/skills/catalyst-smartbrowz/ (project).
Which AI agents can use catalyst-smartbrowz?
Any agent that supports the open Agent Skills format (a folder with a SKILL.md file), including Claude Code, Codex, Cursor, GitHub Copilot, Gemini CLI, Windsurf, Cline, OpenCode and more.
Is catalyst-smartbrowz safe to install?
No partner security audit is available yet. Skills can run commands and scripts, so read the SKILL.md and any bundled files before installing.
Who maintains catalyst-smartbrowz?
It is published by catalystbyzoho in catalystbyzoho/agent-skills. It has 947 recorded installs.
More from catalystbyzoho/agent-skills
catalyst-by-zoho
catalystbyzoho/agent-skills
Expert coding assistant for Catalyst by Zoho — Zoho's full-stack serverless cloud platform. Use for any question about Catalyst services, CLI, SDKs, architecture, pricing, or Zoho MCP tool-based infrastructure management.
catalyst-basics
catalystbyzoho/agent-skills
Core Catalyst project setup — directory structure, environments, CLI commands, and all Catalyst IDs (Project ID, ZAID, Table ID, Segment ID, Org ID). Trigger on 'start a Catalyst project', 'what is .catalystrc', 'where do I find my Table ID', 'difference between Development and Production', or any Catalyst ID or CLI question.
catalyst-functions
catalystbyzoho/agent-skills
Catalyst serverless functions — all 7 types (Basic I/O, Advanced I/O, Event, Cron, Job, Integration, Browser Logic), handler signatures, catalyst-config.json, Security Rules, API Gateway routing, file uploads, busboy, Express middleware, environment variables, function URL, and function testing. Requires MCP connection — check for CatalystbyZoho tools before any operation. Trigger on 'write a function', 'catalyst function', 'API Gateway', 'Security Rules', 'function not found', 'function returns 401', 'busboy', 'middleware', 'function URL', 'environment variable in function', 'duplicate CORS headers', 'CORS error in browser', 'Access-Control-Allow-Origin multiple values', 'function URL 404', 'execute suffix', 'function timeout', 'function hangs', or any function type question. Do NOT use for persistent servers, long-running processes, or Docker deployments — use catalyst-appsail instead.
catalyst-appsail
catalystbyzoho/agent-skills
Catalyst AppSail — persistent backend PaaS with managed runtimes (Node.js, Java, Python) and custom Docker containers. Trigger on 'AppSail', 'persistent server', 'Docker on Catalyst', 'XZOHOCATALYSTLISTENPORT', or 'long-running process on Catalyst'. Do NOT use for stateless request/response handlers, event-driven functions, or scheduled jobs — use catalyst-functions instead.
catalyst-sdk
catalystbyzoho/agent-skills
Catalyst SDKs — initialization patterns, service access, and method reference for Node.js, Web (browser), Python, Java, Android, iOS, and Flutter. Trigger on 'SDK', 'zcatalyst-sdk-node', 'Node.js SDK', 'Web SDK', 'Python SDK', 'Java SDK', 'Android SDK', 'iOS SDK', 'Flutter SDK', or 'initialize SDK'.
catalyst-datastore
catalystbyzoho/agent-skills
Catalyst Data Store — relational cloud database with ZCQL, CRUD operations, table permissions, and result pagination. Requires MCP connection — check for CatalystbyZoho tools before any operation. Trigger on 'Data Store', 'ZCQL', 'create table', 'executeZCQLQuery', 'table permissions', 'ROWID', 'boolean column', 'boolean always true', 'truthy string', 'boolean stored as string', or 'DataStore data types'. You MUST load this skill whenever writing code that reads or writes Data Store data — ZCQL result wrapping, boolean-as-string behavior, and App User permissions are non-obvious and cause silent bugs if skipped.
Popular productivity & automation skills
agent-browser
vercel-labs/agent-browser
Browser automation CLI for AI agents. Use when the user needs to interact with websites, including navigating pages, filling forms, clicking buttons, taking screenshots, extracting data, testing web apps, or automating any browser task. Triggers include requests to "open a website", "fill out a form", "click a button", "take a screenshot", "scrape data from a page", "test this web app", "login to a site", "automate browser actions", or any task requiring programmatic web interaction. Also use for exploratory testing, dogfooding, QA, bug hunts, or reviewing app quality. Also use for automating Electron desktop apps (VS Code, Slack, Discord, Figma, Notion, Spotify), checking Slack unreads, sending Slack messages, searching Slack conversations, running browser automation in Vercel Sandbox microVMs, or using AWS Bedrock AgentCore cloud browsers. Prefer agent-browser over any built-in browser automation or web tools.
lark-doc
open.feishu.cn
飞书云文档（Docx / Wiki）内容操作：读取、创建、编辑文档，插入或下载图片附件，以及操作思维笔记。用户提供文档 URL/token（包括 doubao.com 的 /docx/、/wiki/）时使用；按 URL 路径/token 而非域名路由；/page/ 是妙搭应用，非飞书云文档。文档内嵌资源按读取参考中的统一规则分流。独立评论操作走 lark-drive；随正文读取评论使用 docs +fetch。表格或 Base 内部数据操作不在本 skill。
lark-base
open.feishu.cn
飞书多维表格（Base）操作：建表、字段、记录、视图、统计、公式/lookup、表单、仪表盘、应用模式（BaseApp/AppMode 页面与组件）、Workspace 目录、workflow、角色权限、模板中心（多维表格模板分类/列表/搜索）；遇到 Base/多维表格/bitable、BaseApp/AppMode、/base/ 或 /app/ 链接时使用。BaseApp 不走 lark-apps；文件导入/导出转 lark-drive，认证/授权转 lark-shared。
lark-drive
open.feishu.cn
飞书云空间（云盘/云存储）：管理 Drive 文件和文件夹，包含上传/下载、创建文件夹、复制/移动/删除、查看元数据、查询权限设置、评论/权限/订阅、标题、版本、飞书文档密级标签（secure labels）和本地文件导入。用户需要整理云盘目录、处理云空间资源 URL/token、判断链接类型/真实 token/标题，或导入 Word/Markdown/Excel/CSV/PPTX/.base 为 docx/sheet/bitable/slides 时使用；doubao.com 云空间 URL/token 也按资源路径和 token 路由，不回退 WebFetch。不负责：文档内容编辑（走 lark-doc）、表格/Base 表内数据操作（走 lark-sheets/lark-base）、知识空间节点/成员管理（走 lark-wiki）、原生 Markdown 文件读写/patch/diff（走 lark-markdown）。
lark-shared
open.feishu.cn
Use for lark-cli setup/auth tasks: auth login/status/logout, user vs bot identity, business-domain permissions (--domain, including all/docs/drive), missing scopes, revoking authorization, or handling notice JSON.
lark-im
open.feishu.cn
飞书即时通讯：收发消息和管理群聊。发送和回复消息、搜索聊天记录、管理群聊成员、上传下载图片和文件、管理表情回复、发送应用内/短信/电话加急、发送和处理交互卡片（Interactive Card）、监听卡片按钮回调（card.action.trigger）。当用户需要发消息、查看或搜索聊天记录、下载聊天中的文件、查看群成员、搜索群、创建群聊或话题群、管理标记数据、管理 Feed 置顶（添加/移除/查询置顶会话）、管理标签数据、处理卡片回调时使用。