sing-box-node-discovery

Discover and verify sing-box proxy nodes from generated configurations and subscription sources.

Updated Feb 21, 2026
One-click install
npx skills add https://github.com/Gitnapp/Skills --skill sing-box-node-discovery
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: sing-box-node-discovery
Source: https://github.com/Gitnapp/Skills/tree/main/networking/sing-box-node-discovery
Command: npx skills add https://github.com/Gitnapp/Skills --skill sing-box-node-discovery

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

This Skill solves the challenge of finding, validating, and organizing sing-box proxy nodes by automating discovery and connectivity verification workflows.

Core Features & Use Cases

  • Node Discovery: Extract sing-box configurations from FOFA-discovered generators and sing-box-subscribe instances using the correct generation workflow.
  • Connectivity Verification: Test proxy nodes through sing-box binary and Clash API protocol handshakes instead of unreliable raw TCP checks.
  • Result Collection: Produce structured verification records with node metadata, latency, status, and special requirements for analysis.

Quick Start

Use the sing-box-node-discovery skill to discover proxy nodes from sing-box subscription generators and verify which nodes are reachable.

Frequently Asked Questions about sing-box-node-discovery

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

FAQPage Schema
How do I verify sing-box proxy node connectivity automatically?

To verify sing-box proxy node connectivity automatically, execute the sing-box binary and perform Clash API protocol handshakes. This structured connectivity verification replaces unreliable raw TCP checks with accurate latency and status reporting.

What is the best way to discover sing-box configurations from FOFA?

The best way to discover sing-box configurations from FOFA is to extract them from discovered subscription generators using the correct generation workflow. This process automates configuration parsing and organizes nodes for subsequent connectivity testing.

Does sing-box node testing require a specific API for accurate results?

sing-box node testing requires the Clash API for accurate connectivity verification results. Relying on the Clash API protocol handshakes ensures reliable testing compared to basic raw TCP connectivity checks.

How do I collect structured metadata after testing sing-box subscription nodes?

You collect structured metadata after testing sing-box subscription nodes by generating structured verification records. These records output node metadata, latency, status, and special requirements for further analysis.

Why does raw TCP testing fail for sing-box proxy nodes?

Raw TCP testing fails for sing-box proxy nodes because it does not execute actual protocol handshakes. Accurate verification requires running the sing-box binary and testing through the Clash API instead of simple TCP checks.