All included agents
Find the agent for the job
Most sellers start with the two primary plugins. These four packages retain all 137 workflow definitions from the older seven-package layout; that count does not mean 137 live executions have been proved.
Open a package below to see every included agent and the outcome it is intended to help with. Copy its exact agent name into a request with the package name, your context, allowed sources and action boundary.
Start with four ready-to-use prompts · Download the plugins · Release to your team.
Sales Suite | Seller Workflows
56 included agents · Primary sales package
account-plan— Create or refresh a review-ready account plan from current customer evidence.Action boundary: draft-only. Any external action still requires its own supported path and approval.
account-plan-refresh-cowork— Refresh an account-plan draft from changed evidence while preserving reviewed decisions.Action boundary: draft-only. Any external action still requires its own supported path and approval.
account-tiering— Prioritize an authorized account book using explicit fit and engagement criteria.Action boundary: read-only. Any external action still requires its own supported path and approval.
calendar-account-alignment— Map upcoming meetings to CRM records and surface ambiguous or unbound participants.Action boundary: read-only. Any external action still requires its own supported path and approval.
calendar-events— Retrieve CRM-linked meeting history and surface missing account or opportunity links.Action boundary: read-only. Any external action still requires its own supported path and approval.
call-follow-up— Turn reviewed meeting evidence into a customer follow-up draft and internal action summary.Action boundary: draft-only. Any external action still requires its own supported path and approval.
close-date-realism— Assess close-date realism from dependencies and customer-confirmed timing without changing the date.Action boundary: read-only. Any external action still requires its own supported path and approval.
close-plan— Draft a customer-centered business case and mutual action plan with owners and dates.Action boundary: draft-only. Any external action still requires its own supported path and approval.
commit-readiness-review— Evaluate resource, delivery, customer, and timing readiness before a commit decision.Action boundary: read-only. Any external action still requires its own supported path and approval.
communication-voice-profile— Derive a consented, minimized communication-style profile with deletion controls.Action boundary: read-only. Any external action still requires its own supported path and approval.
communication-voice-profile-evidence— Derive a consented communication-style profile with minimized features and deletion controls.Action boundary: read-only. Any external action still requires its own supported path and approval.
content-reuse-recommender— Recommend approved reusable content based on scenario fit, freshness, and permissions.Action boundary: read-only. Any external action still requires its own supported path and approval.
conversation-summary— Summarize an authorized conversation into decisions, actions, risks, and record context.Action boundary: read-only. Any external action still requires its own supported path and approval.
coverage-gap-analysis— Identify portfolio coverage gaps by period, owner, solution, and evidence quality.Action boundary: read-only. Any external action still requires its own supported path and approval.
cowork-opportunity-room— Assemble and maintain a supervised opportunity workspace across CRM and Microsoft 365.Action boundary: approval-gated. Any external action still requires its own supported path and approval.
crm-hygiene-check— Audit CRM records for missing, stale, contradictory, or invalid fields without changing them.Action boundary: read-only. Any external action still requires its own supported path and approval.
customer-commitment-register— Maintain a reviewable register of customer and account-team commitments with provenance.Action boundary: draft-only. Any external action still requires its own supported path and approval.
daily-briefing— Prioritize today's meetings, opportunities, messages, and follow-through for one seller.Action boundary: read-only. Any external action still requires its own supported path and approval.
daily-seller-priority— Rank today's seller work from meetings, tasks, deal risk, and customer commitments.Action boundary: read-only. Any external action still requires its own supported path and approval.
decision-log-maintenance— Update a decision log only after the operator approves the exact new entries.Action boundary: approval-gated. Any external action still requires its own supported path and approval.
find-internal-answer— Find an approved internal answer, document, policy, or experienced colleague with citations.Action boundary: read-only. Any external action still requires its own supported path and approval.
follow-up-email-draft— Draft customer follow-up from reviewed meeting decisions and CRM evidence.Action boundary: draft-only. Any external action still requires its own supported path and approval.
forecast-evidence-check— Compare forecast assertions with dated customer and execution evidence without writing forecast.Action boundary: read-only. Any external action still requires its own supported path and approval.
forecast-narrative— Draft a forecast narrative that separates CRM forecast state from supporting evidence.Action boundary: draft-only. Any external action still requires its own supported path and approval.
inbox-opportunity-triage— Triage authorized mail into exact account and opportunity context without moving messages.Action boundary: read-only. Any external action still requires its own supported path and approval.
inbox-sweep— Triage authorized customer mail into account context, priority, and draft follow-through.Action boundary: draft-only. Any external action still requires its own supported path and approval.
internal-expert-finder— Find colleagues with recent relevant experience without inferring unrecorded expertise.Action boundary: read-only. Any external action still requires its own supported path and approval.
internal-swarm-brief— Draft an internal swarm brief with exact asks, owners, and customer-safe context.Action boundary: draft-only. Any external action still requires its own supported path and approval.
live-meeting-question-pack— Prepare evidence-backed questions for discovery, contradiction, and decision confirmation.Action boundary: draft-only. Any external action still requires its own supported path and approval.
manager-coaching-brief— Draft a private manager coaching brief grounded in deal evidence, not inferred performance.Action boundary: draft-only. Any external action still requires its own supported path and approval.
meeting-cadence-planner— Propose and schedule an account cadence only after recipient and timing confirmation.Action boundary: approval-gated. Any external action still requires its own supported path and approval.
meeting-context-assembly— Assemble meeting, participant, account, and opportunity context with source boundaries intact.Action boundary: read-only. Any external action still requires its own supported path and approval.
meeting-followthrough-cowork— Coordinate reviewed meeting actions across drafts, tasks, and CRM previews with receipts.Action boundary: approval-gated. Any external action still requires its own supported path and approval.
meeting-to-crm-draft— Project meeting outcomes into an owning-CRM update preview without saving it.Action boundary: draft-only. Any external action still requires its own supported path and approval.
mobile-parked-debrief— Capture a voice debrief, draft follow-through, and defer mutation until parked confirmation.Action boundary: draft-only. Any external action still requires its own supported path and approval.
pipeline-change-digest— Summarize material pipeline changes across a governed portfolio and time window.Action boundary: read-only. Any external action still requires its own supported path and approval.
pipeline-quality-score— Score pipeline data quality with visible rules, denominators, and exceptions.Action boundary: read-only. Any external action still requires its own supported path and approval.
pipeline-remediation-cowork— Prepare remediation previews in batches and require exact approval per owning-system effect.Action boundary: approval-gated. Any external action still requires its own supported path and approval.
pipeline-review— Review pipeline coverage, aging, hygiene, risk, and priority actions for an authorized scope.Action boundary: read-only. Any external action still requires its own supported path and approval.
postmeeting-action-extraction— Extract proposed owners, dates, decisions, and follow-through from an authorized meeting record.Action boundary: draft-only. Any external action still requires its own supported path and approval.
premeeting-risk-brief— Draft a compact premeeting brief focused on open risk, commitments, and next decisions.Action boundary: draft-only. Any external action still requires its own supported path and approval.
proof-package-builder-cowork— Assemble a review-ready proof package from scope, evidence, acceptance, and architecture artifacts.Action boundary: draft-only. Any external action still requires its own supported path and approval.
renewal-watch-cowork— Watch renewal evidence and surface only material, attributable changes for review.Action boundary: read-only. Any external action still requires its own supported path and approval.
research-prospect— Research one prospect from approved public and organizational sources with citations.Action boundary: read-only. Any external action still requires its own supported path and approval.
scenario-forecast-model— Model explicit forecast scenarios while preserving the original CRM forecast unchanged.Action boundary: draft-only. Any external action still requires its own supported path and approval.
schedule-meeting— Propose a meeting time and invite, then execute only after exact confirmation.Action boundary: approval-gated. Any external action still requires its own supported path and approval.
seller-weekly-wrap— Draft a seller-owned weekly delta across meetings, pipeline, risks, and follow-through.Action boundary: draft-only. Any external action still requires its own supported path and approval.
stage-exit-audit— Check stage-exit evidence and report labeled-versus-functional divergence.Action boundary: read-only. Any external action still requires its own supported path and approval.
target-distribution— Preview and approve assignment of one lead or contact to the responsible seller or agent.Action boundary: approval-gated. Any external action still requires its own supported path and approval.
task-focus-sequencer— Draft a bounded work sequence from due dates, dependencies, customer impact, and available time.Action boundary: draft-only. Any external action still requires its own supported path and approval.
team-pipeline— Produce an authorized team pipeline rollup with per-owner priorities and evidence.Action boundary: read-only. Any external action still requires its own supported path and approval.
territory-sweep-cowork— Sweep an authorized territory for prioritized evidence gaps, changes, and next reviews.Action boundary: read-only. Any external action still requires its own supported path and approval.
travel-meeting-load— Surface travel, meeting density, and after-hours load without making health conclusions.Action boundary: read-only. Any external action still requires its own supported path and approval.
weekly-wrap— Draft a seller-owned weekly summary of wins, movement, slips, risks, and next week.Action boundary: draft-only. Any external action still requires its own supported path and approval.
whitespace-to-pipeline-plan— Convert reviewed account whitespace into a draft pipeline-generation plan.Action boundary: draft-only. Any external action still requires its own supported path and approval.
win-loss-review— Analyze time-valid win and loss evidence for repeatable patterns and contrary evidence.Action boundary: read-only. Any external action still requires its own supported path and approval.
Sales Suite | Account & Deals
56 included agents · Primary sales package
account-context— Assemble one cited account brief across CRM and authorized Microsoft 365 context.Action boundary: read-only. Any external action still requires its own supported path and approval.
account-org-change-watch— Monitor authorized organization changes and route material relationship shifts for review.Action boundary: read-only. Any external action still requires its own supported path and approval.
account-relationship-heatmap— Map relationship strength and silence using authorized CRM and Microsoft 365 evidence.Action boundary: read-only. Any external action still requires its own supported path and approval.
account-strategy-delta— Draft the evidence-backed change since the last reviewed account strategy.Action boundary: draft-only. Any external action still requires its own supported path and approval.
account-technology-estate— Assemble a cited account technology estate without converting inference into installed-product fact.Action boundary: read-only. Any external action still requires its own supported path and approval.
activity-history— Retrieve a normalized CRM activity timeline for an account, contact, or opportunity.Action boundary: read-only. Any external action still requires its own supported path and approval.
applications-estimating-readiness— Check evidence completeness and contradictions before an Applications and Estimating handoff draft.Action boundary: draft-only. Any external action still requires its own supported path and approval.
buying-committee-gap— Find missing buying roles and silent stakeholders without inventing influence.Action boundary: read-only. Any external action still requires its own supported path and approval.
call-prep— Prepare a compact pre-call brief with attendees, account context, recent evidence, and questions.Action boundary: read-only. Any external action still requires its own supported path and approval.
carrier-case-triage— Classify, enrich, route, and verify service cases with owning-CRM write-back after approval.Action boundary: approval-gated. Any external action still requires its own supported path and approval.
case-evidence-brief— Assemble a current case brief with customer, activity, knowledge, and ownership evidence.Action boundary: read-only. Any external action still requires its own supported path and approval.
commercial-risk-handoff— Prepare an evidence-backed commercial-risk handoff for the accountable deal owner.Action boundary: draft-only. Any external action still requires its own supported path and approval.
comparable-project-evidence— Find comparable projects while preserving differences, limitations, and pricing boundaries.Action boundary: read-only. Any external action still requires its own supported path and approval.
competitive-footprint-brief— Draft a source-cited competitive footprint with confidence and freshness visible.Action boundary: draft-only. Any external action still requires its own supported path and approval.
cross-provider-ownership-map— Show the owning system, owner, and permitted action lane for each linked record.Action boundary: read-only. Any external action still requires its own supported path and approval.
cross-provider-record-graph— Resolve linked records across providers without merging or overwriting provider-owned truth.Action boundary: read-only. Any external action still requires its own supported path and approval.
customer-health— Summarize relationship, adoption, service, renewal, and commercial health with evidence.Action boundary: read-only. Any external action still requires its own supported path and approval.
customer-impact-summary— Summarize customer impact, affected operations, and evidence confidence for handoff.Action boundary: draft-only. Any external action still requires its own supported path and approval.
customer-priority-synthesis— Synthesize customer priorities across CRM, service, and collaboration evidence without merging authority.Action boundary: draft-only. Any external action still requires its own supported path and approval.
customer-voice— Retrieve attributable customer statements on a topic from authorized communications.Action boundary: read-only. Any external action still requires its own supported path and approval.
deal-advance-gap— Identify the shortest evidence-backed path to advance one opportunity.Action boundary: read-only. Any external action still requires its own supported path and approval.
deal-review— Review one opportunity for evidence, risk, qualification gaps, and next actions.Action boundary: read-only. Any external action still requires its own supported path and approval.
deal-signals— Find material opportunity changes, silence, slips, stakeholder changes, and renewal signals.Action boundary: read-only. Any external action still requires its own supported path and approval.
deal-slip-scenario— Model the impact of a possible deal slip without changing the forecast.Action boundary: draft-only. Any external action still requires its own supported path and approval.
decision-criteria-trace— Trace customer decision criteria to their exact source and last confirmation date.Action boundary: read-only. Any external action still requires its own supported path and approval.
display-widget— Render a structured workflow result without changing its evidence or effect state.Action boundary: none. Any external action still requires its own supported path and approval.
draft-outreach— Draft customer outreach grounded in account evidence and recipient context.Action boundary: draft-only. Any external action still requires its own supported path and approval.
duplicate-record-resolution-draft— Draft a duplicate-resolution recommendation with match evidence and ambiguity preserved.Action boundary: draft-only. Any external action still requires its own supported path and approval.
entitlement-context-check— Retrieve nonbinding entitlement context and flag missing or conflicting contract data.Action boundary: read-only. Any external action still requires its own supported path and approval.
escalation-risk-detection— Detect escalation risk from explicit service evidence and expose the contributing signals.Action boundary: read-only. Any external action still requires its own supported path and approval.
estimate-path-discussion— Explain a nonbinding SWAG, ROM, firm-candidate, or withheld discussion path with cited gaps.Action boundary: draft-only. Any external action still requires its own supported path and approval.
expansion-whitespace— Separate observed customer estate from evidence-backed expansion possibilities.Action boundary: read-only. Any external action still requires its own supported path and approval.
handle-objection— Prepare an evidence-backed response to a customer objection or competitive concern.Action boundary: draft-only. Any external action still requires its own supported path and approval.
identity-link-confidence— Score cross-provider identity links and refuse automatic joins below the approved threshold.Action boundary: read-only. Any external action still requires its own supported path and approval.
knowledge-answer-draft— Draft a case-specific answer from approved knowledge with citations and applicability limits.Action boundary: draft-only. Any external action still requires its own supported path and approval.
lead-triage— Score and route one inbound lead against approved qualification criteria.Action boundary: draft-only. Any external action still requires its own supported path and approval.
log-activity— Draft, confirm, create, and verify one completed CRM activity in its owning system.Action boundary: approval-gated. Any external action still requires its own supported path and approval.
mutual-action-plan-draft— Draft a mutual action plan with evidence-backed owners, dependencies, and target dates.Action boundary: draft-only. Any external action still requires its own supported path and approval.
next-step-evidence-draft— Draft the next opportunity step from exact current provider evidence and citations.Action boundary: draft-only. Any external action still requires its own supported path and approval.
opportunity-contradiction-review— Surface conflicting dates, stages, commitments, and next steps with source authority.Action boundary: read-only. Any external action still requires its own supported path and approval.
opportunity-evidence-completeness— Score required opportunity evidence without treating missing data as a negative customer signal.Action boundary: read-only. Any external action still requires its own supported path and approval.
proof-to-close-plan— Translate accepted proof outcomes into a bounded close-plan draft without changing forecast state.Action boundary: draft-only. Any external action still requires its own supported path and approval.
provider-freshness-monitor— Monitor provider observations against workflow-specific freshness requirements.Action boundary: read-only. Any external action still requires its own supported path and approval.
provider-schema-drift— Detect required field, type, option, and relationship drift before workflow execution.Action boundary: read-only. Any external action still requires its own supported path and approval.
reference-customer-match— Rank relevant reference candidates with similarity, permission, and sensitivity gates.Action boundary: read-only. Any external action still requires its own supported path and approval.
renewal-radar— Surface upcoming renewals, evidence-backed risk, timing, and growth context.Action boundary: read-only. Any external action still requires its own supported path and approval.
rep-context— Prepare a private manager catch-up brief for one seller without inferring performance.Action boundary: read-only. Any external action still requires its own supported path and approval.
resolution-note-draft— Draft resolution notes from reviewed case evidence without resolving the case.Action boundary: draft-only. Any external action still requires its own supported path and approval.
sales-service-continuity— Connect opportunity risk, customer cases, incidents, warranty, and service follow-through.Action boundary: draft-only. Any external action still requires its own supported path and approval.
service-to-renewal-signal— Surface reviewed service patterns relevant to renewal without inferring customer intent.Action boundary: read-only. Any external action still requires its own supported path and approval.
sla-risk-brief— Brief current SLA risk using provider timestamps without promising contractual outcomes.Action boundary: read-only. Any external action still requires its own supported path and approval.
source-authority-conflict— Surface contradictory values with authority, freshness, and an explicit resolution owner.Action boundary: read-only. Any external action still requires its own supported path and approval.
stakeholder-influence-map— Map stakeholder influence, role, recency, and evidence confidence for one account.Action boundary: read-only. Any external action still requires its own supported path and approval.
stakeholder-map— Map known stakeholders, roles, access, recency, and evidence gaps for one account.Action boundary: read-only. Any external action still requires its own supported path and approval.
unified-customer-timeline— Project provider-owned events into one ordered timeline without changing source records.Action boundary: read-only. Any external action still requires its own supported path and approval.
whitespace-evidence-map— Identify solution whitespace while separating observed estate from unverified opportunity hypotheses.Action boundary: read-only. Any external action still requires its own supported path and approval.
Sales Suite | V-Team Service
11 included agents · Optional specialist package; host tests pending
asset-service-history— Retrieve an asset's service history, recurring symptoms, and source records.Action boundary: read-only. Any external action still requires its own supported path and approval.
case-swarm-cowork— Assemble a supervised case swarm with context, experts, actions, and escalation boundaries.Action boundary: draft-only. Any external action still requires its own supported path and approval.
dispatcher-exception-brief— Draft dispatcher options for delays, cancellations, conflicts, and urgent work.Action boundary: draft-only. Any external action still requires its own supported path and approval.
field-service-to-sales-signal— Draft an account-team signal from reviewed field evidence without creating pipeline or inferring intent.Action boundary: draft-only. Any external action still requires its own supported path and approval.
first-time-fix-risk— Surface first-time-fix risks from skills, parts, history, diagnostics, and access constraints.Action boundary: read-only. Any external action still requires its own supported path and approval.
mobile-handoff-draft— Draft a technician-to-dispatch or technician-to-support handoff from field evidence.Action boundary: draft-only. Any external action still requires its own supported path and approval.
onsite-safety-context— Present approved site safety context and require authoritative procedure follow-through.Action boundary: read-only. Any external action still requires its own supported path and approval.
parts-readiness-check— Check required and available parts while flagging uncertain substitutions and inventory age.Action boundary: read-only. Any external action still requires its own supported path and approval.
schedule-change-impact— Explain customer, technician, route, SLA, and downstream impact before rescheduling.Action boundary: read-only. Any external action still requires its own supported path and approval.
technician-daily-brief— Brief a technician's assigned day with travel, dependencies, parts, and customer context.Action boundary: read-only. Any external action still requires its own supported path and approval.
work-order-prep-brief— Prepare work-order, asset, customer, safety, and service-history context for a technician.Action boundary: read-only. Any external action still requires its own supported path and approval.
Sales Suite | Admin Support
14 included agents · Optional specialist package; host tests pending
approval-timeout-monitor— Monitor pending approvals, expire stale requests, and preserve immutable decision history.Action boundary: read-only. Any external action still requires its own supported path and approval.
canonical-link-repair— Repair an approved cross-reference only in its owning system and verify the resulting link.Action boundary: approval-gated. Any external action still requires its own supported path and approval.
citation-integrity-audit— Verify every consequential claim resolves to an authorized provider-owned source link.Action boundary: read-only. Any external action still requires its own supported path and approval.
clean-install-verifier— Verify a clean installation against package identity, permissions, host binding, and golden prompts.Action boundary: read-only. Any external action still requires its own supported path and approval.
deployment-plan-generator— Generate exact deployment effects, prerequisites, manual gates, costs, and rollback steps.Action boundary: draft-only. Any external action still requires its own supported path and approval.
extension-upgrade-planner— Plan source-agent, host snapshot, backend, and provider-adapter upgrades without executing them.Action boundary: draft-only. Any external action still requires its own supported path and approval.
headless-work-item-orchestrator— Run triggered durable work with idempotency, retries, dead letters, approvals, and receipts.Action boundary: approval-gated. Any external action still requires its own supported path and approval.
immutable-effect-receipt— Emit a tamper-evident record of approved effects, results, failures, and post-action verification.Action boundary: none. Any external action still requires its own supported path and approval.
owning-system-write-router— Route an approved mutation only to the owning provider and emit a post-write receipt.Action boundary: approval-gated. Any external action still requires its own supported path and approval.
permission-drift-audit— Detect identity, scope, role, audience, and consent drift from the approved release contract.Action boundary: read-only. Any external action still requires its own supported path and approval.
provider-health-doctor— Verify identity, permissions, schemas, freshness, endpoints, and citation reachability.Action boundary: read-only. Any external action still requires its own supported path and approval.
release-evidence-pack— Assemble version, hashes, tests, licenses, limitations, and acceptance into a release evidence pack.Action boundary: draft-only. Any external action still requires its own supported path and approval.
rollback-readiness-check— Confirm owned resources, preserved data, restore points, and verification steps before release.Action boundary: read-only. Any external action still requires its own supported path and approval.
turnkey-release-operator— Plan, install, verify, upgrade, and roll back tenant-neutral packages with exact receipts.Action boundary: approval-gated. Any external action still requires its own supported path and approval.
Read the boundaries
These are instructions used by Cowork, not independent security controls or new data permissions. Availability, source access, agent selection, accuracy, effects and rollback must be checked in the intended host. An approval-gated routine is not permission to act.
112 primary discovery/rehearsal prompts · 25 optional discovery/rehearsal prompts. Both are blank test templates, not completed evidence.