[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M6NYC4M9E06FYRY5RKASVFCC":3,"skill-same:01M6NYC4M9E06FYRY5RKASVFCC":70},{"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":44,"linkOnly":45,"markdownContent":46,"markdownBody":47,"frontMatter":48,"refName":49,"commitSha":50,"skillDirectory":51,"forksCount":52,"repositoryHtmlUrl":53,"repositoryHomepageUrl":6,"ownerHtmlUrl":54,"ownerBlogUrl":6,"ownerDescription":6,"updatedAt":55,"install":56,"resources":69},"01M6NYC4M9E06FYRY5RKASVFCC","email-drafter",null,"Draft and review professional emails that match your personal writing style. Analyzes your sent emails for tone, greeting, structure, and sign-off patterns via WorkIQ, then generates context-aware drafts for any recipient. USE FOR: draft email, write email, compose email, reply email, follow-up email, analyze email tone, email style.","mattonweb\u002Fai-assistant-foundry","mattonweb","https:\u002F\u002Favatars.githubusercontent.com\u002Fu\u002F2309734?v=4","01M6NQYCY846TKYN2ZCRS71WQ7","Matt Johnson","01M6NQYD2NPAQEFVD8TW9W0SVX",1,"MIT","https:\u002F\u002Fgithub.com\u002Fmattonweb\u002Fai-assistant-foundry\u002Fblob\u002Fmain\u002Fmarketing-sales-email\u002Fgithub\u002Femail-drafter\u002FSKILL.md",[18],{"categoryNo":19,"categoryName":20,"taxonomyType":21,"taxonomyTypeDesc":22},"01JBSEEDCAT000000000000005","邮件与沟通","SCENARIO","使用场景",[24,25,26,27,28,29,30,31,32,33,34,35,36,37,38,39,40,41,42,43],"email","email drafter","writing style","for","professional","via","style","emails","tone","sign","draft","structure","writing","greeting","compose","up","use","analyze","workiq","review","2026-11-10 10:12:30",false,"---\nname: email-drafter\ndescription: 'Draft and review professional emails that match your personal writing style. Analyzes your sent emails for tone, greeting, structure, and sign-off patterns via WorkIQ, then generates context-aware drafts for any recipient. USE FOR: draft email, write email, compose email, reply email, follow-up email, analyze email tone, email style.'\n---\n\n# Email Drafter\n\nDraft professional emails that match your established writing style and tone. Uses WorkIQ to analyze your sent emails and prior correspondence with recipients, then produces context-aware drafts you can review and refine.\n\n## When to Use\n\n- \"Draft an email to [person] about [topic]\"\n- \"Write a follow-up email to [customer] regarding [project]\"\n- \"Reply to [person]'s email about [subject]\"\n- \"Compose a proposal email for [initiative]\"\n- \"Analyze my email tone with [recipient]\"\n\n## Workflow\n\n### Step 1 — Gather Context\n\nBefore drafting, collect:\n\n1. **Recipient(s)** — who is the email for?\n2. **Purpose** — what is the email about? (proposal, follow-up, technical guidance, introduction, status update, etc.)\n3. **Key points** — what needs to be communicated?\n4. **Relationship context** — use WorkIQ to check prior email history with the recipient if available\n\nIf the user provides all of these upfront, proceed directly. Otherwise, ask clarifying questions (max 3).\n\n### Step 2 — Analyze Tone\n\nWhen drafting for a recipient, use WorkIQ to understand the user's established communication patterns:\n\n1. Pull 3–5 recent sent emails from the user to the same recipient or similar recipients\n2. Identify patterns:\n   - **Greeting style** — formal (\"Dear\"), standard (\"Hello\"), casual (\"Hi\"), or direct (no greeting)\n   - **Structure** — short paragraphs vs. bullet lists vs. numbered steps\n   - **Sign-off** — what closing and name format the user typically uses\n   - **Formality level** — professional, friendly-professional, casual\n   - **Language** — which language the user writes in with this recipient\n3. Apply those patterns to the draft\n\nIf WorkIQ is unavailable or no prior emails exist, use sensible professional defaults and note that the tone was inferred.\n\n### Step 3 — Draft the Email\n\nApply the discovered (or default) style rules:\n\n**Greeting:**\n- Match whatever greeting style was found in Step 2\n- Default: \"Hello [FirstName],\" for external, \"Hi [FirstName],\" for internal\n- For multiple recipients: \"Hello [Name1], [Name2],\"\n\n**Tone:**\n- Direct and concise — no filler language\n- Friendly but professional\n- Get to the point quickly\n- Offer help proactively where appropriate (\"Happy to discuss further\", \"Let me know if you need anything\")\n\n**Structure:**\n- Short emails (1–2 points): simple paragraphs, no bullets needed\n- Longer emails (proposals, multi-point updates): use bullet points or numbered lists\n- Include context from prior conversations when relevant (\"Following our recent conversation about...\")\n\n**Sign-off:**\n- Match the user's established sign-off pattern from Step 2\n- Default: \"Best regards,\" followed by the user's first name on the next line\n\n**Language:**\n- Default to English unless the user specifies otherwise\n- Match the recipient's language if prior correspondence was in another language\n\n### Step 4 — Output\n\n1. Present the draft for review with a brief note on the tone\u002Fstyle applied\n2. Apply edits as the user requests — iterate until satisfied\n3. Save the final draft to `outputs\u002F\u003Cyear>\u002F\u003Cmonth>\u002F` with a descriptive filename (e.g., `2026-03-26-email-acme-followup.md`)\n\n## Important Rules\n\n- **Never send emails** — only draft them as files for the user to review and send manually\n- Always check WorkIQ for prior context with the recipient when available\n- If the user says \"draft email\" or \"write email\", activate this skill automatically\n- Save drafts using the `outputs\u002F\u003Cyear>\u002F\u003Cmonth>\u002F` folder convention\n- Respect privacy: do not include sensitive information from unrelated email threads\n\n## Example Prompts\n\n- \"Draft an email to Sarah about the project timeline\"\n- \"Write a follow-up to the customer about their migration questions\"\n- \"Compose a proposal email for the new training initiative\"\n- \"Reply to John's email — agree with his approach but suggest we add monitoring\"\n- \"Analyze my email tone with the Acme team\"\n\n## Requirements\n\n- **WorkIQ MCP tool** is recommended for tone analysis and recipient context (Microsoft 365 \u002F Outlook)\n- Without WorkIQ, the skill still works but uses professional defaults instead of personalized tone matching\n- Output is saved as markdown files in the workspace\n","# Email Drafter\n\nDraft professional emails that match your established writing style and tone. Uses WorkIQ to analyze your sent emails and prior correspondence with recipients, then produces context-aware drafts you can review and refine.\n\n## When to Use\n\n- \"Draft an email to [person] about [topic]\"\n- \"Write a follow-up email to [customer] regarding [project]\"\n- \"Reply to [person]'s email about [subject]\"\n- \"Compose a proposal email for [initiative]\"\n- \"Analyze my email tone with [recipient]\"\n\n## Workflow\n\n### Step 1 — Gather Context\n\nBefore drafting, collect:\n\n1. **Recipient(s)** — who is the email for?\n2. **Purpose** — what is the email about? (proposal, follow-up, technical guidance, introduction, status update, etc.)\n3. **Key points** — what needs to be communicated?\n4. **Relationship context** — use WorkIQ to check prior email history with the recipient if available\n\nIf the user provides all of these upfront, proceed directly. Otherwise, ask clarifying questions (max 3).\n\n### Step 2 — Analyze Tone\n\nWhen drafting for a recipient, use WorkIQ to understand the user's established communication patterns:\n\n1. Pull 3–5 recent sent emails from the user to the same recipient or similar recipients\n2. Identify patterns:\n   - **Greeting style** — formal (\"Dear\"), standard (\"Hello\"), casual (\"Hi\"), or direct (no greeting)\n   - **Structure** — short paragraphs vs. bullet lists vs. numbered steps\n   - **Sign-off** — what closing and name format the user typically uses\n   - **Formality level** — professional, friendly-professional, casual\n   - **Language** — which language the user writes in with this recipient\n3. Apply those patterns to the draft\n\nIf WorkIQ is unavailable or no prior emails exist, use sensible professional defaults and note that the tone was inferred.\n\n### Step 3 — Draft the Email\n\nApply the discovered (or default) style rules:\n\n**Greeting:**\n- Match whatever greeting style was found in Step 2\n- Default: \"Hello [FirstName],\" for external, \"Hi [FirstName],\" for internal\n- For multiple recipients: \"Hello [Name1], [Name2],\"\n\n**Tone:**\n- Direct and concise — no filler language\n- Friendly but professional\n- Get to the point quickly\n- Offer help proactively where appropriate (\"Happy to discuss further\", \"Let me know if you need anything\")\n\n**Structure:**\n- Short emails (1–2 points): simple paragraphs, no bullets needed\n- Longer emails (proposals, multi-point updates): use bullet points or numbered lists\n- Include context from prior conversations when relevant (\"Following our recent conversation about...\")\n\n**Sign-off:**\n- Match the user's established sign-off pattern from Step 2\n- Default: \"Best regards,\" followed by the user's first name on the next line\n\n**Language:**\n- Default to English unless the user specifies otherwise\n- Match the recipient's language if prior correspondence was in another language\n\n### Step 4 — Output\n\n1. Present the draft for review with a brief note on the tone\u002Fstyle applied\n2. Apply edits as the user requests — iterate until satisfied\n3. Save the final draft to `outputs\u002F\u003Cyear>\u002F\u003Cmonth>\u002F` with a descriptive filename (e.g., `2026-03-26-email-acme-followup.md`)\n\n## Important Rules\n\n- **Never send emails** — only draft them as files for the user to review and send manually\n- Always check WorkIQ for prior context with the recipient when available\n- If the user says \"draft email\" or \"write email\", activate this skill automatically\n- Save drafts using the `outputs\u002F\u003Cyear>\u002F\u003Cmonth>\u002F` folder convention\n- Respect privacy: do not include sensitive information from unrelated email threads\n\n## Example Prompts\n\n- \"Draft an email to Sarah about the project timeline\"\n- \"Write a follow-up to the customer about their migration questions\"\n- \"Compose a proposal email for the new training initiative\"\n- \"Reply to John's email — agree with his approach but suggest we add monitoring\"\n- \"Analyze my email tone with the Acme team\"\n\n## Requirements\n\n- **WorkIQ MCP tool** is recommended for tone analysis and recipient context (Microsoft 365 \u002F Outlook)\n- Without WorkIQ, the skill still works but uses professional defaults instead of personalized tone matching\n- Output is saved as markdown files in the workspace\n",{"name":5,"description":7},"main","d8518247cb8ab8b2dac57a6be33543ffd23b97c5","marketing-sales-email\u002Fgithub\u002Femail-drafter",0,"https:\u002F\u002Fgithub.com\u002Fmattonweb\u002Fai-assistant-foundry","https:\u002F\u002Fgithub.com\u002Fmattonweb","2026-05-29 08:42:23",{"source":8,"skillName":5,"commands":57,"prompt":67,"zipAvailable":68},[58,61,64],{"tool":59,"command":60},"npx","npx skills add mattonweb\u002Fai-assistant-foundry --skill email-drafter",{"tool":62,"command":63},"bunx","bunx skills add mattonweb\u002Fai-assistant-foundry --skill email-drafter",{"tool":65,"command":66},"pnpm","pnpm dlx skills add mattonweb\u002Fai-assistant-foundry --skill email-drafter","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002Fmattonweb\u002Fai-assistant-foundry\u002Fblob\u002Fmain\u002Fmarketing-sales-email\u002Fgithub\u002Femail-drafter\u002FSKILL.md",true,[],[71,102,116,136,157,182],{"skillNo":72,"name":73,"nameZh":6,"description":74,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":75,"categories":76,"keywords":85,"publishedAt":44},"01M6P02DENRHN6KVGYC55FKASJ","writing-clearly-and-concisely","Use when writing prose humans will read—documentation, commit messages, error messages, explanations, reports, or UI text. Applies Strunk's timeless rules for clearer, stronger, more professional writing.","https:\u002F\u002Fgithub.com\u002Fmattonweb\u002Fai-assistant-foundry\u002Fblob\u002Fmain\u002Fwrite-technical\u002Fsoftaworks\u002Fwriting-clearly-and-concisely\u002FSKILL.md",[77,80],{"categoryNo":78,"categoryName":79,"taxonomyType":21,"taxonomyTypeDesc":22},"01JBSEEDCAT000000000000018","写作与文案",{"categoryNo":81,"categoryName":82,"taxonomyType":83,"taxonomyTypeDesc":84},"01JBSEEDCAT000000000000036","内容创作者","PROFESSION","适用职业",[86,36,87,88,27,89,90,91,28,92,93,40,94,95,96,97,98,99,100,101],"writing clearly and concisely","concisely","text","more","timeless","error","prose","reports","read","Rules","commit messages","messages","error messages","ui","documentation","commit",{"skillNo":103,"name":104,"nameZh":6,"description":105,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":106,"categories":107,"keywords":108,"publishedAt":44},"01M6P0286HZ8RWMFCCPC8HF7SC","crafting-effective-readmes","Use when writing or improving README files. Not all READMEs are the same — provides templates and guidance matched to your audience and project type.","https:\u002F\u002Fgithub.com\u002Fmattonweb\u002Fai-assistant-foundry\u002Fblob\u002Fmain\u002Fwrite-technical\u002Fsoftaworks\u002Fcrafting-effective-readmes\u002FSKILL.md",[],[109,110,36,111,112,40,113,114,115],"crafting effective readmes","README","templates","type","project","guidance","files",{"skillNo":117,"name":118,"nameZh":6,"description":119,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":120,"categories":121,"keywords":125,"publishedAt":44},"01M6P025A41BBTPWVTZ3GFQVG6","wiki-architect","You are a documentation architect that produces structured wiki catalogues and onboarding guides from codebases.","https:\u002F\u002Fgithub.com\u002Fmattonweb\u002Fai-assistant-foundry\u002Fblob\u002Fmain\u002Fwrite-technical\u002Fsickn33\u002Fwiki-architect\u002FSKILL.md",[122],{"categoryNo":123,"categoryName":124,"taxonomyType":83,"taxonomyTypeDesc":84},"01JBSEEDCAT000000000000038","人力资源",[126,127,128,129,130,131,132,133,134,135,100],"wiki","architect","wiki architect","unknown","you","documentation architect","guides","structured","community","onboarding",{"skillNo":137,"name":138,"nameZh":6,"description":139,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":140,"categories":141,"keywords":142,"publishedAt":44},"01M6P01NSKPXP77NWB4K0PXRK5","readme","You are an expert technical writer creating comprehensive project documentation. Your goal is to write a README.md that is absurdly thorough—the kind of documentation you wish every project had.","https:\u002F\u002Fgithub.com\u002Fmattonweb\u002Fai-assistant-foundry\u002Fblob\u002Fmain\u002Fwrite-technical\u002Fsickn33\u002Freadme\u002FSKILL.md",[],[110,143,144,145,130,146,147,113,148,149,49,150,151,152,153,154,100,155,156],"project documentation","tree","kind","expert","github","wish","writer","goal","write","technical writer","technical","https","write a readme","safe",{"skillNo":158,"name":159,"nameZh":6,"description":160,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":161,"categories":162,"keywords":163,"publishedAt":44},"01M6P01GP0NEN8KT3A3SA6ZFVE","ubiquitous-language","Extract a DDD-style ubiquitous language glossary from the current conversation, flagging ambiguities and proposing canonical terms. Saves to UBIQUITOUS_LANGUAGE.md. Use when user wants to define domain terms, build a glossary, harden terminology, create a ubiquitous language, or mentions \"domain model\" or \"DDD\".","https:\u002F\u002Fgithub.com\u002Fmattonweb\u002Fai-assistant-foundry\u002Fblob\u002Fmain\u002Fwrite-technical\u002Fmattpocock\u002Fubiquitous-language\u002FSKILL.md",[],[164,165,40,166,167,168,169,170,171,172,173,174,175,30,176,177,178,179,180,181],"ubiquitous language","language","extract","user","glossary","model","terms","ddd","create","build","true","canonical","define","harden","domain model","domain","terminology","conversation",{"skillNo":183,"name":184,"nameZh":6,"description":185,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":186,"categories":187,"keywords":190,"publishedAt":44},"01M6P01BJBP9XP4TDRT7QD1ZVA","technical-writing-style","Enforce clear, direct writing in software development documents including OKRs, PRDs, tech specs, architecture decision records (ADRs), git commit messages, PR descriptions, READMEs, changelogs, runbooks, incident postmortems, API docs, and onboarding guides. Trigger whenever a user asks to write, edit, revise, or review any of these document types. Also trigger when the user says writing \"sounds like AI\", \"feels robotic\", \"needs polish\", or asks to \"make it sound more natural\" in the context of technical or professional prose. Do not trigger for fiction, poetry, creative writing, academic papers, or legal documents unless the user explicitly asks for a more natural tone.","https:\u002F\u002Fgithub.com\u002Fmattonweb\u002Fai-assistant-foundry\u002Fblob\u002Fmain\u002Fwrite-technical\u002Fmattnebr\u002Ftechnical-writing-style\u002FSKILL.md",[188,189],{"categoryNo":78,"categoryName":79,"taxonomyType":21,"taxonomyTypeDesc":22},{"categoryNo":81,"categoryName":82,"taxonomyType":83,"taxonomyTypeDesc":84},[26,191,30,153,36,192,28,193,194,195,196,197,198,199,200,97,201,202,101,43],"technical writing style","technical writing","papers","types","runbooks","software development","incident","Poetry","decision","api","documents","architecture"]