Agents & OrchestrationSûr100100/100
Executive Briefing (Microsoft)
Prepare a concise synthetic pre-meeting briefing and review checklist.
ou envoie-le directement à ton agent.
Installer dans ton projet
$ curl -fsSL https://arboristhree.xyz/cli/install-skill.mjs -o /tmp/arboris-install-skill.mjs && node /tmp/arboris-install-skill.mjs executive-briefing__microsoft-aibast-agents-library__solutions-account-intelligence-manual-skills-ef429e9f2217Microsoft
microsoft/aibast-agents-library
Contenu à copier
--- name: account-intelligence-executive-briefing description: Prepare a concise synthetic pre-meeting briefing and review checklist. metadata: origin: Microsoft --- # Account Intelligence Agent — Executive Briefing ## Persona Customer Success Manager ## Input contract - Operation: `executive_briefing` - Data source: `synthetic` only - Use only the two uploaded knowledge files in this package. ## Guardrails - Use only the fixed Acme snapshot; do not browse, enrich, infer, invent, or use external data. - Treat every recommendation, message, mitigation, and next step as a draft for authorized human review. - Do not send outreach, update CRM, create tasks, schedule meetings, change forecasts, approve pricing, deliver proposals, or contact customers. ## Procedure 1. Confirm that the request matches `executive_briefing`. 2. Read the synthetic records and operating rules before analyzing. 3. Use exact synthetic identifiers when evidence is available; do not invent missing records. 4. Start the response with the exact heading `Account Intelligence Briefing`. 5. Include the exact heading `Pre-Meeting Checklist` before the review actions. 6. End with the exact heading `Evidence boundary`, followed by the boundary below. ## Evidence boundary All exact names, dates, counts, prices, amounts, scores, percentages, and projections are synthetic test evidence. The response is read-only decision support. Do not claim that outreach was sent, a CRM record changed, a task or alert was created, pricing or an approval was granted, a proposal was delivered, or any customer communication occurred. ## Locked demo prompt Prepare a concise synthetic Acme pre-meeting briefing and review checklist. ## Expected evidence marker The response must include the exact headings `Account Intelligence Briefing`, `Pre-Meeting Checklist`, and `Evidence boundary`.
Colle ce Markdown dans ton agent ou utilise les boutons ci-dessus pour l’écrire dans ton projet.
Ce que fait Executive Briefing (Microsoft)
Operation: `executive_briefing`
Data source: `synthetic` only
Use only the two uploaded knowledge files in this package.
Use only the fixed Acme snapshot; do not browse, enrich, infer, invent, or use external data.
Comment utiliser Executive Briefing (Microsoft)
1
Copie le prompt
Un clic copie le prompt packagé (ou l'envoie à ton agent).
2
L'agent installe le skill
Il ajoute le SKILL.md et ses ressources à ton projet.
3
Activation automatique
Le skill s'active dès que le contexte correspond.
Déclencheurs pour Executive Briefing (Microsoft)
Dis simplement à ton agent quelque chose comme :
Applique le skill executive-briefing__microsoft-aibast-agents-library__solutions-account-intelligence-manual-skills-ef429e9f2217 à cette tâche
Utilise executive-briefing__microsoft-aibast-agents-library__solutions-account-intelligence-manual-skills-ef429e9f2217 pour améliorer cette implémentation
Passe en revue ce sujet avec executive-briefing__microsoft-aibast-agents-library__solutions-account-intelligence-manual-skills-ef429e9f2217
Skills liés à Executive Briefing (Microsoft)
Acceleration (Microsoft)
Compare synthetic acceleration options and clearly separate scenario value from forecast commitments.Account Overview (Microsoft)
Create a synthetic Acme account overview and identify evidence that merits seller attention.Acroform Writer (Microsoft)
Use this skill whenever the user wants values written INTO an existing PDF form that lives in the connected SharePoint knowledge source — filling out, completing, populating, or submitting a fillable PDF (application, intake sheet, contract, government form) from data they supply, a spreadsheet row, or the conversation. Triggers include "fill out the job application form", "complete the intake form for [person]", "populate our standard NDA template", and "make this ready to send / non-editable" (flatten). The source form should be found via knowledge search; only ask the user to upload it if knowledge search turns up nothing plausible. different task), and do NOT use it on scanned/image-only PDFs that have no real fillable fields — those need OCR or manual overlay instead, which this skill explicitly detects and reports rather than silently failing.