[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M69BVNEGPZN0YEX2YKWC894B":3,"skill-same:01M69BVNEGPZN0YEX2YKWC894B":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},"01M69BVNEGPZN0YEX2YKWC894B","blast-radius",null,"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.","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\u002Fblast-radius\u002FSKILL.md",[],[19,9,20],"blast radius","infrastructure","2026-11-10 10:12:30",false,"---\nname: blast-radius\ndescription: |\n  Assesses network dependency and shared-infrastructure exposure. Use when the\n  user asks which services, customers, SLA policies, routes, or redundant links\n  are affected by a network fault.\nlicense: MIT\nmetadata:\n  author: Microsoft\n  version: \"1.0\"\n---\n\n# Blast-radius assessment\n\n## Workflow\n\n1. Extract the exact link, router, amplifier, conduit, or site identifier.\n2. Call `noc_investigate` with a narrow request explicitly asking the Fabric IQ topology specialist for dependent services, customers, SLA exposure, alternate paths, and shared-conduit risk.\n3. Present confirmed dependencies first, then indirect or potential exposure.\n4. Always check whether logical redundancy shares the same physical conduit; do not treat a second logical link as independent until this is verified.\n5. State when topology has no matching entity instead of treating an empty result as a connection failure.\n\nFor the reference scenario, use: `If LINK-SYD-MEL-FIBRE-01 goes down completely, what's the blast radius, and is there any other link sharing the same physical conduit?`\n\nUse topology evidence only. Do not substitute ticket narrative, mailbox content, or public web results. Prefer one asset or failure domain per call so the result fits Cowork's sub-30-second tool limit.\n","# Blast-radius assessment\n\n## Workflow\n\n1. Extract the exact link, router, amplifier, conduit, or site identifier.\n2. Call `noc_investigate` with a narrow request explicitly asking the Fabric IQ topology specialist for dependent services, customers, SLA exposure, alternate paths, and shared-conduit risk.\n3. Present confirmed dependencies first, then indirect or potential exposure.\n4. Always check whether logical redundancy shares the same physical conduit; do not treat a second logical link as independent until this is verified.\n5. State when topology has no matching entity instead of treating an empty result as a connection failure.\n\nFor the reference scenario, use: `If LINK-SYD-MEL-FIBRE-01 goes down completely, what's the blast radius, and is there any other link sharing the same physical conduit?`\n\nUse topology evidence only. Do not substitute ticket narrative, mailbox content, or public web results. Prefer one asset or failure domain per call so the result fits Cowork's sub-30-second tool limit.\n",{"name":5,"license":15,"metadata":26,"description":28},{"author":12,"version":27},"1.0","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.\n","master","172907673e305c9f2f7c02864c73bc7950d9cd35","cowork\u002Fskills\u002Fblast-radius",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 blast-radius",{"tool":44,"command":45},"bunx","bunx skills add microsoft\u002Fnoc-agent-a365-iqs --skill blast-radius",{"tool":47,"command":48},"pnpm","pnpm dlx skills add microsoft\u002Fnoc-agent-a365-iqs --skill blast-radius","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002Fmicrosoft\u002Fnoc-agent-a365-iqs\u002Fblob\u002Fmaster\u002Fcowork\u002Fskills\u002Fblast-radius\u002FSKILL.md",true,[],[53,61,70,79,89],{"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},"01M69BVSZDNJ8CMMX9D00JGW0A","on-call-bridge","Retrieves the caller's on-call roster and current incident-bridge context.\nUse for Teams, chat, meeting, mailbox, and responder coordination questions.","https:\u002F\u002Fgithub.com\u002Fmicrosoft\u002Fnoc-agent-a365-iqs\u002Fblob\u002Fmaster\u002Fcowork\u002Fskills\u002Fon-call-bridge\u002FSKILL.md",[],[77,9,78],"on call bridge","teams",{"skillNo":80,"name":81,"nameZh":6,"description":82,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":83,"categories":84,"keywords":85,"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",[],[86,87,9,88],"telemetry","incident telemetry","fabric",{"skillNo":90,"name":91,"nameZh":6,"description":92,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":93,"categories":94,"keywords":95,"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",[],[96,9,86],"evidence vs narrative"]