Agent skill

Ssl Proxy Troubleshoot Fb786c

by HKUDS in HKUDS/OpenSpace

Systematic approach to diagnosing and resolving SSL/proxy connectivity issues with restricted websites

MITAuto-check passedDevOps & Cloud

Install Ssl Proxy Troubleshoot Fb786c

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

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

GitHub CLI
$ gh skill install HKUDS/OpenSpace ssl-proxy-troubleshoot-fb786c --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-fb786c .claude/skills/ssl-proxy-troubleshoot-fb786c && 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-fb786c
GitHub stars
7.8k
Token cost
~1.6k tokens
SKILL.md length
381 words
Files
2
Skills in repo
199
Repo updated
First seen
Licence
MIT

At a glance

Systematic approach to diagnosing and resolving SSL/proxy connectivity issues with restricted websites

  • Works in 9 steps: Initial Connectivity Assessment → SSL Certificate Investigation → Proxy Configuration Testing → …
  • Tasks that involve Cloud networking
  • SKILL.md covers When to Use, Diagnostic Workflow, Fallback Strategies and Decision Tree, plus 2 more sections
  • Calls curl and openssl; reaches target-domain.gov and target-domain.state.il.us

What it does

Ssl Proxy Troubleshoot Fb786c is an agent skill from HKUDS/OpenSpace. Systematic approach to diagnosing and resolving SSL/proxy connectivity issues with restricted websites

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

It sits in DevOps & Cloud, covering Cloud networking. The repository describes itself as: "OpenSpace: The Skill Management Layer for AI Agents" -- https://open-space.cloud/. The licence is MIT.

When your agent uses it

  • Tasks that involve Cloud networking

Example prompts

  • “/ssl-proxy-troubleshoot-fb786c”

Requirements

  • Python 3

Workflow steps

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

  1. Initial Connectivity Assessment
  2. SSL Certificate Investigation
  3. Proxy Configuration Testing
  4. Protocol and Port Variations
  5. User-Agent and Header Manipulation
  6. Python Requests Alternative
  7. Alternative Data Sources
  8. Indirect Access Methods
  9. Documentation and Reporting

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

    Shell commands in SKILL.md call:

    • curl
    • openssl

    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:

    • target-domain.gov
    • target-domain.state.il.us
    • google.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 Fb786c loads about 1.6k tokens when it runs. Until then it costs about 33 tokens; SKILL.md has 381 words of instructions outside code blocks.

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

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). 381 words, ~1,571 tokens.

Download SKILL.mdSave it as .claude/skills/ssl-proxy-troubleshoot-fb786c/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-fb786c
description
Systematic approach to diagnosing and resolving SSL/proxy connectivity issues with restricted websites

SSL/Proxy Connectivity Troubleshooting

This skill provides a structured workflow for diagnosing and resolving network connectivity issues when accessing government websites, corporate portals, or other restricted domains that commonly exhibit SSL certificate problems, proxy requirements, or access restrictions.

When to Use

Apply this skill when:

  • HTTP requests fail with SSL/TLS certificate errors
  • Connections timeout or are refused through corporate/government networks
  • Proxy settings may be interfering with connectivity
  • Primary data sources are inaccessible and alternatives are needed

Diagnostic Workflow

Step 1: Initial Connectivity Assessment

Test basic connectivity before attempting complex solutions:

bash
# Test DNS resolution
nslookup target-domain.gov
dig target-domain.gov

# Test basic TCP connectivity
timeout 5 bash -c 'cat < /dev/null > /dev/tcp/target-domain.gov/443' && echo "Port 443 open" || echo "Port 443 closed"

# Test with curl (verbose)
curl -v https://target-domain.gov 2>&1 | head -50
Step 2: SSL Certificate Investigation

If SSL errors occur, diagnose the certificate issue:

bash
# Check certificate details
openssl s_client -connect target-domain.gov:443 -servername target-domain.gov 2>/dev/null | openssl x509 -noout -dates -subject -issuer

# Test with different SSL versions
curl --tlsv1.2 -v https://target-domain.gov
curl --tlsv1.3 -v https://target-domain.gov

# Try disabling verification (testing only)
curl -k https://target-domain.gov
Step 3: Proxy Configuration Testing

Test various proxy configurations:

bash
# Try without proxy
curl --noproxy "*" https://target-domain.gov

# Try with system proxy
curl -x http://proxy.example.com:8080 https://target-domain.gov

# Try explicit no-proxy for .gov domains
export no_proxy=".gov,.mil,.edu"
curl https://target-domain.gov

