[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M6M0GZW2ASM3G0QHBCFARD7B":3,"skill-same:01M6M0GZW2ASM3G0QHBCFARD7B":46},{"skillNo":4,"name":5,"nameZh":6,"description":6,"descriptionZh":6,"repositoryFullName":7,"ownerLogin":8,"ownerAvatarUrl":9,"ownerAccountNo":10,"ownerDisplayName":11,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":15,"categories":16,"keywords":17,"publishedAt":18,"linkOnly":19,"markdownContent":20,"markdownBody":21,"frontMatter":22,"refName":23,"commitSha":24,"skillDirectory":25,"forksCount":26,"repositoryHtmlUrl":27,"repositoryHomepageUrl":6,"ownerHtmlUrl":28,"ownerBlogUrl":29,"ownerDescription":30,"updatedAt":31,"install":32,"resources":45},"01M6M0GZW2ASM3G0QHBCFARD7B","filedata",null,"microsoft\u002Fcopilot-studio-gallery","microsoft","https:\u002F\u002Favatars.githubusercontent.com\u002Fu\u002F6154722?v=4","01M698VYDXZ6JW5WH3CRV650R8","Microsoft","01M69B5GK6Q5V7Q6S3Q3DAKAAB",16,"MIT","https:\u002F\u002Fgithub.com\u002Fmicrosoft\u002Fcopilot-studio-gallery\u002Fblob\u002Fmain\u002Fsubmissions\u002Fai-use-case-prioritization-agent\u002Fsolution\u002Fbotcomponents\u002Fcadpbm_c.file.skillmd_XRKoT\u002Ffiledata\u002FSKILL.md",[],[5],"2026-11-10 10:12:30",false,"---\nname: confirmation-final-qa\ndescription: Create confirmation summary and final quality checks.\n---# Confirmation and Final QA Skill\n\n## Purpose\n\nCreate the user-facing confirmation summary and block unsafe or incomplete submission.\n\n## When to use\n\nUse after scoring is complete and before any Dataverse write.\n\n## Inputs\n\n- Working object.\n- Assessment output.\n- User intent: Submit, Edit, Cancel, or unknown.\n\n## Confirmation summary must include\n\n- Customer Name\n- Idea Title\n- Use Case Category\n- Use Case Subcategory\n- Summary\n- Problem \u002F Need\n- Proposed Solution\n- Expected Benefits\n- Target Audience\n- Personas Impacted\n- Potential Risks\n- Sample Prompts, Agent Questions, and Example Answers\n- Impact Assessment table: Factor | Score | Rationale\n- Complexity Assessment table: Factor | Score | Rationale\n- Reach Score\n- Agentic Fit\n- Impact Average\n- Complexity Average\n- Weak spots \u002F validation notes\n- Missing or NOT ENOUGH INFO areas\n- Recommended questions to complete the assessment\n\n## Rules\n\n- Ask: Ready to record the findings?\n- Suggested replies:\n  1. Submit\n  2. Edit\n  3. Cancel\n- Tell the user they can reply with the number or the option text.\n- If Edit, ask only which fields to change and re-confirm after edits.\n- If Cancel, end politely without saving.\n- If Submit, validate before save.\n- Do not expose table names, columns, schemas, GUIDs, or duplicate-check logic.\n- Do not reveal CAD Intake Quality.\n- Do not expose internal rubric codes or factor IDs such as I1, I2, I5, C1, or similar.\n- Use plain factor names only in confirmation tables.\n- Use \"Use case area\" and \"Specific use case type\" as the user-facing labels for category and subcategory.\n- If this is a provisional assessment, clearly label it as provisional and show the unresolved gaps before asking for Submit.\n- Use compact tables for confirmation summaries where helpful.\n- Required field confirmation can use columns: Field | Value | Confidence \u002F note.\n- Include sample prompts, agent questions, and example answers in the confirmation summary. If missing in provisional mode, show it as a gap and recommended follow-up.\n- Impact and Complexity assessments must use columns: Factor | Score | Rationale.\n- Provisional gaps can use columns: Area | Status | What is missing | Recommended follow-up.\n\n## Blocking validation\n\nBlock submission if:\n\n- Any required field is missing.\n- Category\u002Fsubcategory is NOT ENOUGH INFO.\n- Any factor is NOT ENOUGH INFO in Guided Completion or Full Assessment mode.\n- Reach Score is missing or outside the allowed range.\n- Averages are missing or inconsistent.\n- User did not explicitly choose Submit.\n- Dataverse save requirements cannot represent NOT ENOUGH INFO values in provisional mode.\n\nAllow submission in Provisional Assessment mode only if:\n\n- The user explicitly chose Run provisional assessment.\n- All missing values are clearly marked NOT ENOUGH INFO.\n- The report will include the missing evidence summary and recommended questions.\n- Dataverse can store unresolved fields without invalid placeholder scores.\n\n## Output contract\n\n```json\n{\n  \"confirmationSummary\": \"\",\n  \"readyToSubmit\": false,\n  \"blockingIssues\": [],\n  \"editPrompt\": \"\",\n  \"cancelMessage\": \"\"\n}\n```\n\n","## Purpose\n\nCreate the user-facing confirmation summary and block unsafe or incomplete submission.\n\n## When to use\n\nUse after scoring is complete and before any Dataverse write.\n\n## Inputs\n\n- Working object.\n- Assessment output.\n- User intent: Submit, Edit, Cancel, or unknown.\n\n## Confirmation summary must include\n\n- Customer Name\n- Idea Title\n- Use Case Category\n- Use Case Subcategory\n- Summary\n- Problem \u002F Need\n- Proposed Solution\n- Expected Benefits\n- Target Audience\n- Personas Impacted\n- Potential Risks\n- Sample Prompts, Agent Questions, and Example Answers\n- Impact Assessment table: Factor | Score | Rationale\n- Complexity Assessment table: Factor | Score | Rationale\n- Reach Score\n- Agentic Fit\n- Impact Average\n- Complexity Average\n- Weak spots \u002F validation notes\n- Missing or NOT ENOUGH INFO areas\n- Recommended questions to complete the assessment\n\n## Rules\n\n- Ask: Ready to record the findings?\n- Suggested replies:\n  1. Submit\n  2. Edit\n  3. Cancel\n- Tell the user they can reply with the number or the option text.\n- If Edit, ask only which fields to change and re-confirm after edits.\n- If Cancel, end politely without saving.\n- If Submit, validate before save.\n- Do not expose table names, columns, schemas, GUIDs, or duplicate-check logic.\n- Do not reveal CAD Intake Quality.\n- Do not expose internal rubric codes or factor IDs such as I1, I2, I5, C1, or similar.\n- Use plain factor names only in confirmation tables.\n- Use \"Use case area\" and \"Specific use case type\" as the user-facing labels for category and subcategory.\n- If this is a provisional assessment, clearly label it as provisional and show the unresolved gaps before asking for Submit.\n- Use compact tables for confirmation summaries where helpful.\n- Required field confirmation can use columns: Field | Value | Confidence \u002F note.\n- Include sample prompts, agent questions, and example answers in the confirmation summary. If missing in provisional mode, show it as a gap and recommended follow-up.\n- Impact and Complexity assessments must use columns: Factor | Score | Rationale.\n- Provisional gaps can use columns: Area | Status | What is missing | Recommended follow-up.\n\n## Blocking validation\n\nBlock submission if:\n\n- Any required field is missing.\n- Category\u002Fsubcategory is NOT ENOUGH INFO.\n- Any factor is NOT ENOUGH INFO in Guided Completion or Full Assessment mode.\n- Reach Score is missing or outside the allowed range.\n- Averages are missing or inconsistent.\n- User did not explicitly choose Submit.\n- Dataverse save requirements cannot represent NOT ENOUGH INFO values in provisional mode.\n\nAllow submission in Provisional Assessment mode only if:\n\n- The user explicitly chose Run provisional assessment.\n- All missing values are clearly marked NOT ENOUGH INFO.\n- The report will include the missing evidence summary and recommended questions.\n- Dataverse can store unresolved fields without invalid placeholder scores.\n\n## Output contract\n\n```json\n{\n  \"confirmationSummary\": \"\",\n  \"readyToSubmit\": false,\n  \"blockingIssues\": [],\n  \"editPrompt\": \"\",\n  \"cancelMessage\": \"\"\n}\n```\n\n",{},"main","651f9403cab1191dcbb11b854aedcd76d0627040","submissions\u002Fai-use-case-prioritization-agent\u002Fsolution\u002Fbotcomponents\u002Fcadpbm_c.file.skillmd_XRKoT\u002Ffiledata",25,"https:\u002F\u002Fgithub.com\u002Fmicrosoft\u002Fcopilot-studio-gallery","https:\u002F\u002Fgithub.com\u002Fmicrosoft","https:\u002F\u002Fopensource.microsoft.com","Open source projects and samples from Microsoft","2026-11-12 13:20:41",{"source":7,"skillName":5,"commands":33,"prompt":43,"zipAvailable":44},[34,37,40],{"tool":35,"command":36},"npx","npx skills add microsoft\u002Fcopilot-studio-gallery --skill filedata",{"tool":38,"command":39},"bunx","bunx skills add microsoft\u002Fcopilot-studio-gallery --skill filedata",{"tool":41,"command":42},"pnpm","pnpm dlx skills add microsoft\u002Fcopilot-studio-gallery --skill filedata","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002Fmicrosoft\u002Fcopilot-studio-gallery\u002Fblob\u002Fmain\u002Fsubmissions\u002Fai-use-case-prioritization-agent\u002Fsolution\u002Fbotcomponents\u002Fcadpbm_c.file.skillmd_XRKoT\u002Ffiledata\u002FSKILL.md",true,[],[47,67,84,116,141,175],{"skillNo":48,"name":49,"nameZh":6,"description":50,"descriptionZh":6,"repositoryFullName":7,"ownerLogin":8,"ownerAvatarUrl":9,"ownerAccountNo":10,"ownerDisplayName":11,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":51,"categories":52,"keywords":58,"publishedAt":18},"01M69B6A39RF106PPXC8V5DD32","dock-assignment-pass-pdf","Render the completed truck loading-dock assignment as a driver-facing one-page PDF.","https:\u002F\u002Fgithub.com\u002Fmicrosoft\u002Fcopilot-studio-gallery\u002Fblob\u002Fmain\u002Fsubmissions\u002Fwandelay-loading-bay-pickup\u002Fsolution\u002Fbotcomponents\u002Fcrf98_curbsidepickupassistant_Q0mRmz.file.skillmd_gYycZ\u002Ffiledata\u002FSKILL.md",[53],{"categoryNo":54,"categoryName":55,"taxonomyType":56,"taxonomyTypeDesc":57},"01JBSEEDCAT000000000000002","文档处理","SCENARIO","使用场景",[59,60,61,62,63,64,65,66],"PDF","dock assignment pass pdf","page","as","driver","render","loading","one-page",{"skillNo":68,"name":69,"nameZh":6,"description":70,"descriptionZh":6,"repositoryFullName":7,"ownerLogin":8,"ownerAvatarUrl":9,"ownerAccountNo":10,"ownerDisplayName":11,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":71,"categories":72,"keywords":73,"publishedAt":18},"01M69B687V6ME6HZZKTPPRHBXT","loading-dock-selector","Reason over weather, one current dock snapshot, optional ETA, and verified Drive Priority Pass to select and explain one loading dock.","https:\u002F\u002Fgithub.com\u002Fmicrosoft\u002Fcopilot-studio-gallery\u002Fblob\u002Fmain\u002Fsubmissions\u002Fwandelay-loading-bay-pickup\u002Fsolution\u002Fbotcomponents\u002Fcrf98_curbsidepickupassistant_Q0mRmz.file.skillmd_FPadO\u002Ffiledata\u002FSKILL.md",[],[74,65,75,76,77,78,79,80,81,82,83],"loading dock selector","selector","weather","explain","select","snapshot","drive","eta","verified","reason",{"skillNo":85,"name":86,"nameZh":6,"description":87,"descriptionZh":6,"repositoryFullName":7,"ownerLogin":8,"ownerAvatarUrl":9,"ownerAccountNo":10,"ownerDisplayName":11,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":88,"categories":89,"keywords":94,"publishedAt":18},"01M69B6435KYGSK2AV9QKDDWFP","newsletter-style-email-composer","Use when the user asks to email a report, findings, or metrics to someone as a polished, newsletter-style message. Builds an Outlook-safe HTML email from figures that already exist (headline, KPI tiles, up to two bar charts drawn with HTML table cells so they render in classic Outlook, Gmail and dark mode, short findings, data notes and the non-audit disclaimer) using the shared brand tokens, attaches the PDF report, and creates a draft for the user to review. Do NOT use for a short plain-text status update, or for building the underlying analysis, charts, or report itself -- this skill only composes the email.","https:\u002F\u002Fgithub.com\u002Fmicrosoft\u002Fcopilot-studio-gallery\u002Fblob\u002Fmain\u002Fsubmissions\u002Fsales-analyser\u002Fsolution\u002Fbotcomponents\u002Fcrf9c_salesanalyser_WEs93i.file.skillmd_oCdhy\u002Ffiledata\u002FSKILL.md",[90,91],{"categoryNo":54,"categoryName":55,"taxonomyType":56,"taxonomyTypeDesc":57},{"categoryNo":92,"categoryName":93,"taxonomyType":56,"taxonomyTypeDesc":57},"01JBSEEDCAT000000000000005","邮件与沟通",[95,96,97,98,99,100,59,101,102,103,104,105,106,107,108,109,110,111,112,64,113,114,115],"newsletter style email composer","email","email composer","newsletter","style","composer","gmail","review","safe","status","notes","analysis","Charts","text","short","only","up","shared","plain-text","mode","when",{"skillNo":117,"name":118,"nameZh":6,"description":119,"descriptionZh":6,"repositoryFullName":7,"ownerLogin":8,"ownerAvatarUrl":9,"ownerAccountNo":10,"ownerDisplayName":11,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":120,"categories":121,"keywords":128,"publishedAt":18},"01M69B6247HGXJN2SMMXSZ6RA9","polished-report-builder","Use when the user asks to turn analysis results, metrics, or findings into a polished, presentation-ready report, one-pager, or executive summary -- especially when existing analysis (e.g. from the spreadsheet analysis skill) needs to become a document someone will actually read. Builds a branded PDF with reportlab from a short content file (headline, KPI tiles, one chart per point, data notes and the non-audit disclaimer) using the shared brand tokens, and runs a QA pass before delivery to catch walls of text, chart clutter, low-resolution charts, missing data notes or poor contrast. Do NOT use for a quick inline chat answer, a single ad-hoc chart with no report structure around it, a raw data export with no narrative, or to compute the figures themselves.","https:\u002F\u002Fgithub.com\u002Fmicrosoft\u002Fcopilot-studio-gallery\u002Fblob\u002Fmain\u002Fsubmissions\u002Fsales-analyser\u002Fsolution\u002Fbotcomponents\u002Fcrf9c_salesanalyser_WEs93i.file.skillmd_k_QDN\u002Ffiledata\u002FSKILL.md",[122,123],{"categoryNo":54,"categoryName":55,"taxonomyType":56,"taxonomyTypeDesc":57},{"categoryNo":124,"categoryName":125,"taxonomyType":126,"taxonomyTypeDesc":127},"01JBSEEDCAT000000000000034","行政与办公人员","PROFESSION","适用职业",[129,130,131,132,59,105,133,134,135,106,107,108,109,136,112,137,138,139,140,115],"polished report builder","report","builder","report builder","executive summary","qa","spreadsheet","ready","chart","quick","catch","data export",{"skillNo":142,"name":143,"nameZh":6,"description":144,"descriptionZh":6,"repositoryFullName":7,"ownerLogin":8,"ownerAvatarUrl":9,"ownerAccountNo":10,"ownerDisplayName":11,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":145,"categories":146,"keywords":156,"publishedAt":18},"01M69B5ZZQAN0F4G895841974H","spreadsheet-data-analysis-reporting","Use for any request that needs figures from the sales spreadsheets (Excel\u002FCSV), even a single file or a single period - e.g. 'analyse Q4', 'how did sales do last month', 'compare regions', YoY\u002FMoM\u002FQoQ\u002FYTD growth, top products, share of revenue, trends, outliers, currency-converted totals, or building\u002Fupdating a consolidated master file. Finds and loads the relevant files, cleans and normalises them, computes metrics with standard definitions and edge-case handling, flags outliers and data issues, explains every transformation, and produces on-brand charts. Use this before the report or email skills whenever numbers must be computed. Do NOT use for questions that need no data (e.g. 'what does YoY mean') or for re-formatting results already computed in this conversation.","https:\u002F\u002Fgithub.com\u002Fmicrosoft\u002Fcopilot-studio-gallery\u002Fblob\u002Fmain\u002Fsubmissions\u002Fsales-analyser\u002Fsolution\u002Fbotcomponents\u002Fcrf9c_salesanalyser_WEs93i.file.skillmd_6IAVT\u002Ffiledata\u002FSKILL.md",[147,150,153],{"categoryNo":148,"categoryName":149,"taxonomyType":56,"taxonomyTypeDesc":57},"01JBSEEDCAT000000000000004","电子表格",{"categoryNo":151,"categoryName":152,"taxonomyType":56,"taxonomyTypeDesc":57},"01JBSEEDCAT000000000000013","分析与可视化",{"categoryNo":154,"categoryName":155,"taxonomyType":126,"taxonomyTypeDesc":127},"01JBSEEDCAT000000000000033","数据分析师",[157,158,159,160,135,106,161,162,163,107,164,165,166,167,168,169,170,171,172,173,174],"data analysis","spreadsheet data analysis reporting","reporting","data","xlsx","spreadsheets","issues","how","files","conversation","flags","currency","revenue","relevant","re","top","request","analyse",{"skillNo":176,"name":177,"nameZh":6,"description":178,"descriptionZh":6,"repositoryFullName":7,"ownerLogin":8,"ownerAvatarUrl":9,"ownerAccountNo":10,"ownerDisplayName":11,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":179,"categories":180,"keywords":185,"publishedAt":18},"01M69B5YC45P39BX11JGAC2NGC","generating-podcast-script","Use this skill whenever the user asks to write, generate, or create a podcast script or podcast episode — from a topic, or from source material such as a news digest, newsletter, email review, or set of articles — and optionally convert it to audio with Azure Text-to-Speech. Handles the initial request and every follow-up refinement (source, topic, length, cast, narration) in the same task.","https:\u002F\u002Fgithub.com\u002Fmicrosoft\u002Fcopilot-studio-gallery\u002Fblob\u002Fmain\u002Fsubmissions\u002Fpodcast-generation-agent\u002Fsolution\u002Fbotcomponents\u002Fcr88d_podcastdemo_OMpe9u.file.skillmd_A9jgI\u002Ffiledata\u002FSKILL.md",[181,182],{"categoryNo":92,"categoryName":93,"taxonomyType":56,"taxonomyTypeDesc":57},{"categoryNo":183,"categoryName":184,"taxonomyType":56,"taxonomyTypeDesc":57},"01JBSEEDCAT000000000000016","图像与多媒体",[186,187,188,189,102,190,191,192,193,194,195,108,196,111,98,197,198,62,199,200,173],"generating podcast script","podcast","script","podcast script","azure","create","generate","speech","SET","Audio","write","narration","digest","follow-up","source"]