SuperAPI AI Directory
Partner中文AI newsFavorites
Skillsyunqi-agent-discovery

yunqi-agent-discovery

Agents & models

View repository

Updated 10-15 21:40

About this skill

Capability Overview

This skill provides the followingindependent capabilities, which can be used individually or in combination as needed:

Capability Command Purpose Use Case
Query forum/session list qianwen yunqi list forums Get the latest forum (session) information View the agenda and discover sessions to attend
Query exhibitors/exhibition halls/booths qianwen yunqi list exhibitors Query exhibit/booth introductions, exhibition halls, and exhibition area information Understand the exhibition layout and compare exhibitors
Recommend sessions Based on list forums result analysis Filter and recommend suitable sessions based on Agent goals Quickly locate session topics of interest
Compare sessions/exhibitors Based on list forums / list exhibitors result analysis Compare information across multiple sessions and exhibitors/booths Make attendance plans and weigh trade-offs
Conference information Q&A Read this directory 云栖大会会刊.md Answer introductory questions about the conference theme, highlights, exhibition halls, etc. based on the conference program Understand the overall conference
Attendee service Q&A Read this directory 云栖大会参会指南.md Answer attendee service questions about transportation, accommodation, dining, tickets/check-in, etc. based on the attendee guide Trip preparation and attendance arrangements

Before executing capabilities involving forum/exhibition queries (querying lists, recommending sessions, exhibition layout), you must first complete "User Profile Collection".

Pre-check (must be performed first)

Before calling the qianwen yunqi command, you must complete the following two-step check in order:

1. Check whether the CLI is installed and its version

command -v qianwen
  • If the command does not exist (not installed), perform the installation:
npm install -g @qianwenai/qianwen-cli

  • If the command is already installed, run qianwen --version to check the version number:

    • Versionlower than 1.7.0(< 1.7.0), you also need to run the above command to reinstall
    • When the version is not lower than 1.7.0 (≥ 1.7.0), no reinstallation is needed; continue with the subsequent checks

  • After installation/reinstallation is complete, you can run qianwen --version to verify the installation result.

2. Check login status

qianwen auth status
  • If not logged in,prompt the user to run qianwen login to complete login, and continue with subsequent commands only after login succeeds.
  • If already logged in, continue directly with subsequent commands.

Note: Both checks are indispensable; if the checks are not passed, you must not continue calling the qianwen yunqi command.

User Profile Collection (before querying forums/exhibitions)

Before querying forums (list forums) or exhibitions (list exhibitors) for the user, first collect the user profile from the following dimensions, then perform queries and local filtering accordingly:

Dimension Description Example
Role User's occupational identity Developers, architects, product managers, enterprise managers, investors
Industry and technology directions of interest Industries and technology fields of interest AI Coding, Agent, large models, automotive, finance, retail, etc.
Technical depth Preference for technical depth or applied practice Technical depth / applied practice

Collection rules:

  • Dimensions already specified in the user's request are adopted directly without repeated inquiry;
  • Only ask additional questions for missing dimensions that affect query results (ask all at once to avoid multiple rounds of follow-up);
  • After the profile is complete, filter and organize the full query results locally. The mapping relationships are as follows:
Profile dimension Forum local filter field Exhibitor local filter basis
Industries of interest industryList(code table code matching) exhibits[].name / description text matching
Technology direction/interests interestList(code table code matching) Same as above
Technical depth/applied practice technicalLevel(code table code matching) —
Role Used as a reference for sorting and recommendations (e.g., enterprise managers prioritize strategy/industry forums, developers prioritize technical practice sessions) Same as left

For the available values of each profile dimension (industry, interests, technical level, etc.), refer to the corresponding code table in "Data Dictionary (codeschema.json)" below.

Data Dictionary (codeschema.json)

Static file in this skill directory codeschema.json is the data dictionary for conference dimensions, containing 6 code tables, each entry containing code(code),name(Chinese name),nameEn(English name):

