resource-browser

Name: resource-browser
Availability: InStock
Author: Seer

Document resource picker debugging across Google Drive, GitHub, Discord, and Supabase providers.

5|1|Updated Oct 14, 2025

Search Tags:#architecture #debugging #frontend-backend #provider-integration #resource-browser #resource-picker

Ready to run

npx skills add https://github.com/seer-engg/seer --skill resource-browser

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: resource-browser
Source: https://github.com/seer-engg/seer/tree/main/.claude/skills/resource-browser
Command: npx skills add https://github.com/seer-engg/seer --skill resource-browser

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

The Resource Browser helps teams understand how Seer browses resources across providers, enabling debugging, extension, and reliable integration of external services.

Core Features & Use Cases

Centralizes resource discovery across Google Drive, GitHub, Discord, and Supabase providers.
Supports hierarchical navigation, search, and pagination.
Facilitates hybrid sources by combining database-backed listings with API calls.
Use Case: A developer visualizes all available channels in a Discord workspace and then fetches related resources from a connected Google Drive account.

Quick Start

Study the Resource Browser architecture and provider interfaces in the codebase to understand how resources are discovered and listed.

Frequently Asked Questions about resource-browser

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

FAQPage Schema

How do I browse resources across Google Drive, GitHub, Discord, and Supabase from a single interface?▼

To browse resources across Google Drive, GitHub, Discord, and Supabase, study the resource browser architecture and provider interfaces in your codebase to understand how resources are discovered, listed, and orchestrated across providers.

Can I combine database-backed listings with API calls for hybrid resource sources?▼

Yes, the resource browser supports multi-auth contexts to handle concurrent provider integrations. It manages authentication across different external services, allowing simultaneous browsing of resources from authenticated Google Drive, GitHub, Discord, and Supabase accounts.

How do I debug provider integration issues during cross-provider resource discovery?▼

Yes, you can combine database-backed listings with API calls to create hybrid resource sources. This approach merges locally stored resource metadata with live provider API responses, optimizing data retrieval and cross-provider orchestration.

What is a unified resource browser and when do I need cross-provider resource discovery?▼

Debug provider integration by examining the resource browser architecture and provider interfaces in the codebase. Trace resource discovery and cross-provider orchestration logic to identify failures in external service fetching, hierarchical navigation, or pagination.

Does the resource browser support lazy loading for hierarchical navigation and search?▼

Yes, the resource browser supports lazy loading to optimize hierarchical navigation and search. It defers fetching resource listings until needed, reducing initial load overhead when browsing large datasets across connected providers.