Weaver E10 Intelligent Workflow Assistant

Problem

In Weaver E10, engineers often need to query todo, done, initiated, or all workflows from natural language, then open, summarize, operate, or create requests. The hard part is ambiguity: workflow names, fields, nodes, and people may have synonyms or multiple candidates, and a model can easily guess parameters, retry, or invent commands. This skill narrows the request to high-level commands such as workflow-search, workflow-detail, workflow-summary, workflow-open, workflow-operate, and workflow-create, and continues only from script-returned candidates and status.

How It Works

• Search: extract --category, --workflow, --field-name, --filter-fields, time, creator, and node parameters from the user request; system conditions use dedicated parameters, while form fields use --filter-fields.
• Memory: optionally call memory-prompt before query or creation to reuse confirmed workflow aliases, field preferences, and display preferences; avoid repeated reads within 6 hours.
• Clarification: when multiple candidates are returned, show them and continue with --resume-query and --candidate instead of rebuilding the original query.
• Creation: follow the workflow lookup, form initialization, data preparation, and submission chain; required fields come from the form response.
• Safety boundaries: stop and report on HTTP failures, expired login, mismatched results, or two consecutive command failures; for expired login, guide the user to weaver-e10-login rather than switching endpoints or guessing commands.

Scope and Notes

Best for teams with a Weaver E10 environment and login context, used for workflow search, status review, detail summaries, controlled operations, and request creation. It is not intended to bypass permissions, batch-guess, auto-retry, or drive non-E10 systems. Output emphasizes rendering the script-provided finalMarkdown unchanged to avoid rewriting business data.