Agent Skills › QuixiAI/Hexis › meeting-follow-up

meeting-follow-up

GitHub

将会议记录转化为摘要、行动项及跟进邮件草稿，确保准确性并需用户确认后再执行创建或发送操作。

skills/installed/meeting-follow-up/SKILL.md QuixiAI/Hexis

Trigger Scenarios

整理已完成会议的记录和待办事项根据会议内容生成跟进邮件草稿

Install

npx skills add QuixiAI/Hexis --skill meeting-follow-up -g -y

More Options

Non-standard path

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

Use without installing

npx skills use QuixiAI/Hexis@meeting-follow-up

指定 Agent (Claude Code)

npx skills add QuixiAI/Hexis --skill meeting-follow-up -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-follow-up",
    "aliases": [
        "followup",
        "recap",
        "minutes",
        "decisions",
        "action-items"
    ],
    "category": "productivity",
    "contexts": [
        "chat"
    ],
    "requires": {
        "tools": [
            "recall"
        ]
    },
    "bound_tools": [
        "calendar_events",
        "email_search",
        "email_read",
        "search_contacts",
        "recall",
        "remember",
        "manage_backlog",
        "gmail_reply",
        "gmail_send",
        "email_send",
        "fathom_transcripts",
        "fathom_ingest",
        "todoist_create_task",
        "asana_list_projects",
        "asana_create_task"
    ],
    "description": "Turn completed meetings into an accurate recap, owned actions, and user-approved follow-up drafts"
}

Meeting Follow-up

Convert evidence from a completed meeting into a concise record and a controlled set of next actions. Use meeting-prep for work before a meeting.

Workflow

Identify the meeting. Use the user's wording and calendar details to confirm the event, date, and attendees. If the match is ambiguous, show likely events instead of choosing silently.
Choose the source. Prefer notes or a transcript supplied by the user. If Fathom is available, list likely recordings and let the user identify the right one before ingesting it. Calendar metadata alone is not evidence of what was discussed.
Extract outcomes. Separate decisions, commitments, action items, owners, due dates, open questions, and topics explicitly deferred. Quote sparingly and preserve uncertainty.
Check context. Use recall and relevant email threads to identify earlier promises or conflicts. Label these as prior context rather than meeting outcomes.
Draft the package. Produce a scannable recap, an owner-by-owner action list, and any requested follow-up email draft. Flag every missing owner or date rather than inventing one.
Confirm mutations. Show proposed memory, backlog, Todoist, or Asana entries before creating them unless the user's request already specified their exact content and destination. Show every outbound message and recipient before sending.
Report completion. Return what was recorded, created, or sent, including anything that failed and the exact retry or manual step.

Control and Failure Boundaries

"Follow up" authorizes analysis and drafting, not sending mail, assigning another person, or creating external tasks without confirmation.
Do not mark a suggestion as a decision, a discussion point as a commitment, or an attendee as an owner without evidence.
Do not ingest a transcript merely because a likely recording exists; ingestion changes local memory and requires a deliberate choice.
When no notes or transcript are available, ask the user for notes or offer a recap template. Never manufacture minutes from the calendar title.