Back to Details

wildix-get-conference

Compare original and translation side by side

🇺🇸

Original

English
🇨🇳

Translation

Chinese

Wildix Get Conference

Wildix 获取会议详情

Fetches conference details from 
wda.wildix.com
for one or more conference IDs.
从
wda.wildix.com
获取一个或多个会议ID对应的会议详情。

Peer Skills

关联技能

Before running, check if 
wildix-auth
is installed:
bash
Glob ~/.claude/skills/wildix-auth/SKILL.md
运行前，请检查是否已安装
wildix-auth
：
bash
Glob ~/.claude/skills/wildix-auth/SKILL.md

If missing: npx skills add Wildix/agent-skills --s wildix-auth -y

若缺失：npx skills add Wildix/agent-skills --s wildix-auth -y


See [`peers.yaml`](peers.yaml) for full peer manifest.

完整的关联清单请查看[`peers.yaml`](peers.yaml)。

Input

输入

Conference IDs can be passed as bare IDs or as full x-bees URLs:
  • 340a8cf1-8268-4f5d-a065-585016bc-11_1778230879698
  • https://app.x-bees.com/insights/conferences/340a8cf1-8268-4f5d-a065-585016bc-11_1778230879698
Extract the ID from the URL: everything after the last 
/
.
会议ID可以直接传入裸ID，也可以传入完整的x-bees URL：
  • 340a8cf1-8268-4f5d-a065-585016bc-11_1778230879698
  • https://app.x-bees.com/insights/conferences/340a8cf1-8268-4f5d-a065-585016bc-11_1778230879698
从URL中提取ID：取最后一个
/
之后的所有内容。

Flow

流程

  1. Get IdToken via 
    wildix-auth
    skill (if not already available)
  2. Extract conferenceId(s) from input (strip URL prefix if needed)
  3. Run the script with the conference ID(s)
  4. Display results
  1. 获取IdToken：通过
    wildix-auth
    技能（如果尚未获取）
  2. 提取conferenceId：从输入中提取会议ID（如有需要，去除URL前缀）
  3. 运行脚本：传入会议ID（多个ID可同时传入）
  4. 展示结果

Script

脚本

bash
bash <BASE_DIR>/scripts/get-conference.sh "$ID_TOKEN" <conferenceId> [conferenceId2 ...]
Fetches all IDs in parallel. Returns a JSON array of conference objects sorted by start time.
bash
bash <BASE_DIR>/scripts/get-conference.sh "$ID_TOKEN" <conferenceId> [conferenceId2 ...]
并行获取所有ID对应的会议信息。返回按开始时间排序的会议对象JSON数组。

Output fields

输出字段

FieldDescription
id
Conference ID
subject
Channel/topic name
startTime
Unix ms timestamp
durationMs
Duration in milliseconds
status
COMPLETED
, 
IN_PROGRESS
, etc.
participants[].name
Participant display name (deduplicated)
participants[].email
Participant email
participants[].xbsId
x-bees user ID (matches Stream user ID)
participants[].speakDurationMs
Speaking time in ms
transcriptionStatus
AVAILABLE
, 
PENDING
, 
NONE
transcriptionLanguage
e.g. 
ru-RU
hasRecording
true
/ 
false
insights.brief.title
AI-generated meeting title
insights.brief.shortSummary
Short summary of the conversation
insights.highlights_internal.topics
List of topics discussed
insights.highlights_internal.decisions
Decisions made
insights.highlights_internal.progress
Progress / what was done
insights.highlights_internal.issues
Issues identified
Insights are only present if 
status: "SUCCEEDED"
and fields are non-empty.
字段描述
id
会议ID
subject
频道/主题名称
startTime
Unix毫秒时间戳
durationMs
会议时长（毫秒）
status
会议状态：
COMPLETED
、
IN_PROGRESS
等
participants[].name
参会者显示名称（已去重）
participants[].email
参会者邮箱
participants[].xbsId
x-bees用户ID（与Stream用户ID匹配）
participants[].speakDurationMs
发言时长（毫秒）
transcriptionStatus
转录状态：
AVAILABLE
、
PENDING
、
NONE
transcriptionLanguage
转录语言，例如
ru-RU
hasRecording
是否有录制：
true
/ 
false
insights.brief.title
AI生成的会议标题
insights.brief.shortSummary
对话简短摘要
insights.highlights_internal.topics
讨论主题列表
insights.highlights_internal.decisions
达成的决策
insights.highlights_internal.progress
进展/已完成事项
insights.highlights_internal.issues
识别出的问题
仅当
status: "SUCCEEDED"
且对应字段非空时，才会返回Insights相关内容。

