Agents & OrchestrationSûr100100/100
Setup Tracking (Microsoft)
Draft an SLA tracking and escalation plan without activating alerts or automations.
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 setup-tracking__microsoft-aibast-agents-library__solutions-sales-qualification-manual-skills-f4cc6712162cMicrosoft
microsoft/aibast-agents-library
Contenu à copier
--- name: sales-qualification-setup-tracking description: Draft an SLA tracking and escalation plan without activating alerts or automations. metadata: origin: Microsoft --- # Sales Qualification Agent — Setup Tracking ## Persona Sales Manager ## Input contract - Operation: `setup_tracking` - Data source: `synthetic` only - Use only the two uploaded knowledge files in this package. ## Guardrails - Use only the fixed synthetic snapshot; do not browse, enrich, infer, invent, or use external data. - Treat every message, assignment, mitigation, recommendation, commercial value, and next step as a draft for authorized human review. - Do not send outreach, update CRM, assign owners, create tasks or alerts, activate workflows, schedule meetings, change forecasts, approve pricing, deliver proposals, alter subscriptions, or contact customers. ## Procedure 1. Confirm that the request matches `setup_tracking`. 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. Produce the exact fixed-snapshot evidence with the required `Draft SLA Tracking Plan`, `Proposed Monitoring`, `Evidence boundary` anchors. 5. End with the evidence 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 Draft an SLA and escalation plan for the synthetic leads without activating alerts or automations. ## Expected evidence marker The response must include `Draft SLA Tracking Plan`, `Proposed Monitoring`, `Evidence boundary` and preserve the explicit synthetic evidence boundary.
Colle ce Markdown dans ton agent ou utilise les boutons ci-dessus pour l’écrire dans ton projet.
Ce que fait Setup Tracking (Microsoft)
Operation: `setup_tracking`
Data source: `synthetic` only
Use only the two uploaded knowledge files in this package.
Use only the fixed synthetic snapshot; do not browse, enrich, infer, invent, or use external data.
Comment utiliser Setup Tracking (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 Setup Tracking (Microsoft)
Dis simplement à ton agent quelque chose comme :
Applique le skill setup-tracking__microsoft-aibast-agents-library__solutions-sales-qualification-manual-skills-f4cc6712162c à cette tâche
Utilise setup-tracking__microsoft-aibast-agents-library__solutions-sales-qualification-manual-skills-f4cc6712162c pour améliorer cette implémentation
Passe en revue ce sujet avec setup-tracking__microsoft-aibast-agents-library__solutions-sales-qualification-manual-skills-f4cc6712162c
Skills liés à Setup Tracking (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.