What problem does it solve?
This Skill resolves the common issue where workspace job tools called from chat return an output-error with no meaningful error text, typically caused by invoking the tool with a bare empty object instead of a required prompt argument, and prevents users from making incorrect assumptions like the tool being unbound from the chat session.
Core Features & Use Cases
- Correct invocation guidance: Enforces the required prompt argument for job tool calls, with fallback to job-specific schema parameters when applicable, eliminating bare empty object call errors.
- Job pattern clarification: Distinguishes between Pattern A sequential jobs and Pattern B FSM jobs to prevent incorrect migration fixes for empty output issues.
- Unbound tool workaround: Provides the trigger_signal method for running newly created jobs that are not yet bound to the active chat session, avoiding unnecessary prompts for users to send new messages.
- Use Case: If a chat user calls a workspace reporting job and receives an output-error with no details, this Skill guides them to add the correct prompt parameter instead of assuming the tool is misconfigured or unbound.
Quick Start
Use this Skill to troubleshoot a workspace job tool that returned an output-error when called from chat, starting by verifying the invocation included a required prompt argument.