Display format

展示格式

For each conference with insights:
undefined
对于包含Insights的会议：
undefined

HH:MM — "Title from insights or subject" (Xm)

HH:MM — "Insights生成的标题或会议主题"（X分钟）

Participants: Name1, Name2, ... 🎙 Transcription: AVAILABLE | 🎬 Recording: yes/no
Summary: <shortSummary>
Topics: bullet list Decisions: bullet list Issues: bullet list (if non-empty)

For conferences without insights: show just time, subject, duration, participants.
参会者：Name1, Name2, ... 🎙 转录状态：AVAILABLE | 🎬 是否录制：是/否
摘要： <shortSummary>
讨论主题： 项目符号列表 达成决策： 项目符号列表 识别问题： 项目符号列表（非空时显示）

对于不包含Insights的会议：仅显示时间、主题、时长、参会者。

Obsidian save format

Obsidian保存格式

When saving a conference to Obsidian, use YAML frontmatter followed by metadata and sections:
markdown
---
title: <insights.brief.title or subject — strip any colons>
source: https://app.x-bees.com/insights/conferences/<conferenceId>
ticket: https://wildix.atlassian.net/browse/<TICKET>  # only if subject contains a Jira ticket like WMS-1234; omit if none
channel: <subject — strip any colons>
created: <YYYY-MM-DDTHH:MM>
description: <insights.brief.shortSummary — one sentence>
language: <transcriptionLanguage>
duration: <duration in minutes>
members:
  - <participants[0].name>
tags:
  - <tag1 from topics>
---
将会议信息保存到Obsidian时，需使用YAML前置元数据，后跟元数据和各个章节：
markdown
---
title: <insights.brief.title或会议主题 — 移除所有冒号>
source: https://app.x-bees.com/insights/conferences/<conferenceId>
ticket: https://wildix.atlassian.net/browse/<TICKET>  # 仅当主题中包含Jira工单（如WMS-1234）时添加；无则省略
channel: <会议主题 — 移除所有冒号>
created: <YYYY-MM-DDTHH:MM>
description: <insights.brief.shortSummary — 一句话摘要>
language: <transcriptionLanguage>
duration: <会议时长（分钟）>
members:
  - <participants[0].name>
tags:
  - <从topics中提取的标签1>
---

Short summary

简短摘要

<shortSummary>
<shortSummary>

Topics

讨论主题

  • topic1
  • topic1

Progress

进展情况

  • progress1
  • progress1

Issues

问题列表

  • issue1
  • issue1

Decisions

决策事项

  • decision1

File path: `wildix meetings/YYYY-MM/<YYYY-MM-DD> <title>.md`

Tags: extract 3–6 keywords from `highlights_internal.topics`. Tags must not contain spaces — replace spaces with hyphens.

**Ticket extraction:** scan `subject` for Jira-style ticket IDs using pattern `[A-Z]+-\d+`. If found, add `ticket` field. Omit entirely if no ticket found.

**YAML values must not contain colons** — strip or replace any `:` in scalar fields before writing.
  • decision1

文件路径：`wildix meetings/YYYY-MM/<YYYY-MM-DD> <title>.md`

标签：从`highlights_internal.topics`中提取3–6个关键词。标签不能包含空格，需将空格替换为连字符。

**工单提取规则：** 扫描`subject`字段，查找Jira格式的工单ID（匹配模式`[A-Z]+-\d+`）。如果找到，添加`ticket`字段；未找到则完全省略该字段。

**YAML值注意事项：** 标量字段中不能包含冒号，写入前需移除或替换所有`:`。