[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M76K8VM2032B03FCRE5GFCFZ":3,"skill-same:01M76K8VM2032B03FCRE5GFCFZ":56},{"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":19,"linkOnly":20,"markdownContent":21,"markdownBody":22,"frontMatter":23,"refName":26,"commitSha":27,"skillDirectory":28,"forksCount":29,"repositoryHtmlUrl":30,"repositoryHomepageUrl":31,"ownerHtmlUrl":32,"ownerBlogUrl":33,"ownerDescription":34,"updatedAt":35,"install":36,"resources":49},"01M76K8VM2032B03FCRE5GFCFZ","software-testing-router",null,"Use when choosing or implementing software automation tests across CLI\u002FAPI, web, or Windows\u002FmacOS desktop apps, especially when Computer Use screenshot-and-click loops are slow, only an EXE or .app is available, or the correct test interface is unclear. 适用于软件自动化测试选型、桌面回归、GUI 验收和测试入口探测。","bg-szy\u002FTOP-SKILLS","bg-szy","https:\u002F\u002Favatars.githubusercontent.com\u002Fu\u002F106576190?v=4","01M73A4E8KPV67SFXRY8XZGNBX","ShuZhiyong","01M73A4E96MQ294MHM74TZBVQD",6,"MIT","https:\u002F\u002Fgithub.com\u002Fbg-szy\u002FTOP-SKILLS\u002Fblob\u002Fmaster\u002Fskills\u002Fmarketplace\u002Fsoftware-testing-router\u002FSKILL.md",[],[],"2026-11-12 13:55:43",false,"---\nname: software-testing-router\ndescription: Use when choosing or implementing software automation tests across CLI\u002FAPI, web, or Windows\u002FmacOS desktop apps, especially when Computer Use screenshot-and-click loops are slow, only an EXE or .app is available, or the correct test interface is unclear. 适用于软件自动化测试选型、桌面回归、GUI 验收和测试入口探测。\nlicense: MIT\nmetadata:\n  version: \"1.1.1\"\n---\n\n# 软件自动化测试方法选择\n\n按验收目标选择软件已有的测试入口，系统能力与验证边界见[完整概述](references\u002Foverview.md)。Mac 原生实现尚未实机验证，Linux 无本包原生 GUI 驱动。\n\n选择**能证明当前验收要求、且总成本较低的稳定入口**。先探测接口和控件能力，再选择工具；开发语言不能单独决定可测性。Computer Use 是缺少合适结构化入口时的备选，不是软件测试的默认起点。\n\n## 先确定要证明什么\n\n从任务和仓库提取：被测版本、目标环境、源码\u002FEXE\u002FURL、已有测试工具、具体行为和预期结果。已有可用工具通常比换框架更省时。只为真正缺失且影响下一步的信息询问用户。\n\n| 要证明的行为 | 优先探测的入口 | 最小有效证据 | 按需阅读 |\n|---|---|---|---|\n| 算法、文件转换、服务业务契约 | 已有函数测试、正式 CLI 或 API | 退出码\u002FHTTP 状态 **及** 业务结果、实际产物 | [CLI \u002F API](references\u002Fcli-api.md) |\n| 网页按钮、表单、导航、异步弹窗 | DOM 自动化；已有框架可沿用，缺少时可选 Playwright | 真实用户事件 → 请求\u002F界面状态 → 业务结果 | [网页](references\u002Fweb.md) |\n| Windows 桌面实际交互，含只有 EXE 的应用 | UIA 控件树与所需 Pattern；本包提供 PowerShell 实现 | 指定进程的控件动作、后置状态与产物 | [Windows UIA](references\u002Fwindows-uia.md) |\n| macOS 原生窗口实际交互，含 .app | Accessibility 属性与动作；本包提供 Python 标准库实现，需已有辅助功能授权 | 指定 PID 的唯一控件动作、后置状态与本次产物；本实现未实机验证 | [macOS Accessibility](references\u002Fmacos-accessibility.md) |\n| 有源码的 PySide\u002FPyQt 控件、信号、线程、取消 | pytest-qt 的 Qt 事件循环 | 信号、状态、错误路径、应出现或不应出现的产物 | [Qt 内部测试](references\u002Fqt.md) |\n| 排版、裁切、颜色、透明度、绘图外观 | 受控截图\u002F导出图 + 有依据的视觉比较 | 固定环境下的原图、对照、差异解释 | [视觉与能力边界](references\u002Fvisual-and-limits.md) |\n\nAPI 成功不能证明按钮有效；控件或信号成功不能证明打包 EXE\u002F.app 可用；DOM\u002FUIA\u002FAX 属性正确不能证明画面无裁切。按验收要求组合必要层次，不为每个任务运行所有路线。只验收文件转换且已确认正式 CLI 时，Mac 上也优先沿用 CLI\u002FAPI。\n\nElectron \u002F WebView 先区分 HTML 内容与原生外壳：**已可用且获授权的**调试连接可走 DOM，原生对话框按系统探测 UIA 或 AX。普通网页测试不等于验证 Electron。没有调试端口时不能假定能附加，也不要为了测试改动用户正在使用的浏览器配置。\n\n## 探测后执行\n\n1. 用一句话记录：`要证明的行为 → 实际发现的入口 → 选择原因 → 成功证据 → 失败时的下一步`。先用小流程验证入口，避免先搭建大套测试框架。\n2. 桌面先确认实际窗口拥有者，再用浅层检查读取区域与 Pattern\u002FAX 属性；`scripts\u002Frun_desktop.py` 按系统选择入口，旧 Windows `run_uia.py` 仍可用。两平台支持 `--probe`、`--inspect-depth`、步骤内 `within` 和 `window`；Mac probe 仅检查已核验的指定 PID，不寻找启动器后代。网页按实际 DOM 建定位。标识必须唯一；重名时缩小作用域，缺失时检查窗口\u002Fiframe\u002F权限\u002F虚拟化。不要靠猜坐标或取第一个匹配掩盖问题。\n3. 把确定的操作和条件等待放进同一脚本\u002F测试，减少模型逐步往返。等待可观察状态，设置条件超时及整个进程的硬超时。动作返回后检查后置条件；有副作用的动作不因超时盲目重试。\n4. 用新测试数据或可追踪任务 ID 核对真实输出，补充与本次风险相关的失败场景。保留简短日志和必要证据；修复后只重跑受影响的检查及明确要求的验证。\n\n中断后先读本次运行的日志：区分已完成步骤、等待中的步骤、已开始但结果未知的动作。UIA\u002FAX 助手会保留 JSONL 进度；它用于恢复判断，不自动重放动作。等待断言的记录必须来自满足条件时的同一次观测，不能用稍后的值代替。\n\n## 何时切换路线\n\n缺少所需 Pattern\u002FAX 动作、辅助功能权限、控件树不可用、调试端口不可用或纯自绘内容：记录具体探测结果，再评估已有应用接口、可测性改进、平台工具或视觉操作。首次短探测失败不是“所有结构化方法均不可用”的证据；也不要在同一路线上无边界重试。Mac 助手只检查已有授权，不触发提示或修改 TCC；Linux 当前只有可移植入口，没有本包原生 GUI 驱动。\n\n用户禁止 Computer Use 时，保留该约束。确实缺少必要能力时，清楚说明尚未验证的部分及所需帮助。现有会话的通知、授权和工具边界仍适用；本技能不扩展权限。\n\n## 交付证据\n\n报告被测对象\u002F版本、实际执行的路线和命令、断言与结果、必要产物、耗时及未覆盖部分。环境缺失、跳过、动作仅已发出、未知结果分别记录，不能计为通过。对旧失败和恢复后的重跑保留原因；不要以重试次数换取“全绿”。\n\n本包已在 Windows 10 验证 CLI、HTTP、Playwright Chromium、Windows UIA 和 pytest-qt 的具体样例；新增 Mac 原生实现与验收用例尚无 Mac 实机结果，Windows 11 与 Linux 也未实测。范围与运行方法见 [实测记录](references\u002Fvalidation.md)。这些局部耗时不构成工具排行榜，也未测出相对 Computer Use 的加速倍数。研究来源与现成技能比较见 [调研](references\u002Fresearch.md)。\n\n增加语言、框架或平台时，按 [扩展规范](references\u002Fextending.md) 复用已有入口、补充有针对性的样例和证据，再更新验证状态。\n\n本包版本及本地维护边界见 [维护说明](references\u002Fmaintenance.md)，使用与分发遵循 [MIT 许可](references\u002Flicense.txt)。\n","# 软件自动化测试方法选择\n\n按验收目标选择软件已有的测试入口，系统能力与验证边界见[完整概述](references\u002Foverview.md)。Mac 原生实现尚未实机验证，Linux 无本包原生 GUI 驱动。\n\n选择**能证明当前验收要求、且总成本较低的稳定入口**。先探测接口和控件能力，再选择工具；开发语言不能单独决定可测性。Computer Use 是缺少合适结构化入口时的备选，不是软件测试的默认起点。\n\n## 先确定要证明什么\n\n从任务和仓库提取：被测版本、目标环境、源码\u002FEXE\u002FURL、已有测试工具、具体行为和预期结果。已有可用工具通常比换框架更省时。只为真正缺失且影响下一步的信息询问用户。\n\n| 要证明的行为 | 优先探测的入口 | 最小有效证据 | 按需阅读 |\n|---|---|---|---|\n| 算法、文件转换、服务业务契约 | 已有函数测试、正式 CLI 或 API | 退出码\u002FHTTP 状态 **及** 业务结果、实际产物 | [CLI \u002F API](references\u002Fcli-api.md) |\n| 网页按钮、表单、导航、异步弹窗 | DOM 自动化；已有框架可沿用，缺少时可选 Playwright | 真实用户事件 → 请求\u002F界面状态 → 业务结果 | [网页](references\u002Fweb.md) |\n| Windows 桌面实际交互，含只有 EXE 的应用 | UIA 控件树与所需 Pattern；本包提供 PowerShell 实现 | 指定进程的控件动作、后置状态与产物 | [Windows UIA](references\u002Fwindows-uia.md) |\n| macOS 原生窗口实际交互，含 .app | Accessibility 属性与动作；本包提供 Python 标准库实现，需已有辅助功能授权 | 指定 PID 的唯一控件动作、后置状态与本次产物；本实现未实机验证 | [macOS Accessibility](references\u002Fmacos-accessibility.md) |\n| 有源码的 PySide\u002FPyQt 控件、信号、线程、取消 | pytest-qt 的 Qt 事件循环 | 信号、状态、错误路径、应出现或不应出现的产物 | [Qt 内部测试](references\u002Fqt.md) |\n| 排版、裁切、颜色、透明度、绘图外观 | 受控截图\u002F导出图 + 有依据的视觉比较 | 固定环境下的原图、对照、差异解释 | [视觉与能力边界](references\u002Fvisual-and-limits.md) |\n\nAPI 成功不能证明按钮有效；控件或信号成功不能证明打包 EXE\u002F.app 可用；DOM\u002FUIA\u002FAX 属性正确不能证明画面无裁切。按验收要求组合必要层次，不为每个任务运行所有路线。只验收文件转换且已确认正式 CLI 时，Mac 上也优先沿用 CLI\u002FAPI。\n\nElectron \u002F WebView 先区分 HTML 内容与原生外壳：**已可用且获授权的**调试连接可走 DOM，原生对话框按系统探测 UIA 或 AX。普通网页测试不等于验证 Electron。没有调试端口时不能假定能附加，也不要为了测试改动用户正在使用的浏览器配置。\n\n## 探测后执行\n\n1. 用一句话记录：`要证明的行为 → 实际发现的入口 → 选择原因 → 成功证据 → 失败时的下一步`。先用小流程验证入口，避免先搭建大套测试框架。\n2. 桌面先确认实际窗口拥有者，再用浅层检查读取区域与 Pattern\u002FAX 属性；`scripts\u002Frun_desktop.py` 按系统选择入口，旧 Windows `run_uia.py` 仍可用。两平台支持 `--probe`、`--inspect-depth`、步骤内 `within` 和 `window`；Mac probe 仅检查已核验的指定 PID，不寻找启动器后代。网页按实际 DOM 建定位。标识必须唯一；重名时缩小作用域，缺失时检查窗口\u002Fiframe\u002F权限\u002F虚拟化。不要靠猜坐标或取第一个匹配掩盖问题。\n3. 把确定的操作和条件等待放进同一脚本\u002F测试，减少模型逐步往返。等待可观察状态，设置条件超时及整个进程的硬超时。动作返回后检查后置条件；有副作用的动作不因超时盲目重试。\n4. 用新测试数据或可追踪任务 ID 核对真实输出，补充与本次风险相关的失败场景。保留简短日志和必要证据；修复后只重跑受影响的检查及明确要求的验证。\n\n中断后先读本次运行的日志：区分已完成步骤、等待中的步骤、已开始但结果未知的动作。UIA\u002FAX 助手会保留 JSONL 进度；它用于恢复判断，不自动重放动作。等待断言的记录必须来自满足条件时的同一次观测，不能用稍后的值代替。\n\n## 何时切换路线\n\n缺少所需 Pattern\u002FAX 动作、辅助功能权限、控件树不可用、调试端口不可用或纯自绘内容：记录具体探测结果，再评估已有应用接口、可测性改进、平台工具或视觉操作。首次短探测失败不是“所有结构化方法均不可用”的证据；也不要在同一路线上无边界重试。Mac 助手只检查已有授权，不触发提示或修改 TCC；Linux 当前只有可移植入口，没有本包原生 GUI 驱动。\n\n用户禁止 Computer Use 时，保留该约束。确实缺少必要能力时，清楚说明尚未验证的部分及所需帮助。现有会话的通知、授权和工具边界仍适用；本技能不扩展权限。\n\n## 交付证据\n\n报告被测对象\u002F版本、实际执行的路线和命令、断言与结果、必要产物、耗时及未覆盖部分。环境缺失、跳过、动作仅已发出、未知结果分别记录，不能计为通过。对旧失败和恢复后的重跑保留原因；不要以重试次数换取“全绿”。\n\n本包已在 Windows 10 验证 CLI、HTTP、Playwright Chromium、Windows UIA 和 pytest-qt 的具体样例；新增 Mac 原生实现与验收用例尚无 Mac 实机结果，Windows 11 与 Linux 也未实测。范围与运行方法见 [实测记录](references\u002Fvalidation.md)。这些局部耗时不构成工具排行榜，也未测出相对 Computer Use 的加速倍数。研究来源与现成技能比较见 [调研](references\u002Fresearch.md)。\n\n增加语言、框架或平台时，按 [扩展规范](references\u002Fextending.md) 复用已有入口、补充有针对性的样例和证据，再更新验证状态。\n\n本包版本及本地维护边界见 [维护说明](references\u002Fmaintenance.md)，使用与分发遵循 [MIT 许可](references\u002Flicense.txt)。\n",{"name":5,"license":15,"metadata":24,"description":7},{"version":25},"1.1.1","master","fd76f882a04e445e899d5cfb2732f2105ea054ee","skills\u002Fmarketplace\u002Fsoftware-testing-router",0,"https:\u002F\u002Fgithub.com\u002Fbg-szy\u002FTOP-SKILLS","https:\u002F\u002Fbg-szy.github.io\u002FTOP-SKILLS\u002F","https:\u002F\u002Fgithub.com\u002Fbg-szy","https:\u002F\u002Fwww.ecust.edu.cn\u002F","a student of East China University of Science and Technology","2026-11-15 03:38:02",{"source":8,"skillName":5,"commands":37,"prompt":47,"zipAvailable":48},[38,41,44],{"tool":39,"command":40},"npx","npx skills add bg-szy\u002FTOP-SKILLS --skill software-testing-router",{"tool":42,"command":43},"bunx","bunx skills add bg-szy\u002FTOP-SKILLS --skill software-testing-router",{"tool":45,"command":46},"pnpm","pnpm dlx skills add bg-szy\u002FTOP-SKILLS --skill software-testing-router","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002Fbg-szy\u002FTOP-SKILLS\u002Fblob\u002Fmaster\u002Fskills\u002Fmarketplace\u002Fsoftware-testing-router\u002FSKILL.md",true,[50],{"path":51,"resourceType":52,"resourceTypeDesc":53,"sizeBytes":54,"sourceHtmlUrl":55},"skill-report.json","REFERENCE","参考文档",137033,"https:\u002F\u002Fgithub.com\u002Fbg-szy\u002FTOP-SKILLS\u002Fblob\u002Fmaster\u002Fskills\u002Fmarketplace\u002Fsoftware-testing-router\u002Fskill-report.json",[57,65,72,79,86,93],{"skillNo":58,"name":59,"nameZh":6,"description":60,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":61,"categories":62,"keywords":63,"publishedAt":64},"01M7DXW9N826PKXK174PVW3038","serpmaven","Scrape Google search results (SERP) to JSON with SERP Maven (serpmaven) - a real Chrome browser on a residential proxy with sticky sessions. Run it as a CLI, a Python library, a local HTTP search API (`serve`), an MCP server or a Docker image; set the proxy login, workers, pages and cost tracking. Use when the user wants Google results, rank tracking, a self-hosted SERP API, or live Google search for an AI agent.","https:\u002F\u002Fgithub.com\u002Fbg-szy\u002FTOP-SKILLS\u002Fblob\u002Fmaster\u002Fskills\u002Fmarketplace\u002Fserpmaven\u002FSKILL.md",[],[],"2026-11-15 14:19:17",{"skillNo":66,"name":67,"nameZh":6,"description":68,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":69,"categories":70,"keywords":71,"publishedAt":64},"01M7DXVHSTWDV65475QEQ915M7","revnu-landing-page-audit","Find out why a landing page isn't turning visitors into signups, demos or sales. Audits one page against what the ad, post or search that sends people there promised, then checks the first screen, proof, call to action, friction and mobile. Returns at most 7 prioritized fixes, plus what is fine and what could not be checked; rewrites specific lines and fixes the page in the repo when asked. Never promises a conversion lift. Works without a Revnu account. Use when the user says or asks: \"audit my landing page\", \"why isn't this page converting\", \"review my homepage\", \"my ads get clicks but no signups\", \"people bounce from the pricing page\", \"CRO review\", \"improve conversion rate\", \"is my hero section clear\", \"roast my landing page\", \"rewrite my headline\", \"what's wrong with this page\", \"landing page feedback\", \"make the signup page convert better\". Not for SEO or AI-search audits, page speed engineering on its own, or building a new page from scratch.","https:\u002F\u002Fgithub.com\u002Fbg-szy\u002FTOP-SKILLS\u002Fblob\u002Fmaster\u002Fskills\u002Fmarketplace\u002Frevnu-landing-page-audit\u002FSKILL.md",[],[],{"skillNo":73,"name":74,"nameZh":6,"description":75,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":76,"categories":77,"keywords":78,"publishedAt":64},"01M7DXV8X2D7B3VTD4HHYYHTGR","revnu-growth-context","Write down once who buys, what they're stuck on, what it costs, what proof you have and what you've already tried, so every growth task starts from facts instead of a questionnaire. Creates or updates .agents\u002Frevnu-growth.md from the repo, the live site and the user, and imports an existing product-marketing.md. Use when the user says \"set up our marketing context\", \"who is our ideal customer\", \"write our ICP\", \"describe the product for marketing\", \"positioning doc\", \"what's our brand voice\", \"remember this about our customers\", \"log what we tried\", \"what have we learned from marketing\", \"we changed pricing, update the context\", \"update our growth notes\", \"summarize the business for the agent\", \"import my product-marketing.md\", \"start a growth doc\", or before a first marketing, SEO, outreach or launch task when no context file exists. Works without a Revnu account.","https:\u002F\u002Fgithub.com\u002Fbg-szy\u002FTOP-SKILLS\u002Fblob\u002Fmaster\u002Fskills\u002Fmarketplace\u002Frevnu-growth-context\u002FSKILL.md",[],[],{"skillNo":80,"name":81,"nameZh":6,"description":82,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":83,"categories":84,"keywords":85,"publishedAt":64},"01M7DXV0DGJ1G0A60PAHC6J3C5","revnu-get-listed","Get onto the third-party pages AI answers and search cite when buyers ask for the best tool in your category: \"best X\" roundups, directories, review sites, GitHub awesome lists, community threads and comparison pages. Finds which ones are cited, ranks them by fit and effort, and drafts each submission, PR or pitch by the target's own rules. Use when the user says \"get us listed\", \"which directories should we submit to\", \"how do we get into best-of lists\", \"why does ChatGPT recommend competitors and not us\", \"get mentioned in AI answers\", \"submit to awesome lists\", \"get on G2\", \"where are our competitors listed\", \"pitch listicle authors\", \"find backlink opportunities\", \"launch directories\", \"get into roundups\", \"Product Hunt alternatives\", \"where should we be listed\", \"get cited by Perplexity\". Never submits, pays or posts without a yes. Works without a Revnu account.","https:\u002F\u002Fgithub.com\u002Fbg-szy\u002FTOP-SKILLS\u002Fblob\u002Fmaster\u002Fskills\u002Fmarketplace\u002Frevnu-get-listed\u002FSKILL.md",[],[],{"skillNo":87,"name":88,"nameZh":6,"description":89,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":90,"categories":91,"keywords":92,"publishedAt":64},"01M7DXTSPMGT9D6DSS0HP9BSTA","revnu-ai-readiness-audit","Audit whether your website gives ChatGPT, Perplexity, Claude, Gemini and Google's AI Overviews something worth quoting, and fix the pages that don't. Use when the user says or asks \"is my site ready for AI search\", \"audit my site for AI answers\", \"AEO audit\", \"GEO audit\", \"why doesn't ChatGPT quote our pricing\", \"make our pages citable by AI\", \"do I need llms.txt\", \"does schema help with ChatGPT\", \"check our structured data\", \"is our content visible without JavaScript\", \"AI SEO audit\", \"optimize our homepage for AI answers\", \"LLM SEO check\", \"why does AI get our product wrong\", \"fix our site for AI Overviews\". Checks fetchability and indexability, answers in the raw HTML, entity facts, schema (including JS-injected markup), headings, dates and llms.txt, then gives at most 10 prioritised fixes and edits the repo when asked. Works without a Revnu account.","https:\u002F\u002Fgithub.com\u002Fbg-szy\u002FTOP-SKILLS\u002Fblob\u002Fmaster\u002Fskills\u002Fmarketplace\u002Frevnu-ai-readiness-audit\u002FSKILL.md",[],[],{"skillNo":94,"name":95,"nameZh":6,"description":96,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":97,"categories":98,"keywords":99,"publishedAt":64},"01M7DXSZHCVTRS620GC3S97JZV","proxy-troubleshooting","Diagnose residential proxy failures, with NodeMaven's gateway as the reference - 407 with correct credentials, 406, 410, 500, a connection that hangs, ERR_TUNNEL_CONNECTION_FAILED in a browser, Playwright or Puppeteer ignoring proxy credentials, a sticky session that changes IP, geo-targeting that is silently ignored, passwords with special characters, and unexpected traffic from headless Chrome. Use when a proxy connection fails, returns the wrong location, or costs more traffic than expected.","https:\u002F\u002Fgithub.com\u002Fbg-szy\u002FTOP-SKILLS\u002Fblob\u002Fmaster\u002Fskills\u002Fmarketplace\u002Fproxy-troubleshooting\u002FSKILL.md",[],[]]