[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M69A6HA97NEF0MS3C113K117":3,"skill-same:01M69A6HA97NEF0MS3C113K117":91},{"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":34,"commitSha":35,"skillDirectory":36,"forksCount":37,"repositoryHtmlUrl":38,"repositoryHomepageUrl":6,"ownerHtmlUrl":39,"ownerBlogUrl":40,"ownerDescription":41,"updatedAt":42,"install":43,"resources":56},"01M69A6HA97NEF0MS3C113K117","lookup-dataverse-table",null,"Use this skill whenever the user wants to search, browse, or look up records in a Microsoft Dataverse table — for example \"look up accounts\", \"find opportunities for Contoso\", \"show me contact details\", or \"search cases by status\". Always prefer this skill (which queries Dataverse live via the Dataverse MCP Server) BEFORE answering any question about Dataverse records.","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\u002Flookup-dataverse-table\u002FSKILL.md",[18],{"categoryNo":19,"categoryName":20,"taxonomyType":21,"taxonomyTypeDesc":22},"01JBSEEDCAT000000000000023","Skill与智能体开发","SCENARIO","使用场景",[24,25,26,27,9,28],"dataverse","lookup dataverse table","MCP","mcp server","status","2026-11-10 10:12:30",false,"---\nname: lookup-dataverse-table\ndescription: >-\n  Use this skill whenever the user wants to search, browse, or look up records\n  in a Microsoft Dataverse table — for example \"look up accounts\", \"find\n  opportunities for Contoso\", \"show me contact details\", or \"search cases by\n  status\". Always prefer this skill (which queries Dataverse live via the\n  Dataverse MCP Server) BEFORE answering any question about Dataverse records.\n---\n\nHelp the user search any Microsoft Dataverse table, browse matching records, and\nview full record details — all sourced live from Dataverse via the Dataverse MCP\nServer tool.\n\n## Data source (critical)\n\n- Always source data **dynamically** from Microsoft Dataverse using the Dataverse\n  MCP Server tool.\n- **NEVER** fabricate, invent, hardcode, guess, or reuse records from examples or\n  prior general knowledge. Every record and every field value you show must come\n  from a live query via the tool.\n- If the tool returns no results or fails, say so plainly and ask the user to try\n  again or refine their search. Do not make up data.\n\n## Workflow\n\n### Step 1 — Identify the table\n\n- If the user names a table (e.g. \"accounts\", \"opportunities\", \"contacts\"), use\n  that table.\n- If the user is ambiguous, ask: *\"Which table would you like to search? For\n  example: contacts, accounts, opportunities, leads, etc.\"*\n- Use `describe('tables\u002F')` to resolve the table's logical name if needed.\n\n### Step 2 — Discover the schema\n\nBefore querying, call `describe('tables\u002F{tablename}')` to retrieve:\n\n- The table's **primary name field** (used for display).\n- The table's **primary key field** (used internally for record lookup).\n- Available columns and their logical names and types.\n\nNote the **primary key field name** (e.g. `accountid`) so you can request its\nvalue when querying. The primary key GUID **values** returned by later queries\nstay **internal** — never display them to the user.\n\n### Step 3 — Find records\n\n1. Query the table using `read_query`, always retrieving at least:\n   - The **primary name field**\n   - A **key identifier field** (e.g. email, account number, status)\n   - The **primary key** (for internal use only)\n2. Apply any search filters the user provides (name, keyword, status, date range,\n   related record, etc.).\n3. Return **at most 15 rows**. If more than 15 records match, show the first 15\n   and prompt the user to narrow the search.\n4. If a field has no value, show `(none)`.\n\nPresent results as a numbered markdown list, or a table with a leading number\ncolumn so the user can select by number:\n\n| # | Record Name | Key Identifier |\n|---|-------------|----------------|\n| 1 | Example Corp | account@example.com |\n| 2 | Another Record | 555-0100 |\n\n### Step 4 — Select a record\n\nWhen the user selects a record (by number, name, or identifier):\n\n1. Re-query the Dataverse table using the internally stored primary key GUID.\n2. Display the most useful ~20 fields for that record, presented as a readable\n   labeled list or table.\n3. Omit empty\u002Fnull fields unless the user requests the full record.\n4. Never reveal GUIDs or internal identifiers.\n\nExample detail view:\n\n| Field | Value |\n|-------|-------|\n| **Name** | Example Corp |\n| **Email** | account@example.com |\n| **Phone** | 555-0100 |\n| **City** | Seattle |\n| **State** | WA |\n\n## Remembering preferred fields\n\n- If the user requests a different set of fields (add, remove, or replace),\n  **remember those preferences** using memory tools.\n- Default to the user's preferred field set on all subsequent detail lookups — in\n  this and future conversations — until the user changes it again.\n\n## Supported tables\n\nThe skill works with **any** Dataverse table. Common examples:\n\n| Table display name | Logical name |\n|--------------------|--------------|\n| Contacts | contact |\n| Accounts | account |\n| Opportunities | opportunity |\n| Leads | lead |\n| Cases | incident |\n| Products | product |\n| Orders | salesorder |\n| Invoices | invoice |\n| Activities | activitypointer |\n| Users | systemuser |\n\nUse `describe('tables\u002F')` to discover all available tables in the environment.\n\n## Guardrails\n\n- Present matching records as a numbered markdown list, or a table with a leading\n  number column (# \u002F Record Name \u002F Key Identifier).\n- Do **not** expose raw GUIDs, internal IDs, query syntax, or raw tool payloads\n  to the user.\n- Do **not** emit adaptive card or suggested-action code blocks.\n- When a search yields no results, say so clearly and suggest alternative search\n  terms.\n- When a table is not found, suggest similar table names or ask the user to\n  clarify.\n- When more than 15 records match, always prompt the user to refine the search\n  rather than paginating silently.\n\n## Tone\n\nBe concise and helpful. Explain uncertainty rather than hiding it, and never\npresent fabricated data as if it came from Dataverse.\n","Help the user search any Microsoft Dataverse table, browse matching records, and\nview full record details — all sourced live from Dataverse via the Dataverse MCP\nServer tool.\n\n## Data source (critical)\n\n- Always source data **dynamically** from Microsoft Dataverse using the Dataverse\n  MCP Server tool.\n- **NEVER** fabricate, invent, hardcode, guess, or reuse records from examples or\n  prior general knowledge. Every record and every field value you show must come\n  from a live query via the tool.\n- If the tool returns no results or fails, say so plainly and ask the user to try\n  again or refine their search. Do not make up data.\n\n## Workflow\n\n### Step 1 — Identify the table\n\n- If the user names a table (e.g. \"accounts\", \"opportunities\", \"contacts\"), use\n  that table.\n- If the user is ambiguous, ask: *\"Which table would you like to search? For\n  example: contacts, accounts, opportunities, leads, etc.\"*\n- Use `describe('tables\u002F')` to resolve the table's logical name if needed.\n\n### Step 2 — Discover the schema\n\nBefore querying, call `describe('tables\u002F{tablename}')` to retrieve:\n\n- The table's **primary name field** (used for display).\n- The table's **primary key field** (used internally for record lookup).\n- Available columns and their logical names and types.\n\nNote the **primary key field name** (e.g. `accountid`) so you can request its\nvalue when querying. The primary key GUID **values** returned by later queries\nstay **internal** — never display them to the user.\n\n### Step 3 — Find records\n\n1. Query the table using `read_query`, always retrieving at least:\n   - The **primary name field**\n   - A **key identifier field** (e.g. email, account number, status)\n   - The **primary key** (for internal use only)\n2. Apply any search filters the user provides (name, keyword, status, date range,\n   related record, etc.).\n3. Return **at most 15 rows**. If more than 15 records match, show the first 15\n   and prompt the user to narrow the search.\n4. If a field has no value, show `(none)`.\n\nPresent results as a numbered markdown list, or a table with a leading number\ncolumn so the user can select by number:\n\n| # | Record Name | Key Identifier |\n|---|-------------|----------------|\n| 1 | Example Corp | account@example.com |\n| 2 | Another Record | 555-0100 |\n\n### Step 4 — Select a record\n\nWhen the user selects a record (by number, name, or identifier):\n\n1. Re-query the Dataverse table using the internally stored primary key GUID.\n2. Display the most useful ~20 fields for that record, presented as a readable\n   labeled list or table.\n3. Omit empty\u002Fnull fields unless the user requests the full record.\n4. Never reveal GUIDs or internal identifiers.\n\nExample detail view:\n\n| Field | Value |\n|-------|-------|\n| **Name** | Example Corp |\n| **Email** | account@example.com |\n| **Phone** | 555-0100 |\n| **City** | Seattle |\n| **State** | WA |\n\n## Remembering preferred fields\n\n- If the user requests a different set of fields (add, remove, or replace),\n  **remember those preferences** using memory tools.\n- Default to the user's preferred field set on all subsequent detail lookups — in\n  this and future conversations — until the user changes it again.\n\n## Supported tables\n\nThe skill works with **any** Dataverse table. Common examples:\n\n| Table display name | Logical name |\n|--------------------|--------------|\n| Contacts | contact |\n| Accounts | account |\n| Opportunities | opportunity |\n| Leads | lead |\n| Cases | incident |\n| Products | product |\n| Orders | salesorder |\n| Invoices | invoice |\n| Activities | activitypointer |\n| Users | systemuser |\n\nUse `describe('tables\u002F')` to discover all available tables in the environment.\n\n## Guardrails\n\n- Present matching records as a numbered markdown list, or a table with a leading\n  number column (# \u002F Record Name \u002F Key Identifier).\n- Do **not** expose raw GUIDs, internal IDs, query syntax, or raw tool payloads\n  to the user.\n- Do **not** emit adaptive card or suggested-action code blocks.\n- When a search yields no results, say so clearly and suggest alternative search\n  terms.\n- When a table is not found, suggest similar table names or ask the user to\n  clarify.\n- When more than 15 records match, always prompt the user to refine the search\n  rather than paginating silently.\n\n## Tone\n\nBe concise and helpful. Explain uncertainty rather than hiding it, and never\npresent fabricated data as if it came from Dataverse.\n",{"name":5,"description":7},"main","3678d23ad8fb8d098c428302a98044ac9514d5a1","submissions\u002Flookup-dataverse-table",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":44,"prompt":54,"zipAvailable":55},[45,48,51],{"tool":46,"command":47},"npx","npx skills add microsoft\u002Fcat-agent-skills --skill lookup-dataverse-table",{"tool":49,"command":50},"bunx","bunx skills add microsoft\u002Fcat-agent-skills --skill lookup-dataverse-table",{"tool":52,"command":53},"pnpm","pnpm dlx skills add microsoft\u002Fcat-agent-skills --skill lookup-dataverse-table","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002Fmicrosoft\u002Fcat-agent-skills\u002Fblob\u002Fmain\u002Fsubmissions\u002Flookup-dataverse-table\u002FSKILL.md",true,[57,63,67,71,75,79,83,87],{"path":58,"resourceType":59,"resourceTypeDesc":60,"sizeBytes":61,"sourceHtmlUrl":62},"metadata.json","REFERENCE","参考文档",466,"https:\u002F\u002Fgithub.com\u002Fmicrosoft\u002Fcat-agent-skills\u002Fblob\u002Fmain\u002Fsubmissions\u002Flookup-dataverse-table\u002Fmetadata.json",{"path":64,"resourceType":59,"resourceTypeDesc":60,"sizeBytes":65,"sourceHtmlUrl":66},"README.md",2207,"https:\u002F\u002Fgithub.com\u002Fmicrosoft\u002Fcat-agent-skills\u002Fblob\u002Fmain\u002Fsubmissions\u002Flookup-dataverse-table\u002FREADME.md",{"path":68,"resourceType":59,"resourceTypeDesc":60,"sizeBytes":69,"sourceHtmlUrl":70},"references\u002Fattribution.md",5091,"https:\u002F\u002Fgithub.com\u002Fgoogle\u002Fskills\u002Fblob\u002Fmain\u002Fskills\u002Fcloud\u002Fapplication-integration-authoring\u002Freferences\u002Fattribution.md",{"path":72,"resourceType":59,"resourceTypeDesc":60,"sizeBytes":73,"sourceHtmlUrl":74},"references\u002Fcicd-promotion.md",11646,"https:\u002F\u002Fgithub.com\u002Fgoogle\u002Fskills\u002Fblob\u002Fmain\u002Fskills\u002Fcloud\u002Fapplication-integration-authoring\u002Freferences\u002Fcicd-promotion.md",{"path":76,"resourceType":59,"resourceTypeDesc":60,"sizeBytes":77,"sourceHtmlUrl":78},"references\u002Fintegration-version-json.md",14704,"https:\u002F\u002Fgithub.com\u002Fgoogle\u002Fskills\u002Fblob\u002Fmain\u002Fskills\u002Fcloud\u002Fapplication-integration-authoring\u002Freferences\u002Fintegration-version-json.md",{"path":80,"resourceType":59,"resourceTypeDesc":60,"sizeBytes":81,"sourceHtmlUrl":82},"references\u002Frest-api-cheatsheet.md",19800,"https:\u002F\u002Fgithub.com\u002Fgoogle\u002Fskills\u002Fblob\u002Fmain\u002Fskills\u002Fcloud\u002Fapplication-integration-authoring\u002Freferences\u002Frest-api-cheatsheet.md",{"path":84,"resourceType":59,"resourceTypeDesc":60,"sizeBytes":85,"sourceHtmlUrl":86},"references\u002Ftasks-and-gotchas.md",13302,"https:\u002F\u002Fgithub.com\u002Fgoogle\u002Fskills\u002Fblob\u002Fmain\u002Fskills\u002Fcloud\u002Fapplication-integration-authoring\u002Freferences\u002Ftasks-and-gotchas.md",{"path":88,"resourceType":59,"resourceTypeDesc":60,"sizeBytes":89,"sourceHtmlUrl":90},"references\u002Ftriggers-and-execution.md",15764,"https:\u002F\u002Fgithub.com\u002Fgoogle\u002Fskills\u002Fblob\u002Fmain\u002Fskills\u002Fcloud\u002Fapplication-integration-authoring\u002Freferences\u002Ftriggers-and-execution.md",[92,119,144,180,198,214],{"skillNo":93,"name":94,"nameZh":6,"description":95,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":96,"categories":97,"keywords":98,"publishedAt":29},"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",[],[99,100,101,102,103,104,105,106,107,108,109,110,111,112,113,114,115,116,117,118],"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":120,"name":121,"nameZh":6,"description":122,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":123,"categories":124,"keywords":125,"publishedAt":29},"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",[],[126,127,128,129,130,131,132,133,105,134,135,136,137,138,139,140,141,142,143,117],"update","sales","progress","sales progress update","change","create","meeting prep","analysis","work","up","done","digest","project","my","updates","manager","weekly","catch",{"skillNo":145,"name":146,"nameZh":6,"description":147,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":148,"categories":149,"keywords":161,"publishedAt":29},"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",[150,153,156],{"categoryNo":151,"categoryName":152,"taxonomyType":21,"taxonomyTypeDesc":22},"01JBSEEDCAT000000000000002","文档处理",{"categoryNo":154,"categoryName":155,"taxonomyType":21,"taxonomyTypeDesc":22},"01JBSEEDCAT000000000000003","演示文稿",{"categoryNo":157,"categoryName":158,"taxonomyType":159,"taxonomyTypeDesc":160},"01JBSEEDCAT000000000000034","行政与办公人员","PROFESSION","适用职业",[162,163,164,165,166,167,168,169,170,171,172,173,135,174,175,176,177,178,179,117],"assemble","submission","submission assemble","docx","pptx","writing","documents","healthcare","open","reviewer","never","only","clean","guardrail","slide decks","sources","filing","loading",{"skillNo":181,"name":182,"nameZh":6,"description":183,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":184,"categories":185,"keywords":186,"publishedAt":29},"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",[],[187,188,189,190,191,133,169,192,172,173,135,100,193,175,177,194,195,196,197,117],"source ingest","ingest","source","database","SET","text","patient","number","lock","definition","transition",{"skillNo":199,"name":200,"nameZh":6,"description":201,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":202,"categories":203,"keywords":205,"publishedAt":29},"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",[204],{"categoryNo":151,"categoryName":152,"taxonomyType":21,"taxonomyTypeDesc":22},[206,207,208,165,167,103,168,133,169,134,172,173,209,210,211,100,175,212,213,117],"plan","section","section plan","ready","reports","structure","word documents","which",{"skillNo":215,"name":216,"nameZh":6,"description":217,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":218,"categories":219,"keywords":220,"publishedAt":29},"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",[],[221,207,222,167,223,169,224,172,173,135,225,100,226,227,228,175,229,194,230,117],"draft","section draft","notes","write","me","human","life","clinical","drafts","at"]