[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M6GX99N3B4R3JB07RT2XSJ1H":3,"skill-same:01M6GX99N3B4R3JB07RT2XSJ1H":132},{"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":16,"sourceHtmlUrl":17,"categories":18,"keywords":32,"publishedAt":55,"linkOnly":56,"markdownContent":57,"markdownBody":58,"frontMatter":59,"refName":65,"commitSha":66,"skillDirectory":67,"forksCount":68,"repositoryHtmlUrl":69,"repositoryHomepageUrl":6,"ownerHtmlUrl":70,"ownerBlogUrl":71,"ownerDescription":72,"updatedAt":73,"install":74,"resources":87},"01M6GX99N3B4R3JB07RT2XSJ1H","square-post",null,"Use when the user wants to publish new content to Binance Square — short text, multi-image\nposts (up to 4), long-form articles with an optional cover, or videos with an auto-generated\ncover frame. Trigger on direct phrasings like \"post to Square\", \"publish to Binance Square\",\n\"发广场\", \"发布到广场\", and on near-miss intents where the user clearly wants to share or\npublish content on Square even without naming the skill: \"share this analysis on Square\",\n\"把这篇文章发出去\", \"发个动态\", \"把这个视频上传到广场\", \"publish my chart to Square as an\narticle\". Also use when the user provides media (images, video) plus a caption and asks to\npush it to Square, or asks to turn a draft into a Square article. Do not use for reading,\nsearching, commenting, liking, editing, deleting, scheduling, or managing existing Square\nposts — this skill only creates new posts.","jiayaoqijia\u002Fcryptoskill","jiayaoqijia","https:\u002F\u002Favatars.githubusercontent.com\u002Fu\u002F1453879?v=4","01M6GMYTX7Q7S504VC6E756ENR","YQ","01M6GMYV1QKJ1CC75MTTGT9PR0",80,"MIT","https:\u002F\u002Fgithub.com\u002Fjiayaoqijia\u002Fcryptoskill\u002Fblob\u002Fmain\u002Fskills\u002Fmcp-servers\u002Fxinyuzjj-square-post\u002FLICENSE","https:\u002F\u002Fgithub.com\u002Fjiayaoqijia\u002Fcryptoskill\u002Fblob\u002Fmain\u002Fskills\u002Fmcp-servers\u002Fxinyuzjj-square-post\u002FSKILL.md",[19,24,27],{"categoryNo":20,"categoryName":21,"taxonomyType":22,"taxonomyTypeDesc":23},"01JBSEEDCAT000000000000016","图像与多媒体","SCENARIO","使用场景",{"categoryNo":25,"categoryName":26,"taxonomyType":22,"taxonomyTypeDesc":23},"01JBSEEDCAT000000000000023","Skill与智能体开发",{"categoryNo":28,"categoryName":29,"taxonomyType":30,"taxonomyTypeDesc":31},"01JBSEEDCAT000000000000036","内容创作者","PROFESSION","适用职业",[33,34,35,36,37,38,39,40,41,42,43,44,45,46,47,48,49,50,51,52,53,54],"square post","post","square","up","new","when","near","posts","auto-generated","chart","images","image","only","auto","generated","short","text","Bash","Media","Video","analysis","publish","2026-11-10 10:12:30",false,"---\nname: square-post\ndescription: |\n  Use when the user wants to publish new content to Binance Square — short text, multi-image\n  posts (up to 4), long-form articles with an optional cover, or videos with an auto-generated\n  cover frame. Trigger on direct phrasings like \"post to Square\", \"publish to Binance Square\",\n  \"发广场\", \"发布到广场\", and on near-miss intents where the user clearly wants to share or\n  publish content on Square even without naming the skill: \"share this analysis on Square\",\n  \"把这篇文章发出去\", \"发个动态\", \"把这个视频上传到广场\", \"publish my chart to Square as an\n  article\". Also use when the user provides media (images, video) plus a caption and asks to\n  push it to Square, or asks to turn a draft into a Square article. Do not use for reading,\n  searching, commenting, liking, editing, deleting, scheduling, or managing existing Square\n  posts — this skill only creates new posts.\nallowed-tools:\n  - Bash\nmetadata:\n  author: binance-square\n  version: \"2.0.0\"\n---\n\n# Square Post Skill\n\n## Purpose\n\nPublish new content to Binance Square by running the local scripts in `scripts\u002F`.\n\nSupported post types:\n- Text-only short posts\n- Image posts with up to 4 images\n- Long articles with a title and optional cover image\n- Video posts with an auto-generated cover image\n\nDo not hand-code API requests for normal posting. The scripts own upload, polling, cover generation, and publish behavior.\n\n## Runtime Dependencies\n\n- Node.js 18 or newer. The scripts use native ES modules and the built-in `fetch` API.\n- `ffmpeg` is required for video posts because `post-video.mjs` extracts the first frame as the cover image.\n- `ffprobe` is required when a video duration is not provided by the user.\n- Network access is required for Binance Square OpenAPI requests and presigned media uploads.\n\n## Authentication\n\nPosting requires a Binance Square OpenAPI key.\n\nBefore posting:\n- Prefer `BINANCE_SQUARE_OPENAPI_KEY` from the user's environment if present.\n- If it is not present, the scripts automatically check `~\u002F.config\u002Fbinance-square\u002Fopenapi-key`.\n- If no valid key is found, ask the user to provide an API key first.\n- If the user wants to reuse the key in future requests, save it with `BINANCE_SQUARE_OPENAPI_KEY=\u003CapiKey> node scripts\u002Fsave-key.mjs`; otherwise use it only for the current command environment.\n- Tell the user they can create an API key at: https:\u002F\u002Fwww.binance.com\u002Fsquare\u002Fcreator-center\u002Fhome\n\nPass the key only via `BINANCE_SQUARE_OPENAPI_KEY` (env or saved file). Never write it into command arguments or print the full key — CLI args appear in `ps` output and shell history. When mentioning a key, show only the first 5 and last 4 characters, such as `abc12...xyz9`.\n\n## Scripts\n\nAll commands should be run from this skill directory.\n\n### Text Or Article Post\n\nUse for text-only short posts or long articles without images.\n\n```bash\nnode scripts\u002Fpost-text.mjs --text \"Hello #crypto $BTC\"\n```\n\nLong article with title and no cover:\n\n```bash\nnode scripts\u002Fpost-text.mjs --text \"Full article body...\" --title \"Market Report\"\n```\n\nFlags:\n- `--text` required, post text content\n- `--title` optional, sets article-style content\n\n### Long Content: Use `--text-file` \u002F `--title-file` (strongly recommended for Agent)\n\nMulti-paragraph content with newlines\u002Fquotes breaks shell argument parsing\n(`命令解析失败（检查引号）`). `cli.mjs` supports reading content from files —\nwrite the body to a file first, then pass the path. This is the ONLY reliable\nway to post long Chinese articles.\n\n```bash\nnode scripts\u002Fcli.mjs text --text-file .\u002Fdraft.md --title \"Article Title\"\nnode scripts\u002Fcli.mjs text --title-file .\u002Ftitle.txt --text-file .\u002Fdraft.md\n```\n\nFlags:\n- `--text-file \u003Cpath>` read post\u002Farticle body from file (replaces `--text`)\n- `--title-file \u003Cpath>` read article title from file (replaces `--title`)\n\n### Image Post\n\nUse for short image posts or long articles with a cover image.\n\n```bash\nnode scripts\u002Fpost-image.mjs --text \"Chart analysis\" --images \".\u002Fchart1.png,.\u002Fchart2.png\"\n```\n\nLong article with title and cover:\n\n```bash\nnode scripts\u002Fpost-image.mjs --text \"Full analysis...\" --title \"Market Report\" --cover \".\u002Fchart.png\"\n```\n\nFlags:\n- `--text` required, post or article content\n- `--images` required for short image posts only. Use comma-separated image paths with max 4.\n- `--title` optional, sets article-style content. When present, do not pass `--images`.\n- `--cover` required when `--title` is present for an article with media. Article mode supports exactly one cover image.\n\nThe script uploads each image, waits for processing, and publishes with the processed image URL returned by the backend. If `--title` is provided, it publishes `contentType=2`, requires `--cover`, and sends that uploaded image URL as `cover` only. If no `--title` is provided, it publishes `contentType=1` and sends all `--images` as `imageList`.\n\n### Video Post\n\nUse for video posts.\n\n```bash\nnode scripts\u002Fpost-video.mjs --video \".\u002Fvideo.mp4\" --duration 7.5 --text \"My analysis\"\n```\n\nFlags:\n- `--video` required, local video path\n- `--duration` required, video duration in seconds\n- `--text` optional, post text content\n\nThe script uploads the video, waits for processing, extracts the first frame with `ffmpeg`, uploads that frame as the cover image, and publishes with `cover` included in the request.\n\nIf the user does not provide a duration, use `ffprobe` to determine it before running the script.\n\n## Agent Workflow\n\n1. Resolve the API key (see Authentication). If unresolved, stop and ask the user before doing anything else.\n\n2. Pick the script from user intent using the table below. Then validate against Constraints — if a constraint is violated, explain it and do not run.\n\n   | User intent | Script | Required flags |\n   |---|---|---|\n   | Short text post | `post-text.mjs` | `--text` |\n   | Long article, no media | `post-text.mjs` | `--text --title` |\n   | Image short post (1–4 imgs, no title) | `post-image.mjs` | `--text --images \"\u003Cp1,p2,...>\"` |\n   | Article with cover | `post-image.mjs` | `--text --title --cover` |\n   | Video post | `post-video.mjs` | `--video --duration` (+ optional `--text`) |\n\n3. Disambiguate edge cases before running:\n   - Title + exactly one image → that image is the cover (`--cover`, not `--images`).\n   - Title + multiple images → stop and ask which single image is the cover.\n   - Video without duration → run `ffprobe` first to get it.\n\n4. Preserve user content exactly. Do not rewrite, translate, add hashtags\u002Fcashtags, or change punctuation. `$coin` and `#topic` text passes through verbatim — the backend parses them.\n\n5. Run the script with `BINANCE_SQUARE_OPENAPI_KEY` injected into the command environment for one-time use (never as a CLI arg).\n\n6. Report the result:\n   - On success, return the `ID` and `Link` printed by the script.\n   - If the script prints `Success!` with `ID: unavailable` and `Link: unavailable`, treat it as successful — `\u002Fcontent\u002Fadd` returned 504 after submission, so no post ID or link is available.\n   - On failure, surface the script error and any API code\u002Fmessage.\n\n## Constraints\n\n- Images: max 4 per post; article cover is exactly 1 image.\n- Video: max 1 per post.\n- Images and video are mutually exclusive in a single post.\n- Only attach media the user explicitly provided; do not auto-attach.\n- Do not modify user-provided text. `#topic` and `$coin` are parsed server-side.\n- Daily limits: 100 posts\u002Fday, 400 uploads\u002Fday.\n\n## Common Errors\n\n- `220003`: API key not found.\n- `220004`: API key expired.\n- `220009`: Daily post limit exceeded for OpenAPI.\n- `220014`: Daily upload limit exceeded.\n- `20002` or `20022`: Sensitive words detected.\n- `20013`: Content length is limited.\n- `20020` or `220011`: Content body must not be empty.\n- `30008`, `2000001`, or `2000002`: Account or device posting restriction.\n\n## Scope\n\nThis skill only supports publishing new posts. It does not support:\n- Reading, listing, or searching existing posts\n- Editing or deleting posts\n- Commenting, liking, or other interactions\n- User profile or account management\n- Scheduling or drafts\n","# Square Post Skill\n\n## Purpose\n\nPublish new content to Binance Square by running the local scripts in `scripts\u002F`.\n\nSupported post types:\n- Text-only short posts\n- Image posts with up to 4 images\n- Long articles with a title and optional cover image\n- Video posts with an auto-generated cover image\n\nDo not hand-code API requests for normal posting. The scripts own upload, polling, cover generation, and publish behavior.\n\n## Runtime Dependencies\n\n- Node.js 18 or newer. The scripts use native ES modules and the built-in `fetch` API.\n- `ffmpeg` is required for video posts because `post-video.mjs` extracts the first frame as the cover image.\n- `ffprobe` is required when a video duration is not provided by the user.\n- Network access is required for Binance Square OpenAPI requests and presigned media uploads.\n\n## Authentication\n\nPosting requires a Binance Square OpenAPI key.\n\nBefore posting:\n- Prefer `BINANCE_SQUARE_OPENAPI_KEY` from the user's environment if present.\n- If it is not present, the scripts automatically check `~\u002F.config\u002Fbinance-square\u002Fopenapi-key`.\n- If no valid key is found, ask the user to provide an API key first.\n- If the user wants to reuse the key in future requests, save it with `BINANCE_SQUARE_OPENAPI_KEY=\u003CapiKey> node scripts\u002Fsave-key.mjs`; otherwise use it only for the current command environment.\n- Tell the user they can create an API key at: https:\u002F\u002Fwww.binance.com\u002Fsquare\u002Fcreator-center\u002Fhome\n\nPass the key only via `BINANCE_SQUARE_OPENAPI_KEY` (env or saved file). Never write it into command arguments or print the full key — CLI args appear in `ps` output and shell history. When mentioning a key, show only the first 5 and last 4 characters, such as `abc12...xyz9`.\n\n## Scripts\n\nAll commands should be run from this skill directory.\n\n### Text Or Article Post\n\nUse for text-only short posts or long articles without images.\n\n```bash\nnode scripts\u002Fpost-text.mjs --text \"Hello #crypto $BTC\"\n```\n\nLong article with title and no cover:\n\n```bash\nnode scripts\u002Fpost-text.mjs --text \"Full article body...\" --title \"Market Report\"\n```\n\nFlags:\n- `--text` required, post text content\n- `--title` optional, sets article-style content\n\n### Long Content: Use `--text-file` \u002F `--title-file` (strongly recommended for Agent)\n\nMulti-paragraph content with newlines\u002Fquotes breaks shell argument parsing\n(`命令解析失败（检查引号）`). `cli.mjs` supports reading content from files —\nwrite the body to a file first, then pass the path. This is the ONLY reliable\nway to post long Chinese articles.\n\n```bash\nnode scripts\u002Fcli.mjs text --text-file .\u002Fdraft.md --title \"Article Title\"\nnode scripts\u002Fcli.mjs text --title-file .\u002Ftitle.txt --text-file .\u002Fdraft.md\n```\n\nFlags:\n- `--text-file \u003Cpath>` read post\u002Farticle body from file (replaces `--text`)\n- `--title-file \u003Cpath>` read article title from file (replaces `--title`)\n\n### Image Post\n\nUse for short image posts or long articles with a cover image.\n\n```bash\nnode scripts\u002Fpost-image.mjs --text \"Chart analysis\" --images \".\u002Fchart1.png,.\u002Fchart2.png\"\n```\n\nLong article with title and cover:\n\n```bash\nnode scripts\u002Fpost-image.mjs --text \"Full analysis...\" --title \"Market Report\" --cover \".\u002Fchart.png\"\n```\n\nFlags:\n- `--text` required, post or article content\n- `--images` required for short image posts only. Use comma-separated image paths with max 4.\n- `--title` optional, sets article-style content. When present, do not pass `--images`.\n- `--cover` required when `--title` is present for an article with media. Article mode supports exactly one cover image.\n\nThe script uploads each image, waits for processing, and publishes with the processed image URL returned by the backend. If `--title` is provided, it publishes `contentType=2`, requires `--cover`, and sends that uploaded image URL as `cover` only. If no `--title` is provided, it publishes `contentType=1` and sends all `--images` as `imageList`.\n\n### Video Post\n\nUse for video posts.\n\n```bash\nnode scripts\u002Fpost-video.mjs --video \".\u002Fvideo.mp4\" --duration 7.5 --text \"My analysis\"\n```\n\nFlags:\n- `--video` required, local video path\n- `--duration` required, video duration in seconds\n- `--text` optional, post text content\n\nThe script uploads the video, waits for processing, extracts the first frame with `ffmpeg`, uploads that frame as the cover image, and publishes with `cover` included in the request.\n\nIf the user does not provide a duration, use `ffprobe` to determine it before running the script.\n\n## Agent Workflow\n\n1. Resolve the API key (see Authentication). If unresolved, stop and ask the user before doing anything else.\n\n2. Pick the script from user intent using the table below. Then validate against Constraints — if a constraint is violated, explain it and do not run.\n\n   | User intent | Script | Required flags |\n   |---|---|---|\n   | Short text post | `post-text.mjs` | `--text` |\n   | Long article, no media | `post-text.mjs` | `--text --title` |\n   | Image short post (1–4 imgs, no title) | `post-image.mjs` | `--text --images \"\u003Cp1,p2,...>\"` |\n   | Article with cover | `post-image.mjs` | `--text --title --cover` |\n   | Video post | `post-video.mjs` | `--video --duration` (+ optional `--text`) |\n\n3. Disambiguate edge cases before running:\n   - Title + exactly one image → that image is the cover (`--cover`, not `--images`).\n   - Title + multiple images → stop and ask which single image is the cover.\n   - Video without duration → run `ffprobe` first to get it.\n\n4. Preserve user content exactly. Do not rewrite, translate, add hashtags\u002Fcashtags, or change punctuation. `$coin` and `#topic` text passes through verbatim — the backend parses them.\n\n5. Run the script with `BINANCE_SQUARE_OPENAPI_KEY` injected into the command environment for one-time use (never as a CLI arg).\n\n6. Report the result:\n   - On success, return the `ID` and `Link` printed by the script.\n   - If the script prints `Success!` with `ID: unavailable` and `Link: unavailable`, treat it as successful — `\u002Fcontent\u002Fadd` returned 504 after submission, so no post ID or link is available.\n   - On failure, surface the script error and any API code\u002Fmessage.\n\n## Constraints\n\n- Images: max 4 per post; article cover is exactly 1 image.\n- Video: max 1 per post.\n- Images and video are mutually exclusive in a single post.\n- Only attach media the user explicitly provided; do not auto-attach.\n- Do not modify user-provided text. `#topic` and `$coin` are parsed server-side.\n- Daily limits: 100 posts\u002Fday, 400 uploads\u002Fday.\n\n## Common Errors\n\n- `220003`: API key not found.\n- `220004`: API key expired.\n- `220009`: Daily post limit exceeded for OpenAPI.\n- `220014`: Daily upload limit exceeded.\n- `20002` or `20022`: Sensitive words detected.\n- `20013`: Content length is limited.\n- `20020` or `220011`: Content body must not be empty.\n- `30008`, `2000001`, or `2000002`: Account or device posting restriction.\n\n## Scope\n\nThis skill only supports publishing new posts. It does not support:\n- Reading, listing, or searching existing posts\n- Editing or deleting posts\n- Commenting, liking, or other interactions\n- User profile or account management\n- Scheduling or drafts\n",{"name":5,"metadata":60,"description":63,"allowed-tools":64},{"author":61,"version":62},"binance-square","2.0.0","Use when the user wants to publish new content to Binance Square — short text, multi-image\nposts (up to 4), long-form articles with an optional cover, or videos with an auto-generated\ncover frame. Trigger on direct phrasings like \"post to Square\", \"publish to Binance Square\",\n\"发广场\", \"发布到广场\", and on near-miss intents where the user clearly wants to share or\npublish content on Square even without naming the skill: \"share this analysis on Square\",\n\"把这篇文章发出去\", \"发个动态\", \"把这个视频上传到广场\", \"publish my chart to Square as an\narticle\". Also use when the user provides media (images, video) plus a caption and asks to\npush it to Square, or asks to turn a draft into a Square article. Do not use for reading,\nsearching, commenting, liking, editing, deleting, scheduling, or managing existing Square\nposts — this skill only creates new posts.\n",[50],"main","3df1d0d67b30ff15236561f8c0f9f06d33f42dfd","skills\u002Fmcp-servers\u002Fxinyuzjj-square-post",17,"https:\u002F\u002Fgithub.com\u002Fjiayaoqijia\u002Fcryptoskill","https:\u002F\u002Fgithub.com\u002Fjiayaoqijia","https:\u002F\u002Feth2030.com","Hardcore infra. Building @alt-research and applied cryptography.","2026-11-11 08:47:40",{"source":8,"skillName":5,"commands":75,"prompt":85,"zipAvailable":86},[76,79,82],{"tool":77,"command":78},"npx","npx skills add jiayaoqijia\u002Fcryptoskill --skill square-post",{"tool":80,"command":81},"bunx","bunx skills add jiayaoqijia\u002Fcryptoskill --skill square-post",{"tool":83,"command":84},"pnpm","pnpm dlx skills add jiayaoqijia\u002Fcryptoskill --skill square-post","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002Fjiayaoqijia\u002Fcryptoskill\u002Fblob\u002Fmain\u002Fskills\u002Fmcp-servers\u002Fxinyuzjj-square-post\u002FSKILL.md",true,[88,92,98,104,108,112,116,120,124,128],{"path":89,"resourceType":89,"resourceTypeDesc":90,"sizeBytes":91,"sourceHtmlUrl":16},"LICENSE","许可证",1065,{"path":93,"resourceType":94,"resourceTypeDesc":95,"sizeBytes":96,"sourceHtmlUrl":97},"README.md","REFERENCE","参考文档",2119,"https:\u002F\u002Fgithub.com\u002Fjiayaoqijia\u002Fcryptoskill\u002Fblob\u002Fmain\u002Fskills\u002Fmcp-servers\u002Fxinyuzjj-square-post\u002FREADME.md",{"path":99,"resourceType":100,"resourceTypeDesc":101,"sizeBytes":102,"sourceHtmlUrl":103},"scripts\u002Fcli.mjs","SCRIPT","脚本",6460,"https:\u002F\u002Fgithub.com\u002Fjiayaoqijia\u002Fcryptoskill\u002Fblob\u002Fmain\u002Fskills\u002Fmcp-servers\u002Fxinyuzjj-square-post\u002Fscripts\u002Fcli.mjs",{"path":105,"resourceType":100,"resourceTypeDesc":101,"sizeBytes":106,"sourceHtmlUrl":107},"scripts\u002Flib.mjs",6915,"https:\u002F\u002Fgithub.com\u002Fjiayaoqijia\u002Fcryptoskill\u002Fblob\u002Fmain\u002Fskills\u002Fmcp-servers\u002Fxinyuzjj-square-post\u002Fscripts\u002Flib.mjs",{"path":109,"resourceType":100,"resourceTypeDesc":101,"sizeBytes":110,"sourceHtmlUrl":111},"scripts\u002Fpost-image.mjs",2360,"https:\u002F\u002Fgithub.com\u002Fjiayaoqijia\u002Fcryptoskill\u002Fblob\u002Fmain\u002Fskills\u002Fmcp-servers\u002Fxinyuzjj-square-post\u002Fscripts\u002Fpost-image.mjs",{"path":113,"resourceType":100,"resourceTypeDesc":101,"sizeBytes":114,"sourceHtmlUrl":115},"scripts\u002Fpost-text.mjs",1092,"https:\u002F\u002Fgithub.com\u002Fjiayaoqijia\u002Fcryptoskill\u002Fblob\u002Fmain\u002Fskills\u002Fmcp-servers\u002Fxinyuzjj-square-post\u002Fscripts\u002Fpost-text.mjs",{"path":117,"resourceType":100,"resourceTypeDesc":101,"sizeBytes":118,"sourceHtmlUrl":119},"scripts\u002Fpost-video.mjs",3214,"https:\u002F\u002Fgithub.com\u002Fjiayaoqijia\u002Fcryptoskill\u002Fblob\u002Fmain\u002Fskills\u002Fmcp-servers\u002Fxinyuzjj-square-post\u002Fscripts\u002Fpost-video.mjs",{"path":121,"resourceType":100,"resourceTypeDesc":101,"sizeBytes":122,"sourceHtmlUrl":123},"scripts\u002Fsave-key.mjs",948,"https:\u002F\u002Fgithub.com\u002Fjiayaoqijia\u002Fcryptoskill\u002Fblob\u002Fmain\u002Fskills\u002Fmcp-servers\u002Fxinyuzjj-square-post\u002Fscripts\u002Fsave-key.mjs",{"path":125,"resourceType":94,"resourceTypeDesc":95,"sizeBytes":126,"sourceHtmlUrl":127},"SOURCE.md",345,"https:\u002F\u002Fgithub.com\u002Fjiayaoqijia\u002Fcryptoskill\u002Fblob\u002Fmain\u002Fskills\u002Fmcp-servers\u002Fxinyuzjj-square-post\u002FSOURCE.md",{"path":129,"resourceType":94,"resourceTypeDesc":95,"sizeBytes":130,"sourceHtmlUrl":131},"TRUST.auto.yaml",2257,"https:\u002F\u002Fgithub.com\u002Fjiayaoqijia\u002Fcryptoskill\u002Fblob\u002Fmain\u002Fskills\u002Fmcp-servers\u002Fxinyuzjj-square-post\u002FTRUST.auto.yaml",[133,160,183,201,214,224],{"skillNo":134,"name":135,"nameZh":6,"description":136,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":137,"sourceHtmlUrl":138,"categories":139,"keywords":140,"publishedAt":55},"01M712C436EQYE43342Q4E7GG1","recipe-performance","Diagnose a specific MetaMask user flow's real-app performance and Sentry critical-user-flow telemetry with deterministic mm-harness recipes. Use for CUF boundaries, cold\u002Fwarm\u002Fbackground-resume behavior, latency regressions, lifecycle tags, duplicate or blocking network requests, long tasks, layout\u002Fpaint cost, screen redraws, React rerenders, or browser trace analysis where tests alone cannot prove the real app.","https:\u002F\u002Fgithub.com\u002Fjiayaoqijia\u002Fcryptoskill\u002Fblob\u002Fmain\u002Fskills\u002Fwallets\u002Fmetamask-official-recipe-performance\u002FLICENSE","https:\u002F\u002Fgithub.com\u002Fjiayaoqijia\u002Fcryptoskill\u002Fblob\u002Fmain\u002Fskills\u002Fwallets\u002Fmetamask-official-recipe-performance\u002FSKILL.md",[],[141,142,143,144,145,146,147,148,149,150,151,152,53,153,154,155,156,157,158,159],"performance","recipe performance","recipe","mm","sentry","harness","app","deterministic","recipes","flow","cold","critical","tasks","react","browser","layout","screen","network","metamask",{"skillNo":161,"name":162,"nameZh":6,"description":163,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":164,"licenseFileUrl":165,"sourceHtmlUrl":166,"categories":167,"keywords":168,"publishedAt":55},"01M70XT2F8A5CQZ81JBP98KSW3","mexc-spot-websocket","MEXC Spot WebSocket workflows for public streams, protobuf handling, depth maintenance, listen keys, and private streams without exposing API keys.","Apache-2.0","https:\u002F\u002Fgithub.com\u002Fjiayaoqijia\u002Fcryptoskill\u002Fblob\u002Fmain\u002Fskills\u002Fexchanges\u002Fmncrftfrcnm-mexc-spot-websocket\u002FLICENSE","https:\u002F\u002Fgithub.com\u002Fjiayaoqijia\u002Fcryptoskill\u002Fblob\u002Fmain\u002Fskills\u002Fexchanges\u002Fmncrftfrcnm-mexc-spot-websocket\u002FSKILL.md",[],[169,170,171,172,173,174,175,176,177,178,179,180,181,182],"mexc spot websocket","spot","websocket","api","workflows","public","listen","streams","depth","keys","for","api keys","maintenance","protobuf",{"skillNo":184,"name":185,"nameZh":6,"description":186,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":164,"licenseFileUrl":187,"sourceHtmlUrl":188,"categories":189,"keywords":190,"publishedAt":55},"01M70XT0MBXN3WZY1BKN0CPNKR","mexc-spot-rest","MEXC Spot REST workflows for public data, signed account requests, orders, wallet\u002Fadmin actions, and secure signing without exposing API keys.","https:\u002F\u002Fgithub.com\u002Fjiayaoqijia\u002Fcryptoskill\u002Fblob\u002Fmain\u002Fskills\u002Fexchanges\u002Fmncrftfrcnm-mexc-spot-rest\u002FLICENSE","https:\u002F\u002Fgithub.com\u002Fjiayaoqijia\u002Fcryptoskill\u002Fblob\u002Fmain\u002Fskills\u002Fexchanges\u002Fmncrftfrcnm-mexc-spot-rest\u002FSKILL.md",[],[191,170,192,193,194,195,196,180,179,178,197,198,199,174,200,173,172],"mexc spot rest","REST","admin","signing","Wallet","requests","actions","secure","data","orders",{"skillNo":202,"name":203,"nameZh":6,"description":204,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":164,"licenseFileUrl":205,"sourceHtmlUrl":206,"categories":207,"keywords":208,"publishedAt":55},"01M70XSYSVZ2N0N91XCAR2CAK0","mexc-futures-websocket","MEXC Futures WebSocket workflows for public streams, private account\u002Forder\u002Fposition streams, ping\u002Fpong, subscriptions, and depth maintenance.","https:\u002F\u002Fgithub.com\u002Fjiayaoqijia\u002Fcryptoskill\u002Fblob\u002Fmain\u002Fskills\u002Fexchanges\u002Fmncrftfrcnm-mexc-futures-websocket\u002FLICENSE","https:\u002F\u002Fgithub.com\u002Fjiayaoqijia\u002Fcryptoskill\u002Fblob\u002Fmain\u002Fskills\u002Fexchanges\u002Fmncrftfrcnm-mexc-futures-websocket\u002FSKILL.md",[],[209,210,171,211,212,181,179,213,177,176,174,173],"mexc futures websocket","futures","position","ping","subscriptions",{"skillNo":215,"name":216,"nameZh":6,"description":6,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":217,"sourceHtmlUrl":218,"categories":219,"keywords":220,"publishedAt":55},"01M6H0ZWHVE5W04WG2DKQE2SQC","0xklen-version-and-refresh-sanctions-lists","https:\u002F\u002Fgithub.com\u002Fjiayaoqijia\u002Fcryptoskill\u002Fblob\u002Fmain\u002Fskills\u002Fpayments\u002F0xklen-version-and-refresh-sanctions-lists\u002FLICENSE","https:\u002F\u002Fgithub.com\u002Fjiayaoqijia\u002Fcryptoskill\u002Fblob\u002Fmain\u002Fskills\u002Fpayments\u002F0xklen-version-and-refresh-sanctions-lists\u002FSKILL.md",[],[221,222,223],"refresh","0xklen version and refresh sanctions lists","version",{"skillNo":225,"name":226,"nameZh":6,"description":227,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":228,"sourceHtmlUrl":229,"categories":230,"keywords":231,"publishedAt":55},"01M6H0Z28Q3R8J0S799GJQWXM3","verify-tests-cover-changed-lines","Use when a PR adds code that the existing suite may not exercise. Measures patch coverage — the share of newly changed lines hit by tests — before approving.","https:\u002F\u002Fgithub.com\u002Fjiayaoqijia\u002Fcryptoskill\u002Fblob\u002Fmain\u002Fskills\u002Fpayments\u002F0xklen-verify-tests-cover-changed-lines\u002FLICENSE","https:\u002F\u002Fgithub.com\u002Fjiayaoqijia\u002Fcryptoskill\u002Fblob\u002Fmain\u002Fskills\u002Fpayments\u002F0xklen-verify-tests-cover-changed-lines\u002FSKILL.md",[],[232,233,234,235,236,237,238,239,240,241,242],"tests","cover","verify tests cover changed lines","verify","coverage","pr","exercise","use","patch","code","share"]