daily-brief
Build a morning brief from Littlebird activity and meetings. Use for today's commitments, changes, and one priority. Read README.md for the guide map.
Mario Aldayuz / Littlebird · 已有静态检查记录
安装与使用
运行命令前先阅读来源与依赖说明。复制命令不会自动安装或执行。
npx skills add legioncodeinc/vibe-coding-tools --skill daily-brief技能说明
name: daily-brief description: "Build a morning brief from Littlebird activity and meetings. Use for today's commitments, changes, and one priority. Read README.md for the guide map." license: AGPL-3.0-or-later compatibility: Claude Cowork, Claude Code 2.1 or newer, Cursor 2.4 or newer, Codex metadata: hive-tier: standalone version: "1.0.0" author: "Mario Aldayuz / Littlebird" requires: "Littlebird MCP (Power or Pro plan)"
Daily brief
Purpose
One screen every morning covering the whole day: the schedule compressed, the commitments actually due, what went cold, the unread threads that genuinely need a reply, the one highest-leverage thing to do, and what changed since yesterday.
This skill is designed around a single constraint, and the constraint is honest: daily digests are the most-abandoned category of recurring automation there is. A brief that restates the calendar is deleted within a week. Daily is the hardest cadence to sustain, and the archive says so directly: daily sending is where fatigue "shows up most clearly", and a daily cadence "raises the bar significantly" for content quality [references/research/distilled-daily-brief-design.md]. Two of the three top unsubscribe reasons, lost interest and irrelevant content, are the same failure at different distances: the digest stopped saying anything about the reader's actual situation [references/research/distilled-daily-brief-design.md].
So every design decision in this skill exists to earn the open again the next day. The length ceiling, the quiet-day rule, the precision bar, the mandatory delta field, and the defended one thing are all the same mechanism seen from different sides.
This skill owns the whole-day view. It does not own per-meeting depth. That is
pre-call-prep, and daily-brief points at it rather than inlining it.
Capability gate
This skill requires the Littlebird MCP on a Power or Pro plan.
Before anything else:
- List the tools actually available in this session. Do not assume tool names. Confirm
that the meeting tools, the routine tools, and
search_user_contextare present under their real names. - If the Littlebird MCP is not connected, stop and tell the user: "This skill needs the Littlebird MCP connected on a Power or Pro plan. Connect it at https://support.littlebird.ai/docs/mcp/ and run this again."
- If the meeting tools are present but the routine tools are missing, run on-demand mode only and say the routine cannot be created from this session.
- Before creating the routine, call
LB_INTERNAL_GET_SUBSCRIPTION_STATUSto confirm the plan allows another routine. Routine count is plan-limited, so if the account is at its limit, name which existing routine should be replaced rather than proposing an addition [references/littlebird-mcp-reference.md].
Tool mechanics, parameters, and return shapes: references/littlebird-mcp-reference.md.
Littlebird MCP calls used
| Tool | Used for |
|---|---|
LB_INTERNAL_GET_ROUTINE_REPORTS | Own memory, and the sibling rollup. Both are mandatory. |
LB_INTERNAL_LIST_ROUTINES | Discovering which sibling routines exist and whether their reports are fresh |
LB_INTERNAL_LIST_MEETINGS | Today's calendar, via a future end_date. Also recent recorded meetings for due Action Items |
LB_INTERNAL_GET_MEETING | The ## Action Items and ## For You sections of recent meetings, which already carry owner attribution |
search_user_context | Direct asks and waiting language with data_source: messages, and yesterday's activity with data_source: summaries |
LB_INTERNAL_GET_SUBSCRIPTION_STATUS | The plan and routine-slot check before creating the routine |
LB_INTERNAL_CREATE_ROUTINE | Creating the daily routine, from an interactive session only |
LB_INTERNAL_GET_ROUTINE_CONFIG and LB_INTERNAL_UPDATE_ROUTINE | Changing the routine later. Read the config first, because prompt and schedule each replace the whole field |
Never used by this skill: LB_INTERNAL_GET_MEETING_TRANSCRIPT. A daily brief has no budget
for transcript reading, and the structured summary carries better attribution anyway
[references/littlebird-mcp-reference.md].
Trigger
Trigger phrases: morning brief, daily digest, brief me on my day, what's on today, start my day, daily rundown, what do I need to know today, what changed since yesterday, what should I do first, set up my morning brief.
Do not trigger for: a single upcoming meeting (that is pre-call-prep), a full commitment
ledger (that is commitment-tracker), or a per-client risk view (that is
client-health-radar).
Routine cadence
Daily. Primary mode.
The timing position, taken deliberately: morning-of, roughly 45 minutes before the user's first real decision of the day. Not the night before.
The reasoning, and the honest limits of it:
- The load-bearing field is what changed since yesterday. A night-before brief structurally cannot see the overnight window, which is where a large share of the delta comes from. Generating before the last hours of signal damages the exact field that earns the open.
- Within-session decision quality degrades modestly, so a hard decision is better surfaced before the session starts. Adjusted odds of an inappropriate prescription rose to 1.26 by the fourth hour of a clinic session, P less than .001 for trend [references/research/distilled-daily-brief-design.md]. That is a real, measured, modest effect. The far more famous parole result that would have supported a stronger claim is largely a statistical artifact, and this skill does not lean on it [references/research/distilled-daily-brief-design.md].
- The night-before slot is already taken, and correctly so.
pre-call-prepruns in the evening because a per-meeting brief needs slack to fix a forgotten commitment before the call. Two routines, two times, one reason each. That is composition,