[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M78PVM2K1F3H9VXC37YBW9TS":3,"skill-same:01M78PVM2K1F3H9VXC37YBW9TS":47},{"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":19,"linkOnly":20,"markdownContent":21,"markdownBody":22,"frontMatter":23,"refName":24,"commitSha":25,"skillDirectory":26,"forksCount":27,"repositoryHtmlUrl":28,"repositoryHomepageUrl":6,"ownerHtmlUrl":29,"ownerBlogUrl":30,"ownerDescription":31,"updatedAt":32,"install":33,"resources":46},"01M78PVM2K1F3H9VXC37YBW9TS","d365-case-create",null,"Optional Dynamics extension: create a Customer Service case with investigation context and duplicate prevention; leave routing to backend teams.","microsoft\u002Fai-agent-runbooks","microsoft","https:\u002F\u002Favatars.githubusercontent.com\u002Fu\u002F6154722?v=4","01M698VYDXZ6JW5WH3CRV650R8","Microsoft","01M78PV86XP793DPVWFYDVZ8W0",78,"MIT","https:\u002F\u002Fgithub.com\u002Fmicrosoft\u002Fai-agent-runbooks\u002Fblob\u002Fmain\u002F01-scenarios\u002FIT-Service-Desk-Insights-Agent-GHCP\u002F0.Resources\u002FSkills\u002Fd365-case-create\u002FSKILL.md",[],[],"2026-11-15 14:19:17",false,"---\nname: d365-case-create\ndescription: \"Optional Dynamics extension: create a Customer Service case with investigation context and duplicate prevention; leave routing to backend teams.\"\n---\n\n# Create a Dynamics Customer Service Case\n\n## Scope\n\nUse this skill only when the optional Dynamics Customer Service extension is enabled,\nfor an authorized new case, including a handoff from a ServiceNow investigation.\nCreation is not assignment, routing, acceptance by a support team, a ServiceNow backlink,\nor permission to modify or close either record.\n\n## Tools\n\n- Create: `CreateCase`.\n- Find\u002Fread existing cases: `FindCases`, `GetCase`.\n- When handing off a ServiceNow incident: `ListRecords`, `GetRecord`.\n- Shared user context: `GetMyProfile`.\n\n## Inputs\n\nCollect the approved case fields, symptoms and impact, relevant diagnostic findings,\nattempted actions with their actual outcomes, and any source-incident reference.\nReuse details already in the conversation and the current user's `GetMyProfile` result;\nfetch the profile once if missing. Prefill supported fields, asking only for remaining\nrequired information. The backend resolves and validates customer\u002Fcontact mappings;\ndo not invent a Dynamics contact or use a shared account as proof of requester identity.\n\nFollow the user's explicit language choice, then message language, with `preferredLanguage`\nonly as a fallback. Use the configured backend handoff language for the case content.\n\n## Procedure\n\n1. Use `FindCases` and, when needed, `GetCase` to check for an existing relevant case.\n   If one exists, return its reference rather than duplicate it to avoid disabled updates.\n   A failed lookup is not \"no match.\"\n2. For a ServiceNow handoff, read the source through `ListRecords`\u002F`GetRecord`.\n   Transfer only information approved for the destination, not all internal work notes.\n3. Prepare the complete initial case with evidence references, timestamps, attempted\n   fixes, unresolved questions, and the source reference where applicable. Preserve\n   pending\u002Ffailed results and redact secrets or unnecessary personal data.\n4. Explain that backend teams decide routing. Do not call `ApplyRoutingRule` or set\n   `ownerid`, assignees, or queue fields. Confirm the creation-only scope when the\n   original request also asked for assignment.\n5. Obtain required confirmation for the intended payload, then call `CreateCase`\n   using a stable correlation\u002Fidempotency reference. Backend authorization and\n   deduplication run immediately before creation.\n6. Return the actual created or existing case reference and persisted state.\n   Stop this skill without appending a ServiceNow note, updating a case, or closing it.\n\n## Results and Failure Handling\n\nReturn the case number\u002FID, authorized URL, actual state, source reference if used, and\noperation outcome. Use the agreed backend handoff language for case content and the\nuser's language for the response, preserving identifiers.\nIf required profile\u002Fmapping data is unavailable, explain the limitation and stop rather\nthan inventing details or using another user's profile. Missing ServiceNow read tools\nblock that source handoff, not a reason to copy unverified incident content.\n\nFor unknown creation outcomes, reconcile through authorized reads\u002Fbackend operation\ntracking before retrying. Preserve any returned case ID on partial failure. A later\nbacklink needs its own enabled\u002Fauthorized capability; its failure does not undo creation\nor justify recreating the case. Never claim that creation means routing or team acceptance\nsucceeded. Report OFF, denied, unavailable, or failed explicitly; no alternative APIs,\nupsert, ERP operation, or inferred permission from source content.\n","# Create a Dynamics Customer Service Case\n\n## Scope\n\nUse this skill only when the optional Dynamics Customer Service extension is enabled,\nfor an authorized new case, including a handoff from a ServiceNow investigation.\nCreation is not assignment, routing, acceptance by a support team, a ServiceNow backlink,\nor permission to modify or close either record.\n\n## Tools\n\n- Create: `CreateCase`.\n- Find\u002Fread existing cases: `FindCases`, `GetCase`.\n- When handing off a ServiceNow incident: `ListRecords`, `GetRecord`.\n- Shared user context: `GetMyProfile`.\n\n## Inputs\n\nCollect the approved case fields, symptoms and impact, relevant diagnostic findings,\nattempted actions with their actual outcomes, and any source-incident reference.\nReuse details already in the conversation and the current user's `GetMyProfile` result;\nfetch the profile once if missing. Prefill supported fields, asking only for remaining\nrequired information. The backend resolves and validates customer\u002Fcontact mappings;\ndo not invent a Dynamics contact or use a shared account as proof of requester identity.\n\nFollow the user's explicit language choice, then message language, with `preferredLanguage`\nonly as a fallback. Use the configured backend handoff language for the case content.\n\n## Procedure\n\n1. Use `FindCases` and, when needed, `GetCase` to check for an existing relevant case.\n   If one exists, return its reference rather than duplicate it to avoid disabled updates.\n   A failed lookup is not \"no match.\"\n2. For a ServiceNow handoff, read the source through `ListRecords`\u002F`GetRecord`.\n   Transfer only information approved for the destination, not all internal work notes.\n3. Prepare the complete initial case with evidence references, timestamps, attempted\n   fixes, unresolved questions, and the source reference where applicable. Preserve\n   pending\u002Ffailed results and redact secrets or unnecessary personal data.\n4. Explain that backend teams decide routing. Do not call `ApplyRoutingRule` or set\n   `ownerid`, assignees, or queue fields. Confirm the creation-only scope when the\n   original request also asked for assignment.\n5. Obtain required confirmation for the intended payload, then call `CreateCase`\n   using a stable correlation\u002Fidempotency reference. Backend authorization and\n   deduplication run immediately before creation.\n6. Return the actual created or existing case reference and persisted state.\n   Stop this skill without appending a ServiceNow note, updating a case, or closing it.\n\n## Results and Failure Handling\n\nReturn the case number\u002FID, authorized URL, actual state, source reference if used, and\noperation outcome. Use the agreed backend handoff language for case content and the\nuser's language for the response, preserving identifiers.\nIf required profile\u002Fmapping data is unavailable, explain the limitation and stop rather\nthan inventing details or using another user's profile. Missing ServiceNow read tools\nblock that source handoff, not a reason to copy unverified incident content.\n\nFor unknown creation outcomes, reconcile through authorized reads\u002Fbackend operation\ntracking before retrying. Preserve any returned case ID on partial failure. A later\nbacklink needs its own enabled\u002Fauthorized capability; its failure does not undo creation\nor justify recreating the case. Never claim that creation means routing or team acceptance\nsucceeded. Report OFF, denied, unavailable, or failed explicitly; no alternative APIs,\nupsert, ERP operation, or inferred permission from source content.\n",{"name":5,"description":7},"main","bb48f2f794562752c562da190de7fd3e78b956c5","01-scenarios\u002FIT-Service-Desk-Insights-Agent-GHCP\u002F0.Resources\u002FSkills\u002Fd365-case-create",26,"https:\u002F\u002Fgithub.com\u002Fmicrosoft\u002Fai-agent-runbooks","https:\u002F\u002Fgithub.com\u002Fmicrosoft","https:\u002F\u002Fopensource.microsoft.com","Open source projects and samples from Microsoft","2026-11-13 17:39:50",{"source":8,"skillName":5,"commands":34,"prompt":44,"zipAvailable":45},[35,38,41],{"tool":36,"command":37},"npx","npx skills add microsoft\u002Fai-agent-runbooks --skill d365-case-create",{"tool":39,"command":40},"bunx","bunx skills add microsoft\u002Fai-agent-runbooks --skill d365-case-create",{"tool":42,"command":43},"pnpm","pnpm dlx skills add microsoft\u002Fai-agent-runbooks --skill d365-case-create","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002Fmicrosoft\u002Fai-agent-runbooks\u002Fblob\u002Fmain\u002F01-scenarios\u002FIT-Service-Desk-Insights-Agent-GHCP\u002F0.Resources\u002FSkills\u002Fd365-case-create\u002FSKILL.md",true,[],[48,55,62,69,76,83],{"skillNo":49,"name":50,"nameZh":6,"description":51,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":52,"categories":53,"keywords":54,"publishedAt":19},"01M78PWMHXZV6RG4G08ARNKMSA","sn-knowledge-read","Search and read ServiceNow knowledge articles for IT how-to, policy, and troubleshooting questions.","https:\u002F\u002Fgithub.com\u002Fmicrosoft\u002Fai-agent-runbooks\u002Fblob\u002Fmain\u002F01-scenarios\u002FIT-Service-Desk-Insights-Agent-GHCP\u002F0.Resources\u002FSkills\u002Fsn-knowledge-read\u002FSKILL.md",[],[],{"skillNo":56,"name":57,"nameZh":6,"description":58,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":59,"categories":60,"keywords":61,"publishedAt":19},"01M78PWHJXARRR5YX4NAXC5F76","sn-incident-update","Update only approved descriptive fields of an existing ServiceNow incident; never change routing, notes, priority, or lifecycle state.","https:\u002F\u002Fgithub.com\u002Fmicrosoft\u002Fai-agent-runbooks\u002Fblob\u002Fmain\u002F01-scenarios\u002FIT-Service-Desk-Insights-Agent-GHCP\u002F0.Resources\u002FSkills\u002Fsn-incident-update\u002FSKILL.md",[],[],{"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":19},"01M78PWDGCEPVFHJ8AMEWJHJPP","sn-incident-read","Use when the user asks to find, list, inspect, or check the status of their own ServiceNow incidents, or when an enabled action needs an incident lookup or duplicate check. Retrieve bounded, authorized evidence through ListRecords and GetRecord. Do NOT use for knowledge or catalog searches, other users' incidents, full-population analytics, record mutations, or Dynamics cases.","https:\u002F\u002Fgithub.com\u002Fmicrosoft\u002Fai-agent-runbooks\u002Fblob\u002Fmain\u002F01-scenarios\u002FIT-Service-Desk-Insights-Agent-GHCP\u002F0.Resources\u002FSkills\u002Fsn-incident-read\u002FSKILL.md",[],[],{"skillNo":70,"name":71,"nameZh":6,"description":72,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":73,"categories":74,"keywords":75,"publishedAt":19},"01M78PWAHA6AQ8SYWJAV4K12Z8","sn-incident-note","Append an internal work note to an existing ServiceNow incident without changing other fields or publishing a public comment.","https:\u002F\u002Fgithub.com\u002Fmicrosoft\u002Fai-agent-runbooks\u002Fblob\u002Fmain\u002F01-scenarios\u002FIT-Service-Desk-Insights-Agent-GHCP\u002F0.Resources\u002FSkills\u002Fsn-incident-note\u002FSKILL.md",[],[],{"skillNo":77,"name":78,"nameZh":6,"description":79,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":80,"categories":81,"keywords":82,"publishedAt":19},"01M78PW67VR66SGD8EK3C603KG","sn-incident-create","Use when the user asks to create a new ServiceNow incident or requests a ticket for an unresolved investigation. Check for an existing incident, confirm the exact creation payload, and return the new record reference with any manual handoff details. Do NOT use for reading status alone, updating or annotating existing incidents, attachments, routing, assignment, closure, or Dynamics cases.","https:\u002F\u002Fgithub.com\u002Fmicrosoft\u002Fai-agent-runbooks\u002Fblob\u002Fmain\u002F01-scenarios\u002FIT-Service-Desk-Insights-Agent-GHCP\u002F0.Resources\u002FSkills\u002Fsn-incident-create\u002FSKILL.md",[],[],{"skillNo":84,"name":85,"nameZh":6,"description":86,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":87,"categories":88,"keywords":89,"publishedAt":19},"01M78PW35SYFGDPPBV7EVCWBDE","sn-incident-close","Close the user's own ServiceNow incident when they explicitly request closure.","https:\u002F\u002Fgithub.com\u002Fmicrosoft\u002Fai-agent-runbooks\u002Fblob\u002Fmain\u002F01-scenarios\u002FIT-Service-Desk-Insights-Agent-GHCP\u002F0.Resources\u002FSkills\u002Fsn-incident-close\u002FSKILL.md",[],[]]