browser-scroll-recovery

Scroll pages, containers, and virtualized lists to reveal hidden browser elements.

38|6|Updated Aug 14, 2026
One-click install
npx skills add https://github.com/7757/Fan-Browser-Agent --skill browser-scroll-recovery-7757
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: browser-scroll-recovery
Source: https://github.com/7757/Fan-Browser-Agent/tree/main/skills/browser/browser-scroll-recovery
Command: npx skills add https://github.com/7757/Fan-Browser-Agent --skill browser-scroll-recovery-7757

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Elements you need to interact with are often missing from the browser observation because they sit below the fold, inside a scrollable panel or iframe, or in a virtualized list that only renders visible rows. This Skill provides a systematic scroll-and-re-observe workflow to bring those elements into view so they can be acted on. ## Core Features & Use Cases - Page vs. Element Scrolling: Use browser_scroll on the main page by default, or pass a container's index to scroll inside modals, sidebars, inner panels, and iframes. - Text-Based Navigation: Use browser_scroll_to_text to jump directly to known visible text instead of guessing scroll distances, optionally paired with browser_search_page to confirm existence first. - Virtualized and Infinite Lists: Follow a scroll, settle, re-observe loop so lazy-loaded rows render and receive valid indices before clicking, with end-of-list detection to avoid infinite loops. - Use Case: An agent filling a long web form cannot find the submit button in the observation; it scrolls the inner form container by index, re-observes, and clicks the button using its freshly assigned index. ## Quick Start Scroll the page or the relevant container until the target element appears in the observation, then act on it using its latest index.

Frequently Asked Questions about browser-scroll-recovery

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

FAQPage Schema
Why does my element index stop working after scrolling?▼

Scrolling re-renders the page, which invalidates previously observed indices. Only indices from the latest observation are valid, so always act on the target immediately after the observation that revealed it.