Agent Skills › QuixiAI/Hexis › meeting-prep

meeting-prep

GitHub

为即将开始的会议生成简报，整合日历详情、参会者背景及历史记忆，提供结构化议程和谈话要点，适用于日常准备或触发式查询。

skills/installed/meeting-prep/SKILL.md QuixiAI/Hexis

Trigger Scenarios

用户询问 upcoming meetings 或要求 prep for next meeting 心跳检测发现30-60分钟内有会议开始每日简报技能委托会议上下文

Install

npx skills add QuixiAI/Hexis --skill meeting-prep -g -y

More Options

Non-standard path

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

Use without installing

npx skills use QuixiAI/Hexis@meeting-prep

指定 Agent (Claude Code)

npx skills add QuixiAI/Hexis --skill meeting-prep -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": "meeting-prep",
    "aliases": [
        "meeting",
        "prep",
        "brief",
        "agenda",
        "attendees",
        "before"
    ],
    "category": "productivity",
    "contexts": [
        "heartbeat",
        "chat"
    ],
    "requires": {
        "env": [
            "GOOGLE_CREDENTIALS_JSON"
        ],
        "tools": [
            "calendar_events",
            "search_contacts",
            "recall"
        ],
        "config": [
            "google_calendar"
        ]
    },
    "bound_tools": [
        "calendar_events",
        "meeting_prep",
        "search_contacts",
        "recall"
    ],
    "description": "Prepare briefings for upcoming calendar events with attendee context and relevant memories"
}

Meeting Preparation Workflow

Compile a briefing for an upcoming meeting by pulling together calendar details, attendee background, relevant memories, and suggested talking points.

When to Use

During heartbeats when a meeting is starting within the next 30-60 minutes
When the user asks "what do I have coming up" or "prep me for my next meeting"
When a daily briefing skill delegates meeting context to this skill
Before any meeting where attendee relationships or prior context would be valuable

Step-by-Step Methodology

Identify the meeting: Use calendar_events to find the next upcoming event (or a specific one if the user named it). Extract the title, time, location/link, and attendee list.
Look up attendees: For each attendee, call search_contacts to pull their name, role, company, and relationship notes. If a contact is unknown, note them as a new face.
Recall prior interactions: Use recall with each attendee's name or company to surface past conversations, decisions, promises, or open items. Focus on the last 30 days of episodic memories.
Recall topic context: If the meeting title or description references a project, product, or topic, run a targeted recall for that subject to gather relevant semantic and strategic memories.
Synthesize the briefing: Combine all gathered context into a structured brief:
- Meeting logistics (time, location, link)
- Attendee profiles and relationship notes
- Key context and recent history
- Open items or promises to follow up on
- Suggested talking points or questions
Deliver or store: In chat context, present the briefing directly. In heartbeat context, store it as a working memory so it surfaces at the right time.

Quality Guidelines

Keep briefings concise. A wall of text defeats the purpose; aim for a scannable format with headers and bullets.
Prioritize actionable context over trivia. "You promised to send them the proposal by Friday" matters more than "they like coffee."
If calendar credentials are unavailable, fall back to asking the user what meeting they want to prepare for.
When attendees are unknown, note this explicitly rather than guessing. Suggest the user add them as contacts.
Respect the energy budget: skip deep recall when energy is low and provide a lighter briefing instead.