# Test with different proxy protocols
curl -x http://proxy:8080 https://target-domain.gov
curl -x https://proxy:8080 https://target-domain.gov
curl -x socks5://proxy:1080 https://target-domain.gov
Step 4: Protocol and Port Variations

Test alternative access methods:

bash
# Try HTTP instead of HTTPS
curl http://target-domain.gov

# Try alternative ports
curl https://target-domain.gov:8443
curl https://target-domain.gov:4443

# Try www subdomain variation
curl https://www.target-domain.gov

# Try alternative domain extensions
curl https://target-domain.state.il.us
Step 5: User-Agent and Header Manipulation

Some sites block automated access:

bash
# Use browser user-agent
curl -A "Mozilla/5.0 (Windows NT 10.0; Win64; x64) AppleWebKit/537.36" https://target-domain.gov

# Add common headers
curl -H "Accept: text/html" -H "Accept-Language: en-US" https://target-domain.gov

# Include referer header
curl -e "https://www.google.com/" https://target-domain.gov
Step 6: Python Requests Alternative

If curl fails, try Python with different configurations:

python
import requests
from requests.adapters import HTTPAdapter

# Disable SSL verification (testing only)
session = requests.Session()
session.verify = False
session.mount('https://', HTTPAdapter())

try:
    response = session.get('https://target-domain.gov', timeout=30)
    print(f"Status: {response.status_code}")
except Exception as e:
    print(f"Error: {e}")

# Try with custom SSL context
import ssl
context = ssl.create_default_context()
context.check_hostname = False
context.verify_mode = ssl.CERT_NONE

Fallback Strategies

When primary data sources remain inaccessible after exhausting troubleshooting:

1. Alternative Data Sources
  • Search for mirror sites or archived versions (Wayback Machine)
  • Check if data is available through state/federal data portals (data.gov)
  • Look for API endpoints that may have different access requirements
  • Search for downloadable datasets on alternative domains
2. Indirect Access Methods
  • Check if the same data is available through partner organizations
  • Look for cached versions through search engines
  • Contact the organization directly for data access
  • Check if data is available through FOIA requests or public records
Show full SKILL.md (146 more words)Show less
3. Documentation and Reporting

When access fails after systematic troubleshooting:

markdown
## Access Attempt Summary
- **Target**: [domain]
- **Methods Tried**: [list all approaches]
- **Errors Encountered**: [specific error messages]
- **Time Spent**: [duration]
- **Recommendation**: [alternative sources or next steps]

Decision Tree

SSL Error?
├── Yes → Try curl -k (test only)
│         ├── Works → Document SSL issue, proceed with verification disabled
│         └── Fails → Continue diagnostics
│
Proxy Issue?
├── Suspected → Try --noproxy "*"
│               ├── Works → Configure no_proxy for target domain
│               └── Fails → Try explicit proxy settings
│
Timeout/Refused?
├── Yes → Try HTTP instead of HTTPS
│         Try alternative ports
│         Try www subdomain
│         └── All fail → Implement fallback strategies
│
All Methods Fail?
└── Implement fallback strategies and document attempts

Important Notes

  1. Security Considerations: Disabling SSL verification should only be used for diagnosis in trusted environments. Never use in production without understanding the risks.

  2. Rate Limiting: Add delays between requests to avoid triggering rate limits or IP blocks.

  3. Documentation: Always document which methods were tried and their results for future reference.

  4. Iteration Limit: If 5+ distinct approaches fail, pivot to fallback strategies rather than continuing to iterate on the same blocked endpoint.

  5. Legal Compliance: Ensure all access attempts comply with terms of service and applicable laws.

Success Criteria

This troubleshooting workflow is complete when:

  • Data successfully retrieved from primary source, OR
  • All reasonable access methods exhausted (minimum 5 distinct approaches), OR
  • Viable alternative data source identified and accessed, OR
  • Clear documentation provided explaining access failure and recommended next steps

© 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-fb786c of HKUDS/OpenSpace.

  • SKILL.md
  • .skill_id

Open the folder on GitHubat commit 3827781

Compare with similar skills

