[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M6PJCYCYJQDX318SQN3EBF0E":3,"skill-same:01M6PJCYCYJQDX318SQN3EBF0E":61},{"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":32,"linkOnly":33,"markdownContent":34,"markdownBody":35,"frontMatter":36,"refName":37,"commitSha":38,"skillDirectory":39,"forksCount":40,"repositoryHtmlUrl":41,"repositoryHomepageUrl":42,"ownerHtmlUrl":43,"ownerBlogUrl":44,"ownerDescription":45,"updatedAt":46,"install":47,"resources":60},"01M6PJCYCYJQDX318SQN3EBF0E","sync-teams-samples-to-agents-sdk",null,"CI instructions for a bounded Teams SDK to Agents SDK sample synchronization using the selected language profile.","microsoft\u002FAgents","microsoft","https:\u002F\u002Favatars.githubusercontent.com\u002Fu\u002F6154722?v=4","01M698VYDXZ6JW5WH3CRV650R8","Microsoft","01M69B7CR81D1HSNV69XDT8KAR",1109,"MIT","https:\u002F\u002Fgithub.com\u002Fmicrosoft\u002FAgents\u002Fblob\u002Fmain\u002Fautomation\u002Fteams-sample-sync\u002Fskills\u002Fsync-teams-samples-to-agents-sdk\u002FSKILL.md",[],[19,20,21,22,23,24,25,26,27,28,29,30,31],"agents sdk","sdk","sync","teams","sync teams samples to agents sdk","ci","synchronization","instructions","profile","language","sample","for","bounded","2026-11-10 10:12:30",false,"---\nname: sync-teams-samples-to-agents-sdk\ndescription: CI instructions for a bounded Teams SDK to Agents SDK sample synchronization using the selected language profile.\n---\n\n# Teams sample synchronization\n\nThis CI caller uses one persistent implementation session. Preserve the source behavior with\nthe smallest necessary changes inside the selected sample. Invoke the public migration skill\nbefore editing code and the manifest skill when updating the Teams app package.\nThe context identifies the language and frozen SDK selection. For .NET, use its\nresolved release line; for JS\u002FTS, use its exact npm package map. The minimum is\na floor. Apply the selected migration skill's package conventions rather than\ncopying the minimum into dependencies or imposing one language's version syntax\non another. Initial imports may have an empty destination.\n\nPlan and implement SDK updates together with the compatibility migrations they require.\n\"Keep current\" means the newest supported selection under the coordinator's stable-release,\nsupported-major and common-package rules, including JS package compatibility; it does not\nauthorize arbitrary latest majors, prereleases, or unrelated third-party dependency upgrades.\nTreat compiler errors from selected SDK APIs as implementation work inside the selected sample.\nPreserve source, manifest, and contract behavior, including meeting timestamps\u002Ftranscripts,\ntask dialogs, message-extension previews, signed upload URLs, and targeted recipients.\nDo not restore obsolete API packages, downgrade below the selected target, remove features or\nhandlers, weaken tests, or suppress diagnostics to obtain a passing result.\n\nFor .NET shared helpers, the authoritative `AspNetExtensions.cs` comes from\n`microsoft\u002FAgents-for-net` at `src\u002Fsamples\u002FShared\u002FAspNetExtensions.cs`. The configured canonical\nsample (`automation\u002Fteams-sample-sync\u002Freference\u002Fdotnet`) supplies a local synchronized copy, fingerprinted by the\ncoordinator. Use that supplied input to maintain copies inside the selected sample as needed.\nDo not download an unpinned replacement or edit the canonical sample from this session.\nIf the input is missing or needs refreshing for the selected SDK, report that prerequisite.\n\nPreserve Agents terminology in README\u002Fcatalog descriptions and user-facing\nmessages: use \"agent\" for the migrated runtime even when upstream says \"bot\".\nKeep platform names (Azure Bot), schema keys (`bots[]`, `botId`), and existing\nsource-derived identifiers. Treat this as an intentional migration difference,\nnot a behavior mismatch to repair. Do not weaken tests to restore upstream wording.\n\nThe first turn is read-only planning. Before finalizing the plan, reconcile every user-facing\ncapability across source handlers, README\u002Fhelp text, the destination implementation, and the\nactual destination manifest JSON. For commands, record the exact title, slash or mention surface,\nhandler evidence, and whether it exists under `bots[].commandLists`. Treat documentation as a\nrequirement to verify, not proof of the manifest's current contents. A claim that no manifest\nchange is needed must cite the relevant JSON path and current value.\n\nReturn a concise Markdown specification with an item for each relevant source behavior: upstream\npath and stable symbol, destination change, Agents-specific behavior to preserve, manifest impact,\nand validation expectation. Include every mismatch found during capability reconciliation. The\ncoordinator freezes that plan before it grants write access.\n\nAfter write access is granted, implement the frozen plan without editing it. The only CI tool is\n`validate_sample`; use `code` during implementation, `manifest` when editing the package, and\n`all` before completing the task. A validation result is authoritative only for the current\ncandidate. Add meaningful selected-sample tests when the behavior can be tested locally.\n\nBefore full validation, re-open the final implementation, README\u002Fhelp text, and manifest. Compare\nthem against the capability inventory by exact command title and surface; schema validation alone\ndoes not prove capability coverage. Finish by returning a Markdown self-audit that accounts for\nevery frozen-plan item and names the validation run. Start it with `## Self-audit`, then write\n`Outcome: changed` or `Outcome: no changes required` on its own line. A no-changes outcome requires\nevidence that every plan item was verified and that no selected-sample file needs modification. If\na required behavior cannot be implemented, state the actual blocker. Do not claim validation passed\nwhen it did not. The coordinator may request one repair for deterministic validation failures; keep\nthe frozen plan unchanged during that repair.\nRun full validation again after repairs. Shared-harness incompatibility, missing canonical input,\nunavailable package feeds, and infrastructure failures must remain visible as blockers; they do\nnot authorize protected-file edits or repeated repair attempts. An unsuccessful migration must\nnot be reported as a successful sync or handed off as a validated candidate.\n","# Teams sample synchronization\n\nThis CI caller uses one persistent implementation session. Preserve the source behavior with\nthe smallest necessary changes inside the selected sample. Invoke the public migration skill\nbefore editing code and the manifest skill when updating the Teams app package.\nThe context identifies the language and frozen SDK selection. For .NET, use its\nresolved release line; for JS\u002FTS, use its exact npm package map. The minimum is\na floor. Apply the selected migration skill's package conventions rather than\ncopying the minimum into dependencies or imposing one language's version syntax\non another. Initial imports may have an empty destination.\n\nPlan and implement SDK updates together with the compatibility migrations they require.\n\"Keep current\" means the newest supported selection under the coordinator's stable-release,\nsupported-major and common-package rules, including JS package compatibility; it does not\nauthorize arbitrary latest majors, prereleases, or unrelated third-party dependency upgrades.\nTreat compiler errors from selected SDK APIs as implementation work inside the selected sample.\nPreserve source, manifest, and contract behavior, including meeting timestamps\u002Ftranscripts,\ntask dialogs, message-extension previews, signed upload URLs, and targeted recipients.\nDo not restore obsolete API packages, downgrade below the selected target, remove features or\nhandlers, weaken tests, or suppress diagnostics to obtain a passing result.\n\nFor .NET shared helpers, the authoritative `AspNetExtensions.cs` comes from\n`microsoft\u002FAgents-for-net` at `src\u002Fsamples\u002FShared\u002FAspNetExtensions.cs`. The configured canonical\nsample (`automation\u002Fteams-sample-sync\u002Freference\u002Fdotnet`) supplies a local synchronized copy, fingerprinted by the\ncoordinator. Use that supplied input to maintain copies inside the selected sample as needed.\nDo not download an unpinned replacement or edit the canonical sample from this session.\nIf the input is missing or needs refreshing for the selected SDK, report that prerequisite.\n\nPreserve Agents terminology in README\u002Fcatalog descriptions and user-facing\nmessages: use \"agent\" for the migrated runtime even when upstream says \"bot\".\nKeep platform names (Azure Bot), schema keys (`bots[]`, `botId`), and existing\nsource-derived identifiers. Treat this as an intentional migration difference,\nnot a behavior mismatch to repair. Do not weaken tests to restore upstream wording.\n\nThe first turn is read-only planning. Before finalizing the plan, reconcile every user-facing\ncapability across source handlers, README\u002Fhelp text, the destination implementation, and the\nactual destination manifest JSON. For commands, record the exact title, slash or mention surface,\nhandler evidence, and whether it exists under `bots[].commandLists`. Treat documentation as a\nrequirement to verify, not proof of the manifest's current contents. A claim that no manifest\nchange is needed must cite the relevant JSON path and current value.\n\nReturn a concise Markdown specification with an item for each relevant source behavior: upstream\npath and stable symbol, destination change, Agents-specific behavior to preserve, manifest impact,\nand validation expectation. Include every mismatch found during capability reconciliation. The\ncoordinator freezes that plan before it grants write access.\n\nAfter write access is granted, implement the frozen plan without editing it. The only CI tool is\n`validate_sample`; use `code` during implementation, `manifest` when editing the package, and\n`all` before completing the task. A validation result is authoritative only for the current\ncandidate. Add meaningful selected-sample tests when the behavior can be tested locally.\n\nBefore full validation, re-open the final implementation, README\u002Fhelp text, and manifest. Compare\nthem against the capability inventory by exact command title and surface; schema validation alone\ndoes not prove capability coverage. Finish by returning a Markdown self-audit that accounts for\nevery frozen-plan item and names the validation run. Start it with `## Self-audit`, then write\n`Outcome: changed` or `Outcome: no changes required` on its own line. A no-changes outcome requires\nevidence that every plan item was verified and that no selected-sample file needs modification. If\na required behavior cannot be implemented, state the actual blocker. Do not claim validation passed\nwhen it did not. The coordinator may request one repair for deterministic validation failures; keep\nthe frozen plan unchanged during that repair.\nRun full validation again after repairs. Shared-harness incompatibility, missing canonical input,\nunavailable package feeds, and infrastructure failures must remain visible as blockers; they do\nnot authorize protected-file edits or repeated repair attempts. An unsuccessful migration must\nnot be reported as a successful sync or handed off as a validated candidate.\n",{"name":5,"description":7},"main","93be4925735518cba1e63592542c388576253a37","automation\u002Fteams-sample-sync\u002Fskills\u002Fsync-teams-samples-to-agents-sdk",346,"https:\u002F\u002Fgithub.com\u002Fmicrosoft\u002FAgents","https:\u002F\u002Faka.ms\u002Fagentsdkdocs","https:\u002F\u002Fgithub.com\u002Fmicrosoft","https:\u002F\u002Fopensource.microsoft.com","Open source projects and samples from Microsoft","2026-11-14 08:54:12",{"source":8,"skillName":5,"commands":48,"prompt":58,"zipAvailable":59},[49,52,55],{"tool":50,"command":51},"npx","npx skills add microsoft\u002FAgents --skill sync-teams-samples-to-agents-sdk",{"tool":53,"command":54},"bunx","bunx skills add microsoft\u002FAgents --skill sync-teams-samples-to-agents-sdk",{"tool":56,"command":57},"pnpm","pnpm dlx skills add microsoft\u002FAgents --skill sync-teams-samples-to-agents-sdk","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002Fmicrosoft\u002FAgents\u002Fblob\u002Fmain\u002Fautomation\u002Fteams-sample-sync\u002Fskills\u002Fsync-teams-samples-to-agents-sdk\u002FSKILL.md",true,[],[62,82,97,110,119,142],{"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":32},"01M6PJCFNGCX555YERYQ459JFE","teams-sdk-to-agents-sdk-typescript-migration","Migrate a JavaScript or TypeScript application using the Microsoft Teams SDK App runtime to Microsoft 365 Agents SDK while preserving its Teams behaviors. Use for Teams SDK migrations, including automated sample synchronization; use the separate Bot Framework migration skill for botbuilder applications.","https:\u002F\u002Fgithub.com\u002Fmicrosoft\u002FAgents\u002Fblob\u002Fmain\u002Fagent-plugins\u002Fagents-for-js\u002Fskills\u002Fteams-sdk-to-agents-sdk-typescript-migration\u002FSKILL.md",[],[69,19,20,22,70,71,72,73,74,9,75,76,25,77,78,29,79,80,81,30],"typescript","agents sdk typescript","migration","teams sdk to agents sdk typescript migration","bot","javascript","applications","migrate","use","migrations","runtime","app","microsoft teams",{"skillNo":83,"name":84,"nameZh":6,"description":85,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":86,"categories":87,"keywords":93,"publishedAt":32},"01M69B8QV24JVPXH25EH77X0SZ","teams-app-manifest","Create or audit a Microsoft Teams app manifest for an existing Microsoft 365 Agents SDK application by mapping declared intent and source-code evidence to released manifest capabilities. Use when manifest.json is missing, incomplete, or must be checked against implemented Teams features. Does not configure Microsoft Entra, Azure Bot, Developer Portal, or deployment unless separately requested.","https:\u002F\u002Fgithub.com\u002Fmicrosoft\u002FAgents\u002Fblob\u002Fmain\u002Fagent-plugins\u002Fagents-sdk-common\u002Fskills\u002Fteams-app-manifest\u002FSKILL.md",[88],{"categoryNo":89,"categoryName":90,"taxonomyType":91,"taxonomyTypeDesc":92},"01JBSEEDCAT000000000000030","开发工程师","PROFESSION","适用职业",[22,94,95,96,9,20,19,73],"teams app manifest","azure","deployment",{"skillNo":98,"name":99,"nameZh":6,"description":100,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":101,"categories":102,"keywords":103,"publishedAt":32},"01M69B8MN62NBY93YTJAQG2Y81","agents-sdk-provision","Use when provisioning Azure resources for a Microsoft Agents SDK application — including creating an Azure Bot Service resource, setting up Entra app registrations, configuring identity credentials (UserManagedIdentity, FederatedCredentials, or ClientSecret), adding a Teams channel, running Bicep deployments for SSO, or setting up OAuth user sign-in connections via az CLI. Trigger even if the user doesn't say \"provision\" — use on requests like \"set up my bot on Azure\", \"deploy my bot\", \"configure Azure for my bot\", or \"get Teams SSO working.\" Applies to all languages (dotnet, Node.js, Python).","https:\u002F\u002Fgithub.com\u002Fmicrosoft\u002FAgents\u002Fblob\u002Fmain\u002Fagent-plugins\u002Fagents-sdk-common\u002Fskills\u002Fagents-sdk-provision\u002FSKILL.md",[],[19,20,104,73,105,106,9,107,108,109,95,22],"agents sdk provision","cli","python","dotnet","identity","deploy",{"skillNo":111,"name":112,"nameZh":6,"description":113,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":114,"categories":115,"keywords":116,"publishedAt":32},"01M69B8HFZ45NQGWQQD483TWPB","agents-sdk-to-prod","Assess, create, harden, deploy, or review production readiness of Python Microsoft 365 Agents SDK agents and their direct hosting\u002Foperations files. Use only for Agents SDK scenarios, not unrelated application hardening.","https:\u002F\u002Fgithub.com\u002Fmicrosoft\u002FAgents\u002Fblob\u002Fmain\u002Fagent-plugins\u002Fagents-for-python\u002Fskills\u002Fagents-sdk-to-prod\u002FSKILL.md",[],[19,20,117,118,106,9,109],"agents sdk to prod","review",{"skillNo":120,"name":121,"nameZh":6,"description":122,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":123,"categories":124,"keywords":133,"publishedAt":32},"01M69B8ENJGC9NPQBZAYAN4706","agents-sdk-python-otel","Use when adding, configuring, validating, or troubleshooting OpenTelemetry observability for a Microsoft 365 Agents SDK application in Python. Trigger when the user mentions OpenTelemetry, OTel, telemetry, traces, metrics, logs, OTLP, Aspire Dashboard, Application Insights, Azure Monitor, distributed tracing, custom tracers or meters, span sampling, or observing microsoft_agents SDK signals.","https:\u002F\u002Fgithub.com\u002Fmicrosoft\u002FAgents\u002Fblob\u002Fmain\u002Fagent-plugins\u002Fagents-for-python\u002Fskills\u002Fagents-sdk-python-otel\u002FSKILL.md",[125,130],{"categoryNo":126,"categoryName":127,"taxonomyType":128,"taxonomyTypeDesc":129},"01JBSEEDCAT000000000000013","分析与可视化","SCENARIO","使用场景",{"categoryNo":131,"categoryName":132,"taxonomyType":91,"taxonomyTypeDesc":92},"01JBSEEDCAT000000000000033","数据分析师",[20,134,135,106,19,136,9,137,138,139,95,140,141],"otel","agents sdk python otel","dashboard","telemetry","aspire","distributed","monitor","aspire dashboard",{"skillNo":143,"name":144,"nameZh":6,"description":145,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":146,"categories":147,"keywords":148,"publishedAt":32},"01M69B8C2FGRWXRJ35ZETW8ZV2","teams-sdk-to-agents-sdk-dotnet-migration","Use when migrating a customer's Teams SDK (teams.net) bot to the Microsoft 365 Agents SDK in .NET. Triggered by projects that depend on Microsoft.Teams.Plugins.AspNetCore, Microsoft.Teams.Apps, or Microsoft.Teams.Api and call builder.AddTeams() \u002F app.UseTeams().","https:\u002F\u002Fgithub.com\u002Fmicrosoft\u002FAgents\u002Fblob\u002Fmain\u002Fagent-plugins\u002Fagents-for-net\u002Fskills\u002Fteams-sdk-to-agents-sdk-dotnet-migration\u002FSKILL.md",[],[19,71,107,22,149,150,20,151,73,9,152,153,154,80,155,156,77,157],"agents sdk dotnet","teams sdk to agents sdk dotnet migration","plugins","customer","builder","apps","call","api","projects"]