[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M75AQHD1EB8DXTE0B0SWZP1B":3,"skill-same:01M75AQHD1EB8DXTE0B0SWZP1B":44},{"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":18,"linkOnly":19,"markdownContent":20,"markdownBody":21,"frontMatter":22,"refName":23,"commitSha":24,"skillDirectory":25,"forksCount":26,"repositoryHtmlUrl":27,"repositoryHomepageUrl":27,"ownerHtmlUrl":28,"ownerBlogUrl":6,"ownerDescription":6,"updatedAt":29,"install":30,"resources":43},"01M75AQHD1EB8DXTE0B0SWZP1B","Enterprise CoS wave loop",null,"use this when the coordinator runs the wave loop — plan the next wave, pace burn, Lane H friend-test plus Dist packets, onboard seats; CoS never launches CloudAgent; quiet on repeat acks; wake hygiene HARD (Blaze poke > stale intake)","0xRayAI\u002Fxray","0xRayAI","https:\u002F\u002Favatars.githubusercontent.com\u002Fu\u002F274879952?v=4","01M75AEEVWK4S4G4N25HAYGB9V","01M75AEEWMHN7H4PQVCJS2938J",2,"MIT","https:\u002F\u002Fgithub.com\u002F0xRayAI\u002Fxray\u002Fblob\u002Fmain\u002Fgrok-bot\u002Fskills\u002Fenterprise-cos-wave-loop\u002FSKILL.md",[],[],"2026-11-12 13:55:43",false,"---\nname: Enterprise CoS wave loop\ndescription: >-\n  use this when the coordinator runs the wave loop — plan the next wave, pace\n  burn, Lane H friend-test plus Dist packets, onboard seats; CoS never\n  launches CloudAgent; quiet on repeat acks; wake hygiene HARD (Blaze poke > stale intake)\n---\n# Coordinator wave loop\n\n## Save compute\n`ops\u002FLEAN-COMPUTE.md` — Light \u002F Normal \u002F Strict · quiet on repeat acks; wake hygiene HARD (Blaze poke > stale intake) · fit for purpose · friend test OS docs.\n\n## Four duties (HARD)\nBlinky does not route dev work. Bifrost keeps the board, the inbox, and wave timing.\n\n1. Plan the next wave at each close. The plan card is on Bifrost.\n2. Pace burn. Do not launch when the day is over pace. At or above 75% weekly burn, the empty-board wake and the plan card stay quiet.\n3. Lane H friend-test plus Dist packets. Herald posts those words and does not invent them.\n4. Onboard a seat, including suit fitting. List a finished or idle seat. Blaze deletes it.\n\n**Fatal:** CoS implement, CloudAgent launch, Dist browser-post, “just finish it myself.”\n\n## Friend test — HARD GATE (Lane H)\n`ops\u002FGIBBERISH-CHECK.md` + [Synaptical comms](sand-workflow:synaptical-comms).\n\nBefore material Dist, board, or Blaze-facing text: include **A friend would hear:** …  \nNo proof line → do not send. Herald\u002Fcritic refuse jargon. CoS does not stamp fake PASS.\n\nLane B (bot-internal) may stay compressed; human audience → H.\n\n## Cloud vs seats (HARD)\n`ops\u002FCLOUD-CONTINUITY.md` + `ops\u002FSEATS.md`.\n\n**Fatal defect:** coordinator launching, resuming, replying to, or dumping eng Cursor clouds (`CloudAgent`). Forge launches the cloud agent.\n\n**Do:** the four duties above. Dev talk is Blaze and forge. The cos-forge 1:1 carries the printed `live-inbox` handoff line. A room post is not a handoff.\n\n**Do not:** implement, deploy, mint, public Dist post, spend, assign dev work, or puppeteer the cloud mid-run.\n\nThis is **ops\u002Fskill law**, not a suit `PreToolUse` deny. Grok Bot chat has no hook path; costume PPE is theater. The mill plant stays on the suit.\n\n## When a teammate messages you\n1. Read the substance.\n2. Repeat of known state → stay quiet.\n3. Ownership \u002F blocker \u002F live \u002F capital changed → board it, queue next work, start the next everyday step, tell the human.\n4. Never wait-only on a real close.\n\n\n## Wake hygiene (HARD — 2026-09-16)\n\n- **Blaze-first HARD:** Blaze 1:1 beats bot pings, rooms, routines. Park other work and answer Blaze first when he is waiting.\n`ops\u002FMISS-CHAT-WAKE-2026-09-16.md` · `OPS-SPEC.md` § Wake hygiene.\n\n1. **Blaze 1:1 always wins.** Any human poke (`stat`, `you there`, `fix yourself`, any question) → answer from live `gh` + `house\u002FATTENTION_STATE.md` first (else `templates\u002Fhouse\u002FATTENTION_STATE.md`). Never stay silent because a stale routine shares the wake.\n2. **Stale intake\u002Froutines** that re-litigate CLOSED\u002FMERGED\u002FLIVE beats → quiet **only** when there is no Blaze message in the turn.\n3. **Eng signal intake** must self-quiet (read ATTENTION before handoff). PAUSED until rearm after a clean new-PR fire.\n4. Bloated 1:1 → STATION parachute; suggest fresh chat if wakes stay sticky. Cover CoS temporary only.\n5. Do not confuse platform wake failure with seat idle — check recovery note before declaring CoS dead.\n\n6. **Latency HARD:** Blaze message in turn → **first tool = chat reply** (short). Then seats\u002Fdisk\u002FDist. Never open with parallel agent cards while Blaze waits.\n\n## Status beat (material only)\n**Done** · **Verify** · **Reflect** · **Next** (no approval \u002F needs human \u002F not now)\n\n## Done means live\nMerged without deploy is not done.\n","# Coordinator wave loop\n\n## Save compute\n`ops\u002FLEAN-COMPUTE.md` — Light \u002F Normal \u002F Strict · quiet on repeat acks; wake hygiene HARD (Blaze poke > stale intake) · fit for purpose · friend test OS docs.\n\n## Four duties (HARD)\nBlinky does not route dev work. Bifrost keeps the board, the inbox, and wave timing.\n\n1. Plan the next wave at each close. The plan card is on Bifrost.\n2. Pace burn. Do not launch when the day is over pace. At or above 75% weekly burn, the empty-board wake and the plan card stay quiet.\n3. Lane H friend-test plus Dist packets. Herald posts those words and does not invent them.\n4. Onboard a seat, including suit fitting. List a finished or idle seat. Blaze deletes it.\n\n**Fatal:** CoS implement, CloudAgent launch, Dist browser-post, “just finish it myself.”\n\n## Friend test — HARD GATE (Lane H)\n`ops\u002FGIBBERISH-CHECK.md` + [Synaptical comms](sand-workflow:synaptical-comms).\n\nBefore material Dist, board, or Blaze-facing text: include **A friend would hear:** …  \nNo proof line → do not send. Herald\u002Fcritic refuse jargon. CoS does not stamp fake PASS.\n\nLane B (bot-internal) may stay compressed; human audience → H.\n\n## Cloud vs seats (HARD)\n`ops\u002FCLOUD-CONTINUITY.md` + `ops\u002FSEATS.md`.\n\n**Fatal defect:** coordinator launching, resuming, replying to, or dumping eng Cursor clouds (`CloudAgent`). Forge launches the cloud agent.\n\n**Do:** the four duties above. Dev talk is Blaze and forge. The cos-forge 1:1 carries the printed `live-inbox` handoff line. A room post is not a handoff.\n\n**Do not:** implement, deploy, mint, public Dist post, spend, assign dev work, or puppeteer the cloud mid-run.\n\nThis is **ops\u002Fskill law**, not a suit `PreToolUse` deny. Grok Bot chat has no hook path; costume PPE is theater. The mill plant stays on the suit.\n\n## When a teammate messages you\n1. Read the substance.\n2. Repeat of known state → stay quiet.\n3. Ownership \u002F blocker \u002F live \u002F capital changed → board it, queue next work, start the next everyday step, tell the human.\n4. Never wait-only on a real close.\n\n\n## Wake hygiene (HARD — 2026-09-16)\n\n- **Blaze-first HARD:** Blaze 1:1 beats bot pings, rooms, routines. Park other work and answer Blaze first when he is waiting.\n`ops\u002FMISS-CHAT-WAKE-2026-09-16.md` · `OPS-SPEC.md` § Wake hygiene.\n\n1. **Blaze 1:1 always wins.** Any human poke (`stat`, `you there`, `fix yourself`, any question) → answer from live `gh` + `house\u002FATTENTION_STATE.md` first (else `templates\u002Fhouse\u002FATTENTION_STATE.md`). Never stay silent because a stale routine shares the wake.\n2. **Stale intake\u002Froutines** that re-litigate CLOSED\u002FMERGED\u002FLIVE beats → quiet **only** when there is no Blaze message in the turn.\n3. **Eng signal intake** must self-quiet (read ATTENTION before handoff). PAUSED until rearm after a clean new-PR fire.\n4. Bloated 1:1 → STATION parachute; suggest fresh chat if wakes stay sticky. Cover CoS temporary only.\n5. Do not confuse platform wake failure with seat idle — check recovery note before declaring CoS dead.\n\n6. **Latency HARD:** Blaze message in turn → **first tool = chat reply** (short). Then seats\u002Fdisk\u002FDist. Never open with parallel agent cards while Blaze waits.\n\n## Status beat (material only)\n**Done** · **Verify** · **Reflect** · **Next** (no approval \u002F needs human \u002F not now)\n\n## Done means live\nMerged without deploy is not done.\n",{"name":5,"description":7},"main","232f39ec089591afb70f9327b481e7428162a97e","grok-bot\u002Fskills\u002Fenterprise-cos-wave-loop",3,"https:\u002F\u002Fgithub.com\u002F0xRayAI\u002Fxray","https:\u002F\u002Fgithub.com\u002F0xRayAI","2026-11-13 22:20:55",{"source":8,"skillName":5,"commands":31,"prompt":41,"zipAvailable":42},[32,35,38],{"tool":33,"command":34},"npx","npx skills add 0xRayAI\u002Fxray --skill \"Enterprise CoS wave loop\"",{"tool":36,"command":37},"bunx","bunx skills add 0xRayAI\u002Fxray --skill \"Enterprise CoS wave loop\"",{"tool":39,"command":40},"pnpm","pnpm dlx skills add 0xRayAI\u002Fxray --skill \"Enterprise CoS wave loop\"","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002F0xRayAI\u002Fxray\u002Fblob\u002Fmain\u002Fgrok-bot\u002Fskills\u002Fenterprise-cos-wave-loop\u002FSKILL.md",true,[],[45,52,59,66,73,80],{"skillNo":46,"name":47,"nameZh":6,"description":48,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":6,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":49,"categories":50,"keywords":51,"publishedAt":18},"01M75AXZY4TX8Z6WF2G4EKYMAA","xray-orchestrator","Main orchestration skill for xray agents.\nProvides commands to coordinate agent work and invoke xray APIs\nthrough the local HTTP API server.","https:\u002F\u002Fgithub.com\u002F0xRayAI\u002Fxray\u002Fblob\u002Fmain\u002Fsrc\u002Fskills\u002Fxray-orchestrator\u002FSKILL.md",[],[],{"skillNo":53,"name":54,"nameZh":6,"description":55,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":6,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":56,"categories":57,"keywords":58,"publishedAt":18},"01M75AXT1TB9SX9JVSP16C85BP","ui-ux-design","User interface and user experience design with mobile-first approach, cognitive simplicity, and accessibility-first principles","https:\u002F\u002Fgithub.com\u002F0xRayAI\u002Fxray\u002Fblob\u002Fmain\u002Fsrc\u002Fskills\u002Fui-ux-design\u002FSKILL.md",[],[],{"skillNo":60,"name":61,"nameZh":6,"description":62,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":6,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":63,"categories":64,"keywords":65,"publishedAt":18},"01M75AXQERT17BTCCY7Y1HPXTA","testing-strategy","Design comprehensive testing strategies and optimize test coverage","https:\u002F\u002Fgithub.com\u002F0xRayAI\u002Fxray\u002Fblob\u002Fmain\u002Fsrc\u002Fskills\u002Ftesting-strategy\u002FSKILL.md",[],[],{"skillNo":67,"name":68,"nameZh":6,"description":69,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":6,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":70,"categories":71,"keywords":72,"publishedAt":18},"01M75AXM7TRVQXXKT0C287VWN7","testing-best-practices","Testing best practices and quality assurance","https:\u002F\u002Fgithub.com\u002F0xRayAI\u002Fxray\u002Fblob\u002Fmain\u002Fsrc\u002Fskills\u002Ftesting-best-practices\u002FSKILL.md",[],[],{"skillNo":74,"name":75,"nameZh":6,"description":76,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":6,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":77,"categories":78,"keywords":79,"publishedAt":18},"01M75AXHAJZK2JBVG638K3RZ5F","tech-writer","Documentation writer for API docs, READMEs, ADRs, changelogs, and developer experience","https:\u002F\u002Fgithub.com\u002F0xRayAI\u002Fxray\u002Fblob\u002Fmain\u002Fsrc\u002Fskills\u002Ftech-writer\u002FSKILL.md",[],[],{"skillNo":81,"name":82,"nameZh":6,"description":83,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":6,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":84,"categories":85,"keywords":86,"publishedAt":18},"01M75AXE7P5MX15WA16TGFKJQG","strategist","Strategic guidance and complex problem-solving with architectural decision-making and risk analysis","https:\u002F\u002Fgithub.com\u002F0xRayAI\u002Fxray\u002Fblob\u002Fmain\u002Fsrc\u002Fskills\u002Fstrategist\u002FSKILL.md",[],[]]