agentsclimarketplace

Browser based tor bridge connectivity checker pure js

Skill ECNU-ICALK/AutoSkill/SkillBank/ConvSkill/english_gpt4_8_GLM4.7/browser-based-tor-bridge-connectivity-checker-pure-js

Create a pure JavaScript tool (no Node.js) to validate Tor bridge IPs from a textarea. The tool extracts IPs from bridge strings, tests connectivity using a timeout-based method, and removes non-responsive bridge lines. It must use string concatenation instead of template literals.From its SKILL.md

Install
npx -y skills add ECNU-ICALK/AutoSkill --skill browser-based-tor-bridge-connectivity-checker-pure-js

Assembled from the repository path, not quoted from the project. Check it against their README if it does not work.

One thing to look at

  • no licenseNo license file was found in the repository. Code published without one is not open source by default, so using it at work is a question for whoever answers licensing questions where you are.

SKILL.md

2.9 KB, 496 tokens by cl100k_base, as published. Nobody here has run it

Browser-based Tor Bridge Connectivity Checker (Pure JS)

Create a pure JavaScript tool (no Node.js) to validate Tor bridge IPs from a textarea. The tool extracts IPs from bridge strings, tests connectivity using a timeout-based method, and removes non-responsive bridge lines. It must use string concatenation instead of template literals.

Prompt

Role & Objective

Act as a front-end developer specializing in pure JavaScript solutions without Node.js. Create a browser-based tool to validate Tor bridge IP addresses.

Communication & Style Preferences

Use strict string concatenation (+ and ') instead of template literals (backticks). Keep the code self-contained in a single HTML file if possible.

Operational Rules & Constraints

  1. Environment: Pure JavaScript running in a browser (Tor Browser, Firefox, Chromium). No Node.js, no specialized plugins, no backend server.
  2. UI Components:
    • An interactive textarea to accept a list of Tor bridge strings.
    • A "Check Reliability" button.
    • Adjustable input fields for "Overall Timeout" (e.g., 2-30 seconds) and "Number of Threads" (e.g., 5).
  3. Input Parsing: The input contains Tor bridge strings (e.g., obfs4 "IP:PORT <TOKEN> cert=..." or "IP:PORT <TOKEN>"). Extract the IP address from each line using a regular expression.
  4. Connectivity Logic:
    • Attempt to check connectivity for each extracted IP.
    • Use a timeout-based method (e.g., loading an image like /favicon.ico or a fetch request with AbortController).
    • If a "fast refusal" or timeout occurs within the specified limit, consider the bridge non-responsive.
  5. Output Handling: If a bridge IP fails the connectivity check, remove the entire bridge string (line) from the textarea.
  6. Concurrency: Implement a reasonable concurrency limit (e.g., 5 threads) for the checks.

Anti-Patterns

Do not use Node.js specific modules (require, fs, etc.). Do not use template literals (backticks). Do not assume a backend server exists.

Triggers

  • create a pure javascript tool to check tor bridges
  • validate tor bridge ips in browser without node.js
  • javascript code to filter dead tor bridges
  • extract ip from tor bridge string and check connectivity

What ships with it

Read from the repository

Just SKILL.md. No reference files, no scripts.

Keep looking

Skills are one crate of 325,949. Ordering is by how many stacks a row turns up in, so the top of any crate is what has actually been picked rather than what has the most stars.