菜单
Draft a concise sales follow-up email after a customer meeting or call. Use when a Northwind Traders seller asks to follow up, recap next steps, thank a customer, confirm an order, or send a note after a demo or discovery call.
用 Codex 或 Claude 帮你安装 复制这段 Prompt，粘贴到 Codex、Claude 或其他助手里，让它检查 Skill 页面并帮你完成安装。
基于 SOC 职业分类
Authors and validates Microsoft Copilot Studio agent definitions (.mcs.yml) for the agents under src/agents/ in this M365 masterclass repo. Covers the topic YAML schema, the prebuilt entity catalog, Adaptive Card nodes, conversation design, and the language-server verification loop that settles "is this valid Copilot Studio YAML?" without guessing. Use when editing a topic, adding a Question or Adaptive Card, picking an entity, or when YAML might be Power Apps syntax instead of Copilot Studio syntax. Trigger phrases: copilot studio yaml, mcs.yml, topic yaml, AdaptiveDialog, Question node, AdaptiveCardPrompt, adaptive card, prebuilt entity, DatePrebuiltEntity, slot filling, trigger queries, is this valid copilot studio yaml, powerapps yaml, agent topic, onboarding agent, travel agent, food stock buddy.
Help a seller respond to common customer objections and push-back about price, timing, budget, or competitors during an active deal. Use when the user asks how to reply to, handle, or overcome a customer objection, a "too expensive" or "not the right time" comment, or a competitor comparison.
Research and summarize a customer account before a sales call. Use when a seller asks for an account brief, account summary, account research, pre-call prep, or a quick briefing on a Northwind Traders customer before a meeting.
Automate creation of Azure DevOps workload identity federation service connections with deployment metadata from deploy.json. Use when users need to create or delete Azure service connections with workload identity federation for secure, passwordless authentication.
Repo-local brand-voice checker for this Microsoft 365 / Copilot Studio & Copilot Cowork masterclass. Audits and fixes Markdown in demos/ and labs/ against the four house rules (no em dashes, quoted Mermaid labels, 4-sentence paragraph cap, topic-specific slash-command tables). Run after writing or significantly editing any readme.md or guide. The create-class master skill discovers this skill by globbing .claude/skills/brand-voice-*. Trigger phrases: brand voice check, brand-voice-copilot, quality check readme, fix em dashes, check mermaid labels, cowork brand voice, audit readme, polish demos readme.
Authors a Microsoft 365 Copilot Cowork custom skill (a SKILL.md plus its companion files) that Cowork reliably discovers and runs. Covers the frontmatter contract, the kebab-case name-matches-folder rule, OneDrive placement, companion-file limits, and the run-and-tune loop that makes a skill trigger on natural phrasing. Use when asked to create a cowork skill, author a custom skill for Cowork, write a SKILL.md for Copilot, build a Copilot Cowork skill, package a skill for upload, or fix a Cowork skill that will not load or will not trigger.
| name | follow-up-email-drafter |
| description | Draft a concise sales follow-up email after a customer meeting or call. Use when a Northwind Traders seller asks to follow up, recap next steps, thank a customer, confirm an order, or send a note after a demo or discovery call. |
Draft a short, professional follow-up email a Northwind Traders seller can send after a customer meeting, call, or demo. Keep it warm and specific, recap what was agreed, and make the next step easy to accept.
Turn the seller's notes about a customer conversation into a ready-to-send email. Capture the customer name, the topic discussed, and any agreed next steps. If a next step or date is missing, propose a reasonable one rather than leaving the email vague.
Return the draft in this shape:
Subject: <clear, specific subject line>
Hi <customer first name>,
<one-line thank-you referencing the conversation>
<two or three sentence recap of key points or decisions>
<one clear next step with a proposed date or timeframe>
Best regards,
<seller name>
Northwind Traders
If the seller's notes do not name a customer or a topic, do not invent details. Ask one short clarifying question for the missing information before drafting the email.