[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M699EGE8NMP7RNFP51JKMB8T":3,"skill-same:01M699EGE8NMP7RNFP51JKMB8T":58},{"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":25,"linkOnly":26,"markdownContent":27,"markdownBody":28,"frontMatter":29,"refName":35,"commitSha":36,"skillDirectory":37,"forksCount":38,"repositoryHtmlUrl":39,"repositoryHomepageUrl":6,"ownerHtmlUrl":40,"ownerBlogUrl":41,"ownerDescription":42,"updatedAt":43,"install":44,"resources":57},"01M699EGE8NMP7RNFP51JKMB8T","clone-agent",null,"Clone a Copilot Studio agent from the cloud. Guides through environment selection, agent selection, and downloads agent YAML files.","microsoft\u002Fskills-for-copilot-studio","microsoft","https:\u002F\u002Favatars.githubusercontent.com\u002Fu\u002F6154722?v=4","01M698VYDXZ6JW5WH3CRV650R8","Microsoft","01M699DXBD563FYBGWKPJJRAVM",492,"MIT","https:\u002F\u002Fgithub.com\u002Fmicrosoft\u002Fskills-for-copilot-studio\u002Fblob\u002Fmain\u002Fskills\u002Fclone-agent\u002FSKILL.md",[18],{"categoryNo":19,"categoryName":20,"taxonomyType":21,"taxonomyTypeDesc":22},"01JBSEEDCAT000000000000023","Skill与智能体开发","SCENARIO","使用场景",[24],"clone agent","2026-11-10 10:12:30",false,"---\nuser-invocable: false\ndescription: Clone a Copilot Studio agent from the cloud. Guides through environment selection, agent selection, and downloads agent YAML files.\nargument-hint: [agent name or environment hint]\nallowed-tools: Bash(node *manage-agent.bundle.js *), Read, Glob, Grep\ncontext: fork\nagent: copilot-studio-manage\n---\n\n# Clone Agent\n\nGuided flow to clone a Copilot Studio agent from the cloud to a local workspace. Walks the user through environment selection, agent selection, and downloads the agent's YAML files.\n\n## IMPORTANT: Do Not Modify Scripts\n\nThis is a new capability under active development. If the manage-agent script fails, **do not attempt to fix, patch, or work around it**. Instead:\n1. Show the user the full error output\n2. Direct them to https:\u002F\u002Fgithub.com\u002Fmicrosoft\u002Fskills-for-copilot-studio\u002Fissues\n3. Suggest using the Copilot Studio VS Code extension directly as a fallback for push\u002Fpull\u002Fclone\n\n## Phase 0: Resolve Configuration\n\nLook for existing connection details in this order. Stop at the first source that provides a `tenantId`:\n\n### 0a. Scan for existing `.mcs\u002Fconn.json` files\n\nSearch the filesystem for previously cloned agents — these already have all the connection details:\n\n```\nGlob: **\u002F.mcs\u002Fconn.json\n```\n\nAlso search common project locations:\n\n```\nGlob: \u002FUsers\u002F**\u002Fprojects\u002F**\u002F.mcs\u002Fconn.json\n```\n\nEach `conn.json` contains `TenantId`, `EnvironmentId`, `DataverseEndpoint`, `AgentManagementEndpoint`, and `AccountInfo`. Parse any found files and collect unique tenant\u002Fenvironment pairs. If matches are found, present them to the user:\n\n> **Found existing agent connections:**\n> 1. Employee Assistant — Elad's Env (tenant: 8a235459...)\n> 2. IT Agent — Contoso Dev (tenant: efb073bb...)\n>\n> Use one of these, or enter a different tenant ID?\n\nIf the user picks one → extract `tenantId`, `environmentId`, `environmentUrl`, `agentMgmtUrl` and **skip to Phase 2** (or Phase 1 if they want a different environment).\n\n### 0b. Check for a Copilot Studio URL\n\nIf the user pastes a Copilot Studio URL (e.g. from their browser while viewing the agent), extract environment and agent IDs directly — no need for `list-envs` or `list-agents`.\n\nRecognised URL formats:\n```\nhttps:\u002F\u002Fcopilotstudio.microsoft.com\u002Fenvironments\u002F\u003CenvId>\u002Fbots\u002F\u003CagentId>\u002Foverview\nhttps:\u002F\u002Fcopilotstudio.preview.microsoft.com\u002Fenvironments\u002F\u003CenvId>\u002Fbots\u002F\u003CagentId>\n```\n\nIf the user provides a URL like this, you still need a `tenantId` (from a `conn.json` or by asking the user). Then **skip to Phase 3**, passing `--url` instead of `--agent-id` \u002F `--environment-id` \u002F `--environment-url` \u002F `--agent-mgmt-url`:\n\n```bash\nnode ${CLAUDE_SKILL_DIR}\u002F..\u002F..\u002Fscripts\u002Fmanage-agent.bundle.js clone \\\n  --workspace \".\" \\\n  --tenant-id \"\u003CtenantId>\" \\\n  --url \"\u003CcopilotStudioUrl>\"\n```\n\nThe script will parse the URL to extract the environment ID and agent ID, then resolve the remaining environment details (Dataverse URL, agent management URL) automatically via the BAP API.\n\n### 0c. Ask the user\n\nIf no `conn.json` found (or user wants a different tenant) → ask for their **tenant ID** (required).\n\nNo `--client-id` is needed — the script uses VS Code's first-party client ID with interactive browser login automatically.\n\n## Phase 1: Select Environment\n\nTell the user: **\"A browser window may open for Microsoft sign-in (tokens are cached after first login).\"**\n\nRun the list-envs command:\n\n```bash\nnode ${CLAUDE_SKILL_DIR}\u002F..\u002F..\u002Fscripts\u002Fmanage-agent.bundle.js list-envs \\\n  --tenant-id \"\u003CtenantId>\"\n```\n\n**Timeout: 300000ms (5 minutes)** — set this on the Bash tool call to allow time for browser auth.\n\nParse the JSON output. On success (`status: \"ok\"`), present the environments as a numbered list to the user:\n\n```\n1. Contoso Dev (abc123-...)\n2. Contoso Prod (def456-...)\n```\n\nAsk the user to pick an environment. Extract:\n- `environmentId`\n- `environmentUrl` (the `url` or `dataverseUrl` field)\n- `agentMgmtUrl` (the `agentManagementUrl` field)\n\n## Phase 2: Select Agent\n\nFirst, ask the user: **\"Do you want to list only agents you own, or all agents in the environment?\"**\n\n- If **only mine** → run without `--no-owner` (default, filters by current user)\n- If **all agents** → add `--no-owner` flag\n\n```bash\nnode ${CLAUDE_SKILL_DIR}\u002F..\u002F..\u002Fscripts\u002Fmanage-agent.bundle.js list-agents \\\n  --tenant-id \"\u003CtenantId>\" \\\n  --environment-url \"\u003CenvironmentUrl>\" \\\n  [--no-owner]\n```\n\n**Timeout: 300000ms (5 minutes)**\n\nParse the JSON output. Each agent has `agentId`, `displayName`, and `ownedByCurrentUser`. Present agents as a numbered list:\n\n```\n1. My Support Bot (yours)\n2. HR Assistant\n3. IT Helpdesk (yours)\n```\n\nAsk the user to pick an agent. Extract the `agentId`.\n\n## Phase 3: Clone\n\nRun the clone command. The workspace should be the current directory (`.`). The `--agent-id` is required (from Phase 2):\n\n```bash\nnode ${CLAUDE_SKILL_DIR}\u002F..\u002F..\u002Fscripts\u002Fmanage-agent.bundle.js clone \\\n  --workspace \".\" \\\n  --tenant-id \"\u003CtenantId>\" \\\n  --agent-id \"\u003CagentId>\" \\\n  --environment-id \"\u003CenvironmentId>\" \\\n  --environment-url \"\u003CenvironmentUrl>\" \\\n  --agent-mgmt-url \"\u003CagentMgmtUrl>\"\n```\n\n**Timeout: 300000ms (5 minutes)**\n\nOn success:\n1. Run `Glob: **\u002Fagent.mcs.yml` to find and show the cloned agent file\n2. Check that `.mcs\u002Fconn.json` was created in the agent directory\n3. Summarize what was cloned and where the files are\n\n## Error Handling\n\n| Error | Resolution |\n|-------|-----------|\n| Browser auth fails or times out | Ask user to try again; check that they have access to the tenant |\n| No environments found | Verify tenant ID is correct and user has Power Platform access |\n| No agents found | Verify environment selection; user may need Copilot Studio access |\n| Clone fails | Check permissions; the user needs maker\u002Fadmin access to the agent |\n","# Clone Agent\n\nGuided flow to clone a Copilot Studio agent from the cloud to a local workspace. Walks the user through environment selection, agent selection, and downloads the agent's YAML files.\n\n## IMPORTANT: Do Not Modify Scripts\n\nThis is a new capability under active development. If the manage-agent script fails, **do not attempt to fix, patch, or work around it**. Instead:\n1. Show the user the full error output\n2. Direct them to https:\u002F\u002Fgithub.com\u002Fmicrosoft\u002Fskills-for-copilot-studio\u002Fissues\n3. Suggest using the Copilot Studio VS Code extension directly as a fallback for push\u002Fpull\u002Fclone\n\n## Phase 0: Resolve Configuration\n\nLook for existing connection details in this order. Stop at the first source that provides a `tenantId`:\n\n### 0a. Scan for existing `.mcs\u002Fconn.json` files\n\nSearch the filesystem for previously cloned agents — these already have all the connection details:\n\n```\nGlob: **\u002F.mcs\u002Fconn.json\n```\n\nAlso search common project locations:\n\n```\nGlob: \u002FUsers\u002F**\u002Fprojects\u002F**\u002F.mcs\u002Fconn.json\n```\n\nEach `conn.json` contains `TenantId`, `EnvironmentId`, `DataverseEndpoint`, `AgentManagementEndpoint`, and `AccountInfo`. Parse any found files and collect unique tenant\u002Fenvironment pairs. If matches are found, present them to the user:\n\n> **Found existing agent connections:**\n> 1. Employee Assistant — Elad's Env (tenant: 8a235459...)\n> 2. IT Agent — Contoso Dev (tenant: efb073bb...)\n>\n> Use one of these, or enter a different tenant ID?\n\nIf the user picks one → extract `tenantId`, `environmentId`, `environmentUrl`, `agentMgmtUrl` and **skip to Phase 2** (or Phase 1 if they want a different environment).\n\n### 0b. Check for a Copilot Studio URL\n\nIf the user pastes a Copilot Studio URL (e.g. from their browser while viewing the agent), extract environment and agent IDs directly — no need for `list-envs` or `list-agents`.\n\nRecognised URL formats:\n```\nhttps:\u002F\u002Fcopilotstudio.microsoft.com\u002Fenvironments\u002F\u003CenvId>\u002Fbots\u002F\u003CagentId>\u002Foverview\nhttps:\u002F\u002Fcopilotstudio.preview.microsoft.com\u002Fenvironments\u002F\u003CenvId>\u002Fbots\u002F\u003CagentId>\n```\n\nIf the user provides a URL like this, you still need a `tenantId` (from a `conn.json` or by asking the user). Then **skip to Phase 3**, passing `--url` instead of `--agent-id` \u002F `--environment-id` \u002F `--environment-url` \u002F `--agent-mgmt-url`:\n\n```bash\nnode ${CLAUDE_SKILL_DIR}\u002F..\u002F..\u002Fscripts\u002Fmanage-agent.bundle.js clone \\\n  --workspace \".\" \\\n  --tenant-id \"\u003CtenantId>\" \\\n  --url \"\u003CcopilotStudioUrl>\"\n```\n\nThe script will parse the URL to extract the environment ID and agent ID, then resolve the remaining environment details (Dataverse URL, agent management URL) automatically via the BAP API.\n\n### 0c. Ask the user\n\nIf no `conn.json` found (or user wants a different tenant) → ask for their **tenant ID** (required).\n\nNo `--client-id` is needed — the script uses VS Code's first-party client ID with interactive browser login automatically.\n\n## Phase 1: Select Environment\n\nTell the user: **\"A browser window may open for Microsoft sign-in (tokens are cached after first login).\"**\n\nRun the list-envs command:\n\n```bash\nnode ${CLAUDE_SKILL_DIR}\u002F..\u002F..\u002Fscripts\u002Fmanage-agent.bundle.js list-envs \\\n  --tenant-id \"\u003CtenantId>\"\n```\n\n**Timeout: 300000ms (5 minutes)** — set this on the Bash tool call to allow time for browser auth.\n\nParse the JSON output. On success (`status: \"ok\"`), present the environments as a numbered list to the user:\n\n```\n1. Contoso Dev (abc123-...)\n2. Contoso Prod (def456-...)\n```\n\nAsk the user to pick an environment. Extract:\n- `environmentId`\n- `environmentUrl` (the `url` or `dataverseUrl` field)\n- `agentMgmtUrl` (the `agentManagementUrl` field)\n\n## Phase 2: Select Agent\n\nFirst, ask the user: **\"Do you want to list only agents you own, or all agents in the environment?\"**\n\n- If **only mine** → run without `--no-owner` (default, filters by current user)\n- If **all agents** → add `--no-owner` flag\n\n```bash\nnode ${CLAUDE_SKILL_DIR}\u002F..\u002F..\u002Fscripts\u002Fmanage-agent.bundle.js list-agents \\\n  --tenant-id \"\u003CtenantId>\" \\\n  --environment-url \"\u003CenvironmentUrl>\" \\\n  [--no-owner]\n```\n\n**Timeout: 300000ms (5 minutes)**\n\nParse the JSON output. Each agent has `agentId`, `displayName`, and `ownedByCurrentUser`. Present agents as a numbered list:\n\n```\n1. My Support Bot (yours)\n2. HR Assistant\n3. IT Helpdesk (yours)\n```\n\nAsk the user to pick an agent. Extract the `agentId`.\n\n## Phase 3: Clone\n\nRun the clone command. The workspace should be the current directory (`.`). The `--agent-id` is required (from Phase 2):\n\n```bash\nnode ${CLAUDE_SKILL_DIR}\u002F..\u002F..\u002Fscripts\u002Fmanage-agent.bundle.js clone \\\n  --workspace \".\" \\\n  --tenant-id \"\u003CtenantId>\" \\\n  --agent-id \"\u003CagentId>\" \\\n  --environment-id \"\u003CenvironmentId>\" \\\n  --environment-url \"\u003CenvironmentUrl>\" \\\n  --agent-mgmt-url \"\u003CagentMgmtUrl>\"\n```\n\n**Timeout: 300000ms (5 minutes)**\n\nOn success:\n1. Run `Glob: **\u002Fagent.mcs.yml` to find and show the cloned agent file\n2. Check that `.mcs\u002Fconn.json` was created in the agent directory\n3. Summarize what was cloned and where the files are\n\n## Error Handling\n\n| Error | Resolution |\n|-------|-----------|\n| Browser auth fails or times out | Ask user to try again; check that they have access to the tenant |\n| No environments found | Verify tenant ID is correct and user has Power Platform access |\n| No agents found | Verify environment selection; user may need Copilot Studio access |\n| Clone fails | Check permissions; the user needs maker\u002Fadmin access to the agent |\n",{"agent":30,"context":31,"description":7,"allowed-tools":32,"argument-hint":33,"user-invocable":26},"copilot-studio-manage","fork","Bash(node *manage-agent.bundle.js *), Read, Glob, Grep",[34],"agent name or environment hint","main","9c42d3a612c6e06389b6e5b4eed579aaed1a8b63","skills\u002Fclone-agent",103,"https:\u002F\u002Fgithub.com\u002Fmicrosoft\u002Fskills-for-copilot-studio","https:\u002F\u002Fgithub.com\u002Fmicrosoft","https:\u002F\u002Fopensource.microsoft.com","Open source projects and samples from Microsoft","2026-11-12 17:03:17",{"source":8,"skillName":5,"commands":45,"prompt":55,"zipAvailable":56},[46,49,52],{"tool":47,"command":48},"npx","npx skills add microsoft\u002Fskills-for-copilot-studio --skill clone-agent",{"tool":50,"command":51},"bunx","bunx skills add microsoft\u002Fskills-for-copilot-studio --skill clone-agent",{"tool":53,"command":54},"pnpm","pnpm dlx skills add microsoft\u002Fskills-for-copilot-studio --skill clone-agent","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002Fmicrosoft\u002Fskills-for-copilot-studio\u002Fblob\u002Fmain\u002Fskills\u002Fclone-agent\u002FSKILL.md",true,[],[59,67,85,94,105,114],{"skillNo":60,"name":61,"nameZh":6,"description":62,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":63,"categories":64,"keywords":66,"publishedAt":25},"01M699FD973RBVBTQYE48GBFPG","validate","Validate Copilot Studio agent YAML files using the LSP binary's full diagnostics (YAML structure, Power Fx, schema, cross-file references). Use when the user asks to check, validate, or verify YAML files.","https:\u002F\u002Fgithub.com\u002Fmicrosoft\u002Fskills-for-copilot-studio\u002Fblob\u002Fmain\u002Fskills\u002Fvalidate\u002FSKILL.md",[65],{"categoryNo":19,"categoryName":20,"taxonomyType":21,"taxonomyTypeDesc":22},[61],{"skillNo":68,"name":69,"nameZh":6,"description":70,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":71,"categories":72,"keywords":79,"publishedAt":25},"01M699FBJC22B4HCFH9MA844C3","test-auth","Authenticate for Copilot Studio evaluation API and SDK chat. Caches a token that is shared across run-eval and chat-sdk skills. Run this before any eval or SDK chat workflow. Requires an App Registration with MakerOperations and Copilots.Invoke permissions.","https:\u002F\u002Fgithub.com\u002Fmicrosoft\u002Fskills-for-copilot-studio\u002Fblob\u002Fmain\u002Fskills\u002Ftest-auth\u002FSKILL.md",[73,76],{"categoryNo":74,"categoryName":75,"taxonomyType":21,"taxonomyTypeDesc":22},"01JBSEEDCAT000000000000008","测试与质量",{"categoryNo":77,"categoryName":78,"taxonomyType":21,"taxonomyTypeDesc":22},"01JBSEEDCAT000000000000010","后端与接口",[80,81,82,83,84],"test","auth","test auth","sdk","workflow",{"skillNo":86,"name":87,"nameZh":6,"description":88,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":89,"categories":90,"keywords":92,"publishedAt":25},"01M699FA38G1TAVA0JWD9DG783","run-tests-kit","Run a batch test suite via the Copilot Studio Kit (Dataverse API). Uses the Power CAT Copilot Studio Kit to execute test cases against a published agent and produces pass\u002Ffail results with latencies. Requires the Kit installed in the environment, an App Registration with Dataverse permissions, and a published agent.","https:\u002F\u002Fgithub.com\u002Fmicrosoft\u002Fskills-for-copilot-studio\u002Fblob\u002Fmain\u002Fskills\u002Frun-tests-kit\u002FSKILL.md",[91],{"categoryNo":74,"categoryName":75,"taxonomyType":21,"taxonomyTypeDesc":22},[93,80],"run tests kit",{"skillNo":95,"name":96,"nameZh":6,"description":97,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":98,"categories":99,"keywords":103,"publishedAt":25},"01M699F8EP4BZT1EA3R4Y40X98","run-eval","Run evaluations against a Copilot Studio agent via the Power Platform Evaluation API. Works on DRAFT agents — no publish step required. Lists test sets, starts a run, polls until complete, fetches results, and proposes YAML fixes for failures. Use when the user wants to test agent changes without publishing.","https:\u002F\u002Fgithub.com\u002Fmicrosoft\u002Fskills-for-copilot-studio\u002Fblob\u002Fmain\u002Fskills\u002Frun-eval\u002FSKILL.md",[100,101,102],{"categoryNo":74,"categoryName":75,"taxonomyType":21,"taxonomyTypeDesc":22},{"categoryNo":77,"categoryName":78,"taxonomyType":21,"taxonomyTypeDesc":22},{"categoryNo":19,"categoryName":20,"taxonomyType":21,"taxonomyTypeDesc":22},[104,80],"run eval",{"skillNo":106,"name":107,"nameZh":6,"description":108,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":109,"categories":110,"keywords":112,"publishedAt":25},"01M699F6NR5Z4RTN5MWH5WYV9H","new-topic","Create a new Copilot Studio topic YAML file. Use when the user asks to create a new topic, conversation flow, or dialog for their agent.","https:\u002F\u002Fgithub.com\u002Fmicrosoft\u002Fskills-for-copilot-studio\u002Fblob\u002Fmain\u002Fskills\u002Fnew-topic\u002FSKILL.md",[111],{"categoryNo":19,"categoryName":20,"taxonomyType":21,"taxonomyTypeDesc":22},[113],"new topic",{"skillNo":115,"name":116,"nameZh":6,"description":117,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":118,"categories":119,"keywords":121,"publishedAt":25},"01M699F4QN5BMQA3X9F7WC1NS0","manage-agent","Push\u002Fpull Copilot Studio agent content via the VS Code extension's LanguageServerHost LSP binary. Handles authentication (interactive browser login for push\u002Fpull, device code flow for chat token), sync push, sync pull, clone, and diff operations.","https:\u002F\u002Fgithub.com\u002Fmicrosoft\u002Fskills-for-copilot-studio\u002Fblob\u002Fmain\u002Fskills\u002Fmanage-agent\u002FSKILL.md",[120],{"categoryNo":19,"categoryName":20,"taxonomyType":21,"taxonomyTypeDesc":22},[122,81,123],"manage agent","sync"]