[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M69BKRPYV9KYVD15B27Y183S":3,"skill-same:01M69BKRPYV9KYVD15B27Y183S":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":23,"publishedAt":29,"linkOnly":30,"markdownContent":31,"markdownBody":32,"frontMatter":33,"refName":38,"commitSha":39,"skillDirectory":40,"forksCount":41,"repositoryHtmlUrl":42,"repositoryHomepageUrl":6,"ownerHtmlUrl":43,"ownerBlogUrl":44,"ownerDescription":45,"updatedAt":46,"install":47,"resources":60},"01M69BKRPYV9KYVD15B27Y183S","copilot-dev-camp-lab-author",null,"Creates new Copilot Dev Camp lab markdown files under docs\u002Fpages\u002F\u003Csubfolder>\u002F with a consistent structure, concise exercises, and required custom components.\nUse when asked to author a new lab, scaffold a lab file, or draft a Copilot Dev Camp lab page.","microsoft\u002Fcopilot-camp","microsoft","https:\u002F\u002Favatars.githubusercontent.com\u002Fu\u002F6154722?v=4","01M698VYDXZ6JW5WH3CRV650R8","Microsoft","01M69BKPGZB373MV703EZS5BBG",679,"MIT","https:\u002F\u002Fgithub.com\u002Fmicrosoft\u002Fcopilot-camp\u002Fblob\u002Fmain\u002F.github\u002Fskills\u002Fcopilot-dev-camp-lab-author\u002FSKILL.md",[18],{"categoryNo":19,"categoryName":20,"taxonomyType":21,"taxonomyTypeDesc":22},"01JBSEEDCAT000000000000016","图像与多媒体","SCENARIO","使用场景",[24,25,26,27,28],"copilot","copilot dev camp lab author","docs","components","scaffold","2026-11-10 10:12:30",false,"---\nname: copilot-dev-camp-lab-author\ndescription: |\n  Creates new Copilot Dev Camp lab markdown files under docs\u002Fpages\u002F\u003Csubfolder>\u002F with a consistent structure, concise exercises, and required custom components.\n  Use when asked to author a new lab, scaffold a lab file, or draft a Copilot Dev Camp lab page.\nlicense: MIT\nmetadata:\n  owner: Copilot Dev Camp\n  version: \"1.0\"\n---\n\n# Copilot Dev Camp Lab Author\n\n## Purpose\n\nAuthor a new lab file for Copilot Dev Camp, with the right structure and writing style, and place it in the correct docs path.\n\n## Required Inputs\n\nCollect all required values before creating the lab:\n\n- Target subfolder under `docs\u002Fpages`.\n- Lab number.\n- Lab unique code.\n- Lab title.\n- Knowledge-base URLs (web sites\u002Fpages to use for grounded content).\n- Badge suggestions (`badgeId`, `badgeName`) for `cc-award`.\n\nIf the target subfolder is missing, ask for it.\nIf the lab number is missing, ask for it.\nIf knowledge-base URLs are missing, ask for them before drafting content.\n\n## File Placement Rules\n\n- Create the file only under `docs\u002Fpages\u002F\u003Csubfolder>\u002F`.\n- Use markdown file extension `.md`.\n- Suggested naming pattern: `\u003Clab-number>-\u003Cslug>.md`.\n- If file already exists, ask whether to pick a new number\u002Fslug or update existing content.\n\n## Frontmatter Requirements\n\nEvery lab markdown file must begin with YAML frontmatter containing the following fields:\n\n```yaml\n---\ncode: \u003Clab-unique-code>\ntitle: \u003Clab-title>\ndescription: \u003Cbrief-description-of-lab>\ntags: [tag1, tag2, tag3]\nlevel: \u003C100|200|300|400|500>\ntime: \u003Ctime-to-complete-in-minutes>\nbadge: \u003Cbadge-code>\nproducts: [product1, product2]\ncreated-date: \u003CYYYY-MM-DD>\nlast-edited-date: \u003CYYYY-MM-DD>\n---\n```\n\n### Frontmatter Field Definitions\n\n- **code**: Unique identifier for the lab (e.g., `WIQ01`).\n- **title**: Lab title matching the lab title in content.\n- **description**: 1-2 sentence summary of what students will learn (infer the value from the lab content, once created).\n- **tags**: Comma-separated list (ask user) converted to YAML list. Examples: `agents`, `copilot`, `m365`.\n- **level**: Difficulty level: `100` (beginner), `200` (intermediate), `300` (advanced), `400` (expert), `500` (professional).\n- **time**: Estimated time in minutes to complete the lab (infer the value based on the length of the content, once created).\n- **badge**: The badge code issued upon lab completion (e.g., `WorkIQ-Expert`).\n- **products**: Comma-separated list (ask user) converted to YAML list. Examples: `Teams`, `Copilot`, `SharePoint`, `Work IQ`.\n- **created-date**: Lab creation date in `YYYY-MM-DD` format.\n- **last-edited-date**: Most recent edit date in `YYYY-MM-DD` format.\n\n## Authoring Constraints\n\n- Every lab must have a unique code and title.\n- Every lab file must include YAML frontmatter with all required fields.\n- Use no more than 4-5 exercises total.\n- Each exercise must have no more than 5-6 steps.\n- Keep steps concise; fewer is preferred when pedagogically valid.\n- All links to external sites must include the `{target=_blank}` attribute so they open in a new tab. Example: `[Link text](https:\u002F\u002Fexample.com){target=_blank}`.\n\n## Writing Style And Structure\n\nUse this style in all generated labs:\n\n- Instructional and practical, focused on outcomes.\n- Clear progression from context to hands-on steps.\n- Short paragraphs and concrete actions.\n- Enterprise-aware language: prerequisites, validation, and expected outcomes.\n- Each exercise should end with a visible checkpoint step component.\n\nUse this baseline structure:\n\n1. Lab title and short intro.\n2. Scenario.\n3. Lab objectives.\n4. Exercises with numbered steps.\n5. Completion section.\n6. Visitor stats image.\n7. `cc-next` component.\n8. One or more `cc-award` components.\n\n## Mandatory Markup\n\n### A) Lab Title Heading\n\nImmediately after the YAML frontmatter (first line of markdown content), always add a level-1 heading with the lab code and title in this format:\n\n```markdown\n# Lab \u003Ccode> - \u003Ctitle>\n```\n\nExample:\n```markdown\n# Lab WIQ02 - Work IQ A2A Protocol\n```\n\n### B) Video placeholder near top (commented out)\n\nAlways add this placeholder block near the top of the lab, after the title:\n\n```html\n\u003C!--\n\u003Cdiv class=\"lab-intro-video\">\n    \u003Cdiv style=\"flex: 1; min-width: 0;\">\n        \u003Ciframe src=\"\u002F\u002Fwww.youtube.com\u002Fembed\u002F\u003CVIDEO_ID>\" frameborder=\"0\" allowfullscreen style=\"width: 100%; aspect-ratio: 16\u002F9;\">\n        \u003C\u002Fiframe>\n        \u003Cdiv>Get a quick overview of the lab in this video.\u003C\u002Fdiv>\n    \u003C\u002Fdiv>\n\u003C\u002Fdiv>\n-->\n```\n\n### C) End each step with cc-end-step\n\n### C) End each step with cc-end-step\n\nAt the end of every step, add:\n\n```xml\n\u003Ccc-end-step lab=\"\u003Clab-code>\" exercise=\"\u003Cexercise-number>\" step=\"\u003Cstep-number>\" \u002F>\n```\n\nValues must match the current lab code, exercise index, and step index.\n\n### D) Add cc-next at lab end\n\nAlways include:\n\n```xml\n\u003Ccc-next \u002F>\n```\n\n### E) Visitor stats image before awards\n\nAlways include, before awards:\n\n```html\n\u003Cimg src=\"https:\u002F\u002Fm365-visitor-stats.azurewebsites.net\u002Fcopilot-camp\u002F\u003Csection>\u002F\u003Clab-id>\" \u002F>\n```\n\n### F) One or more awards\n\nAlways include one or more awards and ask the developer for suitable badges if missing:\n\n```xml\n\u003Ccc-award badgeId=\"\u003CBadgeId>\" badgeName=\"\u003CBadge Name>\" \u002F>\n```\n\n### G) Image placeholders where useful\n\nWhen a step needs a screenshot, add placeholders:\n\n```markdown\n![TODO: replace with screenshot description](..\u002F..\u002Fassets\u002Fimages\u002F\u003Cfolder>\u002F\u003Cimage>.png)\n```\n\nUse the alternate text of the image to suggest to the lab author the image content to capture. The image path should be relative to the lab file.\n\n## Behavior Contract\n\nWhen this skill is triggered:\n\n1. Ask for any missing required inputs.\n2. Confirm target file path under `docs\u002Fpages\u002F\u003Csubfolder>\u002F`.\n3. Confirm lab number and lab code.\n4. Ask for knowledge-base URL list.\n5. Ask which badges to add.\n6. **Collect frontmatter information:**\n   - Prompt for lab title and description.\n   - Ask for tags (comma-separated) and convert to YAML list.\n   - Ask for difficulty level (100–500).\n   - Ask for estimated time to completion (in minutes).\n   - Ask for badge code.\n   - Ask for products (comma-separated) and convert to YAML list.\n   - Record created-date and last-edited-date (use current date if not provided).\n7. Generate the complete lab markdown with YAML frontmatter and required components.\n\nDo not skip questions when required inputs are missing.\n\n## Generation Checklist\n\nBefore finalizing:\n\n- YAML frontmatter is present at the top of the file with all required fields.\n- Lab title heading (format: `# Lab \u003Ccode> - \u003Ctitle>`) is present immediately after frontmatter.\n- Frontmatter values match the collected user inputs (code, title, description, tags, level, time, badge, products).\n- created-date and last-edited-date are in `YYYY-MM-DD` format.\n- File path is under `docs\u002Fpages\u002F\u003Csubfolder>\u002F`.\n- Exercise count is within limits.\n- Step count per exercise is within limits.\n- Every step ends with `cc-end-step`.\n- `cc-next` is present.\n- Visitor stats image is present before awards.\n- At least one `cc-award` exists.\n- Knowledge-base URLs were requested from developer.\n- All links to external sites use the `{target=_blank}` attribute.\n","# Copilot Dev Camp Lab Author\n\n## Purpose\n\nAuthor a new lab file for Copilot Dev Camp, with the right structure and writing style, and place it in the correct docs path.\n\n## Required Inputs\n\nCollect all required values before creating the lab:\n\n- Target subfolder under `docs\u002Fpages`.\n- Lab number.\n- Lab unique code.\n- Lab title.\n- Knowledge-base URLs (web sites\u002Fpages to use for grounded content).\n- Badge suggestions (`badgeId`, `badgeName`) for `cc-award`.\n\nIf the target subfolder is missing, ask for it.\nIf the lab number is missing, ask for it.\nIf knowledge-base URLs are missing, ask for them before drafting content.\n\n## File Placement Rules\n\n- Create the file only under `docs\u002Fpages\u002F\u003Csubfolder>\u002F`.\n- Use markdown file extension `.md`.\n- Suggested naming pattern: `\u003Clab-number>-\u003Cslug>.md`.\n- If file already exists, ask whether to pick a new number\u002Fslug or update existing content.\n\n## Frontmatter Requirements\n\nEvery lab markdown file must begin with YAML frontmatter containing the following fields:\n\n```yaml\n---\ncode: \u003Clab-unique-code>\ntitle: \u003Clab-title>\ndescription: \u003Cbrief-description-of-lab>\ntags: [tag1, tag2, tag3]\nlevel: \u003C100|200|300|400|500>\ntime: \u003Ctime-to-complete-in-minutes>\nbadge: \u003Cbadge-code>\nproducts: [product1, product2]\ncreated-date: \u003CYYYY-MM-DD>\nlast-edited-date: \u003CYYYY-MM-DD>\n---\n```\n\n### Frontmatter Field Definitions\n\n- **code**: Unique identifier for the lab (e.g., `WIQ01`).\n- **title**: Lab title matching the lab title in content.\n- **description**: 1-2 sentence summary of what students will learn (infer the value from the lab content, once created).\n- **tags**: Comma-separated list (ask user) converted to YAML list. Examples: `agents`, `copilot`, `m365`.\n- **level**: Difficulty level: `100` (beginner), `200` (intermediate), `300` (advanced), `400` (expert), `500` (professional).\n- **time**: Estimated time in minutes to complete the lab (infer the value based on the length of the content, once created).\n- **badge**: The badge code issued upon lab completion (e.g., `WorkIQ-Expert`).\n- **products**: Comma-separated list (ask user) converted to YAML list. Examples: `Teams`, `Copilot`, `SharePoint`, `Work IQ`.\n- **created-date**: Lab creation date in `YYYY-MM-DD` format.\n- **last-edited-date**: Most recent edit date in `YYYY-MM-DD` format.\n\n## Authoring Constraints\n\n- Every lab must have a unique code and title.\n- Every lab file must include YAML frontmatter with all required fields.\n- Use no more than 4-5 exercises total.\n- Each exercise must have no more than 5-6 steps.\n- Keep steps concise; fewer is preferred when pedagogically valid.\n- All links to external sites must include the `{target=_blank}` attribute so they open in a new tab. Example: `[Link text](https:\u002F\u002Fexample.com){target=_blank}`.\n\n## Writing Style And Structure\n\nUse this style in all generated labs:\n\n- Instructional and practical, focused on outcomes.\n- Clear progression from context to hands-on steps.\n- Short paragraphs and concrete actions.\n- Enterprise-aware language: prerequisites, validation, and expected outcomes.\n- Each exercise should end with a visible checkpoint step component.\n\nUse this baseline structure:\n\n1. Lab title and short intro.\n2. Scenario.\n3. Lab objectives.\n4. Exercises with numbered steps.\n5. Completion section.\n6. Visitor stats image.\n7. `cc-next` component.\n8. One or more `cc-award` components.\n\n## Mandatory Markup\n\n### A) Lab Title Heading\n\nImmediately after the YAML frontmatter (first line of markdown content), always add a level-1 heading with the lab code and title in this format:\n\n```markdown\n# Lab \u003Ccode> - \u003Ctitle>\n```\n\nExample:\n```markdown\n# Lab WIQ02 - Work IQ A2A Protocol\n```\n\n### B) Video placeholder near top (commented out)\n\nAlways add this placeholder block near the top of the lab, after the title:\n\n```html\n\u003C!--\n\u003Cdiv class=\"lab-intro-video\">\n    \u003Cdiv style=\"flex: 1; min-width: 0;\">\n        \u003Ciframe src=\"\u002F\u002Fwww.youtube.com\u002Fembed\u002F\u003CVIDEO_ID>\" frameborder=\"0\" allowfullscreen style=\"width: 100%; aspect-ratio: 16\u002F9;\">\n        \u003C\u002Fiframe>\n        \u003Cdiv>Get a quick overview of the lab in this video.\u003C\u002Fdiv>\n    \u003C\u002Fdiv>\n\u003C\u002Fdiv>\n-->\n```\n\n### C) End each step with cc-end-step\n\n### C) End each step with cc-end-step\n\nAt the end of every step, add:\n\n```xml\n\u003Ccc-end-step lab=\"\u003Clab-code>\" exercise=\"\u003Cexercise-number>\" step=\"\u003Cstep-number>\" \u002F>\n```\n\nValues must match the current lab code, exercise index, and step index.\n\n### D) Add cc-next at lab end\n\nAlways include:\n\n```xml\n\u003Ccc-next \u002F>\n```\n\n### E) Visitor stats image before awards\n\nAlways include, before awards:\n\n```html\n\u003Cimg src=\"https:\u002F\u002Fm365-visitor-stats.azurewebsites.net\u002Fcopilot-camp\u002F\u003Csection>\u002F\u003Clab-id>\" \u002F>\n```\n\n### F) One or more awards\n\nAlways include one or more awards and ask the developer for suitable badges if missing:\n\n```xml\n\u003Ccc-award badgeId=\"\u003CBadgeId>\" badgeName=\"\u003CBadge Name>\" \u002F>\n```\n\n### G) Image placeholders where useful\n\nWhen a step needs a screenshot, add placeholders:\n\n```markdown\n![TODO: replace with screenshot description](..\u002F..\u002Fassets\u002Fimages\u002F\u003Cfolder>\u002F\u003Cimage>.png)\n```\n\nUse the alternate text of the image to suggest to the lab author the image content to capture. The image path should be relative to the lab file.\n\n## Behavior Contract\n\nWhen this skill is triggered:\n\n1. Ask for any missing required inputs.\n2. Confirm target file path under `docs\u002Fpages\u002F\u003Csubfolder>\u002F`.\n3. Confirm lab number and lab code.\n4. Ask for knowledge-base URL list.\n5. Ask which badges to add.\n6. **Collect frontmatter information:**\n   - Prompt for lab title and description.\n   - Ask for tags (comma-separated) and convert to YAML list.\n   - Ask for difficulty level (100–500).\n   - Ask for estimated time to completion (in minutes).\n   - Ask for badge code.\n   - Ask for products (comma-separated) and convert to YAML list.\n   - Record created-date and last-edited-date (use current date if not provided).\n7. Generate the complete lab markdown with YAML frontmatter and required components.\n\nDo not skip questions when required inputs are missing.\n\n## Generation Checklist\n\nBefore finalizing:\n\n- YAML frontmatter is present at the top of the file with all required fields.\n- Lab title heading (format: `# Lab \u003Ccode> - \u003Ctitle>`) is present immediately after frontmatter.\n- Frontmatter values match the collected user inputs (code, title, description, tags, level, time, badge, products).\n- created-date and last-edited-date are in `YYYY-MM-DD` format.\n- File path is under `docs\u002Fpages\u002F\u003Csubfolder>\u002F`.\n- Exercise count is within limits.\n- Step count per exercise is within limits.\n- Every step ends with `cc-end-step`.\n- `cc-next` is present.\n- Visitor stats image is present before awards.\n- At least one `cc-award` exists.\n- Knowledge-base URLs were requested from developer.\n- All links to external sites use the `{target=_blank}` attribute.\n",{"name":5,"license":15,"metadata":34,"description":37},{"owner":35,"version":36},"Copilot Dev Camp","1.0","Creates new Copilot Dev Camp lab markdown files under docs\u002Fpages\u002F\u003Csubfolder>\u002F with a consistent structure, concise exercises, and required custom components.\nUse when asked to author a new lab, scaffold a lab file, or draft a Copilot Dev Camp lab page.\n","main","b5b1f8a1e488713063b46883d5f56d3442607155",".github\u002Fskills\u002Fcopilot-dev-camp-lab-author",179,"https:\u002F\u002Fgithub.com\u002Fmicrosoft\u002Fcopilot-camp","https:\u002F\u002Fgithub.com\u002Fmicrosoft","https:\u002F\u002Fopensource.microsoft.com","Open source projects and samples from Microsoft","2026-11-13 13:01:25",{"source":8,"skillName":5,"commands":48,"prompt":58,"zipAvailable":59},[49,52,55],{"tool":50,"command":51},"npx","npx skills add microsoft\u002Fcopilot-camp --skill copilot-dev-camp-lab-author",{"tool":53,"command":54},"bunx","bunx skills add microsoft\u002Fcopilot-camp --skill copilot-dev-camp-lab-author",{"tool":56,"command":57},"pnpm","pnpm dlx skills add microsoft\u002Fcopilot-camp --skill copilot-dev-camp-lab-author","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002Fmicrosoft\u002Fcopilot-camp\u002Fblob\u002Fmain\u002F.github\u002Fskills\u002Fcopilot-dev-camp-lab-author\u002FSKILL.md",true,[],[62,74,102,114],{"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":29},"01M69BM1A6XP5W1V51F1PVNNQ5","weekly-status-mail","Drafts a concise weekly status-update email to the user's team, covering open\ntasks, upcoming meetings, and action items, with light emoji formatting in the\nbody. Use when the user asks to \"draft my weekly status email\", \"write my weekly\nteam update\", \"send my team the weekly status\", \"create my Monday status mail\",\n\"weekly status update for the team\", or \"recap this week for the team\".\nDo NOT use for leadership or executive updates and cross-functional stakeholder\ncommunications — use stakeholder-comms instead. Do NOT use for one-off\nannouncements or non-status emails — use the Outlook tools directly.","https:\u002F\u002Fgithub.com\u002Fmicrosoft\u002Fcopilot-camp\u002Fblob\u002Fmain\u002Fsrc\u002Fcowork\u002Fweekly-status-mail\u002FSKILL.md",[],[69,70,71,72,73],"weekly status mail","status","update","create","tasks",{"skillNo":75,"name":76,"nameZh":6,"description":77,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":78,"categories":79,"keywords":91,"publishedAt":29},"01M69BKYWM44ECXBFRSS59YR92","foundry-research","Researches and compiles comprehensive information about Microsoft Foundry, including documentation, architecture, models, and deployment options.\nUse when user asks to \"research Microsoft Foundry\", \"learn about Foundry\", \"Foundry documentation\", \"Foundry architecture\", \"Foundry models\", \"how to deploy with Foundry\", \"Foundry features\", or \"Foundry capabilities\".","https:\u002F\u002Fgithub.com\u002Fmicrosoft\u002Fcopilot-camp\u002Fblob\u002Fmain\u002Fsrc\u002Fcowork\u002FCopilotDevCamp-for-cowork\u002Fskills\u002Ffoundry-research\u002FSKILL.md",[80,83,86],{"categoryNo":81,"categoryName":82,"taxonomyType":21,"taxonomyTypeDesc":22},"01JBSEEDCAT000000000000021","资料检索与研究",{"categoryNo":84,"categoryName":85,"taxonomyType":21,"taxonomyTypeDesc":22},"01JBSEEDCAT000000000000023","Skill与智能体开发",{"categoryNo":87,"categoryName":88,"taxonomyType":89,"taxonomyTypeDesc":90},"01JBSEEDCAT000000000000030","开发工程师","PROFESSION","适用职业",[92,93,94,95,96,97,98,99,100,101,9],"research","foundry research","foundry","architecture","learn","deployment","foundry models","documentation","deploy","microsoft foundry",{"skillNo":103,"name":104,"nameZh":6,"description":105,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":106,"categories":107,"keywords":112,"publishedAt":29},"01M69BKWRFXN5P0VS679EPF32Y","dev-camp-document","Authors a professional Word document about a Copilot Dev Camp lab or Microsoft technology topic. Researches Microsoft Learn documentation, organizes content into a document structure, and generates a polished one-pager or detailed guide with formatting and citations.\nUse when user asks to \"write a document about\", \"create a guide for\", \"author a one-pager on\", \"write a technical brief on\", or \"create documentation for\" any Copilot Dev Camp lab or Microsoft technology topic.","https:\u002F\u002Fgithub.com\u002Fmicrosoft\u002Fcopilot-camp\u002Fblob\u002Fmain\u002Fsrc\u002Fcowork\u002FCopilotDevCamp-for-cowork\u002Fskills\u002Fdev-camp-document\u002FSKILL.md",[108,111],{"categoryNo":109,"categoryName":110,"taxonomyType":21,"taxonomyTypeDesc":22},"01JBSEEDCAT000000000000002","文档处理",{"categoryNo":87,"categoryName":88,"taxonomyType":89,"taxonomyTypeDesc":90},[113,96,72,99,24,9],"dev camp document",{"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":124,"publishedAt":29},"01M69BKTFDHAXCX3752ZFHTR19","dev-camp-deck","Creates a professional PowerPoint presentation about a Copilot Dev Camp lab or topic. Researches Microsoft Learn documentation, organizes content into a slide structure, and generates a polished deck with speaker notes.\nUse when user asks to \"create a presentation on\", \"make a deck about\", \"build a slideshow for\", \"present on Dev Camp topic\", or \"generate slides about\" any Copilot Dev Camp lab or Microsoft technology topic.","https:\u002F\u002Fgithub.com\u002Fmicrosoft\u002Fcopilot-camp\u002Fblob\u002Fmain\u002Fsrc\u002Fcowork\u002FCopilotDevCamp-for-cowork\u002Fskills\u002Fdev-camp-deck\u002FSKILL.md",[120,123],{"categoryNo":121,"categoryName":122,"taxonomyType":21,"taxonomyTypeDesc":22},"01JBSEEDCAT000000000000003","演示文稿",{"categoryNo":87,"categoryName":88,"taxonomyType":89,"taxonomyTypeDesc":90},[125,24,99,126,96,127,9,72,128],"dev camp deck","notes","powerpoint","generate"]