[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M7576ACJC6WWKQG2HP3S2ZYN":3,"skill-same:01M7576ACJC6WWKQG2HP3S2ZYN":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":6,"ownerHtmlUrl":28,"ownerBlogUrl":6,"ownerDescription":6,"updatedAt":29,"install":30,"resources":43},"01M7576ACJC6WWKQG2HP3S2ZYN","ccb-mobile-relay-maintain",null,"Diagnose and safely maintain the CCB Mobile host service, LAN\u002Ftailnet\u002FCloudflare Tunnel\u002FRelay routes, pairing and devices, Relay invitation or host activation, multi-project terminals, and capability-negotiated Provider controls. Use when Mobile cannot connect, pair, discover projects, open terminals, expose Provider controls, or when a user explicitly asks to activate, update, revoke, or repair a CCB Relay host or device.","SeemSeam\u002Fagent-roles-spec","SeemSeam","https:\u002F\u002Favatars.githubusercontent.com\u002Fu\u002F29205273?v=4","01M7572MDYPSM30Y29C9HRMGK7","01M7572MEGCX02T16BHYV9PBVK",19,"Apache-2.0","https:\u002F\u002Fgithub.com\u002FSeemSeam\u002Fagent-roles-spec\u002Fblob\u002Fmain\u002Froles\u002Fccb-self\u002Fskills\u002Fccb-mobile-relay-maintain\u002FSKILL.md",[],[],"2026-11-12 13:55:43",false,"---\nname: ccb-mobile-relay-maintain\ndescription: Diagnose and safely maintain the CCB Mobile host service, LAN\u002Ftailnet\u002FCloudflare Tunnel\u002FRelay routes, pairing and devices, Relay invitation or host activation, multi-project terminals, and capability-negotiated Provider controls. Use when Mobile cannot connect, pair, discover projects, open terminals, expose Provider controls, or when a user explicitly asks to activate, update, revoke, or repair a CCB Relay host or device.\n---\n\n# CCB Mobile Relay Maintain\n\nRead `references\u002Fccb-mobile-relay-runtime.md` before mutation. Keep the Mobile\nhost's server-wide authority separate from project runtime and Pane evidence.\n\n## Safety Rules\n\n- Never read, print, store, or request Relay credentials, invitation secrets,\n  device secrets, Provider credentials, or raw Provider responses in chat or\n  Role memory.\n- Diagnose before replacing the host or rotating pairing state.\n- Revoke only one exact device, invitation, or host after explicit user intent.\n- Do not infer Mobile host health from a project Pane or `.ccb\u002Fagents\u002F*`.\n- Do not force Provider controls when capability negotiation says unsupported;\n  report the required host update.\n\n## Workflow\n\n1. Classify the incident:\n   - host service not running or unhealthy;\n   - LAN\u002Ftailnet\u002Ftunnel\u002FRelay route unreachable;\n   - pairing handoff expired or unclaimable;\n   - device unauthorized or intentionally revoked;\n   - running project not discovered;\n   - host or project terminal transport failed;\n   - Provider controls hidden, rejected, or pending restart;\n   - native Windows registry, endpoint, TCP descriptor, or readiness mismatch.\n2. Collect sanitized evidence with the smallest applicable commands:\n\n```bash\nccb mobile devices\nccb relay host status \u003Chost_id>\nccb relay host list\nccb relay invite status \u003Cinvite_id>\n```\n\n   Use local health and managed-service diagnostics when available. Do not\n   expose secret-bearing files or arguments.\n3. Verify the active service generation, CCB ownership of the listen endpoint,\n   selected route provider, registered projects, and advertised capabilities.\n4. Choose the least disruptive supported action:\n   - `ccb update mobile` to refresh the server-wide host or rotate an expired\n     pairing handoff;\n   - `ccb mobile revoke \u003Cdevice_id>` for one explicitly selected device;\n   - `ccb relay host activate ...` only from an operator-provided invitation or\n     invitation file already available through the authorized workflow;\n   - exact `ccb relay ... revoke` only for an explicitly selected identifier.\n5. For Provider setting changes, distinguish configured, active, and pending\n   state. Hand guarded post-config Agent restart to `ccb-self-recover` when the\n   host says restart is required.\n6. Verify health, route, project discovery, terminal connection, and capability\n   negotiation after mutation.\n\n## Native Windows\n\nUse native Windows process ownership, registry, TCP descriptor, endpoint\nmarker, readiness, and Herdr namespace evidence. Do not apply Unix tmux or\n`\u002Fproc` assumptions. If the current release reports beta prerequisites or an\nunsigned launcher boundary, preserve that status in the report.\n\n## Output\n\nReport:\n\n- incident class and current route;\n- sanitized host generation\u002Fhealth evidence;\n- project discovery and terminal status;\n- capability status and any host-update guidance;\n- exact mutation performed, if any;\n- identifiers revoked without secret material;\n- remaining platform or external-network blocker.\n","# CCB Mobile Relay Maintain\n\nRead `references\u002Fccb-mobile-relay-runtime.md` before mutation. Keep the Mobile\nhost's server-wide authority separate from project runtime and Pane evidence.\n\n## Safety Rules\n\n- Never read, print, store, or request Relay credentials, invitation secrets,\n  device secrets, Provider credentials, or raw Provider responses in chat or\n  Role memory.\n- Diagnose before replacing the host or rotating pairing state.\n- Revoke only one exact device, invitation, or host after explicit user intent.\n- Do not infer Mobile host health from a project Pane or `.ccb\u002Fagents\u002F*`.\n- Do not force Provider controls when capability negotiation says unsupported;\n  report the required host update.\n\n## Workflow\n\n1. Classify the incident:\n   - host service not running or unhealthy;\n   - LAN\u002Ftailnet\u002Ftunnel\u002FRelay route unreachable;\n   - pairing handoff expired or unclaimable;\n   - device unauthorized or intentionally revoked;\n   - running project not discovered;\n   - host or project terminal transport failed;\n   - Provider controls hidden, rejected, or pending restart;\n   - native Windows registry, endpoint, TCP descriptor, or readiness mismatch.\n2. Collect sanitized evidence with the smallest applicable commands:\n\n```bash\nccb mobile devices\nccb relay host status \u003Chost_id>\nccb relay host list\nccb relay invite status \u003Cinvite_id>\n```\n\n   Use local health and managed-service diagnostics when available. Do not\n   expose secret-bearing files or arguments.\n3. Verify the active service generation, CCB ownership of the listen endpoint,\n   selected route provider, registered projects, and advertised capabilities.\n4. Choose the least disruptive supported action:\n   - `ccb update mobile` to refresh the server-wide host or rotate an expired\n     pairing handoff;\n   - `ccb mobile revoke \u003Cdevice_id>` for one explicitly selected device;\n   - `ccb relay host activate ...` only from an operator-provided invitation or\n     invitation file already available through the authorized workflow;\n   - exact `ccb relay ... revoke` only for an explicitly selected identifier.\n5. For Provider setting changes, distinguish configured, active, and pending\n   state. Hand guarded post-config Agent restart to `ccb-self-recover` when the\n   host says restart is required.\n6. Verify health, route, project discovery, terminal connection, and capability\n   negotiation after mutation.\n\n## Native Windows\n\nUse native Windows process ownership, registry, TCP descriptor, endpoint\nmarker, readiness, and Herdr namespace evidence. Do not apply Unix tmux or\n`\u002Fproc` assumptions. If the current release reports beta prerequisites or an\nunsigned launcher boundary, preserve that status in the report.\n\n## Output\n\nReport:\n\n- incident class and current route;\n- sanitized host generation\u002Fhealth evidence;\n- project discovery and terminal status;\n- capability status and any host-update guidance;\n- exact mutation performed, if any;\n- identifiers revoked without secret material;\n- remaining platform or external-network blocker.\n",{"name":5,"description":7},"main","d07398b0a36ffa994efd970a554dd9596932ed5c","roles\u002Fccb-self\u002Fskills\u002Fccb-mobile-relay-maintain",2,"https:\u002F\u002Fgithub.com\u002FSeemSeam\u002Fagent-roles-spec","https:\u002F\u002Fgithub.com\u002FSeemSeam","2026-08-14 10:00:06",{"source":8,"skillName":5,"commands":31,"prompt":41,"zipAvailable":42},[32,35,38],{"tool":33,"command":34},"npx","npx skills add SeemSeam\u002Fagent-roles-spec --skill ccb-mobile-relay-maintain",{"tool":36,"command":37},"bunx","bunx skills add SeemSeam\u002Fagent-roles-spec --skill ccb-mobile-relay-maintain",{"tool":39,"command":40},"pnpm","pnpm dlx skills add SeemSeam\u002Fagent-roles-spec --skill ccb-mobile-relay-maintain","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002FSeemSeam\u002Fagent-roles-spec\u002Fblob\u002Fmain\u002Froles\u002Fccb-self\u002Fskills\u002Fccb-mobile-relay-maintain\u002FSKILL.md",true,[],[45,51,58,65,72,79],{"skillNo":46,"name":47,"nameZh":6,"description":6,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":6,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":48,"categories":49,"keywords":50,"publishedAt":18},"01M757C4HNYHR92Z3MDGPW9JSA","example-skill","https:\u002F\u002Fgithub.com\u002FSeemSeam\u002Fagent-roles-spec\u002Fblob\u002Fmain\u002Ftemplates\u002Frole-with-skills\u002Fskills\u002Fexample-skill\u002FSKILL.md",[],[],{"skillNo":52,"name":53,"nameZh":6,"description":54,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":6,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":55,"categories":56,"keywords":57,"publishedAt":18},"01M757C2B2YT62JBH98CG1BKWG","su-status","从 docs 人读真相源与 .ccb 协调件读取当前项目、Requirement 或子任务状态。","https:\u002F\u002Fgithub.com\u002FSeemSeam\u002Fagent-roles-spec\u002Fblob\u002Fmain\u002Froles\u002Fsu-ccb\u002Fskills\u002Fsu-status\u002FSKILL.md",[],[],{"skillNo":59,"name":60,"nameZh":6,"description":61,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":6,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":62,"categories":63,"keywords":64,"publishedAt":18},"01M757C0DVFT88AFBXN1PFXH9D","su-revise-breakdown","根据用户反馈重写 Requirement breakdown draft。","https:\u002F\u002Fgithub.com\u002FSeemSeam\u002Fagent-roles-spec\u002Fblob\u002Fmain\u002Froles\u002Fsu-ccb\u002Fskills\u002Fsu-revise-breakdown\u002FSKILL.md",[],[],{"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":18},"01M757BY5XVMPKEK118D782PRM","su-review","审查执行回执、diff 和验证证据，决定通过、返工、replan 或升级用户。","https:\u002F\u002Fgithub.com\u002FSeemSeam\u002Fagent-roles-spec\u002Fblob\u002Fmain\u002Froles\u002Fsu-ccb\u002Fskills\u002Fsu-review\u002FSKILL.md",[],[],{"skillNo":73,"name":74,"nameZh":6,"description":75,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":6,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":76,"categories":77,"keywords":78,"publishedAt":18},"01M757BW1R61F61X7JJF2SSJET","su-resume","从 docs 人读真相源与 .ccb 协调件恢复 paused\u002Fdeferred\u002Fin-progress 主体的上下文。","https:\u002F\u002Fgithub.com\u002FSeemSeam\u002Fagent-roles-spec\u002Fblob\u002Fmain\u002Froles\u002Fsu-ccb\u002Fskills\u002Fsu-resume\u002FSKILL.md",[],[],{"skillNo":80,"name":81,"nameZh":6,"description":82,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":6,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":83,"categories":84,"keywords":85,"publishedAt":18},"01M757BTEAFRRXA9DY3KBRTRNY","su-reconcile","AI-native 自检 docs 人读真相源、.ccb 协调件与 Console 投影漂移，并按审批结果执行修复。","https:\u002F\u002Fgithub.com\u002FSeemSeam\u002Fagent-roles-spec\u002Fblob\u002Fmain\u002Froles\u002Fsu-ccb\u002Fskills\u002Fsu-reconcile\u002FSKILL.md",[],[]]