spider-king

Reverse hostile web clients into Python protocol collectors.

425|84|Updated Apr 15, 2026
One-click install
npx skills add https://github.com/aoyunyang/spider-king-skill --skill spider-king
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: spider-king
Source: https://github.com/aoyunyang/spider-king-skill/tree/main/spider-king
Command: npx skills add https://github.com/aoyunyang/spider-king-skill --skill spider-king

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) and references (resource) components.

What problem does it solve?

It enables turning hostile web clients that rely on browser state into pure-protocol data collectors that run offline in Python, delivering reproducible, testable results and long-term maintainability.

Core Features & Use Cases

  • Startup Gate and lightweight dual-tool analysis (chrome-devtools and js-reverse) to gather evidence before building the final collector.
  • Identify the real wire path and the true moving state (sign, token, cookie, wrapper, bootstrap, fonts, or encryption) for offline reconstruction.
  • Python-first delivery that produces a browser-free collector, with optional tiny JS/WASM helpers only when porting to Python is not cheaper or safer.

Quick Start

Provide a target URL or data sample to begin building a protocol-first collector.

Frequently Asked Questions about spider-king

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

FAQPage Schema
How do I reverse engineer a web client that depends on browser context into a pure Python collector?

You reverse engineer hostile web clients into pure-protocol collectors by identifying the true wire path and moving state, then reconstructing the protocol offline in Python using initial evidence gathered from chrome-devtools and js-reverse.

What is the best way to extract data from sign and cookie gates without running a full browser?

The best way to bypass sign and cookie gates without a full browser is to build a browser-free Python collector that reconstructs offline state, using minimal local JS or WASM helpers only when Python porting is not cheaper or safer.

Can I reconstruct offline state for GraphQL and WebSocket transports using Python?

Yes, you can reconstruct offline state for GraphQL and WebSocket transports using a Python-first collector that identifies the true moving state and dynamic decoding steps, delivering reproducible browser-free results.

Does this protocol recovery approach require porting all JavaScript encryption to Python?

No, protocol recovery emphasizes Python-first delivery but retains minimal local JS or WASM helpers for encryption or bootstrap challenges only when porting to Python is not yet safer or cheaper for offline replay.

When do I need to use a local JS or WASM helper for offline replay instead of pure Python?

You need a local JS or WASM helper for offline replay when porting dynamic decoding steps or bootstrap challenges to Python is not yet safer, cheaper, or more maintainable than executing a minimal local helper.