Fetches daily-briefing from anthropics/knowledge-work-plugins and configures it for Cursor.
3
Select Cursor when prompted
The CLI shows a list of agents. Use arrow keys and space to select Cursor:
◆ Which agents do you want to install to?
│
│ ── Universal (.agents/skills) ────────────────
│ · Cline · Codex · Goose · Windsurf
│ ●Cursor(selected)
│ · Cursor · Aider · Continue
4
Verify installation
Confirm successful installation by checking the skill directory location:
.cursor/skills/daily-briefing
Restart Cursor to activate daily-briefing. Access via /daily-briefing in your agent's command palette.
⚠
Security Notice
We perform automated surface-level scans (Gen AI Scanner, Socket, Snyk) during installation. These checks detect common vulnerabilities but do not guarantee complete security. Always review skill source code and verify the publisher's reputation before production use.
Skills execute code in your environment. Always review source, verify the publisher, and test in isolation before production.
Get a clear view of what matters most today. This skill works with whatever you tell me, and gets richer when you connect your tools.
How It Works
┌─────────────────────────────────────────────────────────────────┐
│ DAILY BRIEFING │
├─────────────────────────────────────────────────────────────────┤
│ ALWAYS (works standalone) │
│ ✓ You tell me: today's meetings, key deals, priorities │
│ ✓ I organize: prioritized action plan for your day │
│ ✓ Output: scannable 2-minute briefing │
├─────────────────────────────────────────────────────────────────┤
│ SUPERCHARGED (when you connect your tools) │
│ + Calendar: auto-pull today's meetings with attendees │
│ + CRM: pipeline alerts, tasks, deal health │
│ + Email: unread from key accounts, waiting on replies │
│ + Enrichment: overnight signals on your accounts │
└─────────────────────────────────────────────────────────────────┘
Getting Started
When you run this skill, I'll ask for what I need:
If no calendar connected:
"What meetings do you have today? (Just paste your calendar or list them)"
If no CRM connected:
"What deals are you focused on this week? Any that need attention?"
If you have connectors:
I'll pull everything automatically and just show you the briefing.
Connectors (Optional)
Connect your tools to supercharge this skill:
Connector
What It Adds
Calendar
Today's meetings with attendees, times, and context
CRM
Open pipeline, deals closing soon, overdue tasks, stale deals
Email
Unread from opportunity contacts, emails waiting on replies
Enrichment
Overnight signals: funding, hiring, news on your accounts
No connectors? No problem. Tell me your meetings and deals, and I'll create your briefing.
Output Format
# Daily Briefing | [Day, Month Date]---## #1 Priority**[Most important thing to do today]**[Why it matters and what to do about it]
---## Today's Numbers| Open Pipeline | Closing This Month | Meetings Today | Action Items ||---------------|-------------------|----------------|--------------|| $[X] | $[X] | [N] | [N] |---## Today's Meetings### [Time] — [Company] ([Meeting Type])**Attendees:** [Names]
**Context:** [One-line: deal status, last touch, what's at stake]
**Prep:** [Quick action before this meeting]
### [Time] — [Company] ([Meeting Type])**Attendees:** [Names]
**Context:** [One-line context]
**Prep:** [Quick action]
*Run `call-prep [company]` for detailed meeting prep*---## Pipeline Alerts### Needs Attention| Deal | Stage | Amount | Alert | Action ||------|-------|--------|-------|--------|| [Deal] | [Stage] | $[X] | [Why flagged] | [What to do] |### Closing This Week| Deal | Close Date | Amount | Confidence | Blocker ||------|------------|--------|------------|---------|| [Deal] | [Date] | $[X] | [H/M/L] | [If any] |---## Email Priorities### Needs Response| From | Subject | Received ||------|---------|----------|| [Name @ Company] | [Subject] | [Time] |### Waiting On Reply| To | Subject | Sent | Days Waiting ||----|---------|------|--------------|| [Name @ Company] | [Subject] | [Date] | [N] |---## Suggested Actions1.**[Action]** — [Why now]
2.**[Action]** — [Why now]
3.**[Action]** — [Why now]
---*Run `call-prep [company]` before your meetings**Run `call-follow-up` after each call*
Execution Flow
Step 1: Gather Context
If connectors available:
1. Calendar → Get today's events
- Filter to external meetings (non-company attendees)
- Pull: time, title, attendees, description
2. CRM → Query your pipeline
- Open opportunities owned by you
- Flag: closing this week, no activity 7+ days, slipped dates
- Get: overdue tasks, upcoming tasks
3. Email → Check priority messages
- Unread from opportunity contact domains
- Sent messages with no reply (3+ days)
4. Enrichment → Check signals (if available)
- Funding, hiring, news on open accounts
If no connectors:
Ask user:
1. "What meetings do you have today?"
2. "What deals are you focused on? Any closing soon or needing attention?"
3. "Anything urgent I should know about?"
Work with whatever they provide.
Step 2: Prioritize
Priority ranking:
1. URGENT: Deal closing today/tomorrow not yet won
2. HIGH: Meeting today with high-value opportunity
3. HIGH: Unread email from decision-maker
4. MEDIUM: Deal closing this week
5. MEDIUM: Stale deal (7+ days no activity)
6. LOW: Tasks due this week
Select #1 Priority:
- If meeting with >$50K deal today → prep that
- If deal closing today → focus on close
- If urgent email from buyer → respond first
- Else → highest-value stale deal
Step 3: Generate Briefing
Assemble sections based on available data:
1. #1 Priority — Always include (even if simple)
2. Today's Numbers — If CRM connected, otherwise skip
3. Today's Meetings — From calendar or user input
4. Pipeline Alerts — If CRM connected
5. Email Priorities — If email connected
6. Suggested Actions — Always include top 3 actions
Quick Mode
Say "quick brief" or "tldr my day" for abbreviated version:
Say "wrap up my day" or "end of day summary" after your last meeting:
# End of Day | [Date]**Completed:**- [Meeting 1] — [Outcome]
- [Meeting 2] — [Outcome]
**Pipeline Changes:**- [Deal] moved to [Stage]
Implementation Guide
Prerequisites
›Claude Desktop or compatible AI client with skill support
›Clear understanding of task or problem to solve
›Willingness to iterate and refine outputs
Time Estimate
15-45 minutes depending on use case complexity
Steps
1Install skill using provided installation command
2Test with simple use case relevant to your work
3Evaluate output quality and relevance
4Iterate on prompts to improve results
5Integrate into regular workflow if valuable
Common Pitfalls
⚠Expecting perfect results without iteration
⚠Not providing enough context in prompts
⚠Using skill for tasks outside its intended scope
⚠Accepting outputs without review and validation
Best Practices
✓ Do
+Start with clear, specific prompts
+Provide relevant context and constraints
+Review and refine all outputs before using
+Iterate to improve output quality
+Document successful prompt patterns
✗ Don't
−Don't use without understanding skill limitations
−Don't skip validation of outputs
−Don't share sensitive information in prompts
−Don't expect skill to replace human judgment
💡 Pro Tips
★Be specific about desired format and style
★Ask for multiple options to choose from
★Request explanations to understand reasoning
★Combine AI efficiency with human expertise
When to Use This
✓ Use when
Use when skill capabilities match your task, clear ROI on time saved, and you can validate outputs. Best for repetitive tasks, learning, and quality improvement.
✗ Avoid when
Avoid when task requires deep expertise you can't validate, involves sensitive decisions, or when learning process is more valuable than speed of completion.
Learning Path
1Familiarize yourself with skill capabilities and limitations
2Start with low-risk, non-critical tasks
3Progress to more complex and valuable use cases
4Build expertise through regular use and experimentation
