browse

Fetch JavaScript-rendered pages and extract content via CSS selectors.

10|Updated Feb 17, 2026
One-click install
npx skills add https://github.com/istota-project/istota --skill browse-istota-project
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: browse
Source: https://github.com/istota-project/istota/tree/main/src/istota/skills/browse
Command: npx skills add https://github.com/istota-project/istota --skill browse-istota-project

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Rendering JavaScript-heavy webpages and bypassing basic bot protections require a capable browser environment; this skill provides a reliable headless browsing interface with session management and content extraction.

Core Features & Use Cases

  • Fetch pages that need JavaScript rendering
  • Extract content with CSS selectors
  • Take screenshots and interact with existing sessions

Quick Start

Fetch a page by running istota-skill browse get 'https://example.com'.

Frequently Asked Questions about browse

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

FAQPage Schema
How do I fetch pages that require JavaScript rendering?

To fetch pages requiring JavaScript rendering, you can use a headless browser session that processes the dynamic content and returns the fully rendered page data in structured JSON format.

Can I extract specific content from a webpage using CSS selectors?

Yes, you can extract specific content using CSS selectors. The headless browsing session supports targeted content extraction, allowing you to isolate and retrieve precise elements from the rendered page.

Does headless browsing support session management for navigating multiple pages?

Headless browsing supports session management, allowing you to maintain state and interact with existing sessions across multiple page navigations, ensuring continuous automated workflows.

What is the best way to take screenshots of dynamic web pages?

The best way to take screenshots of dynamic web pages is by using a headless browser session, which renders the JavaScript-heavy content first and then captures the visual state.

Why does my web scraper fail to get content from JavaScript-heavy sites?

Web scrapers fail on JavaScript-heavy sites because they cannot execute client-side scripts; a headless browser solves this by rendering the page completely before extracting the content.