Agent skill

Ssl Proxy Troubleshoot

by HKUDS in HKUDS/OpenSpace

Systematic workflow for troubleshooting SSL/proxy connectivity issues with government websites

MITAuto-check passed

Install Ssl Proxy Troubleshoot

skills CLI
$ npx skills add HKUDS/OpenSpace --skill ssl-proxy-troubleshoot -a claude-code

Project install by default; add -g for ~/.claude/skills/.

GitHub CLI
$ gh skill install HKUDS/OpenSpace ssl-proxy-troubleshoot --agent claude-code

Project scope by default; add --scope user for a personal install. Needs GitHub CLI 2.90.0 or later (public preview).

Manual copy
$ git clone --depth 1 https://github.com/HKUDS/OpenSpace.git skills-src && mkdir -p .claude/skills && cp -r skills-src/benchmarks/gdpval/skills/ssl-proxy-troubleshoot .claude/skills/ssl-proxy-troubleshoot && rm -rf skills-src

Use ~/.claude/skills/ instead of .claude/skills for a personal install. The folder must contain SKILL.md.

Claude Code skills documentation · loads skills from .claude/skills/

Facts

Skill name
ssl-proxy-troubleshoot
GitHub stars
7.8k
Token cost
~1.9k tokens
SKILL.md length
405 words
Files
2
Skills in repo
199
Repo updated
First seen
Licence
MIT

At a glance

Systematic workflow for troubleshooting SSL/proxy connectivity issues with government websites

  • Works in 6 steps: Diagnose the Connection Issue → Try Protocol Variations → Disable SSL Verification (Temporary Debug) → …
  • SKILL.md covers When to Use This Skill, Systematic Troubleshooting…, Fallback Strategies When… and Decision Matrix, plus 2 more sections
  • Reaches web.archive.org and webcache.googleusercontent.com

What it does

Ssl Proxy Troubleshoot is an agent skill from HKUDS/OpenSpace. Systematic workflow for troubleshooting SSL/proxy connectivity issues with government websites

Its SKILL.md is about 1.9k tokens, which your agent loads only when the skill is triggered. The skill folder holds 1 other file.

The repository describes itself as: "OpenSpace: The Skill Management Layer for AI Agents" -- https://open-space.cloud/. The licence is MIT.

Example prompts

  • “/ssl-proxy-troubleshoot”

Requirements

  • Python 3

Workflow steps

6 steps, taken from the step headings in SKILL.md.

  1. Diagnose the Connection Issue
  2. Try Protocol Variations
  3. Disable SSL Verification (Temporary Debug)
  4. Manipulate Proxy Settings
  5. Test Alternative Domains and Endpoints
  6. Use Different HTTP Clients

What it can do on your machine

Read from SKILL.md and the folder at commit 3827781. It shows what the files ask for, not the result of running them.

  • Tool permissions

    Pre-approves nothing: there is no allowed-tools line, so your agent's usual permission prompts apply.

    From allowed-tools in the SKILL.md frontmatter.

  • Runs code

    No scripts in the folder and no shell commands in SKILL.md (its code samples are python).

    From the folder's file list and the shell code blocks in SKILL.md.

  • Network

    Hosts in commands or code, which the agent is likely to contact:

    • web.archive.org
    • webcache.googleusercontent.com

    From URLs in SKILL.md, links to its own repository left out.

  • Credentials

    Names no API keys, tokens, secrets or passwords.

    From names ending in _API_KEY, _TOKEN, _SECRET, _KEY or _PASSWORD in SKILL.md.

Context cost

Ssl Proxy Troubleshoot loads about 1.9k tokens when it runs. Until then it costs about 29 tokens; SKILL.md has 405 words of instructions outside code blocks.

Always · name and description, kept in context so the agent knows when to use it
~29
When it runs · the whole SKILL.md, loaded when a task matches
~1.9k

