[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M6HX3X20RY6225HJB6SQER31":3,"skill-same:01M6HX3X20RY6225HJB6SQER31":60},{"skillNo":4,"name":5,"nameZh":6,"description":7,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":16,"categories":17,"keywords":18,"publishedAt":27,"linkOnly":28,"markdownContent":29,"markdownBody":30,"frontMatter":31,"refName":32,"commitSha":33,"skillDirectory":34,"forksCount":35,"repositoryHtmlUrl":36,"repositoryHomepageUrl":6,"ownerHtmlUrl":37,"ownerBlogUrl":38,"ownerDescription":6,"updatedAt":39,"install":40,"resources":53},"01M6HX3X20RY6225HJB6SQER31","ssl-proxy-troubleshoot-fb786c",null,"Systematic approach to diagnosing and resolving SSL\u002Fproxy connectivity issues with restricted websites","HKUDS\u002FAgentPilot","HKUDS","https:\u002F\u002Favatars.githubusercontent.com\u002Fu\u002F118165258?v=4","01M6HW8VRNZP64G0P4MVJW2KKQ","✨Data Intelligence Lab@HKU✨","01M6HW8VWZVHBRHYH3T330PFWV",8029,"MIT","https:\u002F\u002Fgithub.com\u002FHKUDS\u002FAgentPilot\u002Fblob\u002Fmain\u002Fopenspace\u002Fbenchmarks\u002Fgdpval\u002Fskills\u002Fssl-proxy-troubleshoot-fb786c\u002FSKILL.md",[],[19,20,21,22,23,24,25,26],"troubleshoot","proxy","ssl","ssl proxy troubleshoot fb786c","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","6b84b0689ca0d9e7b1e4061188ff6b60758e0f8a","openspace\u002Fbenchmarks\u002Fgdpval\u002Fskills\u002Fssl-proxy-troubleshoot-fb786c",944,"https:\u002F\u002Fgithub.com\u002FHKUDS\u002FAgentPilot","https:\u002F\u002Fgithub.com\u002FHKUDS","https:\u002F\u002Fsites.google.com\u002Fview\u002Fchaoh","2026-11-12 22:26:39",{"source":8,"skillName":5,"commands":41,"prompt":51,"zipAvailable":52},[42,45,48],{"tool":43,"command":44},"npx","npx skills add HKUDS\u002FAgentPilot --skill ssl-proxy-troubleshoot-fb786c",{"tool":46,"command":47},"bunx","bunx skills add HKUDS\u002FAgentPilot --skill ssl-proxy-troubleshoot-fb786c",{"tool":49,"command":50},"pnpm","pnpm dlx skills add HKUDS\u002FAgentPilot --skill ssl-proxy-troubleshoot-fb786c","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002FHKUDS\u002FAgentPilot\u002Fblob\u002Fmain\u002Fopenspace\u002Fbenchmarks\u002Fgdpval\u002Fskills\u002Fssl-proxy-troubleshoot-fb786c\u002FSKILL.md",true,[54],{"path":55,"resourceType":56,"resourceTypeDesc":57,"sizeBytes":58,"sourceHtmlUrl":59},".skill_id","OTHER","其他",43,"https:\u002F\u002Fgithub.com\u002FHKUDS\u002FAgentPilot\u002Fblob\u002Fmain\u002Fopenspace\u002Fbenchmarks\u002Fgdpval\u002Fskills\u002Fssl-proxy-troubleshoot-fb786c\u002F.skill_id",[61,80,99,124,148,171],{"skillNo":62,"name":63,"nameZh":6,"description":64,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":65,"categories":66,"keywords":67,"publishedAt":27},"01M6HYB297NDABRERJRVG0K8R0","agentpilot","Set up AgentPilot and use its single entry to prepare missing inputs and run configured RSI experiments. Use when the user requests AgentPilot installation or work with AgentPilot.","https:\u002F\u002Fgithub.com\u002FHKUDS\u002FAgentPilot\u002Fblob\u002Fmain\u002Fplugins\u002Fagentpilot\u002Fskills\u002Fagentpilot\u002FSKILL.md",[],[63,68,69,26,70,71,72,73,74,75,76,77,78,79],"prepare","requests","missing","installation","rsi","up","use","user","work","SET","run","experiments",{"skillNo":81,"name":82,"nameZh":6,"description":83,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":84,"categories":85,"keywords":86,"publishedAt":27},"01M6HYAYWXTTE1J7DJM0MFNQ4H","remember","Review auto-memory entries and propose promotions to OPENSPACE.md, OPENSPACE.local.md, or retained auto-memory topics; detect duplicates, stale facts, conflicts, and ambiguous entries before making changes.","https:\u002F\u002Fgithub.com\u002FHKUDS\u002FAgentPilot\u002Fblob\u002Fmain\u002Fopenspace\u002Fopenspace\u002Fskills\u002Fremember\u002FSKILL.md",[],[82,87,88,89,90,91,92,93,94,95,96,97,98],"memory","review","auto","openspace","changes","facts","detect","entries","local","conflicts","stale","duplicates",{"skillNo":100,"name":101,"nameZh":6,"description":102,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":103,"categories":104,"keywords":110,"publishedAt":27},"01M6HYAVMPM4SBDV60R2B5HPV8","skill-discovery","Search reusable OpenSpace skills locally, and browse cloud packages step by step when a cloud skill may help. Reusing proven skills saves tokens, improves reliability, and extends your capabilities beyond built-in tools.","https:\u002F\u002Fgithub.com\u002FHKUDS\u002FAgentPilot\u002Fblob\u002Fmain\u002Fopenspace\u002Fopenspace\u002Fhost_skills\u002Fskill-discovery\u002FSKILL.md",[105],{"categoryNo":106,"categoryName":107,"taxonomyType":108,"taxonomyTypeDesc":109},"01JBSEEDCAT000000000000023","Skill与智能体开发","SCENARIO","使用场景",[111,112,113,90,114,115,116,117,118,119,120,121,122,123],"skill discovery","discovery","reusable","step by step","tokens","packages","help","cloud","reliability","capabilities","browse","search","Tools",{"skillNo":125,"name":126,"nameZh":6,"description":127,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":128,"categories":129,"keywords":131,"publishedAt":27},"01M6HYAR811B3RB0M50RBEDGN6","delegate-task","Delegate tasks to OpenSpace — a full-stack autonomous worker for coding, DevOps, web research, and desktop automation, backed by an extensive MCP tool and skill library. Skills auto-improve through use, reducing token consumption over time. A cloud community lets agents share and collectively evolve reusable skills.","https:\u002F\u002Fgithub.com\u002FHKUDS\u002FAgentPilot\u002Fblob\u002Fmain\u002Fopenspace\u002Fopenspace\u002Fhost_skills\u002Fdelegate-task\u002FSKILL.md",[130],{"categoryNo":106,"categoryName":107,"taxonomyType":108,"taxonomyTypeDesc":109},[132,133,134,90,135,136,137,138,139,113,89,74,140,141,142,143,144,145,146,147],"delegate","task","delegate task","time","improve","desktop automation","worker","community","autonomous","tool","stack","for","share","tasks","automation","MCP",{"skillNo":149,"name":150,"nameZh":6,"description":151,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":152,"categories":153,"keywords":154,"publishedAt":27},"01M6HYAM9FSGV6E52AYENDQXYH","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\u002FHKUDS\u002FAgentPilot\u002Fblob\u002Fmain\u002Fopenspace\u002Flegacy\u002Fv1\u002Fshowcase\u002Fskills\u002Fwrite-special-chars-ts-check\u002FSKILL.md",[],[155,156,157,158,159,160,161,162,163,164,165,166,167,168,143,169,170],"write special chars ts check","write","check","type","files","filters","only","template","file","python","typescript","output","Existing","type-checking","errors","script",{"skillNo":172,"name":173,"nameZh":6,"description":174,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":175,"categories":176,"keywords":177,"publishedAt":27},"01M6HYAH05HGV7SVWSVR8PJRQD","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\u002FHKUDS\u002FAgentPilot\u002Fblob\u002Fmain\u002Fopenspace\u002Flegacy\u002Fv1\u002Fshowcase\u002Fskills\u002Fwrite-special-chars-readback\u002FSKILL.md",[],[178,179,156,26,143,170,180,181,182,183,184,162,163,185,186,164],"write special chars readback","readback","helper","post","via","scripts","read","verification","cleanup"]