SKILLEMALL.ai
GitHub ↗ RU Sign in

BC mu-meeting-flow

AI Agent 原生的会议全流程编排 Skill。覆盖会前排期、忙闲查询、会议室预订、日程创建、会前材料生成、会中主持指导、会后纪要提取、TODO 跟踪与知识沉淀。通过可配置适配器对接 Google Calendar、Whisper、Notion、Slack 等工具，零内部依赖，任何 Agent 可用。触发词：meeting flow、会议流程、meeting assistant、会议编排、帮我开个会、预约会议、开会准备、会前材料、会议总结、会议纪要、会后TODO、查忙闲、改期、取消会议、查会议记录、meeting notes、meeting scheduler。不适用：纯任务管理（非会议场景的待办请用专门的任务管理工具）。即使没说 meeting flow，只要提到开会/约会议/会议纪要也要用。

ClawHub Agent Skills author: 木先生iPPT v1.0.3 MIT-0 12 files body ≈ 1 443 tokens Open the sourceclawhub.ai↗ analyzed 3 d ago

AI Agent 原生的会议全流程编排 Skill。覆盖会前排期、忙闲查询、会议室预订、日程创建、会前材料生成、会中主持指导、会后纪要提取、TODO 跟踪与知识沉淀。通过可配置适配器对接 Google Calendar、Whisper、Notion、Slack 等工具，零内部依赖，任何 Agent…

As a process C 53/100 · Has gaps — weak spots: result and completion, when it triggers, inputs and preconditions

ProcedureNotionSlackPersonal productivityAI and agentstype and topics are labelled automatically from the skill text
Runs in: OpenClaw Claude / Claude Code ChatGPT / Codex Gemini CLI Cursor GitHub Copilot / VS Code Qwen Code Kimi Code CLI Z.ai (GLM) DeepSeek (Deep Code) Mistral Vibe LangChain (deepagents) Goose OpenCode
JSON
Technical rating
B
88/100
safety, quality, tests
Safety 60%
99
Quality 40%
71
Run on models
none yet
Process rating
C
53/100
Has gaps
Result and completion w 14
0
Inputs and preconditions w 11
0
Failures and branches w 10
0
the three weakest of ten parameters · all ten

How to improve

  1. Say in the description WHEN to use the skill ("use when…", example requests): that is the agent's main cue.
For the model run — optional
  • Your own cases (evals/evals.json, 4–6 real requests with expected answers): the full check would then run those instead of a model-drafted suite.
  • A spec.yaml with trigger phrases and assertions — a behaviour contract for CI; `skilltest init` writes a template.

Guard findings · 1

✓ No critical or high findings

Medium and low: 1
  • low Exfiltration exfil-webhook-url config/adapters.example.json:19
    Webhook / callback URL commonly used for exfiltration (verify the destination) (test fixture / example file; the skill's own vendor host; quoted — discussed, not commanded)
    "webhook_url": "https://hooks.slack.com/services/your/webhook/url"
    fixturevendor-hostquoted

Files scanned: 12. Evidence is masked. Grey chips explain why severity was lowered.

Against the Agent Skills spec

  • warning description-no-when description does not say WHEN to use the skill (no "use when")
  • note frontmatter-key unknown frontmatter key "display_name"

Process rating: all ten parameters 53/100

  • 0Result and completion. Does not say what the result is
  • 0Inputs and preconditions. Does not say what the process needs to start
  • 0Failures and branches. Linear process with no failure handling
  • 0Progress reporting. Says nothing while it works
  • 20When it triggers. No condition that starts the skill
  • 100Tools and files. No external tools needed
  • 100Steps. 11 steps
  • 100Consistency. Name and required fields are in place
  • 100Execution cost. Instruction body is 1443 tokens
  • 100Running it twice. No mutating operations
  • low 10 top-level sections: this looks like several domains in one skill

Everything here is measured from the skill text rather than judged by a model, so the numbers are checkable. A parameter weighs more when it is a more common reason for the process to stall.

Quality signals

  • +5Description has no quoted example phrases that should trigger the skill
  • +4Description does not say when NOT to use the skill (false activations)
  • +3Output format is not stated: the model decides each time
  • -5TODO / placeholder text left in the skill
  • +2Single-language instructions
  • +3Description length 354: enough signal without eating the budget
  • +4Structure: 16 headings
  • +3Step-by-step instructions: 11 items
  • +4Has examples (2 code blocks)
  • +4Reference files are cited in the instructions (4 of 4)
  • +1License stated

Quality base 70; lint remarks subtract, signals add up to 100. Result: 71.

External checks

ClawHub: suspicious
This meeting automation skill is not malicious, but it needs Review because it can automatically use calendars, meeting records, documents, notifications, and persistent TODO data with broad triggers and limited consent controls.
LLM: suspicious (high) · 3 Sept 2026