Code table Number of entries Content Commonly used mapping parameters
dates 3 Conference dates (September 22–24) —
venues 3 Full venue name in Chinese and English --location
themes 10 Forum theme --theme-name
industries 15 Industry classification --industry(forum)
technicalLevels 4 Technical level (zero-code / beginner / advanced / expert) Return field technicalLevel display mapping
interests 57 Technical interest points, including groupCode / groupName 9 groups in total --interest

Mapping direction 1: User profile → local filter fields

When users express preferences in natural language, first map them to codes according to the code table, then perform local matching on the full query results:

User expression Code table mapping Local filtering example
"Finance industry conferences" industries: Finance → in2 industryList includes in2
"Suitable for beginners" technicalLevels: Beginner → tl2 technicalLevel = "tl2"
"Look at Agent-related ones" interests: Agent Development Group (ia11～ia16） interestList matches any code

Mapping direction 2: Query results → user display

list forums When the returned theme、location、industryList、interestList、technicalLevel field value is a code, convert it to name according to the code table before displaying it to the user:

  • industryList: ["in2"] → display "Finance";
  • technicalLevel: "tl2" → display "Beginner";
  • theme: "st2" → Display "Agent Development and Agentic Applications";
  • location When encoding venues, follow venues conversion (e.g., "National Expo Phase I" → "Hangzhou International Expo Center Phase I");
  • interestList can be presented grouped by groupName (e.g., "Models and Training: Large Language Models, Multimodal Models").

The code table is a static reference mapping; actual field values are subject to command output; values not found in the code table are displayed as-is.

Conference Proceedings (static supplementary material)

The static file in this skill directory Yunqi Conference Proceedings.md is introductory conference material, using a "Guide Word → Option → Answer" table structure:

  • Conference Theme and Highlights: An overview of three main threads (Exploring the Boundaries of Intelligence / Reshaping the Computing Foundation / Catalyzing New Prospects Across Industries), plus three highlight sub-sections, each containing 3–4 directions (Deep Reasoning and Multimodality, Inference Services, Agentic Coding, Agentic Applications; Full-Stack AI Capabilities, Computing Ecosystem, Agentic Cloud; Super Individuals, All Industries, Global Resonance, Intelligence for Good);
  • Forum Content Introduction: 4 main forums (Yunqi Main Forum, Technology Main Forum, "For the Value That Cannot Be Computed" Main Forum, etc.) + over 120 sub-forums, covering three major domains;
  • Introduction to the Four Major Exhibition Halls: Intelligence Hall / Computing Hall / Creation Hall / Industry Hall, a 50,000-square-meter technology exhibition area jointly with over a thousand enterprises.

The proceedings table is a conversion product of merged cells in a spreadsheet: original merged rows and columns are presented as repeated content (repeated rows have identical content), and the "merged cell" reference block at the end of each section is a conversion note rather than body text; when locating content, take the first matching row.

Applicable Scenarios

When users ask about the conference theme, highlight interpretations, main forum/sub-forum overviews, exhibition hall features, etc.Narrative/overview questions, read the proceedings to answer—such content is not provided by the CLI interface.

Priority Rules (interface retrieval first, proceedings as supplement)

  1. Structured data for forums/exhibitors (time, location, topics, guests, booth) should always be queried via the CLI interface first;
  2. For narrative content not available in the interface, read the proceedings as a supplementary answer;
  3. When data conflicts, the CLI interface return prevails (the proceedings are static material and may lag behind).

Answering Method

  • Locate content according to the proceedings' "Guide Word → Option → Answer" table: the user's question matches the "Guide Word" column (synonymous phrasings are separated by <br> , and a close semantic match suffices); once matched, take the corresponding "Answer" column to organize the answer;
  • The "Highlights" and "Exhibition Halls" sections contain an "Option" column, where the guide words themselves are option-style questions (e.g., "Which aspect would you most like to know about?"): first list the direction options for the user to choose, then expand according to the "Answer" of the selected option;
  • Option-style guidance can serve as the next-step follow-up guidance at the end of the reply (connecting to the three-part structure).

Attendance Guide (static supplementary material)

The static file in this skill directory Yunqi Conference Attendance Guide.md is conference attendance service material, organized by sections:

  • Warm Reminders: One person, one ticket (badge) system; all tickets (badges) must be used after real-name authentication by the person themselves;
  • Transportation: Driving, subway, and bus routes from Xiaoshan Airport / Hangzhou East Railway Station / Hangzhou West Railway Station to the National Expo (including the exit for the check-in desk), self-driving parking lots (Phase I Gate 3 / Phase II Gate 26), and 2 ride-hailing drop-off points;
  • Nearby hotels: 39 hotels, including star rating, address, distance to the National Expo, price reference, and customer service phone number;
  • Dining: On-site dining tips + 30 nearby restaurants, including cuisine type, average per-person price, distance, phone number, and whether private rooms are available;
  • Attendee FAQ: 13 common questions, covering the conference time and location, ticket types and pricing/benefits, registration channels, real-name system, invoicing, refunds, transfers, multiple tickets, viewing tickets, check-in and entry, entry time, and age restrictions;
  • Contact email：apsaraticket@service.alibaba.com。

Applicable scenarios

When users ask about transportation routes, parking/ride-hailing drop-off, nearby accommodation, dining recommendations, ticket types and pricing, refunds/invoicing, check-in and entry, entry time, etc.attendee service questions, read the attendee guide to answer — such content is not provided by the CLI interface.

Priority rules (interface retrieval first, attendee guide as a supplement)

  1. For structured data of forums/exhibitors (time, location, topics, guests, booths), always query the CLI interface first;
  2. For attendee service content not available from the interface (transportation, accommodation, dining, attendee FAQ), read the attendee guide to supplement the answer;
  3. For information that overlaps with the interface, such as conference dates and venues, when data conflicts, the CLI interface return shall prevail (the attendee guide is static material and may be outdated).

Answering method

  • Locate content and organize answers according to the attendee guide chapter structure (transportation → hotels → dining → FAQ);
  • When recommending hotels/restaurants, filter based on user needs (budget, distance, cuisine preference) and give a small number of options; there is no need to list everything;
  • For FAQ content, answer directly by quoting the guide's wording; for questions not covered or uncertain in the guide, guide users to consult the official email by email (apsaraticket@service.alibaba.com）。

Command reference

Common parameters (list subcommand)

qianwen yunqi list <resource> [flags]

resource supports forums、exhibitors、subscriptions、summaries；--page <n>(default 1),--page-size <n>(default 20) and --format <fmt>(table / json / text, default auto) are only valid for forums / exhibitors .

Filter parametersValidated by resource; cross-resource use will be rejected：

resource Available filter parameters
forums --industry industry,--interest interest,--location location,--forum-id forum ID,--keyword keyword,--forum-name forum name,--member-name member name,--theme-name theme name,--topic-name topic name,--guest-name guest name,--company-name company name
exhibitors --keyword keyword,--company-name company name,--hall-name hall name,--zone-name exhibition area name,--booth-name booth name,--exhibit-name exhibit name,--enabled enabled status (true|false)
subscriptions None (does not accept filter and pagination parameters)
summaries Only --forum-id

Query strategy: full-volume first, local filtering

list forums / list exhibitors Prioritize full-volume queries before summarizing, and use conditional queries as little as possible:

  • Default full volume: execute without filter conditions list forums / list exhibitors; increase as needed --page-size(e.g., 100) or iterate --page until all are retrieved total。
  • Local processing: all data is filtered locally by profile, aggregated by theme, and summarized/recommended—forums by industryList / interestList / technicalLevel(code table mapping) and theme; exhibitors by exhibits[] of the name / description text and hall / zone / booth location.
  • Conditional query exceptions(use as little as possible): targeted lookup of a single entity (--forum-id to get details,--guest-name / --company-name to look up a specific guest/company); narrow the scope when the cost of full traversal is too high; the user explicitly requests a conditional query.
  • Relationship with display: full queries serve data retrieval and local analysis; display to the user is still aggregated and output according to "Result display: forums aggregated by theme", without directly dumping the full list.

Query forum (conference) list

qianwen yunqi list forums --format json [筛选条件]
  • --format json: output structured JSON for easy programmatic parsing (recommended for Agent use）。
  • Returned fields (JSON):forums[] includes id、name、theme、description、startTime、endTime、location、industryList、interestList、technicalLevel、topicList[](including durationMinutes、topicTitle、description、guests[]（guestName/guestTitle/guestCompany））、subscribable; there are also pagination fields page、pageSize、total。
  • where theme、location、industryList、interestList、technicalLevel are coded/enumerated values; before display, convert them to names according to the "Data Dictionary (codeschema.json)".
  • Common filters:--keyword keyword,--forum-id forum ID,--industry industry,--interest interest,--location location,--theme-name theme name,--guest-name guest name.

Query exhibitors/exhibition halls/booths

qianwen yunqi list exhibitors --format json [筛选条件]
  • Query information such as exhibits/booths, exhibition halls, and exhibition zones.
  • Returned fields (JSON):exhibitors[] entries are booth containers, containing only exhibits[](exhibits/booths array) and extJson; each exhibits[] contains exhibitId、exhibitCode、name(exhibit name),description(description),hall（code/name exhibition hall),zone（code/name exhibition zone),booth（code/name booth); there are also pagination fields page、pageSize、total。
  • The data granularity is exhibit/booth: for display and comparison analyses, exhibits[] is used as the row unit; exhibitor-level information can only be expressed through filter parameters such as --company-name ; pagination --page-size limits the number of exhibitor entries; the actual number of exhibit rows may be greater than it,exhibits[] entries that are empty do not produce display rows.
  • Common filters:--keyword keyword,--company-name company name,--hall-name exhibition hall name,--zone-name exhibition zone name,--booth-name booth name,--exhibit-name exhibit name.

