[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M6KK5ZQTFWE39J0RCMY4WF78":3,"skill-same:01M6KK5ZQTFWE39J0RCMY4WF78":59},{"skillNo":4,"name":5,"nameZh":6,"description":7,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":9,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":15,"categories":16,"keywords":17,"publishedAt":27,"linkOnly":28,"markdownContent":29,"markdownBody":30,"frontMatter":31,"refName":32,"commitSha":33,"skillDirectory":34,"forksCount":13,"repositoryHtmlUrl":35,"repositoryHomepageUrl":6,"ownerHtmlUrl":36,"ownerBlogUrl":6,"ownerDescription":37,"updatedAt":38,"install":39,"resources":52},"01M6KK5ZQTFWE39J0RCMY4WF78","ssl-proxy-troubleshoot-fb786c",null,"Systematic approach to diagnosing and resolving SSL\u002Fproxy connectivity issues with restricted websites","AG064\u002FOpenSpace","AG064","https:\u002F\u002Favatars.githubusercontent.com\u002Fu\u002F184930299?v=4","01M6KHVFG7TB73NHX3RDYSTMH2","01M6KHVFMM7XA2PZA9Z83PHS3V",0,"MIT","https:\u002F\u002Fgithub.com\u002FAG064\u002FOpenSpace\u002Fblob\u002Fmain\u002Fgdpval_bench\u002Fskills\u002Fssl-proxy-troubleshoot-fb786c\u002FSKILL.md",[],[18,19,20,21,22,23,24,25,26],"troubleshoot","proxy","ssl","ssl proxy troubleshoot fb786c","ssl proxy troubleshoot","issues","connectivity","systematic","with","2026-11-10 10:12:30",false,"---\nname: ssl-proxy-troubleshoot-fb786c\ndescription: Systematic approach to diagnosing and resolving SSL\u002Fproxy connectivity issues with restricted websites\n---\n\n# SSL\u002FProxy Connectivity Troubleshooting\n\nThis 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.\n\n## When to Use\n\nApply this skill when:\n- HTTP requests fail with SSL\u002FTLS certificate errors\n- Connections timeout or are refused through corporate\u002Fgovernment networks\n- Proxy settings may be interfering with connectivity\n- Primary data sources are inaccessible and alternatives are needed\n\n## Diagnostic Workflow\n\n### Step 1: Initial Connectivity Assessment\n\nTest basic connectivity before attempting complex solutions:\n\n```bash\n# Test DNS resolution\nnslookup target-domain.gov\ndig target-domain.gov\n\n# Test basic TCP connectivity\ntimeout 5 bash -c 'cat \u003C \u002Fdev\u002Fnull > \u002Fdev\u002Ftcp\u002Ftarget-domain.gov\u002F443' && echo \"Port 443 open\" || echo \"Port 443 closed\"\n\n# Test with curl (verbose)\ncurl -v https:\u002F\u002Ftarget-domain.gov 2>&1 | head -50\n```\n\n### Step 2: SSL Certificate Investigation\n\nIf SSL errors occur, diagnose the certificate issue:\n\n```bash\n# Check certificate details\nopenssl s_client -connect target-domain.gov:443 -servername target-domain.gov 2>\u002Fdev\u002Fnull | openssl x509 -noout -dates -subject -issuer\n\n# Test with different SSL versions\ncurl --tlsv1.2 -v https:\u002F\u002Ftarget-domain.gov\ncurl --tlsv1.3 -v https:\u002F\u002Ftarget-domain.gov\n\n# Try disabling verification (testing only)\ncurl -k https:\u002F\u002Ftarget-domain.gov\n```\n\n### Step 3: Proxy Configuration Testing\n\nTest various proxy configurations:\n\n```bash\n# Try without proxy\ncurl --noproxy \"*\" https:\u002F\u002Ftarget-domain.gov\n\n# Try with system proxy\ncurl -x http:\u002F\u002Fproxy.example.com:8080 https:\u002F\u002Ftarget-domain.gov\n\n# Try explicit no-proxy for .gov domains\nexport no_proxy=\".gov,.mil,.edu\"\ncurl https:\u002F\u002Ftarget-domain.gov\n\n# Test with different proxy protocols\ncurl -x http:\u002F\u002Fproxy:8080 https:\u002F\u002Ftarget-domain.gov\ncurl -x https:\u002F\u002Fproxy:8080 https:\u002F\u002Ftarget-domain.gov\ncurl -x socks5:\u002F\u002Fproxy:1080 https:\u002F\u002Ftarget-domain.gov\n```\n\n### Step 4: Protocol and Port Variations\n\nTest alternative access methods:\n\n```bash\n# Try HTTP instead of HTTPS\ncurl http:\u002F\u002Ftarget-domain.gov\n\n# Try alternative ports\ncurl https:\u002F\u002Ftarget-domain.gov:8443\ncurl https:\u002F\u002Ftarget-domain.gov:4443\n\n# Try www subdomain variation\ncurl https:\u002F\u002Fwww.target-domain.gov\n\n# Try alternative domain extensions\ncurl https:\u002F\u002Ftarget-domain.state.il.us\n```\n\n### Step 5: User-Agent and Header Manipulation\n\nSome sites block automated access:\n\n```bash\n# Use browser user-agent\ncurl -A \"Mozilla\u002F5.0 (Windows NT 10.0; Win64; x64) AppleWebKit\u002F537.36\" https:\u002F\u002Ftarget-domain.gov\n\n# Add common headers\ncurl -H \"Accept: text\u002Fhtml\" -H \"Accept-Language: en-US\" https:\u002F\u002Ftarget-domain.gov\n\n# Include referer header\ncurl -e \"https:\u002F\u002Fwww.google.com\u002F\" https:\u002F\u002Ftarget-domain.gov\n```\n\n### Step 6: Python Requests Alternative\n\nIf curl fails, try Python with different configurations:\n\n```python\nimport requests\nfrom requests.adapters import HTTPAdapter\n\n# Disable SSL verification (testing only)\nsession = requests.Session()\nsession.verify = False\nsession.mount('https:\u002F\u002F', HTTPAdapter())\n\ntry:\n    response = session.get('https:\u002F\u002Ftarget-domain.gov', timeout=30)\n    print(f\"Status: {response.status_code}\")\nexcept Exception as e:\n    print(f\"Error: {e}\")\n\n# Try with custom SSL context\nimport ssl\ncontext = ssl.create_default_context()\ncontext.check_hostname = False\ncontext.verify_mode = ssl.CERT_NONE\n```\n\n## Fallback Strategies\n\nWhen primary data sources remain inaccessible after exhausting troubleshooting:\n\n### 1. Alternative Data Sources\n- Search for mirror sites or archived versions (Wayback Machine)\n- Check if data is available through state\u002Ffederal data portals (data.gov)\n- Look for API endpoints that may have different access requirements\n- Search for downloadable datasets on alternative domains\n\n### 2. Indirect Access Methods\n- Check if the same data is available through partner organizations\n- Look for cached versions through search engines\n- Contact the organization directly for data access\n- Check if data is available through FOIA requests or public records\n\n### 3. Documentation and Reporting\nWhen access fails after systematic troubleshooting:\n```markdown\n## Access Attempt Summary\n- **Target**: [domain]\n- **Methods Tried**: [list all approaches]\n- **Errors Encountered**: [specific error messages]\n- **Time Spent**: [duration]\n- **Recommendation**: [alternative sources or next steps]\n```\n\n## Decision Tree\n\n```\nSSL Error?\n├── Yes → Try curl -k (test only)\n│         ├── Works → Document SSL issue, proceed with verification disabled\n│         └── Fails → Continue diagnostics\n│\nProxy Issue?\n├── Suspected → Try --noproxy \"*\"\n│               ├── Works → Configure no_proxy for target domain\n│               └── Fails → Try explicit proxy settings\n│\nTimeout\u002FRefused?\n├── Yes → Try HTTP instead of HTTPS\n│         Try alternative ports\n│         Try www subdomain\n│         └── All fail → Implement fallback strategies\n│\nAll Methods Fail?\n└── Implement fallback strategies and document attempts\n```\n\n## Important Notes\n\n1. **Security Considerations**: Disabling SSL verification should only be used for diagnosis in trusted environments. Never use in production without understanding the risks.\n\n2. **Rate Limiting**: Add delays between requests to avoid triggering rate limits or IP blocks.\n\n3. **Documentation**: Always document which methods were tried and their results for future reference.\n\n4. **Iteration Limit**: If 5+ distinct approaches fail, pivot to fallback strategies rather than continuing to iterate on the same blocked endpoint.\n\n5. **Legal Compliance**: Ensure all access attempts comply with terms of service and applicable laws.\n\n## Success Criteria\n\nThis troubleshooting workflow is complete when:\n- [ ] Data successfully retrieved from primary source, OR\n- [ ] All reasonable access methods exhausted (minimum 5 distinct approaches), OR\n- [ ] Viable alternative data source identified and accessed, OR\n- [ ] Clear documentation provided explaining access failure and recommended next steps","# SSL\u002FProxy Connectivity Troubleshooting\n\nThis 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.\n\n## When to Use\n\nApply this skill when:\n- HTTP requests fail with SSL\u002FTLS certificate errors\n- Connections timeout or are refused through corporate\u002Fgovernment networks\n- Proxy settings may be interfering with connectivity\n- Primary data sources are inaccessible and alternatives are needed\n\n## Diagnostic Workflow\n\n### Step 1: Initial Connectivity Assessment\n\nTest basic connectivity before attempting complex solutions:\n\n```bash\n# Test DNS resolution\nnslookup target-domain.gov\ndig target-domain.gov\n\n# Test basic TCP connectivity\ntimeout 5 bash -c 'cat \u003C \u002Fdev\u002Fnull > \u002Fdev\u002Ftcp\u002Ftarget-domain.gov\u002F443' && echo \"Port 443 open\" || echo \"Port 443 closed\"\n\n# Test with curl (verbose)\ncurl -v https:\u002F\u002Ftarget-domain.gov 2>&1 | head -50\n```\n\n### Step 2: SSL Certificate Investigation\n\nIf SSL errors occur, diagnose the certificate issue:\n\n```bash\n# Check certificate details\nopenssl s_client -connect target-domain.gov:443 -servername target-domain.gov 2>\u002Fdev\u002Fnull | openssl x509 -noout -dates -subject -issuer\n\n# Test with different SSL versions\ncurl --tlsv1.2 -v https:\u002F\u002Ftarget-domain.gov\ncurl --tlsv1.3 -v https:\u002F\u002Ftarget-domain.gov\n\n# Try disabling verification (testing only)\ncurl -k https:\u002F\u002Ftarget-domain.gov\n```\n\n### Step 3: Proxy Configuration Testing\n\nTest various proxy configurations:\n\n```bash\n# Try without proxy\ncurl --noproxy \"*\" https:\u002F\u002Ftarget-domain.gov\n\n# Try with system proxy\ncurl -x http:\u002F\u002Fproxy.example.com:8080 https:\u002F\u002Ftarget-domain.gov\n\n# Try explicit no-proxy for .gov domains\nexport no_proxy=\".gov,.mil,.edu\"\ncurl https:\u002F\u002Ftarget-domain.gov\n\n# Test with different proxy protocols\ncurl -x http:\u002F\u002Fproxy:8080 https:\u002F\u002Ftarget-domain.gov\ncurl -x https:\u002F\u002Fproxy:8080 https:\u002F\u002Ftarget-domain.gov\ncurl -x socks5:\u002F\u002Fproxy:1080 https:\u002F\u002Ftarget-domain.gov\n```\n\n### Step 4: Protocol and Port Variations\n\nTest alternative access methods:\n\n```bash\n# Try HTTP instead of HTTPS\ncurl http:\u002F\u002Ftarget-domain.gov\n\n# Try alternative ports\ncurl https:\u002F\u002Ftarget-domain.gov:8443\ncurl https:\u002F\u002Ftarget-domain.gov:4443\n\n# Try www subdomain variation\ncurl https:\u002F\u002Fwww.target-domain.gov\n\n# Try alternative domain extensions\ncurl https:\u002F\u002Ftarget-domain.state.il.us\n```\n\n### Step 5: User-Agent and Header Manipulation\n\nSome sites block automated access:\n\n```bash\n# Use browser user-agent\ncurl -A \"Mozilla\u002F5.0 (Windows NT 10.0; Win64; x64) AppleWebKit\u002F537.36\" https:\u002F\u002Ftarget-domain.gov\n\n# Add common headers\ncurl -H \"Accept: text\u002Fhtml\" -H \"Accept-Language: en-US\" https:\u002F\u002Ftarget-domain.gov\n\n# Include referer header\ncurl -e \"https:\u002F\u002Fwww.google.com\u002F\" https:\u002F\u002Ftarget-domain.gov\n```\n\n### Step 6: Python Requests Alternative\n\nIf curl fails, try Python with different configurations:\n\n```python\nimport requests\nfrom requests.adapters import HTTPAdapter\n\n# Disable SSL verification (testing only)\nsession = requests.Session()\nsession.verify = False\nsession.mount('https:\u002F\u002F', HTTPAdapter())\n\ntry:\n    response = session.get('https:\u002F\u002Ftarget-domain.gov', timeout=30)\n    print(f\"Status: {response.status_code}\")\nexcept Exception as e:\n    print(f\"Error: {e}\")\n\n# Try with custom SSL context\nimport ssl\ncontext = ssl.create_default_context()\ncontext.check_hostname = False\ncontext.verify_mode = ssl.CERT_NONE\n```\n\n## Fallback Strategies\n\nWhen primary data sources remain inaccessible after exhausting troubleshooting:\n\n### 1. Alternative Data Sources\n- Search for mirror sites or archived versions (Wayback Machine)\n- Check if data is available through state\u002Ffederal data portals (data.gov)\n- Look for API endpoints that may have different access requirements\n- Search for downloadable datasets on alternative domains\n\n### 2. Indirect Access Methods\n- Check if the same data is available through partner organizations\n- Look for cached versions through search engines\n- Contact the organization directly for data access\n- Check if data is available through FOIA requests or public records\n\n### 3. Documentation and Reporting\nWhen access fails after systematic troubleshooting:\n```markdown\n## Access Attempt Summary\n- **Target**: [domain]\n- **Methods Tried**: [list all approaches]\n- **Errors Encountered**: [specific error messages]\n- **Time Spent**: [duration]\n- **Recommendation**: [alternative sources or next steps]\n```\n\n## Decision Tree\n\n```\nSSL Error?\n├── Yes → Try curl -k (test only)\n│         ├── Works → Document SSL issue, proceed with verification disabled\n│         └── Fails → Continue diagnostics\n│\nProxy Issue?\n├── Suspected → Try --noproxy \"*\"\n│               ├── Works → Configure no_proxy for target domain\n│               └── Fails → Try explicit proxy settings\n│\nTimeout\u002FRefused?\n├── Yes → Try HTTP instead of HTTPS\n│         Try alternative ports\n│         Try www subdomain\n│         └── All fail → Implement fallback strategies\n│\nAll Methods Fail?\n└── Implement fallback strategies and document attempts\n```\n\n## Important Notes\n\n1. **Security Considerations**: Disabling SSL verification should only be used for diagnosis in trusted environments. Never use in production without understanding the risks.\n\n2. **Rate Limiting**: Add delays between requests to avoid triggering rate limits or IP blocks.\n\n3. **Documentation**: Always document which methods were tried and their results for future reference.\n\n4. **Iteration Limit**: If 5+ distinct approaches fail, pivot to fallback strategies rather than continuing to iterate on the same blocked endpoint.\n\n5. **Legal Compliance**: Ensure all access attempts comply with terms of service and applicable laws.\n\n## Success Criteria\n\nThis troubleshooting workflow is complete when:\n- [ ] Data successfully retrieved from primary source, OR\n- [ ] All reasonable access methods exhausted (minimum 5 distinct approaches), OR\n- [ ] Viable alternative data source identified and accessed, OR\n- [ ] Clear documentation provided explaining access failure and recommended next steps",{"name":5,"description":7},"main","ff671ef61ed6587c49bd54c81cdc751c0b99e363","gdpval_bench\u002Fskills\u002Fssl-proxy-troubleshoot-fb786c","https:\u002F\u002Fgithub.com\u002FAG064\u002FOpenSpace","https:\u002F\u002Fgithub.com\u002FAG064","AG064, E.Mi.\r\n\r\nA person who thinks all the time, yet all they have to think about is nothing. I want to improve the world and work on open source projects","2026-10-08 06:53:48",{"source":8,"skillName":5,"commands":40,"prompt":50,"zipAvailable":51},[41,44,47],{"tool":42,"command":43},"npx","npx skills add AG064\u002FOpenSpace --skill ssl-proxy-troubleshoot-fb786c",{"tool":45,"command":46},"bunx","bunx skills add AG064\u002FOpenSpace --skill ssl-proxy-troubleshoot-fb786c",{"tool":48,"command":49},"pnpm","pnpm dlx skills add AG064\u002FOpenSpace --skill ssl-proxy-troubleshoot-fb786c","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002FAG064\u002FOpenSpace\u002Fblob\u002Fmain\u002Fgdpval_bench\u002Fskills\u002Fssl-proxy-troubleshoot-fb786c\u002FSKILL.md",true,[53],{"path":54,"resourceType":55,"resourceTypeDesc":56,"sizeBytes":57,"sourceHtmlUrl":58},".skill_id","OTHER","其他",43,"https:\u002F\u002Fgithub.com\u002FAG064\u002FOpenSpace\u002Fblob\u002Fmain\u002Fgdpval_bench\u002Fskills\u002Fssl-proxy-troubleshoot-fb786c\u002F.skill_id",[60,84,100,109,139,155],{"skillNo":61,"name":62,"nameZh":6,"description":63,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":9,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":64,"categories":65,"keywords":66,"publishedAt":27},"01M6KKMPWA0B5SCCH766F8M5EA","write-special-chars-ts-check","Workaround for write_file failures caused by special characters (apostrophes, backticks, template literals) using a Python heredoc script, plus a reliable TypeScript type-checking step that filters output to only the newly-written files to avoid being misled by pre-existing errors.","https:\u002F\u002Fgithub.com\u002FAG064\u002FOpenSpace\u002Fblob\u002Fmain\u002Fshowcase\u002Fskills\u002Fwrite-special-chars-ts-check\u002FSKILL.md",[],[67,68,69,70,71,72,73,74,75,76,77,78,79,80,81,82,83],"write special chars ts check","check","write","filters","Existing","type-checking","for","errors","script","output","type","files","only","template","file","python","typescript",{"skillNo":85,"name":86,"nameZh":6,"description":87,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":9,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":88,"categories":89,"keywords":90,"publishedAt":27},"01M6KKMJXVBNVEY3TRK055F4A7","write-special-chars-readback","Workaround for write_file failures caused by special characters (apostrophes, backticks, template literals) using a Python heredoc script, with mandatory post-write verification via read_file and cleanup of \u002Ftmp helper scripts.","https:\u002F\u002Fgithub.com\u002FAG064\u002FOpenSpace\u002Fblob\u002Fmain\u002Fshowcase\u002Fskills\u002Fwrite-special-chars-readback\u002FSKILL.md",[],[91,92,69,80,93,94,81,82,95,96,97,98,99,73,75,26],"readback","write special chars readback","cleanup","read","scripts","verification","via","post","helper",{"skillNo":101,"name":102,"nameZh":6,"description":103,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":9,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":104,"categories":105,"keywords":106,"publishedAt":27},"01M6KKMEGX9M9NC105J0W3Q5B9","write-special-chars-heredoc","Workaround for write_file failures caused by special characters (apostrophes, backticks, template literals) by using a Python heredoc script executed via shell.","https:\u002F\u002Fgithub.com\u002FAG064\u002FOpenSpace\u002Fblob\u002Fmain\u002Fshowcase\u002Fskills\u002Fwrite-special-chars-heredoc\u002FSKILL.md",[],[69,107,82,73,97,80,108,81,75],"write special chars heredoc","shell",{"skillNo":110,"name":111,"nameZh":6,"description":112,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":9,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":113,"categories":114,"keywords":120,"publishedAt":27},"01M6KKM8EJ2AATVHZBNB916WT0","worldmonitor-reference","Curated architecture index of the WorldMonitor open-source dashboard. Reference for extracting patterns — vanilla TypeScript, Panel class hierarchy, service layer, CSS grid, API edge functions, refresh scheduler, and 60+ data source integrations.","https:\u002F\u002Fgithub.com\u002FAG064\u002FOpenSpace\u002Fblob\u002Fmain\u002Fshowcase\u002Fskills\u002Fworldmonitor-reference\u002FSKILL.md",[115],{"categoryNo":116,"categoryName":117,"taxonomyType":118,"taxonomyTypeDesc":119},"01JBSEEDCAT000000000000033","数据分析师","PROFESSION","适用职业",[121,122,123,124,83,125,126,127,128,129,73,130,131,132,133,134,135,136,137,138],"reference","worldmonitor","worldmonitor reference","dashboard","css","architecture","extracting","hierarchy","source","layer","panel","patterns","edge functions","integrations","open","api","data","scheduler",{"skillNo":140,"name":141,"nameZh":6,"description":142,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":9,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":143,"categories":144,"keywords":145,"publishedAt":27},"01M6KKM39PHYK627F19GE2B9XN","virtual-list","Implement efficient virtual scrolling for rendering large lists with DOM recycling, chunk-based rendering, and performance optimizations","https:\u002F\u002Fgithub.com\u002FAG064\u002FOpenSpace\u002Fblob\u002Fmain\u002Fshowcase\u002Fskills\u002Fvirtual-list\u002FSKILL.md",[],[146,147,148,149,73,150,26,151,152,153,154],"virtual list","list","virtual","chunk","dom","rendering","recycling","implement","performance",{"skillNo":156,"name":157,"nameZh":6,"description":158,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":9,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":159,"categories":160,"keywords":161,"publishedAt":27},"01M6KKKY7T2P61Y0JH54CDEJKQ","verify-directory-structure","Diagnose and resolve file access issues by first verifying the directory structure.","https:\u002F\u002Fgithub.com\u002FAG064\u002FOpenSpace\u002Fblob\u002Fmain\u002Fshowcase\u002Fskills\u002Fverify-directory-structure\u002FSKILL.md",[],[162,163,164,165,166,167,81,23,168,169],"directory","verify","structure","verify directory structure","access","first","diagnose","file access"]