Ssl Proxy Troubleshoot Fb786c 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 Fb786c compared with similar skills
SkillStarsUsed inTokensAuto-checkLicenceRepo updated
Ssl Proxy Troubleshoot Fb786c this skillHKUDS/OpenSpace7.8k—~1.6kAutomated safety check: PassMIT
Kubeshark KFL2 Filter Referencekubeshark/kubeshark12k—~3.6kAutomated safety check: PassApache-2.0
Nginx To Higress Migrationhigress-group/higress9.5k—~3.9kAutomated safety check: PassApache-2.0
Bfe Rd Workflowbfenetworks/bfe6.3k—~1.3kAutomated safety check: PassApache-2.0
NGINX Ingress Controller Feature Checklistsnginx/kubernetes-ingress5.1k—~1.4kAutomated safety check: PassApache-2.0
NGINX Ingress Policy CRD Guidenginx/kubernetes-ingress5.1k—~2kAutomated safety check: PassApache-2.0

Similar skills

  • Syntax reference for KFL2, the CEL-based display filter language used to search Kubernetes network traffic captured by Kubeshark, loaded before any filter is written.

    12k GitHub stars~3.6k tokensUpdated today
    DevOps & CloudAuto-check passed
  • Nginx To Higress Migration

    higress-group/higress

    Migrate from ingress-nginx to Higress in Kubernetes environments.

    9.5k GitHub stars~3.9k tokensUpdated 2 days ago
    DevOps & CloudAuto-check passed
  • Bfe Rd Workflow

    bfenetworks/bfe

    引导用户在 bfe 代码库中完成一次完整的功能研发流程,包括需求对齐、文档修改、代码实现、集成测试与回归验证. An agent skill from bfenetworks/bfe.

    6.3k GitHub stars~1.3k tokensUpdated yesterday
    DevOps & CloudAuto-check passed
  • Gives step-by-step checklists for adding Ingress annotations, VirtualServer fields and Helm values to the NGINX Kubernetes Ingress Controller, with common gotchas.

    5.1k GitHub stars~1.4k tokensUpdated today
    DevOps & CloudAuto-check passed
  • NGINX Ingress Policy CRD Guide

    nginx/kubernetes-ingress

    Step-by-step checklist for adding a new Policy CRD type to the NGINX Ingress Controller, from the Go types and validation to config generation and templates.

    5.1k GitHub stars~2k tokensUpdated today
    DevOps & CloudAuto-check passed
  • ArvanCloud API Operator

    erfnzdeh/arvancloud-agent-skill

    Drives ArvanCloud's REST APIs for CDN, DNS, cloud servers, object storage and more, with helper scripts for calls, account inventory and certificates.

    134 GitHub stars~3.9k tokensUpdated 12 days ago
    DevOps & CloudAuto-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

Categories

Questions about Ssl Proxy Troubleshoot Fb786c

What does Ssl Proxy Troubleshoot Fb786c do?

Systematic approach to diagnosing and resolving SSL/proxy connectivity issues with restricted websites. Ssl Proxy Troubleshoot Fb786c is an agent skill from HKUDS/OpenSpace.

When should I use Ssl Proxy Troubleshoot Fb786c?

Ssl Proxy Troubleshoot Fb786c fits situations like: tasks that involve Cloud networking.

How do I install Ssl Proxy Troubleshoot Fb786c in Claude Code?

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

How do I install Ssl Proxy Troubleshoot Fb786c in Codex?

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

Can I use Ssl Proxy Troubleshoot Fb786c 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-fb786c -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-fb786c, .gemini/skills/ssl-proxy-troubleshoot-fb786c, .github/skills/ssl-proxy-troubleshoot-fb786c and .opencode/skills/ssl-proxy-troubleshoot-fb786c in your project.

What does Ssl Proxy Troubleshoot Fb786c need to run?

Going by SKILL.md and its folder, Ssl Proxy Troubleshoot Fb786c needs the command-line tools its instructions call (curl and openssl). Our summary lists: Python 3.

Does Ssl Proxy Troubleshoot Fb786c access the network?

SKILL.md names 3 domains. In commands or code: target-domain.gov, target-domain.state.il.us and google.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 Fb786c 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 Fb786c use?

Ssl Proxy Troubleshoot Fb786c 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 Fb786c use?

About 1.6k tokens (SKILL.md is roughly 6.3k 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 Fb786c?

Skills that share tags, products or a category with Ssl Proxy Troubleshoot Fb786c: Kubeshark KFL2 Filter Reference (kubeshark/kubeshark, 12k stars), Nginx To Higress Migration (higress-group/higress, 9.5k stars), Bfe Rd Workflow (bfenetworks/bfe, 6.3k stars) and NGINX Ingress Controller Feature Checklists (nginx/kubernetes-ingress, 5.1k 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 Fb786c?

HKUDS (a GitHub organization) maintains it in HKUDS/OpenSpace, which has 7,754 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.