Reply Current

Overview

Use this skill whenever you need to return a normal successful result to QQ. Do not ask the bridge to mirror your last assistant message automatically. Send the result yourself.

When to Use

• You finished a task and need to answer the current QQ conversation.
• You generated an image, markdown file, report, or other artifact under .run/artifacts/.
• You need to send a short text result directly.

Do not use this skill for failures. Bridge-generated errors are handled by the runtime.

Rules

• Reply only to the current active conversation. Do not invent QQ IDs or group IDs.
• Use exactly one local reply_current.py command per message you want to send.
• Always pass --context-file <path>. The path is given to you in the "# Reply context" section of your developer_instructions and is specific to THIS thread's conversation. The legacy singleton at .run/default/run/reply_context.json is shared across all active tasks and may point at the wrong group under concurrency — skill calls that omit --context-file can silently deliver the reply into another chat.
• Attachments must already exist under .run/artifacts/.
• Prefer text for short answers, image for visual output, and file for markdown/report artifacts.