[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M69BR7H3EEAYF7PWDD9THT1X":3,"skill-same:01M69BR7H3EEAYF7PWDD9THT1X":90},{"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":23,"publishedAt":47,"linkOnly":48,"markdownContent":49,"markdownBody":50,"frontMatter":51,"refName":52,"commitSha":53,"skillDirectory":54,"forksCount":55,"repositoryHtmlUrl":56,"repositoryHomepageUrl":57,"ownerHtmlUrl":58,"ownerBlogUrl":59,"ownerDescription":60,"updatedAt":61,"install":62,"resources":75},"01M69BR7H3EEAYF7PWDD9THT1X","add-acp-agent-support",null,"Add first-class support for an ACP-compatible agent CLI to Intelligent Terminal. Use when integrating a new built-in AI agent, ACP server command, authentication flow, model selection, interactive delegation, session hooks, onboarding, Settings, branding, GPO policy, documentation, tests, build, deployment, or live ACP and hook log verification.","microsoft\u002Fintelligent-terminal","microsoft","https:\u002F\u002Favatars.githubusercontent.com\u002Fu\u002F6154722?v=4","01M698VYDXZ6JW5WH3CRV650R8","Microsoft","01M69BR4043X0X0KRBRZVGJP2V",2217,"MIT","https:\u002F\u002Fgithub.com\u002Fmicrosoft\u002Fintelligent-terminal\u002Fblob\u002Fmain\u002F.github\u002Fskills\u002Fadd-acp-agent-support\u002FSKILL.md",[18],{"categoryNo":19,"categoryName":20,"taxonomyType":21,"taxonomyTypeDesc":22},"01JBSEEDCAT000000000000023","Skill与智能体开发","SCENARIO","使用场景",[24,25,26,27,28,29,30,31,32,33,34,35,36,37,38,39,40,41,42,43,44,45,46],"support","add","acp","add acp agent support","delegation","new","agent cli","when","selection","log","hooks","command","model","server","verification","cli","authentication","deployment","model selection","documentation","ai agent","policy","terminal","2026-11-10 10:12:30",false,"---\r\nname: add-acp-agent-support\r\ndescription: 'Add first-class support for an ACP-compatible agent CLI to Intelligent Terminal. Use when integrating a new built-in AI agent, ACP server command, authentication flow, model selection, interactive delegation, session hooks, onboarding, Settings, branding, GPO policy, documentation, tests, build, deployment, or live ACP and hook log verification.'\r\n---\r\n\r\n# Add ACP Agent Support\r\n\r\nIntegrate a new built-in agent across WTA, Terminal UI, settings, policy,\r\ntelemetry, documentation, and validation without leaving agent-specific\r\nbehavior inconsistent between layers.\r\n\r\n## When to Use This Skill\r\n\r\n- Add a native ACP-speaking agent CLI to Intelligent Terminal.\r\n- Add an ACP adapter for a CLI that does not speak ACP itself.\r\n- Promote a custom ACP command into a first-class built-in agent.\r\n- Add or repair ACP authentication, model probing, delegate, icon, or policy\r\n  support for an existing agent.\r\n- Add or repair session-tracking hooks, hook onboarding, Settings status, or\r\n  hook runtime behavior for a built-in agent.\r\n\r\n## Prerequisites\r\n\r\n- Work on a feature branch, never directly on `main` or `master`.\r\n- Read the repository and area-specific instructions before editing, including\r\n  `tools\u002Fwta\u002FAGENTS.md` and the Rust instruction files for WTA changes.\r\n- Obtain the agent's official CLI documentation and install a pinned or known\r\n  version for live verification.\r\n- Confirm that the CLI either exposes a long-running ACP server over stdio or\r\n  has a maintained ACP adapter. A normal interactive TUI is not an ACP server.\r\n\r\n## Workflow\r\n\r\nTrack the work with a TODO list because the Rust and C++ registries, UI,\r\npolicy, tests, and live verification must stay synchronized.\r\n\r\n1. **Define the agent contract.** Complete the capability matrix in\r\n   [integration-map.md](.\u002Freferences\u002Fintegration-map.md): executable, ACP\r\n   command, native-vs-adapter ownership, auth, model selection, interactive\r\n   delegate syntax, session resume, installation, and official branding.\r\n2. **Prove ACP behavior before editing.** Run the exact ACP command and verify\r\n   stdio initialization, session creation, model discovery, prompt streaming,\r\n   cancellation, and shutdown. Record the tested CLI\u002Fadapter version.\r\n3. **Inventory current integration surfaces.** Search for every existing\r\n   built-in agent ID and follow the current patterns. Do not rely on old line\r\n   numbers or assume the Rust registry is the only source of truth.\r\n4. **Implement the WTA profile and command behavior.** Add the profile,\r\n   ACP launch command, auth flow, model behavior, install guidance, and\r\n   resume metadata. Wire the canonical ID through the session subsystem when\r\n   session listing or resume is supported. Add delegate support only when the\r\n   agent has a true interactive initial-prompt invocation.\r\n5. **Wire Terminal surfaces.** Keep C++ built-in registries, ACP command\r\n   resolution, settings\u002Fmodel probing, telemetry sanitization, branding, and\r\n   policy-facing lists consistent. Use the detailed file map in\r\n   [integration-map.md](.\u002Freferences\u002Fintegration-map.md).\r\n6. **Decide and implement session hooks.** Treat hooks as a separate capability:\r\n   verify the CLI's official hook\u002Fplugin API, map lifecycle events to WTA,\r\n   suppress hook emission from the ACP process to avoid duplicate sessions,\r\n   and wire safe install\u002Fstatus\u002Funinstall\u002Fupgrade behavior through onboarding\r\n   and Settings. If the CLI has no suitable hook API, document session tracking\r\n   as unsupported instead of inferring it from ACP support.\r\n7. **Add focused tests.** Cover profile lookup, ACP command construction,\r\n   identification, session source round-trips and resume dispatch, auth command\r\n   generation, hook lifecycle and ownership behavior when implemented, and\r\n   every delegate shell path that applies: direct Windows, PowerShell 7,\r\n   Windows PowerShell 5.1, and WSL.\r\n8. **Update user and administrator documentation.** Document support,\r\n   installation\u002Fauth requirements, limitations, delegate behavior, and the\r\n   `AllowedAgents` identifier. Do not advertise hooks or history integration\r\n   unless they were implemented and tested.\r\n9. **Validate end to end.** Follow\r\n   [validation.md](.\u002Freferences\u002Fvalidation.md), including the WTA test suite,\r\n   explicit-target WTA build, Terminal build, package deployment, live ACP\r\n   prompt, auth path, model selection, hook-backed session tracking when\r\n   supported, delegate behavior, GPO filtering, and log inspection.\r\n10. **Prepare the PR.** Keep the diff scoped, cite the tested agent version and\r\n    ACP command, describe native-vs-adapter and hook support, list unsupported\r\n    features, and link the tracking issue with a closing keyword when\r\n    appropriate.\r\n\r\n## Decision Rules\r\n\r\n| Capability | Required decision |\r\n|------------|-------------------|\r\n| ACP launch | Prefer the CLI's native stdio mode. Use a maintained adapter only when native ACP is unavailable; pin the adapter when unbounded updates could break startup. |\r\n| Authentication | Use `InProtocol` only when ACP advertises and completes authentication. Use `External` when a separate CLI\u002Fprovider login is required, then verify the running ACP process can refresh credentials. |\r\n| Models | Distinguish flags accepted by the ACP server process from flags accepted by the interactive delegate CLI. Prefer ACP model APIs when the server supports them. |\r\n| Delegation | Use an interactive TUI invocation with an initial prompt. If the only interface is one-shot, omit first-class delegate support or explicitly ask the user to accept an auto-closing tab. |\r\n| Resume | Configure resume\u002Fnew-session metadata only after proving the exact CLI syntax and identifier semantics. Also add the agent to the session source type and every conversion boundary; profile metadata alone does not make a session resumable. |\r\n| Hooks\u002Fhistory | Treat these as separate integrations. ACP compatibility alone does not imply shell hooks or historical session support. Use only the CLI's documented hook\u002Fplugin API, define ownership-safe install semantics, and suppress duplicate tracking from ACP-mode processes. |\r\n\r\n## Gotchas\r\n\r\n- **Never substitute a TUI or one-shot command for the ACP server command.**\r\n  The agent pane requires a long-running JSON-RPC\u002FACP stdio process.\r\n- **Never use a one-shot delegate subcommand when an interactive prompt flag\r\n  exists.** A successful one-shot process exits and Terminal closes its tab.\r\n- **Preserve the CLI's argument grammar.** Top-level flags, subcommands, model\r\n  flags, and prompt arguments may require a specific order.\r\n- **Test every quoting layer.** Multiline prompts and paths with spaces pass\r\n  through different escaping in direct Windows, pwsh, Windows PowerShell, and\r\n  WSL launches.\r\n- **Keep both registries synchronized.** Update Rust execution metadata and\r\n  C++ discoverability\u002FGPO arrays together, including compile-time array sizes.\r\n- **Do not stop at `AgentProfile` for session support.** Add the canonical agent\r\n  to `CliSource`, parsing\u002Ffiltering, wire conversions, labels, resume command\r\n  synthesis, and ACP\u002FWSL session discovery where supported. Otherwise\r\n  `session\u002Flist` rows can appear as `Unknown(\"custom\")` and Enter fails with\r\n  \"source agent is unknown to this build\" even though the agent profile has a\r\n  valid resume flag.\r\n- **Do not run session hooks inside the shared ACP process.** ACP sessions are\r\n  already tracked by the helper\u002Fmaster path; hook emission there creates\r\n  duplicate session rows. Gate the plugin using a reliable ACP-mode signal and\r\n  verify normal interactive sessions still emit.\r\n- **Never overwrite user-owned hook files.** Use a managed-file marker or\r\n  manifest, commit ownership metadata last, preserve it until uninstall\r\n  cleanup succeeds, and make partial installs repairable.\r\n- **Keep the hook lifecycle complete.** Adding a runtime script is insufficient:\r\n  update install, status, uninstall, startup auto-upgrade, onboarding, Settings,\r\n  packaged bundle contents, tests, documentation, and diagnostics together.\r\n- **Separate ACP and delegate model flags.** Passing a TUI-only model flag to\r\n  the ACP server can prevent startup even when delegation works.\r\n- **Treat agent IDs as telemetry-sensitive.** Add only the canonical built-in\r\n  ID to the allowlist; continue bucketing custom commands and paths as\r\n  `custom`.\r\n- **Use official, license-compatible branding.** Make header artwork respond\r\n  to light, dark, and high-contrast themes; do not silently reuse another\r\n  agent's logo.\r\n- **Build the explicit Cargo target before packaging.** CascadiaPackage prefers\r\n  `target\u002Fx86_64-pc-windows-msvc\u002F...\u002Fwta.exe`; a stale binary there can shadow\r\n  a fresh host-target build.\r\n- **Update policy prose as well as runtime filtering.** `AllowedAgents` is\r\n  generic, but its ADML identifier list and built-in count can drift.\r\n\r\n## References\r\n\r\n- [Integration surface map](.\u002Freferences\u002Fintegration-map.md)\r\n- [Validation and live verification](.\u002Freferences\u002Fvalidation.md)\r\n","# Add ACP Agent Support\r\n\r\nIntegrate a new built-in agent across WTA, Terminal UI, settings, policy,\r\ntelemetry, documentation, and validation without leaving agent-specific\r\nbehavior inconsistent between layers.\r\n\r\n## When to Use This Skill\r\n\r\n- Add a native ACP-speaking agent CLI to Intelligent Terminal.\r\n- Add an ACP adapter for a CLI that does not speak ACP itself.\r\n- Promote a custom ACP command into a first-class built-in agent.\r\n- Add or repair ACP authentication, model probing, delegate, icon, or policy\r\n  support for an existing agent.\r\n- Add or repair session-tracking hooks, hook onboarding, Settings status, or\r\n  hook runtime behavior for a built-in agent.\r\n\r\n## Prerequisites\r\n\r\n- Work on a feature branch, never directly on `main` or `master`.\r\n- Read the repository and area-specific instructions before editing, including\r\n  `tools\u002Fwta\u002FAGENTS.md` and the Rust instruction files for WTA changes.\r\n- Obtain the agent's official CLI documentation and install a pinned or known\r\n  version for live verification.\r\n- Confirm that the CLI either exposes a long-running ACP server over stdio or\r\n  has a maintained ACP adapter. A normal interactive TUI is not an ACP server.\r\n\r\n## Workflow\r\n\r\nTrack the work with a TODO list because the Rust and C++ registries, UI,\r\npolicy, tests, and live verification must stay synchronized.\r\n\r\n1. **Define the agent contract.** Complete the capability matrix in\r\n   [integration-map.md](.\u002Freferences\u002Fintegration-map.md): executable, ACP\r\n   command, native-vs-adapter ownership, auth, model selection, interactive\r\n   delegate syntax, session resume, installation, and official branding.\r\n2. **Prove ACP behavior before editing.** Run the exact ACP command and verify\r\n   stdio initialization, session creation, model discovery, prompt streaming,\r\n   cancellation, and shutdown. Record the tested CLI\u002Fadapter version.\r\n3. **Inventory current integration surfaces.** Search for every existing\r\n   built-in agent ID and follow the current patterns. Do not rely on old line\r\n   numbers or assume the Rust registry is the only source of truth.\r\n4. **Implement the WTA profile and command behavior.** Add the profile,\r\n   ACP launch command, auth flow, model behavior, install guidance, and\r\n   resume metadata. Wire the canonical ID through the session subsystem when\r\n   session listing or resume is supported. Add delegate support only when the\r\n   agent has a true interactive initial-prompt invocation.\r\n5. **Wire Terminal surfaces.** Keep C++ built-in registries, ACP command\r\n   resolution, settings\u002Fmodel probing, telemetry sanitization, branding, and\r\n   policy-facing lists consistent. Use the detailed file map in\r\n   [integration-map.md](.\u002Freferences\u002Fintegration-map.md).\r\n6. **Decide and implement session hooks.** Treat hooks as a separate capability:\r\n   verify the CLI's official hook\u002Fplugin API, map lifecycle events to WTA,\r\n   suppress hook emission from the ACP process to avoid duplicate sessions,\r\n   and wire safe install\u002Fstatus\u002Funinstall\u002Fupgrade behavior through onboarding\r\n   and Settings. If the CLI has no suitable hook API, document session tracking\r\n   as unsupported instead of inferring it from ACP support.\r\n7. **Add focused tests.** Cover profile lookup, ACP command construction,\r\n   identification, session source round-trips and resume dispatch, auth command\r\n   generation, hook lifecycle and ownership behavior when implemented, and\r\n   every delegate shell path that applies: direct Windows, PowerShell 7,\r\n   Windows PowerShell 5.1, and WSL.\r\n8. **Update user and administrator documentation.** Document support,\r\n   installation\u002Fauth requirements, limitations, delegate behavior, and the\r\n   `AllowedAgents` identifier. Do not advertise hooks or history integration\r\n   unless they were implemented and tested.\r\n9. **Validate end to end.** Follow\r\n   [validation.md](.\u002Freferences\u002Fvalidation.md), including the WTA test suite,\r\n   explicit-target WTA build, Terminal build, package deployment, live ACP\r\n   prompt, auth path, model selection, hook-backed session tracking when\r\n   supported, delegate behavior, GPO filtering, and log inspection.\r\n10. **Prepare the PR.** Keep the diff scoped, cite the tested agent version and\r\n    ACP command, describe native-vs-adapter and hook support, list unsupported\r\n    features, and link the tracking issue with a closing keyword when\r\n    appropriate.\r\n\r\n## Decision Rules\r\n\r\n| Capability | Required decision |\r\n|------------|-------------------|\r\n| ACP launch | Prefer the CLI's native stdio mode. Use a maintained adapter only when native ACP is unavailable; pin the adapter when unbounded updates could break startup. |\r\n| Authentication | Use `InProtocol` only when ACP advertises and completes authentication. Use `External` when a separate CLI\u002Fprovider login is required, then verify the running ACP process can refresh credentials. |\r\n| Models | Distinguish flags accepted by the ACP server process from flags accepted by the interactive delegate CLI. Prefer ACP model APIs when the server supports them. |\r\n| Delegation | Use an interactive TUI invocation with an initial prompt. If the only interface is one-shot, omit first-class delegate support or explicitly ask the user to accept an auto-closing tab. |\r\n| Resume | Configure resume\u002Fnew-session metadata only after proving the exact CLI syntax and identifier semantics. Also add the agent to the session source type and every conversion boundary; profile metadata alone does not make a session resumable. |\r\n| Hooks\u002Fhistory | Treat these as separate integrations. ACP compatibility alone does not imply shell hooks or historical session support. Use only the CLI's documented hook\u002Fplugin API, define ownership-safe install semantics, and suppress duplicate tracking from ACP-mode processes. |\r\n\r\n## Gotchas\r\n\r\n- **Never substitute a TUI or one-shot command for the ACP server command.**\r\n  The agent pane requires a long-running JSON-RPC\u002FACP stdio process.\r\n- **Never use a one-shot delegate subcommand when an interactive prompt flag\r\n  exists.** A successful one-shot process exits and Terminal closes its tab.\r\n- **Preserve the CLI's argument grammar.** Top-level flags, subcommands, model\r\n  flags, and prompt arguments may require a specific order.\r\n- **Test every quoting layer.** Multiline prompts and paths with spaces pass\r\n  through different escaping in direct Windows, pwsh, Windows PowerShell, and\r\n  WSL launches.\r\n- **Keep both registries synchronized.** Update Rust execution metadata and\r\n  C++ discoverability\u002FGPO arrays together, including compile-time array sizes.\r\n- **Do not stop at `AgentProfile` for session support.** Add the canonical agent\r\n  to `CliSource`, parsing\u002Ffiltering, wire conversions, labels, resume command\r\n  synthesis, and ACP\u002FWSL session discovery where supported. Otherwise\r\n  `session\u002Flist` rows can appear as `Unknown(\"custom\")` and Enter fails with\r\n  \"source agent is unknown to this build\" even though the agent profile has a\r\n  valid resume flag.\r\n- **Do not run session hooks inside the shared ACP process.** ACP sessions are\r\n  already tracked by the helper\u002Fmaster path; hook emission there creates\r\n  duplicate session rows. Gate the plugin using a reliable ACP-mode signal and\r\n  verify normal interactive sessions still emit.\r\n- **Never overwrite user-owned hook files.** Use a managed-file marker or\r\n  manifest, commit ownership metadata last, preserve it until uninstall\r\n  cleanup succeeds, and make partial installs repairable.\r\n- **Keep the hook lifecycle complete.** Adding a runtime script is insufficient:\r\n  update install, status, uninstall, startup auto-upgrade, onboarding, Settings,\r\n  packaged bundle contents, tests, documentation, and diagnostics together.\r\n- **Separate ACP and delegate model flags.** Passing a TUI-only model flag to\r\n  the ACP server can prevent startup even when delegation works.\r\n- **Treat agent IDs as telemetry-sensitive.** Add only the canonical built-in\r\n  ID to the allowlist; continue bucketing custom commands and paths as\r\n  `custom`.\r\n- **Use official, license-compatible branding.** Make header artwork respond\r\n  to light, dark, and high-contrast themes; do not silently reuse another\r\n  agent's logo.\r\n- **Build the explicit Cargo target before packaging.** CascadiaPackage prefers\r\n  `target\u002Fx86_64-pc-windows-msvc\u002F...\u002Fwta.exe`; a stale binary there can shadow\r\n  a fresh host-target build.\r\n- **Update policy prose as well as runtime filtering.** `AllowedAgents` is\r\n  generic, but its ADML identifier list and built-in count can drift.\r\n\r\n## References\r\n\r\n- [Integration surface map](.\u002Freferences\u002Fintegration-map.md)\r\n- [Validation and live verification](.\u002Freferences\u002Fvalidation.md)\r\n",{"name":5,"description":7},"main","b83c3d762f8727f2ad299ddcc62fcf13bc7f35c7",".github\u002Fskills\u002Fadd-acp-agent-support",177,"https:\u002F\u002Fgithub.com\u002Fmicrosoft\u002Fintelligent-terminal","https:\u002F\u002Fdevblogs.microsoft.com\u002Fcommandline\u002Fannouncing-intelligent-terminal-version-0-1\u002F","https:\u002F\u002Fgithub.com\u002Fmicrosoft","https:\u002F\u002Fopensource.microsoft.com","Open source projects and samples from Microsoft","2026-11-12 20:43:52",{"source":8,"skillName":5,"commands":63,"prompt":73,"zipAvailable":74},[64,67,70],{"tool":65,"command":66},"npx","npx skills add microsoft\u002Fintelligent-terminal --skill add-acp-agent-support",{"tool":68,"command":69},"bunx","bunx skills add microsoft\u002Fintelligent-terminal --skill add-acp-agent-support",{"tool":71,"command":72},"pnpm","pnpm dlx skills add microsoft\u002Fintelligent-terminal --skill add-acp-agent-support","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002Fmicrosoft\u002Fintelligent-terminal\u002Fblob\u002Fmain\u002F.github\u002Fskills\u002Fadd-acp-agent-support\u002FSKILL.md",true,[76,82,86],{"path":77,"resourceType":78,"resourceTypeDesc":79,"sizeBytes":80,"sourceHtmlUrl":81},"references\u002Fintegration-map.md","REFERENCE","参考文档",18077,"https:\u002F\u002Fgithub.com\u002Fmicrosoft\u002Fintelligent-terminal\u002Fblob\u002Fmain\u002F.github\u002Fskills\u002Fadd-acp-agent-support\u002Freferences\u002Fintegration-map.md",{"path":83,"resourceType":78,"resourceTypeDesc":79,"sizeBytes":84,"sourceHtmlUrl":85},"references\u002Fvalidation.md",13953,"https:\u002F\u002Fgithub.com\u002Fmicrosoft\u002Fintelligent-terminal\u002Fblob\u002Fmain\u002F.github\u002Fskills\u002Fadd-acp-agent-support\u002Freferences\u002Fvalidation.md",{"path":87,"resourceType":78,"resourceTypeDesc":79,"sizeBytes":88,"sourceHtmlUrl":89},"research-brief-template.md",1191,"https:\u002F\u002Fgithub.com\u002Fdavila7\u002Fclaude-code-templates\u002Fblob\u002Fmain\u002Fcli-tool\u002Fcomponents\u002Fskills\u002Fai-research\u002Fdeep-research-notebooklm\u002Fresearch-brief-template.md",[91,123,151,173,205,232],{"skillNo":92,"name":93,"nameZh":6,"description":94,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":95,"licenseFileUrl":96,"sourceHtmlUrl":97,"categories":98,"keywords":103,"publishedAt":47},"01M69BS17H119AHC0VA6CGCG80","store-listing-localizer","Automate Microsoft Store (Partner Center) listing localization for Intelligent Terminal (Store ID 9NMQC2SSJX24). Use when asked to export\u002Fimport Store listings, localize release notes \u002F descriptions \u002F captions \u002F features into 80+ languages, update listingData CSV, or push Store listing translations without manually clicking through Partner Center. Drives Partner Center export\u002Fimport via the Playwright MCP and merges per-locale translations into the listingData CSV.","Apache-2.0","https:\u002F\u002Fgithub.com\u002Fmicrosoft\u002Fintelligent-terminal\u002Fblob\u002Fmain\u002F.github\u002Fskills\u002Fstore-listing-localizer\u002FLICENSE.txt","https:\u002F\u002Fgithub.com\u002Fmicrosoft\u002Fintelligent-terminal\u002Fblob\u002Fmain\u002F.github\u002Fskills\u002Fstore-listing-localizer\u002FSKILL.md",[99,102],{"categoryNo":100,"categoryName":101,"taxonomyType":21,"taxonomyTypeDesc":22},"01JBSEEDCAT000000000000004","电子表格",{"categoryNo":19,"categoryName":20,"taxonomyType":21,"taxonomyTypeDesc":22},[104,105,106,107,108,46,9,109,110,111,112,113,114,31,115,116,117,118,119,120,121,122],"store listing localizer","listing","store","notes","playwright","update","release","release notes","MCP","Captions","localize","features","playwright mcp","listings","export","localization","locale","automate","import",{"skillNo":124,"name":125,"nameZh":6,"description":126,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":127,"categories":128,"keywords":130,"publishedAt":47},"01M69BS54V1THPSKYAA7VFSBAY","upstream-sync","Periodically sync new commits from microsoft\u002Fterminal into this manually-forked intelligent-terminal repo by cherry-picking commit-by-commit onto a dated sync branch, auto-skipping revert pairs and empty commits, auto-resolving known take-upstream files, and stopping cleanly on genuine conflicts. The agent (you, reading this file) is the orchestrator — the PowerShell scripts are atomic operations you invoke one at a time. Use when the user asks to \"sync upstream\", \"pull from microsoft\u002Fterminal\", \"run upstream sync\", \"catch up to upstream\", or wires this into a scheduler (weekly\u002Fdaily). Designed to be safe under repeated unattended runs.","https:\u002F\u002Fgithub.com\u002Fmicrosoft\u002Fintelligent-terminal\u002Fblob\u002Fmain\u002F.github\u002Fskills\u002Fupstream-sync\u002FSKILL.md",[129],{"categoryNo":19,"categoryName":20,"taxonomyType":21,"taxonomyTypeDesc":22},[131,132,133,134,46,9,135,136,137,138,139,140,141,142,29,143,144,145,31,146,147,148,149,150],"upstream sync","sync","upstream","run","sync upstream","safe","commit","weekly","branch","powershell","time","up","files","auto","invoke","you","one at a time","conflicts","catch","orchestrator",{"skillNo":152,"name":153,"nameZh":6,"description":154,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":155,"categories":156,"keywords":157,"publishedAt":47},"01M69BRY6Z1T250VCQDTQ8ZFMQ","release-notes","Generate user-facing release notes for Intelligent Terminal. Use when asked to write release notes, changelog, what-is-new summary, or prepare a release. Compares git commits between releases, looks up PR-linked issues and community contributors, then outputs formatted notes with \"Verbed + Impact + Scenario\" style bullets, issue references, and contributor thanks.","https:\u002F\u002Fgithub.com\u002Fmicrosoft\u002Fintelligent-terminal\u002Fblob\u002Fmain\u002F.github\u002Fskills\u002Frelease-notes\u002FSKILL.md",[],[107,110,111,158,159,46,160,161,162,142,163,29,164,165,31,166,167,168,169,170,171,172],"pr","generate","git","prepare","community","issues","impact","contributor","references","changelog","releases","write","scenario","issue","contributors",{"skillNo":174,"name":175,"nameZh":6,"description":176,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":177,"categories":178,"keywords":186,"publishedAt":47},"01M69BRV95KH26NCNHGKX4BGTJ","pr-integration-test","Design, implement, and validate Intelligent Terminal integration tests for a target pull request or regression. Use when asked to add PR integration tests, convert a bug fix into E2E coverage, prove existing behavior still works, map tests to the release checklist, or verify E2E reports mark checklist cases complete.","https:\u002F\u002Fgithub.com\u002Fmicrosoft\u002Fintelligent-terminal\u002Fblob\u002Fmain\u002F.github\u002Fskills\u002Fpr-integration-test\u002FSKILL.md",[179,182,185],{"categoryNo":180,"categoryName":181,"taxonomyType":21,"taxonomyTypeDesc":22},"01JBSEEDCAT000000000000008","测试与质量",{"categoryNo":183,"categoryName":184,"taxonomyType":21,"taxonomyTypeDesc":22},"01JBSEEDCAT000000000000015","视觉设计",{"categoryNo":19,"categoryName":20,"taxonomyType":21,"taxonomyTypeDesc":22},[187,158,188,189,190,191,192,46,110,193,194,195,196,197,198,199,200,31,201,202,203,25,204],"test","pr integration test","integration test","integration","integration tests","pull request","validate","design","implement","coverage","regression","release checklist","fix","map","reports","request","bug","pull",{"skillNo":206,"name":207,"nameZh":6,"description":208,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":209,"categories":210,"keywords":212,"publishedAt":47},"01M69BRR7XQK0K0S4Z2Y81GX20","pr-accessibility","Review and repair native Windows WinUI, XAML, C++, UI Automation, keyboard, focus, screen-reader, high-contrast, scaling, settings, tab, pane, and agent-card accessibility changes. Use for accessibility analysis of Intelligent Terminal UI pull requests and focused local accessibility checks.","https:\u002F\u002Fgithub.com\u002Fmicrosoft\u002Fintelligent-terminal\u002Fblob\u002Fmain\u002F.github\u002Fskills\u002Fpr-accessibility\u002FSKILL.md",[211],{"categoryNo":19,"categoryName":20,"taxonomyType":21,"taxonomyTypeDesc":22},[158,213,214,215,216,217,218,46,219,220,221,222,223,224,225,226,227,228,229,230,204,231],"accessibility","pr accessibility","xaml","windows","pull requests","winui","automation","review","scaling","card","local","analysis","keyboard","focus","native","screen","contrast","ui","repair",{"skillNo":233,"name":234,"nameZh":6,"description":235,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":236,"categories":237,"keywords":238,"publishedAt":47},"01M69BRNTFHGZ2CND9G3KWHPS7","performance-review","Review Intelligent Terminal performance changes in local work, commit ranges, branches, or PRs. Use for renderer, text-buffer, VT, UI-thread, tab\u002Fpane, WTA, async, session, logging, allocation, event-amplification, benchmark, profiling, responsiveness, memory, and CI-cost changes.","https:\u002F\u002Fgithub.com\u002Fmicrosoft\u002Fintelligent-terminal\u002Fblob\u002Fmain\u002F.github\u002Fskills\u002Fperformance-review\u002FSKILL.md",[],[239,240,220,241,46,242,137,243,223,244,245,246,247,248,230,249,250,251,252,253],"performance","performance review","memory","benchmark","ci","branches","buffer","text","work","allocation","logging","for","event","renderer","async"]