[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M69BVSZDNJ8CMMX9D00JGW0A":3,"skill-same:01M69BVSZDNJ8CMMX9D00JGW0A":52},{"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":6,"sourceHtmlUrl":16,"categories":17,"keywords":18,"publishedAt":21,"linkOnly":22,"markdownContent":23,"markdownBody":24,"frontMatter":25,"refName":29,"commitSha":30,"skillDirectory":31,"forksCount":32,"repositoryHtmlUrl":33,"repositoryHomepageUrl":6,"ownerHtmlUrl":34,"ownerBlogUrl":35,"ownerDescription":36,"updatedAt":37,"install":38,"resources":51},"01M69BVSZDNJ8CMMX9D00JGW0A","on-call-bridge",null,"Retrieves the caller's on-call roster and current incident-bridge context.\nUse for Teams, chat, meeting, mailbox, and responder coordination questions.","microsoft\u002Fnoc-agent-a365-iqs","microsoft","https:\u002F\u002Favatars.githubusercontent.com\u002Fu\u002F6154722?v=4","01M698VYDXZ6JW5WH3CRV650R8","Microsoft","01M69BVJVCYBBWT71ZWC3C5EJ9",0,"MIT","https:\u002F\u002Fgithub.com\u002Fmicrosoft\u002Fnoc-agent-a365-iqs\u002Fblob\u002Fmaster\u002Fcowork\u002Fskills\u002Fon-call-bridge\u002FSKILL.md",[],[19,9,20],"on call bridge","teams","2026-11-10 10:12:30",false,"---\nname: on-call-bridge\ndescription: |\n  Retrieves the caller's on-call roster and current incident-bridge context.\n  Use for Teams, chat, meeting, mailbox, and responder coordination questions.\nlicense: MIT\nmetadata:\n  author: Microsoft\n  version: \"1.0\"\n---\n\n# On-call and incident bridge\n\n## Workflow\n\n1. Identify the incident, team, bridge, and relevant time window.\n2. Call `noc_investigate` with a narrow request explicitly asking the Work IQ specialist for the caller's own roster and collaboration context.\n3. Report who is on call, current discussion, decisions, owners, and unresolved questions, with source boundaries.\n4. If first-use OAuth consent is requested, ask the user to complete it and retry rather than substituting another source.\n\nFor the reference scenario, use: `Who's on-call right now, and what's being discussed on the current incident bridge?`\n\nDo not expose another user's private context, invent attendance, or claim a message was sent.\n","# On-call and incident bridge\n\n## Workflow\n\n1. Identify the incident, team, bridge, and relevant time window.\n2. Call `noc_investigate` with a narrow request explicitly asking the Work IQ specialist for the caller's own roster and collaboration context.\n3. Report who is on call, current discussion, decisions, owners, and unresolved questions, with source boundaries.\n4. If first-use OAuth consent is requested, ask the user to complete it and retry rather than substituting another source.\n\nFor the reference scenario, use: `Who's on-call right now, and what's being discussed on the current incident bridge?`\n\nDo not expose another user's private context, invent attendance, or claim a message was sent.\n",{"name":5,"license":15,"metadata":26,"description":28},{"author":12,"version":27},"1.0","Retrieves the caller's on-call roster and current incident-bridge context.\nUse for Teams, chat, meeting, mailbox, and responder coordination questions.\n","master","172907673e305c9f2f7c02864c73bc7950d9cd35","cowork\u002Fskills\u002Fon-call-bridge",3,"https:\u002F\u002Fgithub.com\u002Fmicrosoft\u002Fnoc-agent-a365-iqs","https:\u002F\u002Fgithub.com\u002Fmicrosoft","https:\u002F\u002Fopensource.microsoft.com","Open source projects and samples from Microsoft","2026-11-03 11:48:41",{"source":8,"skillName":5,"commands":39,"prompt":49,"zipAvailable":50},[40,43,46],{"tool":41,"command":42},"npx","npx skills add microsoft\u002Fnoc-agent-a365-iqs --skill on-call-bridge",{"tool":44,"command":45},"bunx","bunx skills add microsoft\u002Fnoc-agent-a365-iqs --skill on-call-bridge",{"tool":47,"command":48},"pnpm","pnpm dlx skills add microsoft\u002Fnoc-agent-a365-iqs --skill on-call-bridge","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002Fmicrosoft\u002Fnoc-agent-a365-iqs\u002Fblob\u002Fmaster\u002Fcowork\u002Fskills\u002Fon-call-bridge\u002FSKILL.md",true,[],[53,61,70,80,88],{"skillNo":54,"name":55,"nameZh":6,"description":56,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":57,"categories":58,"keywords":59,"publishedAt":21},"01M69BVWPECRW80ADJQXKG3GPZ","runbook-history","Retrieves internal NOC runbooks and prior incident history. Use when the user\nasks for the standard procedure, historical tickets, or narrative context.","https:\u002F\u002Fgithub.com\u002Fmicrosoft\u002Fnoc-agent-a365-iqs\u002Fblob\u002Fmaster\u002Fcowork\u002Fskills\u002Frunbook-history\u002FSKILL.md",[],[60,9],"runbook history",{"skillNo":62,"name":63,"nameZh":6,"description":64,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":65,"categories":66,"keywords":67,"publishedAt":21},"01M69BVVBXBJRC4Q9XBTD9AF0B","public-advisory","Searches public telecom vendor advisories and carrier status reports. Use\nfor external NOC-relevant developments, outages, and equipment notices.","https:\u002F\u002Fgithub.com\u002Fmicrosoft\u002Fnoc-agent-a365-iqs\u002Fblob\u002Fmaster\u002Fcowork\u002Fskills\u002Fpublic-advisory\u002FSKILL.md",[],[68,9,69],"public advisory","status",{"skillNo":71,"name":72,"nameZh":6,"description":73,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":74,"categories":75,"keywords":76,"publishedAt":21},"01M69BVRATNTDFVFJ7KV6H4B0G","incident-telemetry","Queries live Fabric RTI Eventhouse evidence for alert timelines, optical\nreadings, per-sensor events, and suppression details.","https:\u002F\u002Fgithub.com\u002Fmicrosoft\u002Fnoc-agent-a365-iqs\u002Fblob\u002Fmaster\u002Fcowork\u002Fskills\u002Fincident-telemetry\u002FSKILL.md",[],[77,78,9,79],"telemetry","incident telemetry","fabric",{"skillNo":81,"name":82,"nameZh":6,"description":83,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":84,"categories":85,"keywords":86,"publishedAt":21},"01M69BVPWWJ22A0V0XN7XG80R2","evidence-vs-narrative","Compares documented incident narrative with measured RTI evidence. Use when\nthe user asks whether ticket timing or claims match actual telemetry.","https:\u002F\u002Fgithub.com\u002Fmicrosoft\u002Fnoc-agent-a365-iqs\u002Fblob\u002Fmaster\u002Fcowork\u002Fskills\u002Fevidence-vs-narrative\u002FSKILL.md",[],[87,9,77],"evidence vs narrative",{"skillNo":89,"name":90,"nameZh":6,"description":91,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":92,"categories":93,"keywords":94,"publishedAt":21},"01M69BVNEGPZN0YEX2YKWC894B","blast-radius","Assesses network dependency and shared-infrastructure exposure. Use when the\nuser asks which services, customers, SLA policies, routes, or redundant links\nare affected by a network fault.","https:\u002F\u002Fgithub.com\u002Fmicrosoft\u002Fnoc-agent-a365-iqs\u002Fblob\u002Fmaster\u002Fcowork\u002Fskills\u002Fblast-radius\u002FSKILL.md",[],[95,9,96],"blast radius","infrastructure"]