bk-improve

name: bk-improve description: BlueKiwi workflow improvement skill. Analyzes an existing workflow, creates a better version, and optionally runs it to compare results. This skill should be used when the user says "/bk-improve", "improve workflow", "make a better version", or wants to refine an existing BlueKiwi workflow. user_invocable: true

BlueKiwi Workflow Improve

Improve an existing workflow by creating a new version, then optionally execute it to compare results.

Which creation skill to use?

• /bk-improve (this one) — a registered workflow exists and needs a better version.
• /bk-create — start from a natural-language goal without an existing workflow.
• /bk-import — external resource (GitHub repo, URL, local skill, pasted text) to convert into a new workflow.

Argument Handling

• /bk-improve → Fetch workflow list, ask user to select.
• /bk-improve <workflow name> → Load that workflow directly.

Execution Steps

Step 1: Select Target Workflow

If no argument, call list_workflows and ask via AskUserQuestion:

• header: "Which workflow?"
• "Which workflow would you like to improve?"
• options: workflow title list (up to 4)

Step 2: Understand Improvement Direction

Ask via AskUserQuestion:

• header: "Improvement goal"
• "What would you like to improve?"
• options: ["Set more quantitative goals", "Break steps into finer detail", "Improve accuracy", "Type my own"]

If "Type my own" → accept free-text improvement direction.

Step 3: Analyze the Current Workflow

Leveraging Feedback Data

When improving a workflow, call advance(peek=true) on a past task to check for feedback_data. If feedback_data exists, use it as the primary input for improvement analysis:

1. Read each feedback item's question and answer
2. Identify negative responses (unsatisfied, insufficient, etc.)
3. Prioritize steps related to that feedback for improvement
4. Explicitly note "based on user feedback" when proposing changes

Display the current workflow node structure:

Current workflow: <title> v<version>
━━━━━━━━━━━━━━━━━━━━━━━━━
1. [Step name] — <instruction summary>
2. [Step name] — <instruction summary>
...
━━━━━━━━━━━━━━━━━━━━━━━━━

Review each node against the improvement direction:

• Vague goals → add quantitative criteria
• Oversized steps → split them
• Missing validation → add it
• Unnecessary steps → remove them
• Missing attachments → add the required script, reference doc, or config file
• Stale attachments → remove outdated files and replace them with the current version
• Unclear attachment usage → update the instruction so it references the attachment by filename and explains when to use it
• Legacy VS nodes using inline onclick/postMessage → migrate to bk-* component fragments
• VS nodes missing component specification in instruction → add which bk-* components to use
• VS response format mismatch → verify downstream steps parse JSON {selections, values, ranking, matrix} instead of plain strings

Step 4: Propose Changes

Design the improvements and show a diff:

Proposed improvements:
━━━━━━━━━━━━━━━━━━━━━━━━━
✏️  Step 1: "Collect keywords" → "Collect top 10 keywords (by search volume)"
✏️  Step 3: instruction refined (add termination criteria)
➕  Step 4 added: "Quantitative validation (retry if below threshold)"
🗑️  Step 6 removed: redundant summary
━━━━━━━━━━━━━━━━━━━━━━━━━

Step 5: Choose Modification Strategy

Ask via AskUserQuestion:

• header: "How to apply?"
• options: ["Edit in place (patch current version)", "Create new version (v<x.y>)", "Adjust more", "Cancel"]

Edit in place — for minor tweaks (instruction wording, adding/removing 1-2 nodes). Modifies the current active version directly.

Create new version — for substantial restructuring (reordering steps, changing node types, major logic changes). Creates a new version in the same family; old version is archived.

Step 5a: Edit in Place (update_node)

Apply changes one by one using granular MCP tools:

# Update inline instruction for a single node
update_node(workflow_id=67, node_id=109, instruction="new instruction text")

# Update node title
update_node(workflow_id=67, node_id=110, title="New Title")

# Change node type or add loop
update_node(workflow_id=67, node_id=112, node_type="loop", loop_back_to=7)

# Add a new node after step 3
insert_node(workflow_id=67, after_step=3, title="Validation", instruction="...", node_type="action")

# Remove a node
remove_node(workflow_id=67, node_id=115)

✅ Workflow updated in place
Workflow: <title> v<version>
Changes: <n> nodes modified, <n> added, <n> removed

{
  "workflow_id": <existing id>,
  "create_new_version": true,
  "version": "<new version>",
  "nodes": [<full improved node array>]
}

✅ New version created
Workflow: <title>
Previous: v<old>  →  New: v<new>
Changed steps: <n>

open "${WEBUI_URL}/workflows/${WORKFLOW_ID}"