browse

Automates browser sessions with Nu wrapper commands for navigation, scripting, and extraction.

Updated Aug 27, 2026
One-click install
npx skills add https://github.com/raystyle/skills --skill browse-raystyle
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: browse
Source: https://github.com/raystyle/skills/tree/main/skills/browse
Command: npx skills add https://github.com/raystyle/skills --skill browse-raystyle

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

streamlines browser automation by providing a high-level Nu wrapper that standardizes common browser interactions across skills and tasks, reducing boilerplate and ensuring consistent session handling.

Core Features & Use Cases

  • Persistent sessions: manage a browser session across multiple steps without reinitialization.
  • High-level commands: wrapper commands like browser-open, browser-goto, browser-eval, browser-close for deterministic flows.
  • SDK integration: built-in checks and guards for SDK readiness and compatibility.

Quick Start

Open a browser session, navigate to a page, execute scripts, and extract results with a single repeatable workflow.

Frequently Asked Questions about browse

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I automate browser interactions and maintain a persistent session across multiple steps?

Browser automation with Nu requires a Nu environment with MCP support and a persistent session mechanism. You also need the browse-sdk to perform built-in SDK checks, guards, and JavaScript calls.

What is the best way to execute JavaScript and extract results during a web automation workflow?

To start browser automation, use high-level wrapper commands: browser-open to open a session, browser-goto to navigate to a page, browser-eval to execute scripts, and browser-close to extract results with a single repeatable workflow.

Do I need a specific environment to use Nu for browser automation?

Yes, Nu browser automation requires a Nu environment with MCP support, a persistent session mechanism, and the browse-sdk. These dependencies perform the necessary SDK checks, guards, and JavaScript calls.

Can I standardize browser session handling across different tasks to reduce boilerplate?

Yes, a high-level Nu wrapper standardizes common browser interactions across skills and tasks. It reduces boilerplate and ensures consistent session handling for deterministic web automation flows.