[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M75AR649NCWF7QZ3DFJ53GSY":3,"skill-same:01M75AR649NCWF7QZ3DFJ53GSY":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},"01M75AR649NCWF7QZ3DFJ53GSY","setup-house",null,"use this when a team has no house\u002F folder yet","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\u002Fsetup-house\u002FSKILL.md",[],[],"2026-11-12 13:55:43",false,"---\nname: setup-house\ndescription: use this when a team has no house\u002F folder yet\n---\n\n# Set up a house\n\nThe operating page is the same for every team. Your house is who you are, where you post, and what you allow.\n\n1. Run `grok-bot house init`. It copies `templates\u002Fhouse\u002F` into `.\u002Fhouse`, including `watchers\u002F` and `fleet\u002F`, and refuses if a target file already exists. The board is `house\u002FWAVEBOARD.md` when `LIVE_URL` is unset, and Bifrost (`GET \u002Fcards`) when `LIVE_URL` is set. Read `house\u002FATTENTION_STATE.md` in either case. The copied `bifrost-waves.json` is an empty wave list. If the board is still `ops\u002FWAVEBOARD.md`, or an existing HOUSE.md has no Cadence section, run `grok-bot house init --migrate`. That moves the board to `house\u002FWAVEBOARD.md`, starts `ATTENTION_STATE.md` and any missing watcher or fleet files, appends the template Cadence block when HOUSE.md lacks it, and leaves a file you already changed (including a ledger). When both boards exist and `house\u002FWAVEBOARD.md` is not the untouched template, migrate exits 1 and writes nothing.\n2. Fill HOUSE.md from what the owner has already said. Ask the owner only for what's missing, one question at a time. Set `name:` to the owner name and `OP-PROC:` to the procedure file (`grok-bot\u002FOP-PROC.md` unless the house has an overlay). Delete the Cadence section if this house has no code loop. Otherwise name the four watcher owners and set the stall thresholds. ROLE-MAP.md is an optional roster (role, seat name, agent id). Leave it blank until you have ids. The label and the BOOT line live under that table.\n3. Show the owner the filled HOUSE.md. Nothing in Allowed counts until they approve it. Paste the same Ask first and Allow lines into AUTO-REVIEW.md. That file is the only house file that enforces them.\n4. Run `grok-bot doctor` until it passes. A HOUSE.md line that is exactly `wallet off` skips Open Wallet, Clearing, and hangar pay steps.\n5. Tell every seat to read `house\u002F` on its next wake. Each new seat runs `seat-label` in its own chat, then uses `~\u002Fbin\u002Fgh-\u003Cseat>` instead of plain `gh`. Board rule. On every owner message run `live-inbox \u003Cseat> --prompt --from owner --note \"\u003Cgist>\"`. Ack a handled line with `live-inbox \u003Cseat> --ack \u003Cid>`, or `live-inbox \u003Cseat> --ack all` once every open line is handled. A cloud agent run uses `live-inbox \u003Cseat> --turn start --tag \"bc-\u003Cfirst8> \u003Ctrack>\"` beside `live-inbox \u003Cseat> --cloud launch --agent \u003Cbc-id> --tag \u003Ccard>` on first start or `--cloud reply` on resume, and `live-inbox \u003Cseat> --turn end --tag \"bc-\u003Cfirst8>\"` beside `live-inbox \u003Cseat> --cloud finished --agent \u003Cbc-id> --tag \u003Ccard>` (cancel is `--cloud cancel`). The tag is owner\u002Frepo#n or xray#n. The cloud agent does not post that line. `--from owner` is required today. Kanban note. The live page shows a read-only kanban above Activity. Columns are open, review, fix, merge, retest, and done. The deep link is `?card=`. History note. Every activity line is archived to history. The word owner is the owner via LIVE_OWNER or the owner-name.\n\nChange the house when the owner says a rule twice. Don't put rules there that belong on the operating page.\n","# Set up a house\n\nThe operating page is the same for every team. Your house is who you are, where you post, and what you allow.\n\n1. Run `grok-bot house init`. It copies `templates\u002Fhouse\u002F` into `.\u002Fhouse`, including `watchers\u002F` and `fleet\u002F`, and refuses if a target file already exists. The board is `house\u002FWAVEBOARD.md` when `LIVE_URL` is unset, and Bifrost (`GET \u002Fcards`) when `LIVE_URL` is set. Read `house\u002FATTENTION_STATE.md` in either case. The copied `bifrost-waves.json` is an empty wave list. If the board is still `ops\u002FWAVEBOARD.md`, or an existing HOUSE.md has no Cadence section, run `grok-bot house init --migrate`. That moves the board to `house\u002FWAVEBOARD.md`, starts `ATTENTION_STATE.md` and any missing watcher or fleet files, appends the template Cadence block when HOUSE.md lacks it, and leaves a file you already changed (including a ledger). When both boards exist and `house\u002FWAVEBOARD.md` is not the untouched template, migrate exits 1 and writes nothing.\n2. Fill HOUSE.md from what the owner has already said. Ask the owner only for what's missing, one question at a time. Set `name:` to the owner name and `OP-PROC:` to the procedure file (`grok-bot\u002FOP-PROC.md` unless the house has an overlay). Delete the Cadence section if this house has no code loop. Otherwise name the four watcher owners and set the stall thresholds. ROLE-MAP.md is an optional roster (role, seat name, agent id). Leave it blank until you have ids. The label and the BOOT line live under that table.\n3. Show the owner the filled HOUSE.md. Nothing in Allowed counts until they approve it. Paste the same Ask first and Allow lines into AUTO-REVIEW.md. That file is the only house file that enforces them.\n4. Run `grok-bot doctor` until it passes. A HOUSE.md line that is exactly `wallet off` skips Open Wallet, Clearing, and hangar pay steps.\n5. Tell every seat to read `house\u002F` on its next wake. Each new seat runs `seat-label` in its own chat, then uses `~\u002Fbin\u002Fgh-\u003Cseat>` instead of plain `gh`. Board rule. On every owner message run `live-inbox \u003Cseat> --prompt --from owner --note \"\u003Cgist>\"`. Ack a handled line with `live-inbox \u003Cseat> --ack \u003Cid>`, or `live-inbox \u003Cseat> --ack all` once every open line is handled. A cloud agent run uses `live-inbox \u003Cseat> --turn start --tag \"bc-\u003Cfirst8> \u003Ctrack>\"` beside `live-inbox \u003Cseat> --cloud launch --agent \u003Cbc-id> --tag \u003Ccard>` on first start or `--cloud reply` on resume, and `live-inbox \u003Cseat> --turn end --tag \"bc-\u003Cfirst8>\"` beside `live-inbox \u003Cseat> --cloud finished --agent \u003Cbc-id> --tag \u003Ccard>` (cancel is `--cloud cancel`). The tag is owner\u002Frepo#n or xray#n. The cloud agent does not post that line. `--from owner` is required today. Kanban note. The live page shows a read-only kanban above Activity. Columns are open, review, fix, merge, retest, and done. The deep link is `?card=`. History note. Every activity line is archived to history. The word owner is the owner via LIVE_OWNER or the owner-name.\n\nChange the house when the owner says a rule twice. Don't put rules there that belong on the operating page.\n",{"name":5,"description":7},"main","232f39ec089591afb70f9327b481e7428162a97e","grok-bot\u002Fskills\u002Fsetup-house",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 setup-house",{"tool":36,"command":37},"bunx","bunx skills add 0xRayAI\u002Fxray --skill setup-house",{"tool":39,"command":40},"pnpm","pnpm dlx skills add 0xRayAI\u002Fxray --skill setup-house","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002F0xRayAI\u002Fxray\u002Fblob\u002Fmain\u002Fgrok-bot\u002Fskills\u002Fsetup-house\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",[],[]]