bluekiwi 0.2.3 → 0.2.4
This diff represents the content of publicly available package versions that have been released to one of the supported registries. The information contained in this diff is provided for informational purposes only and reflects changes between package versions as they appear in their respective public registries.
package/dist/assets/index.js
CHANGED
|
@@ -1,6 +1,6 @@
|
|
|
1
1
|
---
|
|
2
2
|
name: bk-start
|
|
3
|
-
description: BlueKiwi workflow execution skill. Selects a registered workflow and starts the first step immediately. This skill should be used when the user says "/bk-start", "start workflow", "run BlueKiwi", or wants to begin a registered instruction workflow.
|
|
3
|
+
description: BlueKiwi workflow execution skill. Selects a registered workflow and starts the first step immediately. This skill should be used when the user says "/bk-start", "/bk-run", "start workflow", "run workflow", "execute workflow", "run BlueKiwi", or wants to begin a registered instruction workflow.
|
|
4
4
|
user_invocable: true
|
|
5
5
|
---
|
|
6
6
|
|
package/package.json
CHANGED
|
@@ -1,50 +0,0 @@
|
|
|
1
|
-
---
|
|
2
|
-
name: bk-run
|
|
3
|
-
description: BlueKiwi workflow run skill. Selects a workflow and immediately starts it — a streamlined alias for /bk-start with explicit workflow selection. This skill should be used when the user says "/bk-run", "run workflow", "execute workflow", or wants to quickly start a specific workflow by name.
|
|
4
|
-
user_invocable: true
|
|
5
|
-
---
|
|
6
|
-
|
|
7
|
-
# BlueKiwi Workflow Run
|
|
8
|
-
|
|
9
|
-
Quickly select and start a specific workflow. Delegates to `/bk-start` execution flow once a workflow is selected.
|
|
10
|
-
|
|
11
|
-
## Argument Handling
|
|
12
|
-
|
|
13
|
-
- `/bk-run` → List workflows and ask the user to select.
|
|
14
|
-
- `/bk-run <name>` → Find the best-matching workflow and confirm before starting.
|
|
15
|
-
|
|
16
|
-
## Execution Steps
|
|
17
|
-
|
|
18
|
-
### Step 1: Select Workflow
|
|
19
|
-
|
|
20
|
-
Call `list_workflows` to get the active workflow list.
|
|
21
|
-
|
|
22
|
-
If an argument is provided, find the best match by title and confirm:
|
|
23
|
-
|
|
24
|
-
```
|
|
25
|
-
Run '{title}' (v<version>)?
|
|
26
|
-
```
|
|
27
|
-
|
|
28
|
-
Ask via AskUserQuestion:
|
|
29
|
-
|
|
30
|
-
- header: "Run workflow"
|
|
31
|
-
- options: ["Run", "Pick a different one", "Cancel"]
|
|
32
|
-
|
|
33
|
-
If no argument, show the full list via AskUserQuestion (up to 4 options).
|
|
34
|
-
|
|
35
|
-
### Step 2: Start
|
|
36
|
-
|
|
37
|
-
Call `start_workflow` with the selected `workflow_id`.
|
|
38
|
-
|
|
39
|
-
Collect and pass `session_meta` exactly as described in `/bk-start`.
|
|
40
|
-
|
|
41
|
-
### Step 3: Execute
|
|
42
|
-
|
|
43
|
-
Continue with the same execution loop as `/bk-start`:
|
|
44
|
-
|
|
45
|
-
- Show the roadmap.
|
|
46
|
-
- Execute the first step immediately.
|
|
47
|
-
- Follow the auto_advance loop.
|
|
48
|
-
- Pause at `auto_advance: false` steps — if `execute_step` returns `next_action: "wait_for_human_approval"`, call `request_approval` and stop (HITL pause).
|
|
49
|
-
|
|
50
|
-
Refer to `/bk-start` for all execution details including HITL handling, credential handling, and execute_step requirements.
|