[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M69BVRATNTDFVFJ7KV6H4B0G":3,"skill-same:01M69BVRATNTDFVFJ7KV6H4B0G":53},{"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":22,"linkOnly":23,"markdownContent":24,"markdownBody":25,"frontMatter":26,"refName":30,"commitSha":31,"skillDirectory":32,"forksCount":33,"repositoryHtmlUrl":34,"repositoryHomepageUrl":6,"ownerHtmlUrl":35,"ownerBlogUrl":36,"ownerDescription":37,"updatedAt":38,"install":39,"resources":52},"01M69BVRATNTDFVFJ7KV6H4B0G","incident-telemetry",null,"Queries live Fabric RTI Eventhouse evidence for alert timelines, optical\nreadings, per-sensor events, and suppression details.","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\u002Fincident-telemetry\u002FSKILL.md",[],[19,20,9,21],"telemetry","incident telemetry","fabric","2026-11-10 10:12:30",false,"---\nname: incident-telemetry\ndescription: |\n  Queries live Fabric RTI Eventhouse evidence for alert timelines, optical\n  readings, per-sensor events, and suppression details.\nlicense: MIT\nmetadata:\n  author: Microsoft\n  version: \"1.0\"\n---\n\n# Incident telemetry\n\n## Workflow\n\n1. Extract the exact asset and UTC time window.\n2. Call `noc_investigate` with a narrow request explicitly asking the RTI incident-telemetry specialist for Eventhouse evidence, not ticket narrative.\n3. Request one table at a time when needed: optical readings, network alerts, then incident events.\n4. Return exact UTC timestamps, sensor IDs, measured dBm values, alert counts, and suppression state. Never smooth, infer, or rewrite measured values.\n\nFor live verification, use: `For LINK-SYD-MEL-FIBRE-01, what was the alert timeline and optical readings around 2025-08-14 03:22 UTC — when exactly did loss of light hit each sensor, and was anything suppressed?`\n\nThe expected fixture includes `SENS-SYD-MEL-F1-OPT-002` and `SENS-SYD-MEL-F1-OPT-003` dropping to approximately -30 dBm at `03:22:18`. Treat this only as a verification expectation; report the rows actually returned by Eventhouse.\n","# Incident telemetry\n\n## Workflow\n\n1. Extract the exact asset and UTC time window.\n2. Call `noc_investigate` with a narrow request explicitly asking the RTI incident-telemetry specialist for Eventhouse evidence, not ticket narrative.\n3. Request one table at a time when needed: optical readings, network alerts, then incident events.\n4. Return exact UTC timestamps, sensor IDs, measured dBm values, alert counts, and suppression state. Never smooth, infer, or rewrite measured values.\n\nFor live verification, use: `For LINK-SYD-MEL-FIBRE-01, what was the alert timeline and optical readings around 2025-08-14 03:22 UTC — when exactly did loss of light hit each sensor, and was anything suppressed?`\n\nThe expected fixture includes `SENS-SYD-MEL-F1-OPT-002` and `SENS-SYD-MEL-F1-OPT-003` dropping to approximately -30 dBm at `03:22:18`. Treat this only as a verification expectation; report the rows actually returned by Eventhouse.\n",{"name":5,"license":15,"metadata":27,"description":29},{"author":12,"version":28},"1.0","Queries live Fabric RTI Eventhouse evidence for alert timelines, optical\nreadings, per-sensor events, and suppression details.\n","master","172907673e305c9f2f7c02864c73bc7950d9cd35","cowork\u002Fskills\u002Fincident-telemetry",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":40,"prompt":50,"zipAvailable":51},[41,44,47],{"tool":42,"command":43},"npx","npx skills add microsoft\u002Fnoc-agent-a365-iqs --skill incident-telemetry",{"tool":45,"command":46},"bunx","bunx skills add microsoft\u002Fnoc-agent-a365-iqs --skill incident-telemetry",{"tool":48,"command":49},"pnpm","pnpm dlx skills add microsoft\u002Fnoc-agent-a365-iqs --skill incident-telemetry","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002Fmicrosoft\u002Fnoc-agent-a365-iqs\u002Fblob\u002Fmaster\u002Fcowork\u002Fskills\u002Fincident-telemetry\u002FSKILL.md",true,[],[54,62,71,80,88],{"skillNo":55,"name":56,"nameZh":6,"description":57,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":58,"categories":59,"keywords":60,"publishedAt":22},"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",[],[61,9],"runbook history",{"skillNo":63,"name":64,"nameZh":6,"description":65,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":66,"categories":67,"keywords":68,"publishedAt":22},"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",[],[69,9,70],"public advisory","status",{"skillNo":72,"name":73,"nameZh":6,"description":74,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":75,"categories":76,"keywords":77,"publishedAt":22},"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",[],[78,9,79],"on call bridge","teams",{"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":22},"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,19],"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":22},"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"]