/daily-briefing

name: daily-briefing
description: "Start your day with a prioritized CRM briefing — works for any monday CRM setup: pipeline, contacts, accounts, leads, or no board at all. Use when someone says 'morning briefing', 'daily brief', 'what's on my plate today', 'catch me up on my deals', 'what needs attention', 'what needs my attention', 'anything urgent in my deals', 'what's hot in my pipeline', 'pipeline summary', 'start my day', or 'daily standup prep'."
argument-hint: "[optional: board name or ID, e.g. 'Deals', 'Contacts', or '12345678']"
user-invocable: true
allowed-tools: [Read, AskUserQuestion, mcp__monday__get_user_context, mcp__monday__list_workspaces, mcp__monday__search, mcp__monday__get_board_info, mcp__monday__get_column_type_info, mcp__monday__get_board_items_page, mcp__monday__board_insights, mcp__monday__get_notetaker_meetings, mcp__monday__get_board_activity, mcp__monday__get_updates, mcp__monday__create_update, mcp__monday__create_doc, mcp__monday__create_notification, mcp__monday__list_users_and_teams, mcp__monday__all_monday_api]

Morning Briefing

Produces a daily prioritized briefing over the user's monday CRM data and **publishes it as a monday artifact** — so the brief lives inside monday, not just in the chat.

Works for **any monday CRM setup**: pipeline users get deal buckets and pipeline totals; contacts/accounts users get relationship health and follow-up queues; lead managers get inbound lead status. If the user has no monday CRM board at all, the skill runs in standalone mode — ask for context, produce a useful brief from what they tell you.

When monday CRM features are in use, the brief automatically gets richer:

| monday CRM feature | What it adds | MCP access | |---|---|---| | **Notetaker** | Recent meeting notes matched to open deals or contacts | `get_notetaker_meetings` | | **Activity log** | Logged calls, emails, and meetings on deals/contacts (last 48h) | `get_board_activity` + `get_updates` | | **Tasks / follow-ups** | Items with a date column = today across deals or contacts board | `get_board_items_page` with date filter | | **Calendar sync** (Outlook/Google) | Today's CRM-linked meetings | Not yet in MCP — skipped; wired when available (see workset status.md) | | **Email sync** (Gmail/Outlook) | Tracked email threads on deals/contacts | Not yet in MCP — skipped; logged emails accessible today via `get_updates` on contacts/deals |

> monday CRM's calendar and email sync features exist in the product but are not fully exposed via the MCP connector yet. The skill attempts to reach them via `all_monday_api` raw GraphQL. If the data isn't there, it notes the gap in the brief and skips the section — it does not error out.

Flow: **Connector check → Mode → Connector discovery → Board detection → Board type → Data pull → Synthesize → Publish → Share (opt-in) → Proactive (opt-in)**.

Input

• Optional: board name or ID via argument.
• Optional: mode override (Default / Silent / Proactive) via project instructions or one-shot prompt.

Output

• **α (default):** A monday update on a pinned "My Morning" item OR a new doc in the user's personal workspace, titled `Morning Briefing — <weekday>, <Mon DD>`. Body carries the `Generated by Claude` footer + an HTML comment `<!-- claude-skill-id: daily-briefing -->` for idempotency. Markdown brief printed in chat as a mirror.
• **β (Share mode, opt-in):** Notification to manager + update on team-rollup board.
• **Proactive extension (opt-in):** Per-item `create_update` on stalled records; `create_notification` for commitments due today.
• **Standalone mode (no board):** Brief printed in chat only — no monday artifact (nothing to publish to).

Knowledge

• Board type detection + synthesis buckets per type (§ Steps 2b and 6).
• Shared artifact conventions (§ Shared patterns).

Tools (MCP)

• `get_user_context` — resolve user + favorite boards.
• `list_workspaces` — enumerate workspaces when search is ambiguous.
• `search` — find CRM boards by broad search terms.
• `get_board_info` — board schema + column IDs + labels.
• `get_column_type_info` — resolve columns by type when names aren't English.
• `get_board_items_page` — pull active records, recently closed, recent activity.
• `board_insights` — aggregate fallback when >200 items.
• `create_update` — publish α to pinned item; proactive nudges on stalled records.
• `create_doc` — publish α as a doc when no pinned item exists.
• `create_notification` — β share; proactive alert for commitments due today.
• `list_users_and_teams` — resolve recipient for β share.
• `all_monday_api` — escape hatch for doc updates / metadata lookups not in wrapped tools.

Cross-skill handoffs

• **To forecast-dashboard:** If briefing surfaces forecast hygiene issues, suggest `/monday-crm:forecast-dashboard`.
• **To board-diagnosis:** If >30% of records are unowned, or core fields missing on most items, suggest `/monday-crm:board-diagnosis`.

---

Step 0: Connector check

**Goal:** Fail fast if the user has no monday MCP connection.

1. Try `mcp__monday__get_user_context`. 2. If the tool is missing, returns auth-style error, or the user has no accessible workspace:

• Print: *"I don't see the monday connector active on this session. Install it from https://monday.com/mcp, then run this skill again."*
• Stop. Do not proceed.

3. If connector works, cache `user.id` and `user.name`.

> **PAUSE**: do not write any `create_*` call before Step 6, and never before Step 0 passes.

---

Step 1: Detect mode and output config

**Goal:** Know write behavior and output preferences before doing anything else.

Write mode

• **Default** — confirm every `create_*` or `change_*` call in chat before executing.
• **Silent** — skip confirmations, stay on α scope.
• **Proactive** — ask **once** at the top of the session: *"Proactive mode will post per-item updates on stalled records and notify you on commitments due today. (a) Approve all, (b) Review each, (c) Deny all?"* Store the