Agent Skills › QuixiAI/Hexis › daily-briefing

daily-briefing

GitHub

每日简报技能，整合日历、目标与待办事项生成结构化晨间摘要。本次更新通过添加别名提升技能发现率，并修复审批门禁漏洞以增强安全性。

skills/installed/daily-briefing/SKILL.md QuixiAI/Hexis

Trigger Scenarios

用户主动请求简报每日首次心跳检查

Install

npx skills add QuixiAI/Hexis --skill daily-briefing -g -y

More Options

Non-standard path

npx skills add https://github.com/QuixiAI/Hexis/tree/main/skills/installed/daily-briefing -g -y

Use without installing

npx skills use QuixiAI/Hexis@daily-briefing

指定 Agent (Claude Code)

npx skills add QuixiAI/Hexis --skill daily-briefing -a claude-code -g -y

安装 repo 全部 skill

npx skills add QuixiAI/Hexis --all -g -y

预览 repo 内 skill

npx skills add QuixiAI/Hexis --list

SKILL.md

Frontmatter

{
    "name": "daily-briefing",
    "aliases": [
        "briefing",
        "brief",
        "today",
        "morning",
        "agenda",
        "day",
        "catch"
    ],
    "category": "productivity",
    "contexts": [
        "heartbeat",
        "chat"
    ],
    "requires": {
        "tools": [
            "recall",
            "calendar_events"
        ]
    },
    "bound_tools": [
        "recall",
        "calendar_events",
        "search_contacts",
        "aggregate_signals"
    ],
    "description": "Compile a comprehensive daily briefing from calendar, contacts, goals, and recent activity"
}

Daily Briefing Compilation

Assemble a structured morning briefing that gives the user a complete picture of their day: schedule, priorities, pending items, and relevant context.

When to Use

During the first heartbeat of the user's active hours (typically morning)
When the user explicitly asks for a briefing ("brief me", "what's on today")
Only once per day -- after generating a briefing, store a working memory noting it was delivered, and skip on subsequent heartbeats

Step-by-Step Methodology

Check if already delivered: Use recall to see if a daily briefing was already generated today. If so, skip unless the user explicitly asks for a refresh.
Pull today's calendar: Call calendar_events for today's date range. Extract meeting times, titles, attendees, and locations.
Enrich meetings: For each meeting, run a lightweight contact lookup and memory recall on attendees and meeting topics. Do not go deep -- this is a summary, not full meeting prep. Delegate to the meeting-prep skill for any meeting the user wants to dive into.
Review active goals: Use recall to surface active goals and their recent progress. Identify which goals have actionable next steps for today.
Check pending items: Recall any action items, promises, or deadlines that fall on or near today. These might come from email digests, prior conversations, or meeting notes.
Aggregate signals: If aggregate_signals is available, pull together any overnight notifications, alerts, or environmental changes worth noting.
Compose the briefing: Structure the output as:
- Schedule: Chronological list of today's events with times and key attendees
- Priorities: Top 3-5 items that need attention today, drawn from goals and pending actions
- Context: Any relevant background (yesterday's outcomes, approaching deadlines, notable signals)
- Suggested focus: A brief recommendation on where to spend energy today
Store and surface: Save the briefing as a working memory with a 24-hour expiry. Queue it for delivery to the user via the outbox.

Quality Guidelines

Keep the briefing to one screenful of text. If the day is packed, prioritize ruthlessly rather than listing everything.
Lead with the most time-sensitive items. A meeting in 30 minutes matters more than a goal due next week.
Use plain, direct language. This is an operational briefing, not a narrative.
If calendar access is unavailable, still produce a briefing from goals and memories -- note that calendar data is missing.
Never fabricate calendar events or action items. If data is sparse, the briefing should be short, not padded.
Respect energy budget. The daily briefing is a valuable but non-trivial operation. If energy is critically low, defer to the next heartbeat.