omnibox-spider

Write, debug, and maintain OmniBox spider sources in JavaScript or Python.

60|46|Updated Mar 22, 2026
One-click install
npx skills add https://github.com/Silent1566/OmniBox-Spider-Skills --skill omnibox-spider
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: omnibox-spider
Source: https://github.com/Silent1566/OmniBox-Spider-Skills/tree/main
Command: npx skills add https://github.com/Silent1566/OmniBox-Spider-Skills --skill omnibox-spider

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

OmniBox spider development is complex; this skill provides a structured framework to help developers write, debug, and maintain OmniBox spider sources in JavaScript or Python, enabling safer, repeatable, and scalable spider creation and maintenance.

Core Features & Use Cases

  • Unified 5-method handler pattern (home, category, detail, search, play) with context-aware execution
  • SDK-injected utilities for requests, logging, environment variables, and drive/pan-scraping capabilities
  • Guidance for building new sources, debugging existing ones, and answering questions about APIs, environments, and return formats
  • Safe, logs-first operation with error handling and fallback defaults

Quick Start

Create a minimal spider by exporting five handlers (home, category, detail, search, and play) and running the spider runner to execute requests.

Frequently Asked Questions about omnibox-spider

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

FAQPage Schema
How do I write a spider script with a standard handler pattern?

To write a spider script, you export five standard handlers: home, category, detail, search, and play. This unified model ensures context-aware execution, deterministic behavior, and safe logging for your scraping tasks.

Can I use Python and JavaScript for spider source development?

Yes, you can use either Python or JavaScript for spider source development. The framework supports both languages, allowing you to create new sources, fix bugs, and integrate with third-party APIs seamlessly.

How do I debug an existing spider that fails during execution?

To debug an existing spider, rely on the logs-first operation model and SDK-injected utilities. This approach provides safe error handling, fallback defaults, and explicit environment variable conventions to identify and resolve failures.

What's the best way to structure a new spider source?

The best way to structure a new spider source is implementing the five-method handler pattern. This enforces safety, logging, and deterministic execution while providing SDK-injected utilities for requests and environment variables.

Why does my spider return a fallback default instead of scraped data?

Your spider returns a fallback default because the framework enforces safe operation with structured error handling. When requests fail or return unexpected formats, the deterministic execution model triggers fallback defaults.

Do I need SDK integration for pan-scraping capabilities?

Yes, you need SDK integration for pan-scraping capabilities. The SDK injects necessary utilities for requests, logging, and drive operations, ensuring your spider sources maintain safe and repeatable scraping behavior.