Estimates: characters ÷ 4, the usual rule of thumb; real counts depend on the model's tokenizer. Scripts and assets cost tokens only if the agent reads them.

Safety

Auto-check passed

The automated check found no risky patterns in SKILL.md.

Automated static check — not a guarantee. Review scripts before installing. It scans the text of SKILL.md for risky patterns (piping downloads into a shell, reading credential files, hidden Unicode, destructive commands); files beside SKILL.md are not scanned.

SKILL.md

The full file from HKUDS/OpenSpace at commit 3827781, republished under its MIT licence (© HKUDS). 405 words, ~1,896 tokens.

Download SKILL.mdSave it as .claude/skills/ssl-proxy-troubleshoot/SKILL.md (or your agent's skills folder). This skill also uses 1 other file; get the full folder from GitHub.
name
ssl-proxy-troubleshoot
description
Systematic workflow for troubleshooting SSL/proxy connectivity issues with government websites

SSL/Proxy Troubleshooting for Government Websites

This skill provides a systematic approach to diagnosing and resolving SSL certificate and proxy connectivity issues when accessing government websites, which often have stricter security configurations than commercial sites.

When to Use This Skill

  • Cannot access a government or institutional website
  • SSL certificate validation errors occur
  • Proxy configuration blocks or interferes with requests
  • Primary data sources are intermittently or persistently inaccessible

Systematic Troubleshooting Workflow

Step 1: Diagnose the Connection Issue

First, identify what type of connectivity problem you're facing:

python
import requests
import ssl

url = "https://example.gov/data"

# Test basic connectivity
try:
    response = requests.get(url, timeout=10)
    print(f"Status: {response.status_code}")
except requests.exceptions.SSLError as e:
    print(f"SSL Error: {e}")
except requests.exceptions.ProxyError as e:
    print(f"Proxy Error: {e}")
except requests.exceptions.ConnectionError as e:
    print(f"Connection Error: {e}")
except Exception as e:
    print(f"Other Error: {e}")
Step 2: Try Protocol Variations

Government sites sometimes have misconfigured redirects or support only specific protocols:

python
urls_to_try = [
    "https://example.gov/data",
    "http://example.gov/data",  # Try unencrypted
    "https://www.example.gov/data",  # Try www subdomain
    "http://www.example.gov/data",
]

for url in urls_to_try:
    try:
        response = requests.get(url, timeout=10, verify=False)
        if response.status_code == 200:
            print(f"Success with: {url}")
            break
    except Exception as e:
        print(f"Failed {url}: {e}")
Step 3: Disable SSL Verification (Temporary Debug)

Only use this for debugging. If it works, the issue is SSL certificate-related:

python
# Option A: Disable verification entirely (debug only)
response = requests.get(url, verify=False, timeout=30)

# Option B: Use custom SSL context with relaxed settings
import ssl
ssl_context = ssl.create_default_context()
ssl_context.check_hostname = False
ssl_context.verify_mode = ssl.CERT_NONE

response = requests.get(url, verify=False, timeout=30)

Warning: Never use verify=False in production. If this is the only working option, document the SSL issue and seek alternative data sources.

Step 4: Manipulate Proxy Settings

Government networks often require specific proxy configurations:

python
# Option A: Disable proxy entirely
session = requests.Session()
session.trust_env = False  # Ignore environment proxy settings
response = session.get(url, timeout=30)

# Option B: Explicitly set proxy
proxies = {
    "http": "http://proxy.example.com:8080",
    "https": "http://proxy.example.com:8080",
}
response = requests.get(url, proxies=proxies, timeout=30, verify=False)

# Option C: Try without any proxy configuration
import os
os.environ.pop("HTTP_PROXY", None)
os.environ.pop("HTTPS_PROXY", None)
os.environ.pop("http_proxy", None)
os.environ.pop("https_proxy", None)
response = requests.get(url, timeout=30)
Step 5: Test Alternative Domains and Endpoints

Government data is often mirrored or available through alternative access points:

python
# Common alternative patterns for government sites
alternative_urls = [
    url.replace(".gov", ".gov.uk"),  # Regional variations
    url.replace("data.", "api."),  # API subdomain
    url.replace("https://", "https://archive."),  # Archive mirror
    url.replace("/data", "/download"),  # Alternative path
]

# Check for data.gov or similar portals
portal_search = f"site:data.gov {topic_keyword}"
Step 6: Use Different HTTP Clients

Some clients handle SSL/proxy differently:

python
# Try urllib instead of requests
import urllib.request
import ssl

ssl_context = ssl._create_unverified_context()
response = urllib.request.urlopen(url, context=ssl_context, timeout=30)

# Try curl via subprocess
import subprocess
result = subprocess.run(
    ["curl", "-k", "-L", "--max-time", "30", url],
    capture_output=True,
    text=True
)

Fallback Strategies When Primary Sources Fail

When all troubleshooting attempts fail after 5-10 iterations:

Strategy 1: Search for Alternative Data Sources
python
# Search for the same data from different sources
search_queries = [
    f"{dataset_name} site:epa.gov",
    f"{dataset_name} site:data.gov",
    f"{dataset_name} state database",
    f"{dataset_name} public download",
]
Strategy 2: Check for Archived Versions
python
# Try Wayback Machine
wayback_url = f"https://web.archive.org/web/*/{original_url}"

# Check for cached versions
# Try Google Cache: http://webcache.googleusercontent.com/search?q=cache:{url}
Strategy 3: Look for API Alternatives

Many government datasets have REST APIs even when web interfaces fail:

python
# Common API patterns
api_endpoints = [
    url.replace("/portal", "/api"),
    url + "/api/v1/data",
    url + "/rest/data",
]
Show full SKILL.md (178 more words)Show less
Strategy 4: Contact or Document

If data is critical and unavailable:

  1. Document all attempted URLs and error messages
  2. Note the timeframe of access attempts
  3. Search for contact information to report the issue
  4. Consider if the task can proceed with partial or alternative data

Decision Matrix

Issue TypeSymptomRecommended Action
SSL CertificateSSLError, CERT_VERIFY_FAILEDTry verify=False for debug, then find alternative source
Proxy BlockingProxyError, Connection refusedSet trust_env=False, try direct connection
TimeoutReadTimeout, ConnectTimeoutIncrease timeout, try different client
403/401 ErrorsHTTP status errorsCheck for required headers, authentication
DNS FailureName resolution errorTry IP address directly, check alternative domains

Best Practices

  1. Limit iterations: After 5-10 failed attempts with different approaches, pivot to fallback strategies
  2. Log everything: Record which URLs, settings, and methods were tried
  3. Respect rate limits: Government sites may throttle automated access
  4. Check robots.txt: Verify automated access is permitted
  5. Prefer official APIs: More stable than web scraping
  6. Document SSL issues: If verify=False is required, flag this as a security concern

Example: Complete Troubleshooting Function

python
def robust_government_request(url, max_attempts=5):
    """Attempt to fetch government URL with multiple fallback strategies."""
    
    strategies = [
        {"verify": True, "trust_env": True, "timeout": 30},
        {"verify": False, "trust_env": True, "timeout": 30},
        {"verify": False, "trust_env": False, "timeout": 30},
        {"verify": False, "trust_env": False, "timeout": 60},
    ]
    
    for i, config in enumerate(strategies[:max_attempts]):
        try:
            session = requests.Session()
            session.trust_env = config["trust_env"]
            response = session.get(
                url,
                verify=config["verify"],
                timeout=config["timeout"]
            )
            if response.status_code == 200:
                return response
        except Exception as e:
            print(f"Attempt {i+1} failed: {e}")
            continue
    
    return None  # All strategies failed

© HKUDS, MIT. Rendered from Markdown: HTML in the file is shown as text, images as links, and headings moved down two levels. Raw file

Files

SKILL.md and 1 other file in benchmarks/gdpval/skills/ssl-proxy-troubleshoot of HKUDS/OpenSpace.

  • SKILL.md
  • .skill_id

Open the folder on GitHubat commit 3827781

Compare with similar skills

Ssl Proxy Troubleshoot next to the 5 skills that share the most tags, products or categories with it. Stars are the repository's; “used in” counts other GitHub owners with a copy.

Ssl Proxy Troubleshoot compared with similar skills
SkillStarsUsed inTokensAuto-checkLicenceRepo updated
Ssl Proxy Troubleshoot this skillHKUDS/OpenSpace7.8k—~1.9kAutomated safety check: PassMIT
ConnectComposioHQ/awesome-claude-skills77k3 repos~987Automated safety check: PassNone
Node Connectopenclaw/openclaw392k—~1.6kAutomated safety check: PassMIT
Iron Proxy Gateway Rulesnanocoai/nanoclaw31k—~598Automated safety check: PassMIT
Openwork Connectdifferent-ai/openwork24k—~370Automated safety check: PassCustom licence
Startup It Troubleshootingsickn33/agentic-awesome-skills47k2 repos~3.6kAutomated safety check: NotesMIT

Similar skills

  • Connect

    ComposioHQ/awesome-claude-skills

    Connect Claude to any app. An agent skill from ComposioHQ/awesome-claude-skills.

    77k GitHub starsUsed in 3 repos~987 tokens
    Productivity & AutomationAuto-check passed
  • Node Connect

    openclaw/openclaw

    Diagnose OpenClaw Control UI browser and native Android, iOS, or macOS node connection failures across route, auth, pairing, QR/setup-code, and reconnect states.

    392k GitHub stars~1.6k tokensUpdated today
    MobileAuto-check passed
  • Iron Proxy Gateway Rules

    nanocoai/nanoclaw

    Rules for working behind Iron Proxy: connect external accounts without handling raw tokens, treat blocked requests as policy outcomes, and never claim a connection before it works.

    31k GitHub stars~598 tokensUpdated 3 days ago
    Agent WorkflowsAuto-check passed
  • Openwork Connect

    different-ai/openwork

    Search and use the skills, MCP connections, and connected services available through the user's OpenWork organization.

    24k GitHub stars~370 tokensUpdated today
    Agent WorkflowsAuto-check passed
  • Startup It Troubleshooting

    sickn33/agentic-awesome-skills

    Practical IT troubleshooting playbooks for small teams without dedicated IT staff.

    47k GitHub starsUsed in 2 repos~3.6k tokens
    Auto-check: notes
  • Connection Auth Rules

    sickn33/agentic-awesome-skills

    Build a Connection Auth Rules for a Monte Carlo connection type.

    47k GitHub starsUsed in 1 repo~2.1k tokens
    Backend & APIsAuto-check passed

More from HKUDS/OpenSpace

All 199 skills in this repo
  • Walks through producing a master audio track plus stems in Python, from checking a reference file and timing sections by BPM to effects, a zip archive and final verification.

    7.8k GitHub stars~2.9k tokensUpdated 1 mo ago
    Auto-check passed
  • Handle cascading data retrieval tool failures by falling back to embedded knowledge generation

    7.8k GitHub stars~765 tokensUpdated 1 mo ago
    Auto-check passed
  • Gives an agent a workaround when its code-execution sandbox keeps failing: save the Python script to a file and run it through the shell instead.

    7.8k GitHub stars~588 tokensUpdated 1 mo ago
    Auto-check passed
  • A recovery routine for agents whose sandboxed code runner keeps failing: save the Python script to disk, then run it through the shell and read the output.

    7.8k GitHub stars~652 tokensUpdated 1 mo ago
    Auto-check passed
  • Fallback ladder for failed sandboxed code runs, plus the habit of fixing the working directory first so generated files land in the right place.

    7.8k GitHub stars~1.1k tokensUpdated 1 mo ago
    Auto-check passed
  • Fallback workflow for executing Python code when executecodesandbox fails repeatedly

    7.8k GitHub stars~1.1k tokensUpdated 1 mo ago
    Auto-check passed

Questions about Ssl Proxy Troubleshoot

What does Ssl Proxy Troubleshoot do?

Systematic workflow for troubleshooting SSL/proxy connectivity issues with government websites. Ssl Proxy Troubleshoot is an agent skill from HKUDS/OpenSpace.

How do I install Ssl Proxy Troubleshoot in Claude Code?

Run `npx skills add HKUDS/OpenSpace --skill ssl-proxy-troubleshoot -a claude-code`. Or copy the skill folder (benchmarks/gdpval/skills/ssl-proxy-troubleshoot in HKUDS/OpenSpace) into .claude/skills/ssl-proxy-troubleshoot in your project. Claude Code loads it when a task matches its description.

How do I install Ssl Proxy Troubleshoot in Codex?

Run `npx skills add HKUDS/OpenSpace --skill ssl-proxy-troubleshoot -a codex`. Or copy the skill folder (benchmarks/gdpval/skills/ssl-proxy-troubleshoot in HKUDS/OpenSpace) into .agents/skills/ssl-proxy-troubleshoot in your project. Codex loads it when a task matches its description.

Can I use Ssl Proxy Troubleshoot in Cursor, Gemini CLI or GitHub Copilot?

Cursor, Gemini CLI, GitHub Copilot and OpenCode also load SKILL.md folders. With the skills CLI, run `npx skills add HKUDS/OpenSpace --skill ssl-proxy-troubleshoot -a cursor` (or -a gemini-cli, github-copilot or opencode for the others). To copy it by hand, put the folder in .cursor/skills/ssl-proxy-troubleshoot, .gemini/skills/ssl-proxy-troubleshoot, .github/skills/ssl-proxy-troubleshoot and .opencode/skills/ssl-proxy-troubleshoot in your project.

What does Ssl Proxy Troubleshoot need to run?

SKILL.md names no scripts, command-line tools or credentials: Ssl Proxy Troubleshoot is instructions for the agent only. Our summary lists: Python 3.

Does Ssl Proxy Troubleshoot access the network?

SKILL.md names 2 domains. In commands or code: web.archive.org and webcache.googleusercontent.com; the agent is likely to contact these when it follows the instructions. This is read from the text; nothing was executed.

Is Ssl Proxy Troubleshoot safe to install?

Our automated static check of SKILL.md found no risky patterns, such as piping downloads into a shell, reading credential files or hidden Unicode. It is not a guarantee. Review the folder before installing.

What licence does Ssl Proxy Troubleshoot use?

Ssl Proxy Troubleshoot is published under the MIT licence (the repository's licence). It allows redistribution, so the full SKILL.md is shown on this page.

How many tokens does Ssl Proxy Troubleshoot use?

About 1.9k tokens (SKILL.md is roughly 7.6k characters). Agents keep only the skill's name and description in context until a task matches; then they load SKILL.md in full.

What are the alternatives to Ssl Proxy Troubleshoot?

Skills that share tags, products or a category with Ssl Proxy Troubleshoot: Connect (ComposioHQ/awesome-claude-skills, 77k stars), Node Connect (openclaw/openclaw, 392k stars), Iron Proxy Gateway Rules (nanocoai/nanoclaw, 31k stars) and Openwork Connect (different-ai/openwork, 24k stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.

Who maintains Ssl Proxy Troubleshoot?

HKUDS (a GitHub organization) maintains it in HKUDS/OpenSpace, which has 7,750 GitHub stars. The repository holds 199 skills in this directory. The repository was last updated on August 12, 2026.

Source: HKUDS/OpenSpace on GitHub. Facts on this page come from the repository at the commit we read; the author's words are quoted as theirs.