[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M69AC47PXE7RWEF9Z5SCRY3F":3,"skill-same:01M69AC47PXE7RWEF9Z5SCRY3F":60},{"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":18,"publishedAt":22,"linkOnly":23,"markdownContent":24,"markdownBody":25,"frontMatter":26,"refName":27,"commitSha":28,"skillDirectory":29,"forksCount":30,"repositoryHtmlUrl":31,"repositoryHomepageUrl":6,"ownerHtmlUrl":32,"ownerBlogUrl":33,"ownerDescription":34,"updatedAt":35,"install":36,"resources":49},"01M69AC47PXE7RWEF9Z5SCRY3F","style-analyzer",null,"Analyze the user's communication style across their Teams chats and emails to build a reusable mimicry profile — greetings, tone, length, punctuation, sign-offs, common phrases, and quirks. Use this skill when the user asks to capture or analyze their writing style, or before configuring an assistant (e.g. an OOO auto-responder) that should write in their voice.","microsoft\u002Fcat-agent-skills","microsoft","https:\u002F\u002Favatars.githubusercontent.com\u002Fu\u002F6154722?v=4","01M698VYDXZ6JW5WH3CRV650R8","Microsoft","01M69A1AHE1MABT7GVP5143M5Z",103,"MIT","https:\u002F\u002Fgithub.com\u002Fmicrosoft\u002Fcat-agent-skills\u002Fblob\u002Fmain\u002Fsubmissions\u002Fstyle-analyzer\u002FSKILL.md",[],[19,20,21],"style analyzer","writing","assistant","2026-11-10 10:12:30",false,"---\nname: style-analyzer\ndescription: Analyze the user's communication style across their Teams chats and emails to build a reusable mimicry profile — greetings, tone, length, punctuation, sign-offs, common phrases, and quirks. Use this skill when the user asks to capture or analyze their writing style, or before configuring an assistant (e.g. an OOO auto-responder) that should write in their voice.\n---\n\n# Style Analyzer\n\nAnalyze the user's communication patterns across Teams and Outlook and build a\nstyle profile that other skills or automations (e.g. an out-of-office\nauto-responder) can use to write in the user's voice. Save the profile to memory\nso it's available across sessions.\n\n> **Tool names.** This skill refers to Microsoft 365 tools as `m365_*` and to\n> memory as remember\u002Frecall tools. If your host exposes these under different\n> names, map them to the equivalent capability.\n\n## Data collection\n\n### 1. Gather sent emails (20–30 samples)\n\n- List the last ~30 emails in the **Sent** folder.\n- For emails with real body content (not just meeting accepts\u002Fdeclines), fetch\n  the full text body.\n\n### 2. Gather Teams chat messages\n\n- List recent chats (~50).\n- For each relevant chat (prioritize active 1:1 and group chats), fetch the last\n  ~30 messages.\n- Filter to messages **from the current user** (match the `from` field to the\n  user's display name).\n\n### 3. Sample diversity\n\nAim for:\n\n- 10+ sent emails with body content\n- 50+ Teams messages across **20–25 different chats**\n- A mix of 1:1, group, and meeting chats\n- Both internal and external conversations where available\n\n## Analysis framework\n\nAnalyze the collected messages across these dimensions:\n\n- **A. Greetings** — how they address people (first name, \"Hi [Name]\", \"Hey\",\n  formal titles); patterns by relationship type (internal vs external).\n- **B. Tone & formality** — professional\u002Fcasual\u002Fmixed; direct vs hedging; warmth\n  indicators.\n- **C. Message length** — average sentence count; frequency of one-word replies;\n  when they write longer messages.\n- **D. Punctuation & grammar** — consistency; common typos (e.g. lowercase \"i\");\n  emoji usage (none \u002F occasional \u002F frequent).\n- **E. Sign-offs** — email signature style; Teams message endings; closing\n  phrases (\"Thanks\", \"Regards\", etc.).\n- **F. Common phrases** — frequently used expressions for agreement (\"sounds\n  good\", \"makes sense\"), requests (\"can you\", \"would you mind\"), availability,\n  and FYI\u002Fcontext-setting.\n- **G. Technical communication** — how they explain technical concepts; level of\n  detail; hedging vs confidence.\n- **H. Action patterns** — how they delegate, loop others in, and schedule\n  meetings.\n\n## Output\n\n### 1. Display a summary\n\nPresent findings as a formatted table:\n\n```markdown\n## Communication Style Profile for [Name]\n\n| Dimension | Pattern |\n|-----------|---------|\n| Greetings | ... |\n| Tone | ... |\n| Length | ... |\n| Emojis | ... |\n| Sign-offs | ... |\n| Technical | ... |\n\n### Common phrases\n- \"...\"\n- \"...\"\n\n### Quirks & notes\n- ...\n```\n\n### 2. Save to memory\n\nStore the style guide in memory. Use two entries to stay within any per-fact\nlength limits:\n\n- **Entry 1** — greetings, tone, brevity, punctuation, emojis.\n- **Entry 2** — common phrases, delegation style, technical communication,\n  quirks.\n\nTag both as a preference so they persist and can be recalled later.\n\n### 3. Confirm storage\n\nTell the user:\n\n- The style profile has been saved to memory.\n- It can be recalled with a query like \"writing style\".\n- It's available to other assistants and automations that write in their voice.\n\n## Usage notes\n\n- Re-run periodically (e.g. quarterly) to keep the profile current.\n- Pairs well with an OOO \u002F auto-responder skill that should mimic the user's\n  voice.\n\n## Privacy\n\nAll analysis happens inside the user's own agent environment against their own\nMicrosoft 365 data. No communication content is sent to any third party. The\nsaved profile describes *how* the user writes, not *what* they wrote — do not\nstore verbatim private message content in the profile.\n","# Style Analyzer\n\nAnalyze the user's communication patterns across Teams and Outlook and build a\nstyle profile that other skills or automations (e.g. an out-of-office\nauto-responder) can use to write in the user's voice. Save the profile to memory\nso it's available across sessions.\n\n> **Tool names.** This skill refers to Microsoft 365 tools as `m365_*` and to\n> memory as remember\u002Frecall tools. If your host exposes these under different\n> names, map them to the equivalent capability.\n\n## Data collection\n\n### 1. Gather sent emails (20–30 samples)\n\n- List the last ~30 emails in the **Sent** folder.\n- For emails with real body content (not just meeting accepts\u002Fdeclines), fetch\n  the full text body.\n\n### 2. Gather Teams chat messages\n\n- List recent chats (~50).\n- For each relevant chat (prioritize active 1:1 and group chats), fetch the last\n  ~30 messages.\n- Filter to messages **from the current user** (match the `from` field to the\n  user's display name).\n\n### 3. Sample diversity\n\nAim for:\n\n- 10+ sent emails with body content\n- 50+ Teams messages across **20–25 different chats**\n- A mix of 1:1, group, and meeting chats\n- Both internal and external conversations where available\n\n## Analysis framework\n\nAnalyze the collected messages across these dimensions:\n\n- **A. Greetings** — how they address people (first name, \"Hi [Name]\", \"Hey\",\n  formal titles); patterns by relationship type (internal vs external).\n- **B. Tone & formality** — professional\u002Fcasual\u002Fmixed; direct vs hedging; warmth\n  indicators.\n- **C. Message length** — average sentence count; frequency of one-word replies;\n  when they write longer messages.\n- **D. Punctuation & grammar** — consistency; common typos (e.g. lowercase \"i\");\n  emoji usage (none \u002F occasional \u002F frequent).\n- **E. Sign-offs** — email signature style; Teams message endings; closing\n  phrases (\"Thanks\", \"Regards\", etc.).\n- **F. Common phrases** — frequently used expressions for agreement (\"sounds\n  good\", \"makes sense\"), requests (\"can you\", \"would you mind\"), availability,\n  and FYI\u002Fcontext-setting.\n- **G. Technical communication** — how they explain technical concepts; level of\n  detail; hedging vs confidence.\n- **H. Action patterns** — how they delegate, loop others in, and schedule\n  meetings.\n\n## Output\n\n### 1. Display a summary\n\nPresent findings as a formatted table:\n\n```markdown\n## Communication Style Profile for [Name]\n\n| Dimension | Pattern |\n|-----------|---------|\n| Greetings | ... |\n| Tone | ... |\n| Length | ... |\n| Emojis | ... |\n| Sign-offs | ... |\n| Technical | ... |\n\n### Common phrases\n- \"...\"\n- \"...\"\n\n### Quirks & notes\n- ...\n```\n\n### 2. Save to memory\n\nStore the style guide in memory. Use two entries to stay within any per-fact\nlength limits:\n\n- **Entry 1** — greetings, tone, brevity, punctuation, emojis.\n- **Entry 2** — common phrases, delegation style, technical communication,\n  quirks.\n\nTag both as a preference so they persist and can be recalled later.\n\n### 3. Confirm storage\n\nTell the user:\n\n- The style profile has been saved to memory.\n- It can be recalled with a query like \"writing style\".\n- It's available to other assistants and automations that write in their voice.\n\n## Usage notes\n\n- Re-run periodically (e.g. quarterly) to keep the profile current.\n- Pairs well with an OOO \u002F auto-responder skill that should mimic the user's\n  voice.\n\n## Privacy\n\nAll analysis happens inside the user's own agent environment against their own\nMicrosoft 365 data. No communication content is sent to any third party. The\nsaved profile describes *how* the user writes, not *what* they wrote — do not\nstore verbatim private message content in the profile.\n",{"name":5,"description":7},"main","3678d23ad8fb8d098c428302a98044ac9514d5a1","submissions\u002Fstyle-analyzer",119,"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-12 02:57:14",{"source":8,"skillName":5,"commands":37,"prompt":47,"zipAvailable":48},[38,41,44],{"tool":39,"command":40},"npx","npx skills add microsoft\u002Fcat-agent-skills --skill style-analyzer",{"tool":42,"command":43},"bunx","bunx skills add microsoft\u002Fcat-agent-skills --skill style-analyzer",{"tool":45,"command":46},"pnpm","pnpm dlx skills add microsoft\u002Fcat-agent-skills --skill style-analyzer","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002Fmicrosoft\u002Fcat-agent-skills\u002Fblob\u002Fmain\u002Fsubmissions\u002Fstyle-analyzer\u002FSKILL.md",true,[50,56],{"path":51,"resourceType":52,"resourceTypeDesc":53,"sizeBytes":54,"sourceHtmlUrl":55},"metadata.json","REFERENCE","参考文档",560,"https:\u002F\u002Fgithub.com\u002Fmicrosoft\u002Fcat-agent-skills\u002Fblob\u002Fmain\u002Fsubmissions\u002Fstyle-analyzer\u002Fmetadata.json",{"path":57,"resourceType":52,"resourceTypeDesc":53,"sizeBytes":58,"sourceHtmlUrl":59},"README.md",2138,"https:\u002F\u002Fgithub.com\u002Fmicrosoft\u002Fcat-agent-skills\u002Fblob\u002Fmain\u002Fsubmissions\u002Fstyle-analyzer\u002FREADME.md",[61,88,113,150,168,184],{"skillNo":62,"name":63,"nameZh":6,"description":64,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":65,"categories":66,"keywords":67,"publishedAt":22},"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",[],[68,69,70,71,72,73,74,75,76,77,78,79,80,81,82,83,84,85,86,87],"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":89,"name":90,"nameZh":6,"description":91,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":92,"categories":93,"keywords":94,"publishedAt":22},"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",[],[95,96,97,98,99,100,101,102,74,103,104,105,106,107,108,109,110,111,112,86],"update","sales","progress","sales progress update","change","create","meeting prep","analysis","work","up","done","digest","project","my","updates","manager","weekly","catch",{"skillNo":114,"name":115,"nameZh":6,"description":116,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":117,"categories":118,"keywords":132,"publishedAt":22},"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",[119,124,127],{"categoryNo":120,"categoryName":121,"taxonomyType":122,"taxonomyTypeDesc":123},"01JBSEEDCAT000000000000002","文档处理","SCENARIO","使用场景",{"categoryNo":125,"categoryName":126,"taxonomyType":122,"taxonomyTypeDesc":123},"01JBSEEDCAT000000000000003","演示文稿",{"categoryNo":128,"categoryName":129,"taxonomyType":130,"taxonomyTypeDesc":131},"01JBSEEDCAT000000000000034","行政与办公人员","PROFESSION","适用职业",[133,134,135,136,137,20,138,139,140,141,142,143,104,144,145,146,147,148,149,86],"assemble","submission","submission assemble","docx","pptx","documents","healthcare","open","reviewer","never","only","clean","guardrail","slide decks","sources","filing","loading",{"skillNo":151,"name":152,"nameZh":6,"description":153,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":154,"categories":155,"keywords":156,"publishedAt":22},"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",[],[157,158,159,160,161,102,139,162,142,143,104,69,163,145,147,164,165,166,167,86],"source ingest","ingest","source","database","SET","text","patient","number","lock","definition","transition",{"skillNo":169,"name":170,"nameZh":6,"description":171,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":172,"categories":173,"keywords":175,"publishedAt":22},"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",[174],{"categoryNo":120,"categoryName":121,"taxonomyType":122,"taxonomyTypeDesc":123},[176,177,178,136,20,72,138,102,139,103,142,143,179,180,181,69,145,182,183,86],"plan","section","section plan","ready","reports","structure","word documents","which",{"skillNo":185,"name":186,"nameZh":6,"description":187,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":188,"categories":189,"keywords":190,"publishedAt":22},"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",[],[191,177,192,20,193,139,194,142,143,104,195,69,196,197,198,145,199,164,200,86],"draft","section draft","notes","write","me","human","life","clinical","drafts","at"]