handoff-brief-generator

handoff-brief-generator is a skill for Claude Code, Codex from microsoft/dataverse-business-skills. It costs 83 tokens per session (4,539 once invoked), scanned A, original, MIT.

A sales-deal handoff brief generator that gathers CRM information into a structured document for someone covering active deals during a vacation or transition.

In plain words
What is it for?
Use it to prepare coverage briefs with deal status, recent activities, next steps, contacts, and risks for active opportunities.
Why use it?
It removes the need to search through scattered customer records and helps the backup person understand each deal without missing important details or risks.

Skill for Claude CodeCodex ✓ vendor

Written for no agent in particular: nothing here depends on one.

Good fit Use it to prepare coverage briefs with deal status, recent activities, next steps, contacts, and risks for active opportunities.

Compare 6 skills from other repositories ↓
Install with agentmods
npx agentmods add skills/microsoft/dataverse-business-skills/handoff-brief-generator
About the project

Dataverse Business Skills is a collection of natural-language instructions that teach AI agents how to follow business processes, policies, and domain knowledge for Microsoft Dataverse. Organizations use the skills with Dataverse environments connected to products such as Power Apps, Dynamics 365, or Power Platform. The catalogue entries are skills from this collection.

microsoft/dataverse-business-skills · 50 stars · on GitHub

Install

Getting it into your agent

One page per mod, every tool's command on it. A separate URL per tool would split the same page into five that compete with each other.

Any agent
npx skills add microsoft/dataverse-business-skills --skill handoff-brief-generator
Clone the repo
git clone --depth 1 https://github.com/microsoft/dataverse-business-skills

Made for: Claude Code, Codex.

Wrote this? Show the measurements

A badge with what this costs and how it scanned, read live from this page, so it follows the numbers instead of freezing them. Markdown for a README, HTML for a documentation site or a project page.

agentmods badge for handoff-brief-generator

README.md
[![agentmods](https://agentmods.dev/badge/skills/microsoft/dataverse-business-skills/handoff-brief-generator/github.svg)](https://agentmods.dev/skills/microsoft/dataverse-business-skills/handoff-brief-generator)
Your own site
<a href="https://agentmods.dev/skills/microsoft/dataverse-business-skills/handoff-brief-generator"><img src="https://agentmods.dev/badge/skills/microsoft/dataverse-business-skills/handoff-brief-generator/github.svg" alt="Measured on agentmods" height="20"></a>

Or the 80×15 button, for a site that already has a row of RSS and ATOM ones. Only the verdict fits; the numbers stay here.

agentmods 80×15 button for handoff-brief-generator

Your own site · 80×15
<a href="https://agentmods.dev/skills/microsoft/dataverse-business-skills/handoff-brief-generator"><img src="https://agentmods.dev/badge/skills/microsoft/dataverse-business-skills/handoff-brief-generator.svg" alt="Reviewed on agentmods" width="80" height="20"></a>
Per session 83 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.
When invoked 4,539 The whole file, excluding the scripts and references it only reads on demand.
Security scan A 0 findings. A grade says what 26 rules found in the file — not that it is safe.
Origin original No closer match found in the catalogue.
Token cost

What it costs to keep this loaded

Counted locally with the o200k_base tokenizer, which is exact for GPT models; Claude uses its own tokenizer and its counts differ. Treat this as one consistent yardstick across the catalogue rather than a bill. Prices are per million input tokens.

ModelPer sessionOnce invoked
Fable 5.1 $0.00083 $0.04539
Opus 5 $0.00042 $0.02269
Sonnet 5 $0.00017 $0.00908
Haiku 4.5 $0.00008 $0.00454

Measured 12d ago against content hash 2492321a68af, method: parsed. Prices are Anthropic first-party input rates as of 2026-09-12, from the pricing page.

Security

Grade A, and why

handoff-brief-generator scanned grade A with 0 findings against 26 rules in 11 categories — prompt injection, anti-refusal, data exfiltration, privilege escalation, supply chain, agent snooping, system-prompt leakage, SSRF and excessive agency — measured 12d ago.

A static scan of the body, not an audit. Every finding is printed with the line that produced it so you can judge whether it matters here. A mod is markdown that instructs an agent; that is exactly why what it instructs is worth reading.

Nothing flagged

None of the 26 patterns this scan looks for appear in this file: no shell pipes, no recursive deletes, no credential paths, no hidden text, no instruction-override or anti-refusal phrasing, no agent-config snooping. That is not a guarantee, it is the absence of the things that are checkable.

skills/handoff-brief-generator/SKILL.md · 574 lines

How it starts

The opening of the file, as written. The whole thing — 574 lines — stays where its author put it; the contents beside it link to each section on GitHub.

Handoff Brief Generator

When a sales rep goes on vacation or needs to hand off deals temporarily, the backup needs to quickly understand the status of each deal. This skill automatically generates comprehensive handoff briefs from Dataverse data, ensuring smooth coverage and no deals fall through the cracks.

Instructions

Step 1: Identify Handoff Scope

When user says "I'm going on vacation - create a handoff brief for my backup on active deals":

1.1 Get User Context:

  • Identify the sales rep going on vacation (current user or specified)
  • Determine vacation dates (if provided)
  • Identify backup person (if specified)

1.2 Query Active Opportunities:

SELECT opportunityid, name, customerid, accountid, estimatedvalue,
       estimatedclosedate, salesstage, stepname, closeprobability,
       budgetstatus, need, purchasetimeframe, decisionmaker,
       description, currentsituation, customerneed,
       msdyn_forecastcategory, msdyn_opportunityscore,
       createdon, modifiedon, statecode
FROM opportunity
WHERE ownerid = '[user_id]'
AND statecode = 0
ORDER BY estimatedclosedate ASC
Step 2: For Each Opportunity, Gather Context

2.1 Get Account Information:

SELECT accountid, name, telephone1, emailaddress1, 
       address1_city, address1_stateorprovince,
       industrycode, numberofemployees, primarycontactid
FROM account
WHERE accountid = '[opportunity.accountid]'

2.2 Get Key Contacts:

SELECT contactid, fullname, jobtitle, emailaddress1, telephone1,
       mobilephone, accountrolecode, msdyn_decisioninfluencetag
FROM contact
WHERE accountid = '[accountid]'
AND statecode = 0
ORDER BY accountrolecode

2.3 Get Recent Activities (Last 30 Days):

SELECT activityid, activitytypecode, subject, description,
       createdon, actualend, statecode, statuscode
FROM activitypointer
WHERE regardingobjectid = '[opportunityid]'
AND createdon >= '[30_days_ago]'
ORDER BY createdon DESC

2.4 Get Open Tasks:

SELECT activityid, subject, description, scheduledend, 
       prioritycode, statecode, statuscode
FROM task
WHERE regardingobjectid = '[opportunityid]'
AND statecode = 0
ORDER BY scheduledend ASC

Read the full file on GitHub · 574 lines

Changes

What this file has done since we first saw it

Hashed on every crawl. A supply-chain change to an agent config is a question of when, not whether, so the history is kept rather than the latest state alone.

  1. 12d ago First seen · 574 lines · 83 tokens per session scan A 2492321a68af

Subscribe to this mod's changes

handoff-brief-generator is a skill published in the GitHub repository microsoft/dataverse-business-skills (50 stars, last pushed 6mo ago), licensed MIT. It adds 83 tokens to every session and 4,539 once invoked, about $0.0004 per session on Opus 5. A static security scan graded it A with 0 findings. No closer match exists in the catalogue, so it is treated as the original; first seen 2026-08-30.

Related

Other skills, from other repositories