bk-import

name: bk-import description: Analyzes an external resource (GitHub repo, local skill, URL, or text) and converts it into a BlueKiwi workflow registered directly on the server. Triggers when the user says "/bk-import", "import from github", "convert this skill to workflow", "create workflow from repo/url/skill", or pastes content they want turned into a workflow. user_invocable: true

bk-import — External Resource to BlueKiwi Workflow

Analyze an external resource, extract its process logic, convert it into a structured BlueKiwi workflow, and register it directly via MCP.

Which creation skill to use?

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

Argument Handling

• /bk-import → Ask for the resource via AskUserQuestion.
• /bk-import <resource> → Start analysis from the provided resource.

Step 1: Parse Input

Determine the resource type from the argument:

If no argument, ask via AskUserQuestion:

• header: "Import from where?"
• "Which resource do you want to convert into a BlueKiwi workflow?"
• options: ["GitHub repo URL or owner/repo", "Local skill (e.g. bk-start)", "External URL", "Paste text or JSON"]

Step 2: Fetch & Analyze Content

GitHub Repository

npx repomix@latest --remote <owner/repo> --compress --output /tmp/bk-import-<repo-name>.xml

After packing, extract in order:

1. File tree → identify architecture layers (API, UI, scripts, config)
2. README.md → purpose, key steps, usage examples
3. Main entry points (index, main, app) → sequential process logic
4. Configuration files → decision points and branching options

Clean up when done: rm /tmp/bk-import-<repo-name>.xml

If the repo URL points to a subdirectory (e.g., …/tree/main/packages/cli), run repomix on the full repo then focus grep analysis on that path.

Local Skill

Resolve path:

• Bare name (e.g. bk-start) → ~/.claude/skills/bk-start/SKILL.md
• Full path → read directly

Read SKILL.md completely. Also read any files under scripts/ if present.

Extract:

• Numbered or headed execution steps → sequential actions
• Options/choices presented to the user → decision points
• "Repeat until" or loop patterns → iterative steps

External URL

WebFetch <url>

Extract the main process described: step sequences, decision criteria, iterative patterns.

Text / JSON Paste

If JSON: detect format (n8n workflow, GitHub Actions, etc.) and parse its nodes/steps/jobs structure.

If plain text: extract numbered or headed steps, conditionals, and loops.

Step 3: Extract Workflow Logic

From the analyzed content, identify and label each element:

Sequential execution → action node candidates

• "Do X, then Y" patterns
• Script / CLI execution steps
• Data fetching or transformation steps
• API calls, file generation, report writing

Decision points → gate node candidates

• User approval required before continuing
• "Choose between A or B" patterns
• Final review before an irreversible action

Iterative patterns → loop node candidates

• "Repeat until condition met"
• Q&A / clarification loops (ask one question, get answer, repeat)
• Review → feedback → revise cycles

Human sign-off for risky actions → hitl: true on action nodes

• Sending emails or external messages
• Deploying to production
• Deleting or overwriting data

Step 4: Design Nodes

Convert the extracted logic into BlueKiwi nodes. Apply the Instruction Depth Standard (same rules as bk-create) to every node:

📦 Importing: <resource name>

Proposed workflow: <title>
━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━
1. [Step Name]           action
2. [Step Name]           gate      ← user approval
3. [Step Name]           loop  ↩   repeats until X
4. [Step Name]           action    🔒 hitl
━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━
<N> steps  ·  source: <resource>

{
  "title": "<derived title — concise, action-oriented>",
  "description": "<1–2 sentences: what this workflow does and when to use it>",
  "version": "1.0",
  "folder_id": <selected folder id>,
  "nodes": [
    {
      "step_order": 1,
      "node_type": "action",
      "title": "...",
      "instruction": "...",
      "hitl": false,
      "loop_back_to": null,
      "visual_selection": false
    }
  ]
}

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

✅ Workflow imported
Name:   <title> (ID: <id>)
Source: <resource>
Steps:  <n>
🔗 ${WEBUI_URL}/workflows/${WORKFLOW_ID}

Type /bk-start to execute it now.