[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M699ZM7XDMZ0PBHGYHT279B3":3,"skill-same:01M699ZM7XDMZ0PBHGYHT279B3":80},{"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":42,"linkOnly":43,"markdownContent":44,"markdownBody":45,"frontMatter":46,"refName":57,"commitSha":58,"skillDirectory":59,"forksCount":60,"repositoryHtmlUrl":61,"repositoryHomepageUrl":6,"ownerHtmlUrl":62,"ownerBlogUrl":63,"ownerDescription":64,"updatedAt":65,"install":66,"resources":79},"01M699ZM7XDMZ0PBHGYHT279B3","pr-delivery",null,"Use to deliver a durable Zava Learning fix as a GitHub pull request once an incident has been root-caused — for either an Infrastructure-as-Code change (Bicep under infra\u002F) or an application code change (under src\u002F). The single skill that creates pull requests; applies after live mitigation and root-cause confirmation. The resulting PR URL is what the ServiceNow Change Request references.","microsoft\u002Fsre-agent","microsoft","https:\u002F\u002Favatars.githubusercontent.com\u002Fu\u002F6154722?v=4","01M698VYDXZ6JW5WH3CRV650R8","Microsoft","01M699YP84JQDX8CY79ZD1TTEF",188,"MIT","https:\u002F\u002Fgithub.com\u002Fmicrosoft\u002Fsre-agent\u002Fblob\u002Fmain\u002Flabs\u002Fzava-learning\u002Fsre-config\u002Fagent-config\u002Fskills\u002Fpr-delivery\u002FSKILL.md",[],[19,20,21,22,23,24,25,26,27,28,29,30,31,32,33,34,35,36,37,38,39,40,41],"pr delivery","pr","delivery","use","deliver","single","for","infrastructure-as","URL","as","incident","either","infra","root-cause","github","fix","confirmation","learning","infrastructure-as-code","pull","code","change","pull requests","2026-11-10 10:12:30",false,"---\nmetadata:\n  api_version: azuresre.ai\u002Fv2\n  kind: Skill\nname: pr-delivery\ndescription: Use to deliver a durable Zava Learning fix as a GitHub pull request once an incident has been root-caused — for either an Infrastructure-as-Code change (Bicep under infra\u002F) or an application code change (under src\u002F). The single skill that creates pull requests; applies after live mitigation and root-cause confirmation. The resulting PR URL is what the ServiceNow Change Request references.\ntools:\n  - RunAzCliReadCommands\n  - GetAzCliHelp\n  - FindConnectedGitHubRepo\n  - GetIaCForGitHub\n  - ExecutePythonCode\n  - SearchMemory\n---\n\n## Zava Learning — Pull Request Delivery (IaC + Code)\n\nSingle owner of GitHub pull-request creation for durable fixes. Repo: `@@REPO@@`\n(hosts the app `src\u002F` and the infrastructure `infra\u002F`). This skill applies once an incident is\nroot-caused and the live mitigation is in place; the pull request it produces is later referenced\nby the ServiceNow Change Request (`servicenow-change-management`).\n\nThere is no native GitHub pull-request tool — author the branch, commit, and open the PR with\n`ExecutePythonCode` (GitHub REST API \u002F `gh`) using `FindConnectedGitHubRepo` and\n`GetIaCForGitHub` to locate the repo and IaC. Never commit secrets. Before opening the PR, retrieve\n`SearchMemory(\"zava-redaction\")` and run its `redact()` over the PR title, body, and commit message\n(and never stage a credential or `.env`\u002F`*.pem`\u002F`git-credentials` file into the diff).\n\n## When to use\n- An incident is root-caused to a durable defect and the live mitigation is already applied.\n- The fix belongs in version control: **IaC** (`infra\u002F`, e.g. an NSG rule in\n  `infra\u002Fmodules\u002Fnetwork.bicep`, or a value in `infra\u002Fmain.parameters.json`) or\n  **application code** (`src\u002F`, e.g. a synchronous crypto regression in\n  `src\u002Fassessment-api\u002Fserver.js`).\n\n## Decide the change class\n- **Infrastructure (IaC):** the fix is a guardrail or config in Bicep \u002F parameters. Make BOTH\n  live Azure and the committed IaC reflect the corrected state so the next deploy keeps the fix.\n- **Application code:** the fix is in `src\u002F`. The live mitigation was a revision\n  rollback\u002Frestart; the PR carries the actual code correction.\n\n## Steps\n1. Resolve the repo and IaC type (`FindConnectedGitHubRepo`, `GetIaCForGitHub`).\n2. Branch from default: `fix\u002F\u003Csymptom-slug>` (e.g. `fix\u002Fquiz-launch-nsg-priority`).\n3. Apply the minimal, surgical change. Match existing style. Touch only what the root cause\n   requires.\n4. Commit with a conventional message: `fix(\u003Carea>): \u003Csymptom> — \u003Croot cause>` and a body that\n   summarizes the RCA and links the PagerDuty incident.\n5. Open the PR against `@@REPO@@`. PR body must include: symptom, root cause, the change,\n   verification evidence (link the Before\u002FAfter), and the PagerDuty incident number.\n6. Capture the **PR URL** — the ServiceNow Change Request (`servicenow-change-management`)\n   references it. Post the PR link back in the PagerDuty incident notes.\n\n## Out of scope (human approval required)\n- Merging the PR, force-pushes, history rewrites, changes outside the root-cause fix,\n  VNet\u002Fsubnet\u002FIAM changes.\n\n## Verification\nThe PR is open against the correct repo\u002Fbranch with a complete RCA-backed description and a\nlinked Change Request; CI (if any) is green. Report the PR URL.\n","## Zava Learning — Pull Request Delivery (IaC + Code)\n\nSingle owner of GitHub pull-request creation for durable fixes. Repo: `@@REPO@@`\n(hosts the app `src\u002F` and the infrastructure `infra\u002F`). This skill applies once an incident is\nroot-caused and the live mitigation is in place; the pull request it produces is later referenced\nby the ServiceNow Change Request (`servicenow-change-management`).\n\nThere is no native GitHub pull-request tool — author the branch, commit, and open the PR with\n`ExecutePythonCode` (GitHub REST API \u002F `gh`) using `FindConnectedGitHubRepo` and\n`GetIaCForGitHub` to locate the repo and IaC. Never commit secrets. Before opening the PR, retrieve\n`SearchMemory(\"zava-redaction\")` and run its `redact()` over the PR title, body, and commit message\n(and never stage a credential or `.env`\u002F`*.pem`\u002F`git-credentials` file into the diff).\n\n## When to use\n- An incident is root-caused to a durable defect and the live mitigation is already applied.\n- The fix belongs in version control: **IaC** (`infra\u002F`, e.g. an NSG rule in\n  `infra\u002Fmodules\u002Fnetwork.bicep`, or a value in `infra\u002Fmain.parameters.json`) or\n  **application code** (`src\u002F`, e.g. a synchronous crypto regression in\n  `src\u002Fassessment-api\u002Fserver.js`).\n\n## Decide the change class\n- **Infrastructure (IaC):** the fix is a guardrail or config in Bicep \u002F parameters. Make BOTH\n  live Azure and the committed IaC reflect the corrected state so the next deploy keeps the fix.\n- **Application code:** the fix is in `src\u002F`. The live mitigation was a revision\n  rollback\u002Frestart; the PR carries the actual code correction.\n\n## Steps\n1. Resolve the repo and IaC type (`FindConnectedGitHubRepo`, `GetIaCForGitHub`).\n2. Branch from default: `fix\u002F\u003Csymptom-slug>` (e.g. `fix\u002Fquiz-launch-nsg-priority`).\n3. Apply the minimal, surgical change. Match existing style. Touch only what the root cause\n   requires.\n4. Commit with a conventional message: `fix(\u003Carea>): \u003Csymptom> — \u003Croot cause>` and a body that\n   summarizes the RCA and links the PagerDuty incident.\n5. Open the PR against `@@REPO@@`. PR body must include: symptom, root cause, the change,\n   verification evidence (link the Before\u002FAfter), and the PagerDuty incident number.\n6. Capture the **PR URL** — the ServiceNow Change Request (`servicenow-change-management`)\n   references it. Post the PR link back in the PagerDuty incident notes.\n\n## Out of scope (human approval required)\n- Merging the PR, force-pushes, history rewrites, changes outside the root-cause fix,\n  VNet\u002Fsubnet\u002FIAM changes.\n\n## Verification\nThe PR is open against the correct repo\u002Fbranch with a complete RCA-backed description and a\nlinked Change Request; CI (if any) is green. Report the PR URL.\n",{"name":5,"tools":47,"metadata":54,"description":7},[48,49,50,51,52,53],"RunAzCliReadCommands","GetAzCliHelp","FindConnectedGitHubRepo","GetIaCForGitHub","ExecutePythonCode","SearchMemory",{"kind":55,"api_version":56},"Skill","azuresre.ai\u002Fv2","main","f3dccc6bae8c932ff4f21e6d4117e14285da4db3","labs\u002Fzava-learning\u002Fsre-config\u002Fagent-config\u002Fskills\u002Fpr-delivery",197,"https:\u002F\u002Fgithub.com\u002Fmicrosoft\u002Fsre-agent","https:\u002F\u002Fgithub.com\u002Fmicrosoft","https:\u002F\u002Fopensource.microsoft.com","Open source projects and samples from Microsoft","2026-11-10 10:20:55",{"source":8,"skillName":5,"commands":67,"prompt":77,"zipAvailable":78},[68,71,74],{"tool":69,"command":70},"npx","npx skills add microsoft\u002Fsre-agent --skill pr-delivery",{"tool":72,"command":73},"bunx","bunx skills add microsoft\u002Fsre-agent --skill pr-delivery",{"tool":75,"command":76},"pnpm","pnpm dlx skills add microsoft\u002Fsre-agent --skill pr-delivery","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002Fmicrosoft\u002Fsre-agent\u002Fblob\u002Fmain\u002Flabs\u002Fzava-learning\u002Fsre-config\u002Fagent-config\u002Fskills\u002Fpr-delivery\u002FSKILL.md",true,[],[81,107,143,157,182,201],{"skillNo":82,"name":83,"nameZh":6,"description":84,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":85,"categories":86,"keywords":87,"publishedAt":42},"01M699ZY06GBDPEYW1HEDRAVK8","zava-reporting","Use to package a completed Zava Learning incident analysis for the audience. First present a branded in-thread executive summary (markdown with the before\u002Fafter visuals inline), then produce the downloadable deliverables — a PowerPoint deck, an HTML email, and a Teams notification — using the Zava corporate template. The calling agent may narrow this to a subset (e.g. only the HTML report). Produces content and artifacts; it does not send them. Assembles the output of rca-analysis, evidence-before-after, recommendations-next-steps, and pr-delivery.","https:\u002F\u002Fgithub.com\u002Fmicrosoft\u002Fsre-agent\u002Fblob\u002Fmain\u002Flabs\u002Fzava-learning\u002Fsre-config\u002Fagent-config\u002Fskills\u002Fzava-reporting\u002FSKILL.md",[],[88,89,90,91,92,93,94,95,96,97,98,99,100,101,102,21,29,103,104,105,106],"zava reporting","reporting","rca","visuals","powerpoint","executive summary","analysis","markdown","html report","template","html","only","evidence","before-after","next","recommendations","present","inline","send",{"skillNo":108,"name":109,"nameZh":6,"description":110,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":111,"categories":112,"keywords":126,"publishedAt":42},"01M699ZWCMAF3M8P4A8P0VXEF7","zava-audit-report","Use to package a completed Zava Learning weekly governance audit (NSG \u002F network security, RBAC \u002F least-privilege, or cloud cost) into a single branded, downloadable PowerPoint deck in the Zava house style. The calling audit agent passes its findings (a list of rows with severity) and a short posture summary; this skill renders the deck, applies redaction, and returns the attachment download link. Produces the artifact; it does not send it.","https:\u002F\u002Fgithub.com\u002Fmicrosoft\u002Fsre-agent\u002Fblob\u002Fmain\u002Flabs\u002Fzava-learning\u002Fsre-config\u002Fagent-config\u002Fskills\u002Fzava-audit-report\u002FSKILL.md",[113,118,121],{"categoryNo":114,"categoryName":115,"taxonomyType":116,"taxonomyTypeDesc":117},"01JBSEEDCAT000000000000003","演示文稿","SCENARIO","使用场景",{"categoryNo":119,"categoryName":120,"taxonomyType":116,"taxonomyTypeDesc":117},"01JBSEEDCAT000000000000023","Skill与智能体开发",{"categoryNo":122,"categoryName":123,"taxonomyType":124,"taxonomyTypeDesc":125},"01JBSEEDCAT000000000000034","行政与办公人员","PROFESSION","适用职业",[127,128,129,130,131,132,133,92,134,135,136,36,137,138,139,140,141,142,106,24],"zava audit report","report","audit","audit report","security","network security","rbac","network","least-privilege","severity","returns","short","list","deck","artifact","weekly",{"skillNo":144,"name":145,"nameZh":6,"description":146,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":147,"categories":148,"keywords":149,"publishedAt":42},"01M699ZV3DK2HK74MMKABQBNC7","servicenow-change-management","Use whenever a Zava Learning investigation produces a durable fix that needs change management — after a GitHub PR is opened for an Infrastructure-as-Code or application code root cause, raise a ServiceNow Change Request referencing the PR and attach the RCA report. The single owner of ServiceNow Change Request and attachment operations.","https:\u002F\u002Fgithub.com\u002Fmicrosoft\u002Fsre-agent\u002Fblob\u002Fmain\u002Flabs\u002Fzava-learning\u002Fsre-config\u002Fagent-config\u002Fskills\u002Fservicenow-change-management\u002FSKILL.md",[],[40,150,151,152,153,33,90,20,39,37,36,34,22,154,155,28,26,25,24,156],"servicenow change management","servicenow","change management","management","attach","github pr","root cause",{"skillNo":158,"name":159,"nameZh":6,"description":160,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":161,"categories":162,"keywords":163,"publishedAt":42},"01M699ZSQAYXNM5YXH35GQXG2E","redaction-guard","Use whenever you are about to emit operator-visible content — a chat\u002Fthread message, a PagerDuty or ServiceNow note, a commit message or pull-request body, or any report artifact (HTML, PowerPoint, Teams card). Deterministically masks secrets, credentials, tokens, private keys, URI-embedded passwords, and PII so they never appear in the thread or in any deliverable. This is a cross-cutting guardrail invoked by the output-producing skills, not a runbook step.","https:\u002F\u002Fgithub.com\u002Fmicrosoft\u002Fsre-agent\u002Fblob\u002Fmain\u002Flabs\u002Fzava-learning\u002Fsre-config\u002Fagent-config\u002Fskills\u002Fredaction-guard\u002FSKILL.md",[],[164,165,166,167,168,169,38,170,171,22,172,173,174,175,176,177,178,179,180,181],"redaction guard","guard","redaction","commit","teams","commit message","runbook","pii","never","pagerduty","chat","tokens","guardrail","card","output","you","passwords","thread",{"skillNo":183,"name":184,"nameZh":6,"description":185,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":186,"categories":187,"keywords":188,"publishedAt":42},"01M699ZRHD3XNYX412M7613ACM","recommendations-next-steps","Use to produce the forward-looking recommendations and next steps for a Zava Learning incident — prioritized preventive, detective, and process actions with owners, target dates, and the risk of inaction. Its output is used in the zava-reporting deliverables.","https:\u002F\u002Fgithub.com\u002Fmicrosoft\u002Fsre-agent\u002Fblob\u002Fmain\u002Flabs\u002Fzava-learning\u002Fsre-config\u002Fagent-config\u002Fskills\u002Frecommendations-next-steps\u002FSKILL.md",[],[189,102,103,190,191,9,192,193,194,195,89,196,36,197,22,29,178,198,199,25,200],"recommendations next steps","next steps","docs","learn","produce","search","actions","risk","process","with","deliverables","dates",{"skillNo":202,"name":203,"nameZh":6,"description":204,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":205,"categories":206,"keywords":207,"publishedAt":42},"01M699ZQBV3ECBCA58WSBCJE54","rca-analysis","Use to produce the root-cause analysis narrative for a resolved or mitigated Zava Learning incident — the incident timeline, the trigger vs. latent root cause (5-Whys), contributing factors, and how to present them. Defines the RCA section format; its output is used in the before\u002Fafter, recommendations, and reporting deliverables.","https:\u002F\u002Fgithub.com\u002Fmicrosoft\u002Fsre-agent\u002Fblob\u002Fmain\u002Flabs\u002Fzava-learning\u002Fsre-config\u002Fagent-config\u002Fskills\u002Frca-analysis\u002FSKILL.md",[],[90,208,94,193,209,210,36,211,22,32,29,103,212,213,214,178,199,25,215,156],"rca analysis","contributing","how","format","trigger","how to","narrative","section"]