编程

Meeting

试用

Orchestrate meeting preparation, capture, and commitment tracking with draft-first confirmation

它能做什么

**Meetings are expensive. Execution is rare.** This skill is a diagnostic and orchestration engine. It treats every meeting as a tactical event with a lifecycle. It identifies the "Gaps" in your coordination and ensures that no decision is lost in the noise.

技能文档

Meeting — The Execution Operator

Meetings are expensive. Execution is rare. This skill is a diagnostic and orchestration engine. It treats every meeting as a tactical event with a lifecycle. It identifies the "Gaps" in your coordination and ensures that no decision is lost in the noise.


🧩 Access & Engineering Model

This skill is an instruction-only advisory engine.

  • No Invisible Recording: This skill does not autonomously start recording meetings. It only processes calendar context, user-provided fragments, or transcripts already available through the host platform.
  • Connector Dependency: It relies on the host platform's connectors (Lark, Outlook, Google Workspace) for data retrieval and distribution.
  • Draft-First Principle: By default, all outputs (minutes, task assignments, emails) are prepared as Drafts. No distribution occurs without explicit user authorization.
  • Persistence Boundary: Commitment tracking is performed via the host's task system. If no persistent storage is available, the skill reverts to a "Structured Follow-up Plan" stored in local conversation context.

What This Skill Does NOT Do

  • It does not autonomously start audio or video recording.
  • It does not distribute minutes or create tasks without user authorization.
  • It does not guarantee persistent tracking unless the host platform provides task/reminder storage.
  • It does not access data outside the permissions granted by the host platform connectors.

🛠️ The Coordination Diagnosis Layer (Internal Logic)

Before every meeting phase, the operator diagnoses the likely failure point:

  1. Preparation Gap: Attendees are entering the room with zero context.
  2. Capture Gap: High-stakes decisions are being made but not anchored.
  3. Follow-through Gap: Tasks are assigned but drift into the "memory void."
  4. Repeat Meeting Syndrome: The same topic is discussed across multiple sessions without resolution.
  5. Load Problem: The cost of the meeting (time * people) exceeds the likely output value.

⚙️ Operating Modes

Mode 1: Brief & Draft (Default / Read-Only)

  • Focus: Preparation and synthesis.
  • Behavior: Prepares briefs, captures notes, generates minutes.
  • Constraint: No external writing. Everything stays in the chat.

Mode 2: Distribute & Track (Authorized)

  • Focus: Execution and accountability.
  • Behavior: Distributes minutes to attendees, creates tasks in the system, and nudges owners.
  • Trigger: Requires user to say "Distribute these minutes" or "Sync these tasks."

The Meeting Lifecycle

1. Pre-Meeting: Intelligence Briefing

Instead of a simple reminder, the operator identifies the Preparation Gap:

  • Stakeholder Context: Who is in the room? What are their recent wins/blocks?
  • Prior Commitments: What was promised in the last session? Is it done?
  • Success Criteria: 3-5 specific questions that must be answered to justify this meeting's ROI.

2. In-Meeting: Fragment Capture

The operator bridges the Capture Gap without being a distraction:

  • Use short "fragments" to anchor high-velocity decisions.
  • Example: "Sarah: Budget 20k approved" -> Captured as a Decision.
  • Example: "Tom: Needs Legal review by Fri" -> Captured as an Action Item.

3. Post-Meeting: The 62-Second Synthesis

Immediately closes the Follow-through Gap with a structured output:

  • Executive Summary: 30-second brief for the busy stakeholder.
  • Decisions: Explicitly recorded (Who, Why, When).
  • Dissent Tracking: Capturing "Tom disagreed because..." to prevent history rewriting.

4. Tracking: Institutional Memory

Resolves Repeat Meeting Syndrome:

  • Identifies if an agenda item has appeared in >3 meetings without resolution.
  • Tracks every action item until it is marked "Complete" in the host's system.
  • If a deadline is missed, prepares a "Tactful Nudge" draft for the user to review.

📋 Standard Output: THE ASSESSMENT

Every response must follow this diagnostic structure:

🔍 MEETING EXECUTION DIAGNOSIS

  • Type: [Decision / Review / Sync / 1:1]
  • Primary Gap: [e.g., Preparation Gap - No agenda found]
  • ROI Rating: [Estimated output vs time cost]

📝 EXECUTION PACKAGE

[Brief / Minutes / Draft Actions]

⚠️ RISK & RED-LINES

  • [Decision ambiguity that needs confirmation]
  • [Sensitive dissent that should not be auto-distributed]
  • [Upcoming deadline risks]

Privacy & Safety

All meeting intelligence is stored within your private agent memory. This skill does not autonomously start recording meetings. It only processes calendar context, user-provided fragments, or transcripts already available through the host platform.

相关技能

按用户明确指令,在得到大脑(Get笔记)中保存、搜索并管理笔记与知识库。

作者 iswalle763 次安装66 星标

figma-use

官方

通过 `use_figma` MCP 工具执行 Figma 插件 API 脚本所需的规则与参考。

作者 OpenAI27.6k 星标

依据微软当前官方文档,按需加载参考,给出 ASP.NET Core 应用模型、管道与代码组织建议。

作者 OpenAI27.6k 星标

提供一套引导式流程,配合定量基准,帮你起草、测试并迭代改进 Claude skill。

作者 Anthropic177.6k 星标

根据 API 文档、SDK、curl 示例或现有脚本,生成可安装、可组合的命令行工具。

作者 OpenAI27.6k 星标

用 p5.js 生成算法艺术,产出可书写的创作宣言和参数可调的交互式查看器。

作者 Anthropic177.6k 星标

AGIsearch 的更多技能

浏览全部技能

Remove AI-sounding patterns from generated text

作者 B*T

Data analysis and visualization. Query databases, generate reports, automate spreadsheets, and turn raw data into clear, actionable insights. Use when (1) yo...

作者 Iván2 次安装

用一份 JSON 描述就能生成标准可编辑的 PPTX,自带 11 种版式与 5 套配色。

作者 ToBeWin1 次安装

Meta-skill for AI agent self-improvement. Analyzes runtime logs to detect error patterns, regressions, and inefficiencies, then generates structured improvem...

作者 claw0x

Review code on two axes — Standards (code quality) and Spec (requirements alignment). Supports multi-agent parallel review, visual review, and file-based handoffs.

作者 wpank

Design and output n8n workflow JSON with robust triggers, idempotency, error handling, and human-...

作者 KOwl64