Magpie Bid Assistant for WorkBuddy

Problem

Bid documents usually require parsing tender files and choosing options for multiple packages, EPC scope, blind bidding, length, body style, tables, images, and export numbering. Asking for each option in chat can miss fields and mixes parsing, configuration submission, generation confirmation, and export.

How It Works

Magpie Bid Assistant for WorkBuddy runs bid workflows through the xique-bid MCP tools. The main steps are:
- Use xique_prepare_source to parse the source file and capture the runId;
- Use xique_bid_configuration to present a single configuration page covering length, writing quality, body style, tables, images, blind bidding, export templates, and output path;
- After submission, use xique_prepare_bid to generate a configuration summary, then start outline generation;
- Follow task status through bidder role, response basis, outline confirmation, directory confirmation, and content generation;
- When the result returns a non-empty savedPath, use present_files to deliver the Word file.

Boundaries

This skill assumes the Magpie MCP is installed and logged in within WorkBuddy. If the version is too low, login is missing, or the task is blocked, fix the login, version, or specific blocker first; do not treat “config written” or tool visibility as generation success.