[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M6C1ZXW06R46STPKQ7CANPS4":3,"skill-same:01M6C1ZXW06R46STPKQ7CANPS4":64},{"skillNo":4,"name":5,"nameZh":6,"description":7,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":6,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":15,"categories":16,"keywords":17,"publishedAt":38,"linkOnly":39,"markdownContent":40,"markdownBody":41,"frontMatter":42,"refName":43,"commitSha":44,"skillDirectory":45,"forksCount":46,"repositoryHtmlUrl":47,"repositoryHomepageUrl":6,"ownerHtmlUrl":48,"ownerBlogUrl":6,"ownerDescription":6,"updatedAt":49,"install":50,"resources":63},"01M6C1ZXW06R46STPKQ7CANPS4","cmux-cloud",null,"Use cmux Cloud to inspect or run work on an existing remote machine, monitor durable jobs, transfer task files, or balance work across available compute.","jleechanorg\u002Fjleechan-skills","jleechanorg","https:\u002F\u002Favatars.githubusercontent.com\u002Fu\u002F221404966?v=4","01M6C1VJ99XG950X1DWPEBCBGX","01M6C1VJDK5YVDNT3362RT5WSB",6,"MIT","https:\u002F\u002Fgithub.com\u002Fjleechanorg\u002Fjleechan-skills\u002Fblob\u002Fmain\u002F.claude\u002Fskills\u002Fcmux-cloud\u002FSKILL.md",[],[18,19,20,21,22,23,24,25,26,27,28,29,30,31,32,33,34,35,36,37],"cloud","cmux cloud","cmux","jobs","run work","Existing","inspect","balance","remote","machine","across","compute","task","monitor","files","use","work","work on","transfer","run","2026-11-10 10:12:30",false,"---\nname: cmux-cloud\ndescription: Use cmux Cloud to inspect or run work on an existing remote machine, monitor durable jobs, transfer task files, or balance work across available compute.\n---\n\n# cmux Cloud machines\n\nUse the installed cmux CLI and its current vendor guidance (`cmux cloud --skill`)\nfor exact syntax. Commands and limits can change; check the relevant\n`cmux cloud \u003Cverb> --help` whenever a flag, limit, or exit behavior matters.\n\n## Inspect before routing\n\nStart with read-only machine inventory, authentication status, and routing\ninformation. Use the vendor's inventory command as the authority for which\nmachines exist and their current capacity. Prefer an already-running suitable\nmachine and pin its identifier on remote execution. A router may provision a\nmachine for an unrecognized path, so inspect its plan before running it.\n\nDo not provision machines, increase a paid plan, or trigger other billable\nresources unless the user authorized that action. Pause or resume a machine only\nwhen the user authorized it and its owner and task impact are clear. Deleting a\nmachine is destructive and always requires explicit user approval, even when the\ntask created it. Never delete a machine outside the explicitly authorized target\nand scope. Pausing may stop compute charges while retaining its disk; confirm\ncurrent semantics with vendor help.\n\n## Run and observe work\n\nUse a short remote-exec command for a bounded probe. For scripts whose next\nsteps depend on their exit status, use the command that propagates the remote\nexit code; some versions of a probe command report only a generic local failure.\nVerify these behaviors in the installed CLI before relying on them.\n\nFor long work, start a durable remote terminal or job. Record its identifier,\nwait for completion, and read its output before reporting a result. A finished\nwait means the process ended; it does not mean the command passed. Keep the\nremote work directory and transferred files scoped to the task.\n\nBefore transferring files, check current size limits and default excludes. Avoid\ncopying credentials, browser profiles, or unrelated repository state. Pulling a\ndirectory may require archiving it on the remote machine first; use the\ndocumented transfer mechanism and verify the resulting file.\n\n## Browser and credentials\n\nUse only the task-authorized isolated browser and authentication route. Keep\npersonal browser profiles separate from automation profiles. Some provider\nconsent or multi-factor steps require a human gesture; report that exact\ndependency rather than automating around it.\n\nNever export, copy, print, or place credentials in task files or command-line\narguments. Use an existing authorized credential store or supported identity\nflow. Creating or rotating credentials and granting new access require the\nappropriate authorization.\n\n## Balance work across machines\n\nCompare current available CPU and memory on the candidate hosts, then route the\nnext independent heavy job to the host with more capacity. Re-measure before\nstarting another heavy batch. Keep shared-resource and simulator exclusivity\nseparate from host scheduling: a capacity note does not reserve an account,\nservice, campaign, or device. Do not start competing builds on the same\nsimulator device and app bundle without coordinating its active operator.\n\nPrefer fewer active machines when the current work fits, because provisioned\nmachines may continue consuming resources while idle. Check live pool limits\nbefore starting work and pause task-owned idle machines when authorized and\nsafe.\n\n## Verify before reporting\n\n- Bind each result to the machine, command, and process\u002Fjob identifier used.\n- Read both the completion status and captured output.\n- Report the actual remote exit status and any missing verification layer.\n- Recheck inventory before claiming a machine was paused, removed, or available.\n\n## Portable skill contract\n\nThis seven-element specification covers the three skill packages in this\nchange.\n\n- **Outcome:** The catalog gains reusable design-comparison,\n  interface-exploration, and cmux Cloud skills.\n- **Non-goals:** No application runtime, live machine, account, profile, or\n  credential is changed; no scripts or unrelated packages are added.\n- **Acceptance:** All three packages have valid frontmatter, are discoverable,\n  omit personal host data, and retain bounded delegation and resource rules.\n- **User story:** As a catalog user, I can find these skills when their tasks\n  apply and use them without inheriting private host configuration.\n- **Proof plan:** Record source hashes and dependencies, validate each package,\n  verify read-only installer discovery, scan for personal data, and inspect the\n  complete base-to-head diff.\n- **Mock exemption:** This instruction-only change does not alter product UI,\n  so screenshots and runtime video do not apply. The design-fidelity skill\n  still requires the approved mock when used for UI implementation.\n- **Risks:** Vendor command behavior can drift, and local discovery checks do\n  not prove installation or runtime success on another host.\n","# cmux Cloud machines\n\nUse the installed cmux CLI and its current vendor guidance (`cmux cloud --skill`)\nfor exact syntax. Commands and limits can change; check the relevant\n`cmux cloud \u003Cverb> --help` whenever a flag, limit, or exit behavior matters.\n\n## Inspect before routing\n\nStart with read-only machine inventory, authentication status, and routing\ninformation. Use the vendor's inventory command as the authority for which\nmachines exist and their current capacity. Prefer an already-running suitable\nmachine and pin its identifier on remote execution. A router may provision a\nmachine for an unrecognized path, so inspect its plan before running it.\n\nDo not provision machines, increase a paid plan, or trigger other billable\nresources unless the user authorized that action. Pause or resume a machine only\nwhen the user authorized it and its owner and task impact are clear. Deleting a\nmachine is destructive and always requires explicit user approval, even when the\ntask created it. Never delete a machine outside the explicitly authorized target\nand scope. Pausing may stop compute charges while retaining its disk; confirm\ncurrent semantics with vendor help.\n\n## Run and observe work\n\nUse a short remote-exec command for a bounded probe. For scripts whose next\nsteps depend on their exit status, use the command that propagates the remote\nexit code; some versions of a probe command report only a generic local failure.\nVerify these behaviors in the installed CLI before relying on them.\n\nFor long work, start a durable remote terminal or job. Record its identifier,\nwait for completion, and read its output before reporting a result. A finished\nwait means the process ended; it does not mean the command passed. Keep the\nremote work directory and transferred files scoped to the task.\n\nBefore transferring files, check current size limits and default excludes. Avoid\ncopying credentials, browser profiles, or unrelated repository state. Pulling a\ndirectory may require archiving it on the remote machine first; use the\ndocumented transfer mechanism and verify the resulting file.\n\n## Browser and credentials\n\nUse only the task-authorized isolated browser and authentication route. Keep\npersonal browser profiles separate from automation profiles. Some provider\nconsent or multi-factor steps require a human gesture; report that exact\ndependency rather than automating around it.\n\nNever export, copy, print, or place credentials in task files or command-line\narguments. Use an existing authorized credential store or supported identity\nflow. Creating or rotating credentials and granting new access require the\nappropriate authorization.\n\n## Balance work across machines\n\nCompare current available CPU and memory on the candidate hosts, then route the\nnext independent heavy job to the host with more capacity. Re-measure before\nstarting another heavy batch. Keep shared-resource and simulator exclusivity\nseparate from host scheduling: a capacity note does not reserve an account,\nservice, campaign, or device. Do not start competing builds on the same\nsimulator device and app bundle without coordinating its active operator.\n\nPrefer fewer active machines when the current work fits, because provisioned\nmachines may continue consuming resources while idle. Check live pool limits\nbefore starting work and pause task-owned idle machines when authorized and\nsafe.\n\n## Verify before reporting\n\n- Bind each result to the machine, command, and process\u002Fjob identifier used.\n- Read both the completion status and captured output.\n- Report the actual remote exit status and any missing verification layer.\n- Recheck inventory before claiming a machine was paused, removed, or available.\n\n## Portable skill contract\n\nThis seven-element specification covers the three skill packages in this\nchange.\n\n- **Outcome:** The catalog gains reusable design-comparison,\n  interface-exploration, and cmux Cloud skills.\n- **Non-goals:** No application runtime, live machine, account, profile, or\n  credential is changed; no scripts or unrelated packages are added.\n- **Acceptance:** All three packages have valid frontmatter, are discoverable,\n  omit personal host data, and retain bounded delegation and resource rules.\n- **User story:** As a catalog user, I can find these skills when their tasks\n  apply and use them without inheriting private host configuration.\n- **Proof plan:** Record source hashes and dependencies, validate each package,\n  verify read-only installer discovery, scan for personal data, and inspect the\n  complete base-to-head diff.\n- **Mock exemption:** This instruction-only change does not alter product UI,\n  so screenshots and runtime video do not apply. The design-fidelity skill\n  still requires the approved mock when used for UI implementation.\n- **Risks:** Vendor command behavior can drift, and local discovery checks do\n  not prove installation or runtime success on another host.\n",{"name":5,"description":7},"main","42ccd02cbf5e8e47839dc3eab6fc754dc6b339cf",".claude\u002Fskills\u002Fcmux-cloud",0,"https:\u002F\u002Fgithub.com\u002Fjleechanorg\u002Fjleechan-skills","https:\u002F\u002Fgithub.com\u002Fjleechanorg","2026-11-11 09:18:40",{"source":8,"skillName":5,"commands":51,"prompt":61,"zipAvailable":62},[52,55,58],{"tool":53,"command":54},"npx","npx skills add jleechanorg\u002Fjleechan-skills --skill cmux-cloud",{"tool":56,"command":57},"bunx","bunx skills add jleechanorg\u002Fjleechan-skills --skill cmux-cloud",{"tool":59,"command":60},"pnpm","pnpm dlx skills add jleechanorg\u002Fjleechan-skills --skill cmux-cloud","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002Fjleechanorg\u002Fjleechan-skills\u002Fblob\u002Fmain\u002F.claude\u002Fskills\u002Fcmux-cloud\u002FSKILL.md",true,[],[65,82,104,118,132,146],{"skillNo":66,"name":67,"nameZh":6,"description":68,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":6,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":69,"categories":70,"keywords":71,"publishedAt":38},"01M716Y5MTJ6GYJZ2ATXCJK8G4","instinct","Use when the user invokes \u002Finstinct or \u002Fin, or asks to \"message Instinct\", \"ask Instinct\", \"tell Instinct\", \"check Instinct\", or read replies from the configured peer assistant. iMessage first, WhatsApp Web as fallback.","https:\u002F\u002Fgithub.com\u002Fjleechanorg\u002Fjleechan-skills\u002Fblob\u002Fmain\u002F.claude\u002Fskills\u002Finstinct\u002FSKILL.md",[],[67,72,73,74,75,33,76,77,78,79,80,81],"user","when","replies","check","identity","whatsapp","gmail","read","message","ask",{"skillNo":83,"name":84,"nameZh":6,"description":85,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":6,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":86,"categories":87,"keywords":93,"publishedAt":38},"01M716Y4HF7FVVMJSA2CCVN5VF","hr","Compatibility alias for history-resume; produce the same fresh-state, provenance-aware resume briefing.","https:\u002F\u002Fgithub.com\u002Fjleechanorg\u002Fjleechan-skills\u002Fblob\u002Fmain\u002F.claude\u002Fskills\u002Fhr\u002FSKILL.md",[88],{"categoryNo":89,"categoryName":90,"taxonomyType":91,"taxonomyTypeDesc":92},"01JBSEEDCAT000000000000038","人力资源","PROFESSION","适用职业",[84,94,95,96,97,98,99,100,101,102,103],"resume","compatibility","provenance","for","history","produce","alias","briefing","state","fresh",{"skillNo":105,"name":106,"nameZh":6,"description":107,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":6,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":108,"categories":109,"keywords":111,"publishedAt":38},"01M716Y1FFNFKFJYYKF8HQA6T8","history-resume","Resume briefing for the current repository branch or worktree using fresh state and admitted history sources.","https:\u002F\u002Fgithub.com\u002Fjleechanorg\u002Fjleechan-skills\u002Fblob\u002Fmain\u002F.claude\u002Fskills\u002Fhistory-resume\u002FSKILL.md",[110],{"categoryNo":89,"categoryName":90,"taxonomyType":91,"taxonomyTypeDesc":92},[98,94,112,113,72,114,101,115,97,116,117,102,103],"history resume","branch","analysis","repository","worktree","sources",{"skillNo":119,"name":120,"nameZh":6,"description":121,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":6,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":122,"categories":123,"keywords":124,"publishedAt":38},"01M716XWXJ8EPHK4RH9T14TR85","grok","Alias for the canonical grokbot browser conversation workflow; \u002Fgrok talks to the Grok bot the same way \u002Fdot talks to Dot.","https:\u002F\u002Fgithub.com\u002Fjleechanorg\u002Fjleechan-skills\u002Fblob\u002Fmain\u002F.claude\u002Fskills\u002Fgrok\u002FSKILL.md",[],[120,125,126,127,97,128,100,129,130,131],"dot","bot","workflow","canonical","conversation","browser","grokbot",{"skillNo":133,"name":134,"nameZh":6,"description":135,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":6,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":136,"categories":137,"keywords":138,"publishedAt":38},"01M70N9Q07DTE0EW5KFXMMMSJ0","codexa-bench","Compare `codexa` and normal `codex` on a fair split of comparable work by default; use `--strict` for duplicate runs of the exact same task.","https:\u002F\u002Fgithub.com\u002Fjleechanorg\u002Fjleechan-skills\u002Fblob\u002Fmain\u002F.claude\u002Fskills\u002Fcodexa-bench\u002FSKILL.md",[],[139,34,140,33,141,97,142,30,143,144,145],"codexa bench","split","default","duplicate","compare","normal","codex",{"skillNo":147,"name":148,"nameZh":6,"description":149,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":6,"repositoryNo":12,"starsCount":13,"licenseSpdxId":150,"licenseFileUrl":151,"sourceHtmlUrl":152,"categories":153,"keywords":165,"publishedAt":38},"01M6C24S2X60SP8BBFGAEKPEGW","frontend-design","Create distinctive, production-grade frontend interfaces with high design quality. Use this skill when the user asks to build web components, pages, artifacts, posters, or applications (examples include websites, landing pages, dashboards, React components, HTML\u002FCSS layouts, or when styling\u002Fbeautifying any web UI). Generates creative, polished code and UI design that avoids generic AI aesthetics.","Apache-2.0","https:\u002F\u002Fgithub.com\u002Fjleechanorg\u002Fjleechan-skills\u002Fblob\u002Fmain\u002F.claude\u002Fskills\u002Ffrontend-design\u002FLICENSE.txt","https:\u002F\u002Fgithub.com\u002Fjleechanorg\u002Fjleechan-skills\u002Fblob\u002Fmain\u002F.claude\u002Fskills\u002Ffrontend-design\u002FSKILL.md",[154,159,162],{"categoryNo":155,"categoryName":156,"taxonomyType":157,"taxonomyTypeDesc":158},"01JBSEEDCAT000000000000009","前端开发","SCENARIO","使用场景",{"categoryNo":160,"categoryName":161,"taxonomyType":157,"taxonomyTypeDesc":158},"01JBSEEDCAT000000000000015","视觉设计",{"categoryNo":163,"categoryName":164,"taxonomyType":91,"taxonomyTypeDesc":92},"01JBSEEDCAT000000000000032","设计师",[166,167,168,33,169,170,171,72,172,173,174,175,176,177,178,179,180,181,182,183,184,185,186,187,188,189,73,190],"frontend","design","frontend design","generic","ui design","react","html","components","code","artifacts","ui","aesthetics","Production","web components","landing","applications","quality","web","css","create","examples","with","react components","web ui","pages"]