Daily Briefing
Prioritizes the sales day from meetings, deals, messages, and next actions.
- Skill Road
- Daily Briefing
Categories
Daily Briefing is an official Anthropic sales skill from the public knowledge-work-plugins repository. Its direct primary source is https://github.com/anthropics/knowledge-work-plugins/tree/main/sales/skills/daily-briefing. According to the provider, the skill starts the workday with a prioritized sales briefing and can work either from information supplied by a person or from approved connections to a calendar, CRM, email, and enrichment sources. It is a Markdown-based instruction set for a compatible Claude workflow, not an independent CRM, calendar service, or automatic messaging service.
Purpose and audience
The skill is intended for sales representatives, account executives, sales development representatives, and managers who need to see quickly which meetings, opportunities, and unanswered messages deserve attention first. The source gives triggers such as morning briefing, daily brief, what is on my plate today, prep my day, or start my day. The exact language may vary in the selected Claude product, while the purpose remains the same: turn scattered daily context into a short, scannable, action-oriented overview. According to the provider, the output is designed for a quick review and does not replace detailed preparation for a particular customer conversation.
Standalone use and connectors
The core workflow works without connectors. A person can provide today's meetings, important deals, urgent issues, and weekly priorities as text or as a pasted calendar excerpt. The skill organizes that context, recommends a main priority, and proposes the most useful next actions. With approved connections, a compatible Claude workflow can, according to the provider, also include calendar meetings with attendees and context, open pipeline, deals approaching their close date, overdue or stale tasks, and unanswered messages from relevant accounts. Optional enrichment may add signals about funding, hiring, or news. Availability depends on the product environment, configured connectors, and actual permissions; the skill itself does not grant access.
Briefing structure
The documented output begins with the number one priority and may then show daily numbers, meetings, pipeline alerts, email priorities, and suggested actions. For meetings it can present time, company, attendees, context, and a short preparation step. For pipeline work it can collect deals that need attention, deals closing soon, stage, alert, and the next action. The source also describes a shorter mode for a rapid overview and an end-of-day mode that records completed meetings, pipeline changes, tomorrow's focus, and open loops. Detailed preparation for one particular conversation belongs to the related Call Prep skill rather than to the core scope of this entry.
Prioritization and boundaries
The source describes a ranking that considers urgent closing opportunities, important meetings, unanswered messages from decision makers, deals closing soon, inactive opportunities, and later tasks. This ranking is a useful heuristic, not an objective revenue forecast. Amounts, close dates, deal stages, and contact information must be checked before any external action. A briefing can be only as complete as its inputs and accessible data sources. Without a calendar or CRM, numbers and automatic alerts may be unavailable; the skill should then work with the context explicitly supplied instead of inventing missing facts.
E-E-A-T, privacy, and security
Anthropic is the provider of the published workflow; professional responsibility for priorities, customer statements, and decisions remains with the sales team. Calendar, CRM, and email content can include personal, confidential, or business-critical information. Before connecting a source, review permissions, data minimization, retention, tenant separation, and internal approval. A local skill document does not automatically mean local model processing, because the chosen Claude client may transmit content to its model provider. Passwords, tokens, and secrets do not belong in prompts, skill files, or stored examples. The skill supplies orientation and drafts, while people must control recipients, deadlines, amounts, and external actions. The repository identifies Apache-2.0 as its license. This classification was checked on September 9, 2026 against the official source and complementary Anthropic documentation at https://docs.anthropic.com/.
- Provider
- Anthropic
- License
- Apache-2.0
- Last reviewed
- 09.09.2026
Repository and documentation
Categories
Compatible with
Related guides
Guides and background related to this entry.
Set up the monday.com MCP Server
Start Set up the monday.com MCP Server with minimal permissions and verified data flow.
20.09.2026
Setting up the Financial Statements Skill: Analyze balance sheets via AI
The Financial Statements Skill calculates ratios from statements. This guide explains input quality, review, and limits.
18.09.2026
Set up Granola MCP Server
Connect the official Granola Remote MCP via OAuth and safely query meeting notes from AI clients.
18.09.2026
Setting up the Google Sheets MCP Server
Step-by-step instructions to create Google Cloud credentials and set up the Google Sheets MCP Server locally.
18.09.2026