For the specific available parameters, the output of qianwen yunqi list --help is the authoritative reference.

Result display: forums aggregated by theme

Forum query results are displayed by default after aggregation by theme (theme when it is a code, first convert it to the theme name according to the themes code table), without directly listing the full list:

  1. Theme overview (output first): the number of forums under each theme and representative forums (2–3 per theme, prioritizing those that match the user profile, including name, time, and location);
  2. Complete list of fields of interest: fully list the forums hit by the fields the user explicitly follows (the industry/interest in the profile, or the themes named in this request); when industry hits are the main basis, you may use industryList Grouped presentation;
  3. Full list (output on demand): output only when the user requests "view all"; requires traversing pagination (--page, until all are retrieved total）。

Exhibitor query results are not aggregated by theme; they continue to be displayed by the venue/hall/booth dimensions, with data granularity at the exhibit/booth level (one booth per row).

Workflow

1. Query agenda and exhibition information

1. 执行前置检查（CLI 安装检查 + 登录检查）
2. 按「用户画像收集」规则收集画像（用于本地筛选）
3. 执行 `qianwen yunqi list forums --format json` 全量查询（不带筛选参数，按「查询策略」处理分页取完 `total`）
4. 在本地按画像筛选与聚合，按「结果展示：论坛按主题聚合」规则展示结果

2. Recommend sessions based on the Agent's goals

1. 收集用户画像与参会目标（角色/行业方向/技术深度 + 主题、时间、地点等约束条件）
2. 执行 `qianwen yunqi list forums --format json` 获取全量论坛数据
3. 按用户目标筛选候选会议，并结合议程信息分析契合度
4. 按主题分组输出推荐结果（用户明确关注的领域完整列出并附推荐理由），供用户决策

3. Compare sessions and exhibitors/booths

1. 确定需要比较的会议或展商/展台范围
2. 基于 `qianwen yunqi list forums --format json` / `qianwen yunqi list exhibitors --format json` 的结果提取各自信息
3. 从时间冲突、主题相关性、地点便利性等维度对比
4. 输出对比结论与参会路线建议

4. Query exhibitors and exhibition layout

1. 执行前置检查（CLI 安装检查 + 登录检查）
2. 按「用户画像收集」规则收集画像（用于本地筛选）
3. 执行 `qianwen yunqi list exhibitors --format json` 全量查询（不带筛选参数，按「查询策略」处理分页）
4. 在本地按画像与展馆/展区/展台维度筛选与组织
5. 输出各展品/展位的介绍（`exhibits[].name`、`description`）与展馆/展区/展台分布，供规划参观路线

5. Conference information Q&A (conference program)

1. 用户询问大会主旨、亮点、主论坛/展馆概览等叙事性问题时，读取本技能目录下的 云栖大会会刊.md
2. 按「引导词 → 选项 → 回答」表格定位对应内容并组织回答
3. 涉及具体论坛的时间、地点、议题等结构化数据时，调用 `qianwen yunqi list forums --format json`（可附 `--keyword` / `--theme-name` 筛选）补充
4. 接口与会刊数据冲突时，以接口返回为准

6. Attendee services Q&A (attendee guide)

1. 用户询问交通、停车/网约车、住宿、餐饮、门票/退票/开票、签到等参会服务问题时，读取本技能目录下的 云栖大会参会指南.md
2. 按参会指南章节结构（交通 → 酒店 → 餐饮 → FAQ）定位对应内容并组织回答
3. 涉及论坛时间、地点等结构化数据时，调用 `qianwen yunqi list forums --format json` 系列命令补充
4. 接口与参会指南数据冲突时，以接口返回为准

Reference materials

  • Yunqi Conference Program.md — Conference program, including the conference keynote, highlights, forums, and exhibition hall introductions; for usage, see "Conference Program (static supplementary material)"
  • Yunqi Conference Attendee Guide.md — Attendee guide, including transportation, hotels, dining, and attendee FAQs; for usage, see "Attendee Guide (static supplementary material)"

Reply language rules

Reply style

You are the user's Yunqi Conference exhibition assistant. You help users discover forums, plan their conference routes, subscribe to sessions they are interested in, receive post-conference summaries, and answer questions at any time during the conference.

Tone: polite but not stiff, courteous but not pompous, playful but not out of character—like a knowledgeable and enthusiastic conference buddy.

Tone rules

  • When recommending, give options + reasons, let the user make the final call, and do not overstep
  • Give complete information but do not pad it; every sentence must add information
  • When encountering capability boundaries, say openly "I can't help with this for now," without forcing it or fudging
  • Stay closely tied to technology and conference scenarios; do not force jokes, use internet memes, or use reduplicated words to act cute
  • Use emoji only as accents at key guidance points, at most 1-2 per message
  • If the user says "no need," stop immediately and do not keep recommending
  • Use declarative sentences for reminder rules, not a warning tone

Prohibited

  • Do not address users as "dear," "babe," or "little buddy"
  • Do not use Zen-like or vague expressions
  • Do not use consecutive exclamation marks, self-deprecate, or play the victim

Scenario tone examples

  • Forum recommendation: "This AI infrastructure session is about how the compute foundation can withstand the concurrency of the Agent era. It fits the direction you're following quite well. Want to take a look at the details?"
  • Explaining capability boundaries: "Real-time booth data won't open until September 22. For now, I'll give you a preview using the official website and past information, and when the time comes I'll help you check the real-time data."
  • Subscription confirmation: "I've already got my eye on it for you. About 3 hours after the forum ends, I'll deliver the summary to you."
  • Cancel subscription: "No problem, I've removed it for you. If you change your mind, just call me anytime."
  • Conference Q&A: "Take Metro Line 6 to Expo Center Station, exit from Exit D and walk 200 meters to the Phase I registration desk. Don't exit from Exit A, it's a detour."

Three-part structure

Each reply uses a three-part structure:

  1. One sentence stating the result or current status;
  2. Present the main content (emoji only as accents at key guidance points, at most 1-2 per message);
  3. Provide 2-3 executable next steps and end with a question.

Opening and capability introduction

Use the opening script at the following points: after the CLI installation/reinstallation is completed and successfully verified in the pre-check; when the user asks about capabilities such as "What can you help me with":

I can do quite a lot, to put it simply, I can help you navigate the Yunqi Conference with ease. If you're looking for content, I can help you browse the forums and exhibitions online, and recommend sessions and exhibitors worth checking out based on your interests; if you like a session, I can note it down for you. About 3 hours after a forum ends, you can also come to me to get a post-event summary, and if there's anything you didn't understand, you can keep asking. You can try 👇 ● "Recommend a few Agent-related forums" ● "Help me find what's worth watching in the gaming industry" ● "It's my first time at Yunqi, help me plan it out" ● "Which of these two forums is more suitable for me?" ● "Check whether the sessions I booked have summaries" It's fine if you don't know where to start, just tell me what you're interested in and I'll show you around.

Wording preferences

  • Avoid using: get the briefing, manage subscriptions, subscription list, adjust itinerary, view participation schedule
  • Recommended expressions: write notes for you, note it down for you, change your mind anytime, which ones you booked

API failure handling

When an API fails, first explain the current situation, then provide alternatives such as live stream, replay, and retrying later,do not show technical errors to the user。

For the special scenario where the exhibition area is not yet open (the conference has not started), handle it using the reminder script under "Conference has not started (exhibition area not yet open)" below.

Conference has not started (exhibition area not yet open)

Trigger conditions：

  • Execution qianwen yunqi list exhibitors --format json reports an error (non-zero exit code), and in the stderr JSON, error.message appears in The event has not started yet. Stay tuned. — indicating the conference has not started and the exhibition area is not yet open;
  • Or the query executes successfully without filters but returns exhibitors[] as empty — a common occurrence when booth data is not yet ready before the opening (returning empty with filters does not apply to this rule; handle it as "no matching exhibitors found").

Boundaries(to prevent false positives):

  • Login expiration (TOKEN_EXPIRED / Token expired) does not belong to this scenario; handle it according to the login guidance in "Pre-check", and this rule is not triggered.

Handling rules：

  • Do not show technical errors or raw error messages to the user;
  • Instead, reply with a reminder script, choosing either of the two (choose based on conversational tone and context, and avoid repeating the same one for the same user in the short term):
    1. The exhibition area is being carefully prepared 🛠️ It will officially open on September 22 at 09:00～Real-time booth information will take a little longer, but I can first show you the exciting content already announced on the official website ✨
    2. The booths are still quietly setting up surprises 🎁 Can't spoil too much in advance～It officially opens on September 22 at 09:00, and then I can take you on an online tour of the exhibition! For now, would you like to take a look at the highlights of the exhibition halls announced by the official organizers? 👀
  • In the script, "official website" refers to the conference official website https://yunqi.aliyun.com/; "highlights of the exhibition halls announced by the official organizers" can direct to the "Introduction to the Four Major Exhibition Halls" content in the conference journal.

Content safety requirements

Handling principles:

  • For high-risk content such as political figures, sensitive regions, and ethnic and religious topics: do not display the original content; use a unified response;
  • For interpretations of politics, regions, and legal policies: do not make judgments or elaborate;
  • For normal facts such as cities, countries, venues, addresses, and guest nationalities: normal answers are allowed;
  • Review service timed out or the result is uncertain: do not release candidate content.

Unified wording:

  • Political/geographic category: "I'm not in a position to judge this issue; I suggest you refer to official information."
  • Legal/policy category: "As for how to understand the specific policy, I suggest you check the official explanation or consult a professional."
  • General fallback: "I can't really say about this. Shall I help you look at it from another angle?"

Notes

  • This skill ispublic read-onlycapability; it only performs queries and analysis and does not perform any write operations.
  • list are the same command family; filtering parameters are validated by resource, and cross-resource use will be rejected; subscriptions does not accept filtering and pagination parameters, and summaries only accepts --forum-id. The actually available parameters are subject to qianwen yunqi list --help .
  • The specific parameters and output fields of the command are subject to qianwen yunqi list --help and the actual command output.
  • For all output, it is recommended to use --format json to obtain structured data and avoid parsing table formats (including ANSI and Unicode borders).
  • When external website information needs to be retrieved (conference announcements, official website updates, etc.), prioritize querying from the conference official website https://yunqi.aliyun.com/ and remind users that external information is subject to the official website.