Feishu Topic Spawn

Create a new Feishu topic in a dedicated topic-group, then optionally post the first thread reply inside it.

Keep this skill lightweight. Use it for topic creation and first-reply bootstrapping, not for session routing magic.

Validated behavior

This workflow has been verified:

1. 1. feishu_im_user_message.send to a topic-group chat_id creates a new top-level topic.
2. INLINECODE2 with reply_in_thread=true posts inside that topic.
3. A reply can @ a user by placing Feishu text markup directly in the content:

CODEBLOCK0

This is the current working path. Prefer it over assumptions about implicit reply routing.

Preconditions

Require all of the following:

• - The destination is a real Feishu topic-group.
• The user has explicitly asked to send the message.
• The user has permission to post in that group.
• User-auth Feishu messaging is available for feishu_im_user_message.

If user auth is unavailable or expired, stop and ask the user to re-authorize.

If the target group is not a topic-group, explain that the result will only be a normal group message, not a topic.

Default target group

Default to the fixed topic-group configured in TOOLS.md, if one exists.

Do not hardcode a personal/local group name into a public skill.

Use feishu_chat with action=search to resolve the group.

If the user explicitly names a target group, use that group.

If the user does not name a group and no local default is configured:

• - Stop.
• Ask which Feishu topic-group to use.

If no matching group is found:

• - Stop.
• Tell the user the topic-group does not exist yet.
• Ask them to create it manually first.

Workflow

1. Resolve target group

• - If the user explicitly names a group, use that name.
• Otherwise use the local default topic-group from TOOLS.md, if configured.
• If no local default exists, ask the user which topic-group to use.
• Resolve the chat_id with feishu_chat.search.

2. Parse requested action

Support four shapes:

A. Open topic only

Send one top-level text message only.

B. Open topic + first thread reply

Interpret as:

• - title = INLINECODE12
• first thread reply = INLINECODE13

C. Open topic + first thread reply + @mention

Interpret as:

• - top-level topic title/text
• then a thread reply
• optionally prepend a Feishu <at user_id="...">...</at> mention

D. Open topic + carry over prior context + ask a new question

Interpret as:

• - create a clean new topic
• carry over only the minimum relevant context
• put both context and the new question into the same top-level topic-opening message
• make the new question impossible to miss
• avoid a second seed message unless the user explicitly wants an extra in-thread reply

3. Create the topic

Use feishu_im_user_message.send:

• - INLINECODE16
• INLINECODE17
• INLINECODE18
• INLINECODE19
• INLINECODE20

The returned message_id is the topic root.

4. Optionally add the first thread reply

If the user asked for an initial reply, use feishu_im_user_message.reply:

• - INLINECODE23
• INLINECODE24
• INLINECODE25
• INLINECODE26
• INLINECODE27

If an @mention is requested, format it directly in the text:

CODEBLOCK5

Use the current user open_id when the user says @我.

5. When carrying context into a new topic, keep it simple

For context carry-over + new question, prefer one single top-level message.
Do not add a second seed reply unless the user explicitly wants one, because two user messages may trigger two assistant replies.

Use a simple structure:

CODEBLOCK6

Or, when a short summary reads better:

CODEBLOCK7

Rules:

• - Put the real question first.
• Keep the summary short.
• Do not add extra instruction-y wording unless absolutely needed.
• The goal is not to outsmart the model; the goal is to make the follow-up obvious.

Example:

CODEBLOCK8

Parsing guidance

Treat all of the following as likely triggers:

• - INLINECODE29
• INLINECODE30
• INLINECODE31
• INLINECODE32
• INLINECODE33
• INLINECODE34
• INLINECODE35

Useful parsing rules:

• - Split on the first ： / : to isolate the command from the payload.
• Treat ｜ / | as a likely separator between title and first reply.
• Phrases like 然后回复一条, 回一条, 在话题里回复, 并且 at 我, @我 indicate an in-thread follow-up.
• Phrases like 把前面几条带过去, 把刚才聊的内容带过去, 新开一个话题聊这个, 继续追问, 新的追问 indicate a context-carrying seed reply rather than a plain freeform reply.
• If only one segment exists, treat it as topic text only.

Do not overfit parsing. If the message is ambiguous, ask one short clarification question.

Tool preference

Prefer the validated user-message path for this skill:

• - INLINECODE52
• INLINECODE53

Reason: this path has been validated end-to-end for:

• - topic creation
• in-thread reply
• @mention markup

Do not rely on ordinary assistant reply routing to create a fresh topic.

Report back

After success, tell the user briefly:

• - target group
• topic text/title used
• whether a thread reply was added
• whether an @mention was included

Keep it short.

Boundaries

• - This skill only works as intended in a Feishu topic-group.
• This skill does not create Feishu groups.
• This skill should not silently send as the user unless the user explicitly asked.
• This skill is for topic bootstrapping: create the topic, optionally seed the first thread reply, then let later conversation continue inside that topic.
• If the user wants a normal group message instead of a topic, do not force this skill.

Minimal examples

Example 1: topic only

Action:

• - resolve the configured default topic-group (or ask the user which group to use)
• send top-level INLINECODE54

Example 2: topic + thread reply

Action:

• - create top-level INLINECODE55
• reply in thread with INLINECODE56

Example 3: topic + thread reply + @me

Action:

• - create top-level INLINECODE57
• reply in thread with:

Example 4: carry context + ask one new question cleanly

Action:

• - create a fresh topic title focused on the new question
• send one top-level topic-opening message
• put 问题：... first
• then add a short INLINECODE59
• do not add a second seed reply unless the user explicitly asks for one