daily-brief

Generates a weekday morning briefing PDF from calendar, email, chat, and ticket data.

Updated Sep 18, 2026
One-click install
npx skills add https://github.com/chatcontract/myproductivity --skill daily-brief-chatcontract
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: daily-brief
Source: https://github.com/chatcontract/myproductivity/tree/main/skills/daily-brief
Command: npx skills add https://github.com/chatcontract/myproductivity --skill daily-brief-chatcontract

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill requires pypdfium2, and includes references (resource) and assets (resource) components.

What problem does it solve? It removes the manual morning routine of checking calendar, inbox, chat, and ticket trackers separately by consolidating everything due, conflicting, or pending into one emailed PDF briefing. ## Core Features & Use Cases - Cross-channel gathering: Reads today's calendar events, unanswered emails, chat mentions, due-date sweeps, and open tracker tickets in one capped batch of tool calls. - Conflict detection and verification: Classifies double-bookings and back-to-back meetings with suggested fixes, and cross-checks each open ask against the user's own sent messages before reporting it as outstanding. - Accountable output: Every actionable item carries a named owner, a deadline, a verified status, and a traceable source, rendered as a two-page-maximum PDF emailed to the user's work mailbox. - Use Case: A manager schedules the skill for 6 AM weekdays and receives a brief listing today's meetings, two scheduling conflicts with suggested fixes, three overdue Jira tickets, and four chat asks verified as still open. ## Quick Start Run /productivity:daily-brief or ask for a daily brief to generate and email today's morning briefing PDF.

Frequently Asked Questions about daily-brief

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I get an automated daily briefing email from my calendar and inbox?

Run /productivity:daily-brief or ask for a daily brief. The skill reads today's calendar, recent email, chat, and tickets, then emails a PDF briefing to your work mailbox. A manual run offers to schedule it for weekday mornings.

How does the daily brief detect meeting conflicts?

It classifies same-day event pairs as hard double-bookings, impossible back-to-backs, or double duty, using event times converted to your local timezone. Every conflict gets a priority-based call plus a suggested fix such as an alternate slot or a regrets note.

What connectors does the daily brief require to run?

Calendar, Mail, and Drive or SharePoint connectors are mandatory; any missing one stops the run with Connect buttons and no output. Chat and ticket trackers like Jira, GitHub, Linear, or Asana are optional and never block the run.

Does the daily brief work on weekends or for dates other than today?

Scheduled runs stop silently on Saturdays and Sundays. Manual runs work any day but only cover today; there is no supported way to brief a different date.

Why does the daily brief report something as Needs confirmation instead of Open?

An item is tagged Needs confirmation when the run could not verify it against the user's own sent mail and chat, or when follow-up searches found no resolution signal. It never guesses a status it did not actually check.

What happens if the daily brief run fails or runs out of time?

A failed run sends one email with the subject prefixed [Failed] and the exact error. If the 13-minute gathering deadline hits, unverified items are tagged Needs confirmation and skipped coverage is named in the Worth double-checking section.