[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M69AB8K9SP6WFZJ73TCF05XW":3,"skill-same:01M69AB8K9SP6WFZJ73TCF05XW":96},{"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":26,"linkOnly":27,"markdownContent":28,"markdownBody":29,"frontMatter":30,"refName":31,"commitSha":32,"skillDirectory":33,"forksCount":34,"repositoryHtmlUrl":35,"repositoryHomepageUrl":6,"ownerHtmlUrl":36,"ownerBlogUrl":37,"ownerDescription":38,"updatedAt":39,"install":40,"resources":53},"01M69AB8K9SP6WFZJ73TCF05XW","sharepoint-list-insight-report-generator",null,"Use this skill whenever the user asks for an insights\u002Freporting analysis of a SharePoint list from a connected SharePoint knowledge source; first validate the list exists, then generate and save a single-file interactive HTML report to a pre-approved SharePoint destination whose audience is no broader than the source list and items, and return its SharePoint URL.","microsoft\u002Fcat-agent-skills","microsoft","https:\u002F\u002Favatars.githubusercontent.com\u002Fu\u002F6154722?v=4","01M698VYDXZ6JW5WH3CRV650R8","Microsoft","01M69A1AHE1MABT7GVP5143M5Z",105,"MIT","https:\u002F\u002Fgithub.com\u002Fmicrosoft\u002Fcat-agent-skills\u002Fblob\u002Fmain\u002Fsubmissions\u002Fsharepoint-list-insight-report-generator\u002FSKILL.md",[18],{"categoryNo":19,"categoryName":20,"taxonomyType":21,"taxonomyTypeDesc":22},"01JBSEEDCAT000000000000034","行政与办公人员","PROFESSION","适用职业",[24,25],"sharepoint list insight report generator","validate","2026-11-10 10:12:30",false,"---\nname: sharepoint-list-insight-report-generator\ndescription: Use this skill whenever the user asks for an insights\u002Freporting analysis of a SharePoint list from a connected SharePoint knowledge source; first validate the list exists, then generate and save a single-file interactive HTML report to a pre-approved SharePoint destination whose audience is no broader than the source list and items, and return its SharePoint URL.\n---\nBefore starting, verify that configured SharePoint connector actions, agent flows, or equivalent tools can discover approved lists and their schemas, retrieve list items page by page, and invoke **Create file** to return the created file's URL or path. A SharePoint knowledge source alone does not guarantee these capabilities. If any capability is unavailable, stop and name the missing capability.\n\n## Step 1 – Identify the Target List\n\n1. Read the user request and identify the requested SharePoint list name.\n2. Inspect the selected SharePoint knowledge source.\n3. Retrieve all available SharePoint lists.\n4. Perform a case-insensitive exact match on list title (and any explicit aliases in list metadata).\n5. Proceed only on an exact match or an explicit user selection; otherwise stop and prompt the user to choose from the available lists.\n\n### Validation Logic\nBefore performing any analysis, enumerate all SharePoint lists available in the selected knowledge source.\n\n  The requested data source must be explicitly mapped to an existing SharePoint list.\n\n  Allowed conditions to continue:\n  - Exact list name match.\n  - User explicitly selects a list from the available lists.\n  - Alias defined in list metadata.\n\n  Forbidden behavior:\n  - Do not infer lists from business terminology.\n  - Do not infer lists from column names.\n  - Do not infer lists from data values.\n  - Do not infer lists from semantic similarity.\n  - Do not select a list because it appears related.\n\n  Examples:\n\n  User request:\n  Create a report for Campaign\n\n  Available lists:\n  - Campaign\n  - Product Catalog\n\n  Result:\n  Proceed with Campaign.\n\n  User request:\n  Create a report for sales data\n\n  Available lists:\n  - Campaign\n  - Product Catalog\n\n  Result:\n  Stop.\n  Return available lists.\n  Ask the user to select one.\n\n  User request:\n  Create a report for quarterly revenue\n\n  Available lists:\n  - Campaign\n  - Product Catalog\n\n  Result:\n  Stop.\n  Do not select Campaign.\n\n### If the requested list does not exist:\n\n- Stop the process immediately.\n- Do not analyze data.\n- Do not generate a report.\n- Return all available SharePoint lists.\n- Return closest matching list names.\n\nProceed only if the requested list exists.\nFor example: if the user requests \"sales\" and only a \"Product\" list exists that happens to contain sales-related data, stop and ask the user to choose an existing list from the knowledge source.\n\n---\n\n## Step 2 – Discover List Structure\n\nRetrieve:\n\n- List title\n- Internal name\n- Item count\n- Created date\n- Last modified date\n- All columns\n- Column types\n- Required fields\n- Indexed fields\n- Lookup fields\n- Choice fields\n- Person fields\n- Managed metadata fields\n\nGenerate a schema summary.\n\n---\n\n## Step 3 – Analyze Data\n\nAnalyze all accessible records within the confirmed scope, retrieving them page by page through the configured tool and following its continuation tokens. Before retrieving a detailed report, enforce the tool's row and report-size limits; when either limit is absent, also use a conservative cap of 1,000 rows. If the scope would exceed an applicable limit, ask the user to narrow it. Never silently truncate or sample records.\n\nGenerate:\n\n### General Statistics\n\n- Total records\n- Distinct values\n- Missing values\n- Data completeness score\n\n### Trend Analysis\n\n- Monthly trends\n- Annual trends\n- Growth trends\n\n### Category Analysis\n\n- Top categories\n- Frequency distribution\n- Ranking statistics\n\n### Ownership Analysis\n\n- Records by owner\n- Top contributors\n\n### Quality Analysis\n\n- Empty fields\n- Duplicate values\n- Potential anomalies\n\n---\n\n## Step 4 – Generate Insights\n\nCreate business-oriented insights.\n\nExamples:\n\n- Most used categories\n- Fastest growing areas\n- Data quality issues\n- Process bottlenecks\n- Trends and anomalies\n\nPrioritize actionable recommendations.\n\n---\n\n## Step 5 – Build Interactive HTML Report\n\nProduce a single HTML file with all CSS and JavaScript embedded inline, except that Chart.js (version 4) may be loaded from an exact versioned CDN URL with matching SRI `integrity` metadata and `crossorigin=\"anonymous\"` as the only permitted external dependency. If the exact version and matching SRI cannot be verified, do not load the CDN asset and use embedded browser APIs instead. Do not use external Bootstrap, DataTables, fonts, stylesheets, scripts, or other CDN resources. Implement table filtering, sorting, pagination, and responsive styling using embedded CSS and JavaScript.\n\nTreat SharePoint field names and values as untrusted data. Use a real JSON serializer; before embedding serialized data in a `\u003Cscript type=\"application\u002Fjson\">` element, escape `\u003C`, `>`, `&`, U+2028, and U+2029, then read it via `textContent` and parse it. Insert data-driven content using `textContent`, `document.createElement`, and other safe DOM APIs, never `innerHTML`. Render rich-text fields as plain text unless a trusted sanitizer is available.\n\n### Technologies\n\nUse:\n- Chart.js\n\nUse only libraries that can be used safely in a browser.\n\n### Executive Summary\n\nDisplay:\n\n- List name\n- Record count\n- Column count\n- Last update date\n- Top insights\n\n### Interactive Filters\n\nProvide filters for:\n\n- Text fields\n- Choice fields\n- Lookup fields\n- Person fields\n- Date fields\n\nFilters must update charts, KPIs and tables dynamically.\n\n### Interactive Charts\n\nGenerate appropriate charts automatically.\n\nSupport:\n\n- Bar charts\n- Pie charts\n- Doughnut charts\n- Line charts\n\nProvide hover tooltips and legend controls.\n\n### Data Table\n\nRequirements:\n\n- Sort on every column\n- Ascending and descending sorting\n- Search box with placeholder:\n  Quick search in table...\n- Pagination\n- Column visibility controls\n- Export buttons:\n  - CSV (Excel-compatible)\n  - Copy\n\nFor CSV export, neutralize spreadsheet formulas by prefixing an apostrophe when a cell's first non-whitespace or control character is `=`, `+`, `-`, or `@`.\n\n### Detail Modal Popup\n\nSelecting a row must open a modal displaying:\n\n- All list fields\n- Display names\n- Internal names\n- Values\n\nUse a responsive two-column layout.\n\n### Open SharePoint Item Button\n\nInside the modal popup provide:\n\nOpen SharePoint Item\n\nRequirements:\n\n- Open in a new browser tab\n- Use only the trusted SharePoint item URL returned by the configured connector or tool\n- Permit the link only when it uses HTTPS and its origin matches the selected SharePoint site's origin; otherwise omit it\n- Use target=\"_blank\" and rel=\"noopener noreferrer\"\n---\n\n## Step 6 – Save Report\n\nAfter generating the HTML report:\n\n- Generate a unique name using a sanitized list name: retain `[A-Za-z0-9_-]`, replace other runs with `_`, trim leading and trailing separators, cap the sanitized list-name portion at 80 characters, and use `SharePointList` if empty.\n\n   Report_\u003CSanitizedListName>_\u003CyyyyMMdd_HHmmss>.html\n\n- Verify that the configured destination's audience is no broader than the source list and included items. If this cannot be verified, do not upload the report.\n- Invoke the configured SharePoint **Create file** action or flow to save the report in the pre-approved SharePoint destination whose audience is no broader than the source list and included items.\n- Capture the URL or path returned by **Create file** and use it in the response. If file creation fails or returns no URL or path, report the failure honestly and never guess a URL.\n\n---\n\n## Output Requirements\n\nReturn:\n\n1. Report summary.\n2. SharePoint URL of the generated report.\n3. Report file name.\n4. List schema summary.\n5. Insights summary.\n6. Storage location within the configured SharePoint destination.\n\n---\n\n## Success Criteria\n\nA successful execution must:\n\n- Detect the requested SharePoint list.\n- Validate its existence.\n- Suggest available lists when not found.\n- Discover schema.\n- Analyze data.\n- Generate insights.\n- Create an interactive HTML report.\n- Save the report in the pre-approved SharePoint destination whose audience is no broader than the source list and included items.\n- Return the direct SharePoint URL of the report.\n- Provide sortable tables.\n- Provide pagination.\n- Provide quick search.\n- Provide modal detail view.\n- Provide Open SharePoint Item action.\n- Generate a unique report name.\n- Support responsive user experience.\n","Before starting, verify that configured SharePoint connector actions, agent flows, or equivalent tools can discover approved lists and their schemas, retrieve list items page by page, and invoke **Create file** to return the created file's URL or path. A SharePoint knowledge source alone does not guarantee these capabilities. If any capability is unavailable, stop and name the missing capability.\n\n## Step 1 – Identify the Target List\n\n1. Read the user request and identify the requested SharePoint list name.\n2. Inspect the selected SharePoint knowledge source.\n3. Retrieve all available SharePoint lists.\n4. Perform a case-insensitive exact match on list title (and any explicit aliases in list metadata).\n5. Proceed only on an exact match or an explicit user selection; otherwise stop and prompt the user to choose from the available lists.\n\n### Validation Logic\nBefore performing any analysis, enumerate all SharePoint lists available in the selected knowledge source.\n\n  The requested data source must be explicitly mapped to an existing SharePoint list.\n\n  Allowed conditions to continue:\n  - Exact list name match.\n  - User explicitly selects a list from the available lists.\n  - Alias defined in list metadata.\n\n  Forbidden behavior:\n  - Do not infer lists from business terminology.\n  - Do not infer lists from column names.\n  - Do not infer lists from data values.\n  - Do not infer lists from semantic similarity.\n  - Do not select a list because it appears related.\n\n  Examples:\n\n  User request:\n  Create a report for Campaign\n\n  Available lists:\n  - Campaign\n  - Product Catalog\n\n  Result:\n  Proceed with Campaign.\n\n  User request:\n  Create a report for sales data\n\n  Available lists:\n  - Campaign\n  - Product Catalog\n\n  Result:\n  Stop.\n  Return available lists.\n  Ask the user to select one.\n\n  User request:\n  Create a report for quarterly revenue\n\n  Available lists:\n  - Campaign\n  - Product Catalog\n\n  Result:\n  Stop.\n  Do not select Campaign.\n\n### If the requested list does not exist:\n\n- Stop the process immediately.\n- Do not analyze data.\n- Do not generate a report.\n- Return all available SharePoint lists.\n- Return closest matching list names.\n\nProceed only if the requested list exists.\nFor example: if the user requests \"sales\" and only a \"Product\" list exists that happens to contain sales-related data, stop and ask the user to choose an existing list from the knowledge source.\n\n---\n\n## Step 2 – Discover List Structure\n\nRetrieve:\n\n- List title\n- Internal name\n- Item count\n- Created date\n- Last modified date\n- All columns\n- Column types\n- Required fields\n- Indexed fields\n- Lookup fields\n- Choice fields\n- Person fields\n- Managed metadata fields\n\nGenerate a schema summary.\n\n---\n\n## Step 3 – Analyze Data\n\nAnalyze all accessible records within the confirmed scope, retrieving them page by page through the configured tool and following its continuation tokens. Before retrieving a detailed report, enforce the tool's row and report-size limits; when either limit is absent, also use a conservative cap of 1,000 rows. If the scope would exceed an applicable limit, ask the user to narrow it. Never silently truncate or sample records.\n\nGenerate:\n\n### General Statistics\n\n- Total records\n- Distinct values\n- Missing values\n- Data completeness score\n\n### Trend Analysis\n\n- Monthly trends\n- Annual trends\n- Growth trends\n\n### Category Analysis\n\n- Top categories\n- Frequency distribution\n- Ranking statistics\n\n### Ownership Analysis\n\n- Records by owner\n- Top contributors\n\n### Quality Analysis\n\n- Empty fields\n- Duplicate values\n- Potential anomalies\n\n---\n\n## Step 4 – Generate Insights\n\nCreate business-oriented insights.\n\nExamples:\n\n- Most used categories\n- Fastest growing areas\n- Data quality issues\n- Process bottlenecks\n- Trends and anomalies\n\nPrioritize actionable recommendations.\n\n---\n\n## Step 5 – Build Interactive HTML Report\n\nProduce a single HTML file with all CSS and JavaScript embedded inline, except that Chart.js (version 4) may be loaded from an exact versioned CDN URL with matching SRI `integrity` metadata and `crossorigin=\"anonymous\"` as the only permitted external dependency. If the exact version and matching SRI cannot be verified, do not load the CDN asset and use embedded browser APIs instead. Do not use external Bootstrap, DataTables, fonts, stylesheets, scripts, or other CDN resources. Implement table filtering, sorting, pagination, and responsive styling using embedded CSS and JavaScript.\n\nTreat SharePoint field names and values as untrusted data. Use a real JSON serializer; before embedding serialized data in a `\u003Cscript type=\"application\u002Fjson\">` element, escape `\u003C`, `>`, `&`, U+2028, and U+2029, then read it via `textContent` and parse it. Insert data-driven content using `textContent`, `document.createElement`, and other safe DOM APIs, never `innerHTML`. Render rich-text fields as plain text unless a trusted sanitizer is available.\n\n### Technologies\n\nUse:\n- Chart.js\n\nUse only libraries that can be used safely in a browser.\n\n### Executive Summary\n\nDisplay:\n\n- List name\n- Record count\n- Column count\n- Last update date\n- Top insights\n\n### Interactive Filters\n\nProvide filters for:\n\n- Text fields\n- Choice fields\n- Lookup fields\n- Person fields\n- Date fields\n\nFilters must update charts, KPIs and tables dynamically.\n\n### Interactive Charts\n\nGenerate appropriate charts automatically.\n\nSupport:\n\n- Bar charts\n- Pie charts\n- Doughnut charts\n- Line charts\n\nProvide hover tooltips and legend controls.\n\n### Data Table\n\nRequirements:\n\n- Sort on every column\n- Ascending and descending sorting\n- Search box with placeholder:\n  Quick search in table...\n- Pagination\n- Column visibility controls\n- Export buttons:\n  - CSV (Excel-compatible)\n  - Copy\n\nFor CSV export, neutralize spreadsheet formulas by prefixing an apostrophe when a cell's first non-whitespace or control character is `=`, `+`, `-`, or `@`.\n\n### Detail Modal Popup\n\nSelecting a row must open a modal displaying:\n\n- All list fields\n- Display names\n- Internal names\n- Values\n\nUse a responsive two-column layout.\n\n### Open SharePoint Item Button\n\nInside the modal popup provide:\n\nOpen SharePoint Item\n\nRequirements:\n\n- Open in a new browser tab\n- Use only the trusted SharePoint item URL returned by the configured connector or tool\n- Permit the link only when it uses HTTPS and its origin matches the selected SharePoint site's origin; otherwise omit it\n- Use target=\"_blank\" and rel=\"noopener noreferrer\"\n---\n\n## Step 6 – Save Report\n\nAfter generating the HTML report:\n\n- Generate a unique name using a sanitized list name: retain `[A-Za-z0-9_-]`, replace other runs with `_`, trim leading and trailing separators, cap the sanitized list-name portion at 80 characters, and use `SharePointList` if empty.\n\n   Report_\u003CSanitizedListName>_\u003CyyyyMMdd_HHmmss>.html\n\n- Verify that the configured destination's audience is no broader than the source list and included items. If this cannot be verified, do not upload the report.\n- Invoke the configured SharePoint **Create file** action or flow to save the report in the pre-approved SharePoint destination whose audience is no broader than the source list and included items.\n- Capture the URL or path returned by **Create file** and use it in the response. If file creation fails or returns no URL or path, report the failure honestly and never guess a URL.\n\n---\n\n## Output Requirements\n\nReturn:\n\n1. Report summary.\n2. SharePoint URL of the generated report.\n3. Report file name.\n4. List schema summary.\n5. Insights summary.\n6. Storage location within the configured SharePoint destination.\n\n---\n\n## Success Criteria\n\nA successful execution must:\n\n- Detect the requested SharePoint list.\n- Validate its existence.\n- Suggest available lists when not found.\n- Discover schema.\n- Analyze data.\n- Generate insights.\n- Create an interactive HTML report.\n- Save the report in the pre-approved SharePoint destination whose audience is no broader than the source list and included items.\n- Return the direct SharePoint URL of the report.\n- Provide sortable tables.\n- Provide pagination.\n- Provide quick search.\n- Provide modal detail view.\n- Provide Open SharePoint Item action.\n- Generate a unique report name.\n- Support responsive user experience.\n",{"name":5,"description":7},"main","3678d23ad8fb8d098c428302a98044ac9514d5a1","submissions\u002Fsharepoint-list-insight-report-generator",120,"https:\u002F\u002Fgithub.com\u002Fmicrosoft\u002Fcat-agent-skills","https:\u002F\u002Fgithub.com\u002Fmicrosoft","https:\u002F\u002Fopensource.microsoft.com","Open source projects and samples from Microsoft","2026-11-13 01:39:10",{"source":8,"skillName":5,"commands":41,"prompt":51,"zipAvailable":52},[42,45,48],{"tool":43,"command":44},"npx","npx skills add microsoft\u002Fcat-agent-skills --skill sharepoint-list-insight-report-generator",{"tool":46,"command":47},"bunx","bunx skills add microsoft\u002Fcat-agent-skills --skill sharepoint-list-insight-report-generator",{"tool":49,"command":50},"pnpm","pnpm dlx skills add microsoft\u002Fcat-agent-skills --skill sharepoint-list-insight-report-generator","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002Fmicrosoft\u002Fcat-agent-skills\u002Fblob\u002Fmain\u002Fsubmissions\u002Fsharepoint-list-insight-report-generator\u002FSKILL.md",true,[54,60,64,70,74,78,84,88,92],{"path":55,"resourceType":56,"resourceTypeDesc":57,"sizeBytes":58,"sourceHtmlUrl":59},"assets\u002Fdeployment.yaml","ASSET","资产文件",1942,"https:\u002F\u002Fgithub.com\u002Fgoogle\u002Fskills\u002Fblob\u002Fmain\u002Fskills\u002Fcloud\u002Fgke-app-onboarding\u002Fassets\u002Fdeployment.yaml",{"path":61,"resourceType":56,"resourceTypeDesc":57,"sizeBytes":62,"sourceHtmlUrl":63},"assets\u002FDockerfile",531,"https:\u002F\u002Fgithub.com\u002Fgoogle\u002Fskills\u002Fblob\u002Fmain\u002Fskills\u002Fcloud\u002Fgke-app-onboarding\u002Fassets\u002FDockerfile",{"path":65,"resourceType":66,"resourceTypeDesc":67,"sizeBytes":68,"sourceHtmlUrl":69},"assets\u002Findex.js","SCRIPT","脚本",863,"https:\u002F\u002Fgithub.com\u002Fgoogle\u002Fskills\u002Fblob\u002Fmain\u002Fskills\u002Fcloud\u002Fgke-app-onboarding\u002Fassets\u002Findex.js",{"path":71,"resourceType":56,"resourceTypeDesc":57,"sizeBytes":72,"sourceHtmlUrl":73},"assets\u002Fpackage-lock.json",193,"https:\u002F\u002Fgithub.com\u002Fgoogle\u002Fskills\u002Fblob\u002Fmain\u002Fskills\u002Fcloud\u002Fgke-app-onboarding\u002Fassets\u002Fpackage-lock.json",{"path":75,"resourceType":56,"resourceTypeDesc":57,"sizeBytes":76,"sourceHtmlUrl":77},"assets\u002Fpackage.json",125,"https:\u002F\u002Fgithub.com\u002Fgoogle\u002Fskills\u002Fblob\u002Fmain\u002Fskills\u002Fcloud\u002Fgke-app-onboarding\u002Fassets\u002Fpackage.json",{"path":79,"resourceType":80,"resourceTypeDesc":81,"sizeBytes":82,"sourceHtmlUrl":83},"metadata.json","REFERENCE","参考文档",918,"https:\u002F\u002Fgithub.com\u002Fmicrosoft\u002Fcat-agent-skills\u002Fblob\u002Fmain\u002Fsubmissions\u002Fsharepoint-list-insight-report-generator\u002Fmetadata.json",{"path":85,"resourceType":80,"resourceTypeDesc":81,"sizeBytes":86,"sourceHtmlUrl":87},"README.md",4255,"https:\u002F\u002Fgithub.com\u002Fmicrosoft\u002Fcat-agent-skills\u002Fblob\u002Fmain\u002Fsubmissions\u002Fsharepoint-list-insight-report-generator\u002FREADME.md",{"path":89,"resourceType":80,"resourceTypeDesc":81,"sizeBytes":90,"sourceHtmlUrl":91},"references\u002Fattribution.md",1894,"https:\u002F\u002Fgithub.com\u002Fgoogle\u002Fskills\u002Fblob\u002Fmain\u002Fskills\u002Fcloud\u002Fgke-app-onboarding\u002Freferences\u002Fattribution.md",{"path":93,"resourceType":80,"resourceTypeDesc":81,"sizeBytes":94,"sourceHtmlUrl":95},"references\u002Fgo-example.md",2045,"https:\u002F\u002Fgithub.com\u002Fgoogle\u002Fskills\u002Fblob\u002Fmain\u002Fskills\u002Fcloud\u002Fgke-app-onboarding\u002Freferences\u002Fgo-example.md",[97,124,149,183,201,217],{"skillNo":98,"name":99,"nameZh":6,"description":100,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":101,"categories":102,"keywords":103,"publishedAt":26},"01M6X3P09R8SJH3QJGMTAA5N90","stakeholder-and-decision-map","Mines customer interactions to identify stakeholders, infer their likely roles and engagement, map the decision process, and highlight who or what may be missing. Use when asked to \"map a deal's buying group\", identify influential or missing stakeholders, \"assess who has gone quiet\", or \"explain how the customer will decide\". Do not use for phased engagement plans, contact sequences, choosing or drafting outreach to the single next contact, seller or team performance reviews, or contacting, scheduling, or changing records.","https:\u002F\u002Fgithub.com\u002Fmicrosoft\u002Fcat-agent-skills\u002Fblob\u002Fmain\u002Fsubmissions\u002Fstakeholder-and-decision-map\u002FSKILL.md",[],[104,105,106,107,108,109,110,111,112,113,114,115,116,117,118,119,120,121,122,123],"decision","map","decision map","stakeholder and decision map","performance","customer","team","how","decide","do","next","infer","missing","records","assess","reviews","for","single","when","sequences",{"skillNo":125,"name":126,"nameZh":6,"description":127,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":128,"categories":129,"keywords":130,"publishedAt":26},"01M6X3NRES2XSZQCH015WD4JN6","sales-progress-update","Creates or refreshes a sales progress update for a manager or team about work done, deal movement, pending outcomes, supported forecast position, and help needed. Use when asked to \"create my weekly sales update\", \"refresh my sales progress deck\", \"report my forecast position\", \"where do I stand against my quarter forecast\", or \"catch my manager up on committed deals\". Do NOT use for non-sales project updates, a since-date deal change digest, momentum or blocker analysis, meeting prep, or outreach drafting.","https:\u002F\u002Fgithub.com\u002Fmicrosoft\u002Fcat-agent-skills\u002Fblob\u002Fmain\u002Fsubmissions\u002Fsales-progress-update\u002FSKILL.md",[],[131,132,133,134,135,136,137,138,110,139,140,141,142,143,144,145,146,147,148,122],"update","sales","progress","sales progress update","change","create","meeting prep","analysis","work","up","done","digest","project","my","updates","manager","weekly","catch",{"skillNo":150,"name":151,"nameZh":6,"description":152,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":153,"categories":154,"keywords":164,"publishedAt":26},"01M6X3MSDTB1E5H6DQAFAY41YP","submission-assemble","Put the checked CSR or 510(k) sections together in template order with a reviewer-facing open-items register, as a draft package for human sign-off. Use when the user asks \"assemble the CSR draft\", \"put the module together for review\", \"build the review package with the open items on top\", \"compile the 510(k) sections in order\" or \"package this up for the submission lead\". Do NOT use for assembling an unchecked draft - use consistency-check instead. Do NOT use for loading protocol, SAP or TLF sources - use source-ingest instead. Do NOT use for compiling general documents or slide decks - use the built-in docx or pptx skill instead. Do NOT use for filing or submitting to a regulator - use the sponsor's validated gateway, operated by a human, instead. Guardrail: draft for human approval only (L1); status is draft_clean or draft_open_items, never submitted.","https:\u002F\u002Fgithub.com\u002Fmicrosoft\u002Fcat-agent-skills\u002Fblob\u002Fmain\u002Fsubmissions\u002Freg-submission-authoring\u002Fsubmission-assemble\u002FSKILL.md",[155,160,163],{"categoryNo":156,"categoryName":157,"taxonomyType":158,"taxonomyTypeDesc":159},"01JBSEEDCAT000000000000002","文档处理","SCENARIO","使用场景",{"categoryNo":161,"categoryName":162,"taxonomyType":158,"taxonomyTypeDesc":159},"01JBSEEDCAT000000000000003","演示文稿",{"categoryNo":19,"categoryName":20,"taxonomyType":21,"taxonomyTypeDesc":22},[165,166,167,168,169,170,171,172,173,174,175,176,140,177,178,179,180,181,182,122],"assemble","submission","submission assemble","docx","pptx","writing","documents","healthcare","open","reviewer","never","only","clean","guardrail","slide decks","sources","filing","loading",{"skillNo":184,"name":185,"nameZh":6,"description":186,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":187,"categories":188,"keywords":189,"publishedAt":26},"01M6X3MM9TVWDQ716QGNV4DS25","source-ingest","Pull every number, date and population definition out of a study's protocol, SAP, TLF tables, investigator brochure and prior approved text into one cited fact map, keyed per config\u002Ffield-dictionary.json, before any CSR or 510(k) section is written. Use when the user asks \"here's the locked TLF set and SAP, set up the CSR\", \"load the protocol and tables before we start drafting\", \"what figures do we have from the database lock?\", \"pull the disposition counts out of Table 14.1.1\" or \"ingest the IB for the 510(k)\". Do NOT use for drafting or assembling submission sections - use section-draft or submission-assemble instead. Do NOT use for reconciling a patient's medications - use the discharge-care-transition plugin instead. Guardrail: reads and cites sources only; never estimates, rounds or invents a fact.","https:\u002F\u002Fgithub.com\u002Fmicrosoft\u002Fcat-agent-skills\u002Fblob\u002Fmain\u002Fsubmissions\u002Freg-submission-authoring\u002Fsource-ingest\u002FSKILL.md",[],[190,191,192,193,194,138,172,195,175,176,140,105,196,178,180,197,198,199,200,122],"source ingest","ingest","source","database","SET","text","patient","number","lock","definition","transition",{"skillNo":202,"name":203,"nameZh":6,"description":204,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":205,"categories":206,"keywords":208,"publishedAt":26},"01M6X3M7ZH5ZNEHP56BQ74HAJR","section-plan","Work out which sections a CSR or 510(k) requires, from the templates in config, check each one against the cited fact map, and name what is missing before a word is drafted. Use when the user asks \"what do we still need before we can draft the CSR?\", \"which sections are ready to start?\", \"what's blocking the performance data section?\", \"do we have everything for the synopsis?\" or \"map our tables to the E3 structure\". Do NOT use for writing section language - use section-draft instead. Do NOT use for cross-checking a finished draft - use consistency-check instead. Do NOT use for outlining general Word documents or business reports - use the built-in docx skill instead. Only structures with a template in config are supported. Guardrail: plans only; never marks a section ready on a missing fact and never invents a structure.","https:\u002F\u002Fgithub.com\u002Fmicrosoft\u002Fcat-agent-skills\u002Fblob\u002Fmain\u002Fsubmissions\u002Freg-submission-authoring\u002Fsection-plan\u002FSKILL.md",[207],{"categoryNo":156,"categoryName":157,"taxonomyType":158,"taxonomyTypeDesc":159},[209,210,211,168,170,108,171,138,172,139,175,176,212,213,214,105,178,215,216,122],"plan","section","section plan","ready","reports","structure","word documents","which",{"skillNo":218,"name":219,"nameZh":6,"description":220,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":221,"categories":222,"keywords":223,"publishedAt":26},"01M6X3M0V1MJNCR653ES9XGVMS","section-draft","Write or revise the language for one planned CSR or 510(k) section - synopsis, efficacy, safety, discussion, device description - using only figures already in the cited fact map, each with its TLF or SAP citation. Use when the user asks \"draft the Synopsis from our locked tables\", \"write up safety from Table 14.3.1\", \"give me a first pass at the discussion\", \"draft the device description for the 510(k)\" or \"tighten the wording of the Discussion section\". Do NOT use for supplying a number not already in source_facts - use source-ingest instead. Do NOT use for verifying a draft's figures - use consistency-check instead. Do NOT use for appeal letters, clinical notes or discharge summaries - use the matching HLS plugin instead. Guardrail: drafts for human approval only (L1); never asserts an unsourced number or harmonises two figures.","https:\u002F\u002Fgithub.com\u002Fmicrosoft\u002Fcat-agent-skills\u002Fblob\u002Fmain\u002Fsubmissions\u002Freg-submission-authoring\u002Fsection-draft\u002FSKILL.md",[],[224,210,225,170,226,172,227,175,176,140,228,105,229,230,231,178,232,197,233,122],"draft","section draft","notes","write","me","human","life","clinical","drafts","at"]