/**
 * chat-progress — a GENERAL "report progress back to the chat" skill for any
 * LONG-RUNNING workflow node. One dead-simple tool, `report_progress(message)`:
 * the node posts a one-line status to the SAME chat that triggered the run,
 * while it's still working, so a human watching the conversation sees the job
 * is alive (not a black box until the completion notify fires).
 *
 * Why a dedicated skill (not "just call slack/lark"):
 *   - Zero fumbling: the node calls report_progress("scored 60/188") — it does
 *     NOT need to know the provider, channel id, or bot token. The target +
 *     auth are resolved here.
 *   - General + reusable: ANY agent's long-running node declares
 *     SKILLS.CHAT_PROGRESS and gets the same primitive for free.
 *   - Fire-and-forget: a post failure is NEVER a run failure (a progress ping
 *     is a courtesy, not the work).
 *
 * TARGET resolution (where the ping goes) — first hit wins:
 *   1. explicit args { provider, chatId } (the node passes state.notify)
 *   2. env ZIBBY_PROGRESS_PROVIDER + ZIBBY_PROGRESS_CHAT_ID (set by the runtime
 *      from the trigger's `notify` — the same coordinates the completion
 *      notification uses, so progress + done land in one conversation)
 *   3. env SLACK_CHANNEL / LARK_RECEIVE_ID (the chat_notify convention)
 * No target resolvable → soft no-op (never an error; the run proceeds).
 *
 * POSTING reuses the slack/lark skills' own handleToolCall (their auth via
 * resolveIntegrationToken, their message APIs) — zero duplication.
 */
export declare const chatProgressSkill: any;
export default chatProgressSkill;