SuperAPI AI Directory
Partner with us中文AI newsFavorites
Skillswind-alice-meeting-expert

wind-alice-meeting-expert

Office & productivity

View repository

Updated 10-15 17:27

About this skill

wind-alice-meeting-expert

Call Wind Alice "Meeting Expert": send the user'soriginal wordsto the Alice Agent, pull the analysis results as an SSE stream, and print them.

When to use

Use this skill when the user's question falls into any of the following scenarios:

  • Check which earnings calls, roadshows, or research visits are scheduled in an upcoming period
  • Pre-meeting preparation: retrieve information on the meeting counterpart and background materials, and organize points of interest, risks, and a question list
  • Have the AI assistant join a Tencent Meeting on time and complete notes and real-time transcription
  • After the meeting, look up meeting minutes, subtitles, verbatim transcripts, and key Q&A
  • Ask in-depth follow-up questions in the meeting records around a certain metric or viewpoint
  • Organize follow-up items after the meeting

Typical phrasings:

  • Which listed companies have earnings calls in the next week?
  • Help me attend this Tencent Meeting and take notes; use "Research Assistant" as the participant name; meeting invitation link:
  • What was said in Tesla's most recent earnings call?

Scenarios where this skill should not be used：

  • The user names a specific Alice sub-skill ("Company One-Pager", "Fact Verification", "Stock Picking by Theme", etc.) -> use wind-alice。
  • General financial Q&A, where it does not matter which pipeline is used -> use wind-alice to go with auto.

How to use

  1. First cd to this skill's directory: the following scripts/ paths are relative to the directory where SKILL.md is located.
  2. Remind the user before calling: the Alice expert pipeline often takesseveral minutes to over ten minutes, and may consume a large number of credits; this is normal, so do not cancel midway or repeatedly issue the same request.
  3. Execute:
node scripts/wind-alice-meeting-expert.mjs --prompt "<用户原话>"

For example:

node scripts/wind-alice-meeting-expert.mjs --prompt "未来一周有哪些上市公司业绩会召开？"
  1. Wait for the process to exit before delivering. During the wait, it is normal for the terminal to show no new output for a long time;do not mistake it for being stuck。

--prompt must be the user's original words: do not "help the user organize their wording", do not extract only the stock ticker, and do not translate or rewrite. This skill does not prepend any skill-name prefix; the user's question is sent to the server as-is. Use only the --prompt single parameter;--skill is an optional parameter inherited from wind-alice , and this skill should not pass it.

Configuration

Requires WIND_API_KEY, read by priority:

  1. %USERPROFILE%\.wind-aifinmarket\config（dotenv：WIND_API_KEY=...）
  2. This skill directory config.json（{"wind_api_key":"..."}）
  3. environment variable WIND_API_KEY

Do notmanually check the sources one by one and then conclude the Key is missing—just execute the CLI; only if the CLI returns KEY_MISSING does it mean it is truly not configured. Key acquisition entry point:https://aifinmarket.wind.com.cn/#/user/overview。

Deliver to the user

  • For the body, take the content in stdout after agentResult.value: ,present it as-is; summarizing, abstracting, or rewriting is prohibited.
  • Do not add an opening line (such as "The following is the XX report"), and do not label internal field names such as agentResult.value .
  • Attachments have already been downloaded by the CLI to .agents/download/, local pathAlready inlined in the main text; do not append "saved to…" at the end.
  • ProhibitedRead .agents/download/ to paste the full attachment text to the user—the main text is already the user-facing core content, and attachments are for the user to open locally.

Hard requirements

  1. Never output the real WIND_API_KEY, Bearer token, or config.json content; always use Authorization: Bearer <WIND_API_KEY> placeholders in examples.
  2. --prompt cannot be empty, otherwise the CLI exits directly with code 2.
  3. Streaming must wait until the process exits; it must not be changed to "return as soon as sent".
  4. Must not interrupt the CLI due to waiting too long, switch to other tools, or repeatedly initiate the same task in parallel.
  5. Under PowerShell, reading this document requires explicit UTF-8:Get-Content -Encoding UTF8 skills\wind-alice-meeting-expert\SKILL.md; if garbled text appears, reread as UTF-8 first.