[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M6BXNA2SWVRKFNX289JKKM4G":3,"skill-same:01M6BXNA2SWVRKFNX289JKKM4G":82},{"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":30,"publishedAt":54,"linkOnly":55,"markdownContent":56,"markdownBody":57,"frontMatter":58,"refName":60,"commitSha":61,"skillDirectory":62,"forksCount":63,"repositoryHtmlUrl":64,"repositoryHomepageUrl":6,"ownerHtmlUrl":65,"ownerBlogUrl":6,"ownerDescription":66,"updatedAt":67,"install":68,"resources":81},"01M6BXNA2SWVRKFNX289JKKM4G","go-binance-mcp-http-api-mirror",null,"Maintain the go_binance_futures Streamable HTTP MCP server when its explicit REST allowlist, JWT forwarding, transport, or documentation changes. Use for adding or removing categorized MCP tools while ensuring unrelated HTTP routes remain unexposed and conf\u002Fapp.conf stays untouched.","sorry510\u002Fgo_binance_futures","sorry510","https:\u002F\u002Favatars.githubusercontent.com\u002Fu\u002F19152210?v=4","01M6BXN7R4CADT83P4NDJBFSBQ","01M6BXN7W8QZGQGWPXHYC23B56",255,"MIT","https:\u002F\u002Fgithub.com\u002Fsorry510\u002Fgo_binance_futures\u002Fblob\u002Fmaster\u002F.claude\u002Fskills\u002Fgo-binance-mcp-http-api-mirror\u002FSKILL.md",[17,22,25],{"categoryNo":18,"categoryName":19,"taxonomyType":20,"taxonomyTypeDesc":21},"01JBSEEDCAT000000000000010","后端与接口","SCENARIO","使用场景",{"categoryNo":23,"categoryName":24,"taxonomyType":20,"taxonomyTypeDesc":21},"01JBSEEDCAT000000000000023","Skill与智能体开发",{"categoryNo":26,"categoryName":27,"taxonomyType":28,"taxonomyTypeDesc":29},"01JBSEEDCAT000000000000030","开发工程师","PROFESSION","适用职业",[31,32,33,34,35,36,37,38,39,40,41,42,43,44,45,46,47,48,49,50,51,52,53],"go","api mirror","mirror","http api","binance","go binance mcp http api mirror","api","http","MCP","futures","REST","Tools","jwt","server","mcp tools","use","maintain","app","false","documentation","mcp server","for","when","2026-11-10 10:12:30",false,"---\nname: go-binance-mcp-http-api-mirror\ndescription: Maintain the go_binance_futures Streamable HTTP MCP server when its explicit REST allowlist, JWT forwarding, transport, or documentation changes. Use for adding or removing categorized MCP tools while ensuring unrelated HTTP routes remain unexposed and conf\u002Fapp.conf stays untouched.\nversion: 1.0.0\ntrusted: false\n---\n\n# Go Binance MCP HTTP API Mirror\n\nUse this workflow when adding or changing MCP coverage in `\u002FUsers\u002Fzhz\u002Fwork\u002Fbinance\u002Fgo_binance_futures`.\n\n1. Read `routers\u002Frouter.go`, `mcpserver\u002F`, `middlewares\u002Fauth.go`, and the relevant controller inputs. Establish the user-approved MCP allowlist before editing; never infer that every non-login route should be exposed.\n2. Keep only explicitly allowed, stable, categorized tools in `mcpserver\u002Fapi_tools.go`. Keep tool paths fixed in code; never accept an arbitrary target URL. Use `path_params`, `query`, and `body` to preserve each allowed REST contract.\n3. Keep MCP transport Streamable HTTP only at `\u002Fmcp`. Do not add stdio, command, or a separate local port. Require the existing login JWT and forward the incoming `Authorization` header to the internal HTTP call.\n4. Do not register MCP-specific notification, scanner, system, account, order, or other privileged tools unless the user explicitly adds them to the allowlist. Removing an MCP-only notification tool also removes its dedicated adapter and template while preserving the project's ordinary notification services.\n5. Test the exact tool-name and method\u002Fpath allowlist, confirm every allowed operation still exists in `routers\u002Frouter.go`, and ensure unrelated routes are not required or auto-exposed. Also test `tools\u002Flist`, an actual allowed `tools\u002Fcall`, Authorization propagation, and internal HTTP request construction.\n6. Run MCP tests from an isolated `\u002Ftmp` config and language directory. Compile from the repository, but never modify or use the real `conf\u002Fapp.conf` as test setup. Bind only a temporary localhost port for Streamable HTTP protocol tests.\n7. Update `doc\u002Fmcp.md` with endpoint, JWT setup, common arguments, the exact current allowlist, removed tool groups, and destructive-operation warnings. Verify every registered tool appears in the document and deleted tool names do not remain.\n8. Finish with `git diff --check`, focused `go vet`, a main-package compile-only check, an exact residual route\u002Ftool comparison, and `git diff --exit-code -- conf\u002Fapp.conf`. Preserve unrelated worktree changes.\n","# Go Binance MCP HTTP API Mirror\n\nUse this workflow when adding or changing MCP coverage in `\u002FUsers\u002Fzhz\u002Fwork\u002Fbinance\u002Fgo_binance_futures`.\n\n1. Read `routers\u002Frouter.go`, `mcpserver\u002F`, `middlewares\u002Fauth.go`, and the relevant controller inputs. Establish the user-approved MCP allowlist before editing; never infer that every non-login route should be exposed.\n2. Keep only explicitly allowed, stable, categorized tools in `mcpserver\u002Fapi_tools.go`. Keep tool paths fixed in code; never accept an arbitrary target URL. Use `path_params`, `query`, and `body` to preserve each allowed REST contract.\n3. Keep MCP transport Streamable HTTP only at `\u002Fmcp`. Do not add stdio, command, or a separate local port. Require the existing login JWT and forward the incoming `Authorization` header to the internal HTTP call.\n4. Do not register MCP-specific notification, scanner, system, account, order, or other privileged tools unless the user explicitly adds them to the allowlist. Removing an MCP-only notification tool also removes its dedicated adapter and template while preserving the project's ordinary notification services.\n5. Test the exact tool-name and method\u002Fpath allowlist, confirm every allowed operation still exists in `routers\u002Frouter.go`, and ensure unrelated routes are not required or auto-exposed. Also test `tools\u002Flist`, an actual allowed `tools\u002Fcall`, Authorization propagation, and internal HTTP request construction.\n6. Run MCP tests from an isolated `\u002Ftmp` config and language directory. Compile from the repository, but never modify or use the real `conf\u002Fapp.conf` as test setup. Bind only a temporary localhost port for Streamable HTTP protocol tests.\n7. Update `doc\u002Fmcp.md` with endpoint, JWT setup, common arguments, the exact current allowlist, removed tool groups, and destructive-operation warnings. Verify every registered tool appears in the document and deleted tool names do not remain.\n8. Finish with `git diff --check`, focused `go vet`, a main-package compile-only check, an exact residual route\u002Ftool comparison, and `git diff --exit-code -- conf\u002Fapp.conf`. Preserve unrelated worktree changes.\n",{"name":5,"trusted":55,"version":59,"description":7},"1.0.0","master","9ffe4f5dee0927e2c656589a0ede070fc0f1e56e",".claude\u002Fskills\u002Fgo-binance-mcp-http-api-mirror",57,"https:\u002F\u002Fgithub.com\u002Fsorry510\u002Fgo_binance_futures","https:\u002F\u002Fgithub.com\u002Fsorry510","freedom","2026-11-11 22:43:32",{"source":8,"skillName":5,"commands":69,"prompt":79,"zipAvailable":80},[70,73,76],{"tool":71,"command":72},"npx","npx skills add sorry510\u002Fgo_binance_futures --skill go-binance-mcp-http-api-mirror",{"tool":74,"command":75},"bunx","bunx skills add sorry510\u002Fgo_binance_futures --skill go-binance-mcp-http-api-mirror",{"tool":77,"command":78},"pnpm","pnpm dlx skills add sorry510\u002Fgo_binance_futures --skill go-binance-mcp-http-api-mirror","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002Fsorry510\u002Fgo_binance_futures\u002Fblob\u002Fmaster\u002F.claude\u002Fskills\u002Fgo-binance-mcp-http-api-mirror\u002FSKILL.md",true,[],[83,98,117],{"skillNo":84,"name":85,"nameZh":6,"description":86,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":9,"repositoryNo":12,"starsCount":13,"licenseSpdxId":87,"licenseFileUrl":6,"sourceHtmlUrl":88,"categories":89,"keywords":90,"publishedAt":54},"01M6BXNHZ8H45NQ9YHXWM06RD0","valid-resources","Use a bundled reference when a task needs the fixture policy.","Apache-2.0","https:\u002F\u002Fgithub.com\u002Fsorry510\u002Fgo_binance_futures\u002Fblob\u002Fmaster\u002Fagent\u002Fportableskill\u002Ftestdata\u002Fvalid-resources\u002FSKILL.md",[],[91,92,93,94,46,95,96,97,53],"resources","valid resources","valid","policy","reference","task","fixture",{"skillNo":99,"name":100,"nameZh":6,"description":101,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":9,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":102,"categories":103,"keywords":104,"publishedAt":54},"01M6BXNFZ65QVYA6P9TZ6F4XZC","valid-minimal","Summarize a user request. Use when a concise structured summary is needed.","https:\u002F\u002Fgithub.com\u002Fsorry510\u002Fgo_binance_futures\u002Fblob\u002Fmaster\u002Fagent\u002Fportableskill\u002Ftestdata\u002Fvalid-minimal\u002FSKILL.md",[],[105,106,93,107,108,109,110,111,53,46,112,113,114,115,116],"minimal","valid minimal","get","user request","condition","concise","request","structured","summary","Market","user","summarize",{"skillNo":118,"name":119,"nameZh":6,"description":120,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":9,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":121,"categories":122,"keywords":123,"publishedAt":54},"01M6BXNDAZZRA5E7BS3HCTH1MA","go-binance-web-notification","Implement and verify persisted browser notifications with authenticated WebSocket delivery across go_binance_futures and go_binance_futrues_new_ui.","https:\u002F\u002Fgithub.com\u002Fsorry510\u002Fgo_binance_futures\u002Fblob\u002Fmaster\u002F.claude\u002Fskills\u002Fgo-binance-web-notification\u002FSKILL.md",[],[124,31,125,35,126,127,128,129,130,131,132,40,133,134,135,136],"web","go binance web notification","notification","new","with","across","delivery","verify","websocket","notifications","ui","browser","implement"]