workflow-creator
/workflow-creator
Tworzy lub aktualizuje wielokrotnego użytku pliki JavaScript Dynamic Workflow w katalogu .qwen/workflows.
- Autor
- qwenlm ↗
- Repozytorium
- qwen-code ↗
- Licencja
- Apache-2.0
- Ostatnia zmiana repozytorium
- 27.10.2026
Ocena i bezpieczeństwo
- Pliki w paczce
- 2
- Skrypty
- 1
- Komentarze HTML
- 0
- Adresy URL w SKILL.md
- 0
Brak sygnałów. Repozytorium zmienione 27.10.2026, bez odwołań do wycofanych modeli i API.
Apache-2.0, otwarta: można używać i zmieniać, z zachowaniem licencji i informacji o zmianach.
- 1 skrypt w paczce. Przejrzyj je przed instalacją, bo Claude może je uruchomić.
Skrypty: SKILL.test.ts
Co robi i kiedy
Tworzy lub aktualizuje wielokrotnego użytku pliki JavaScript Dynamic Workflow w katalogu .qwen/workflows.
Oryginalny opis (EN)
Create or update reusable Dynamic Workflow JavaScript files under .qwen/workflows. Use when the user asks to create, save, edit, or reuse a Dynamic Workflow, including requests started from the Web Shell Workflows page.
Jak działa
- Boundary
- Workflow
- Script contract
- Updates
Podgląd SKILL.md
---
name: workflow-creator
description: Create or update reusable Dynamic Workflow JavaScript files under .qwen/workflows. Use when the user asks to create, save, edit, or reuse a Dynamic Workflow, including requests started from the Web Shell Workflows page.
---
# Workflow Creator
Create and maintain saved Dynamic Workflows for the current workspace.
## Boundary
- This skill manages `.qwen/workflows/<name>.js` files used by the `workflow` tool and exposed as `/<name>` slash commands.
- Do not create or edit `qwen-workflow-design/*.yaml`; those Task Flow definitions are a different feature.
- Local hosts may also discover trusted ancestor `.qwen/workflows` directories up to the nearest Git root, with the nearest definition first. Discovery does not change the project save destination: use the current session target.
- Use project scope by default. Write to `~/.qwen/workflows` only when the user explicitly asks for a workflow shared across projects.
## Workflow
1. Inspect the current task and any existing workflow with the requested name. Ask a question only when the goal, ordering, or write scope is materially ambiguous.
2. Choose a lower-case name containing only letters, digits, and hyphens. It must start with a letter and be at most 41 characters.
3. Create the smallest script that captures the requested phases, dependencies, and final result. Do not add speculative branches, retries, or agents.
4. Read the saved file back and verify its name, metadata, phase order, dependency flow, and final return value. Do not execute it unless the user also asks to run it.
5. Report the saved path and slash command. In the interactive TUI's ink renderer, the slash command runs in the foreground: progress stays in the tool card, and completion displays the result and notifies the model. The OpenTUI renderer does not yet run client-scheduled tools; there, ask the model to call `Workflow({ name: '<name>' })` instead. `/workflows <runId>` shows the run after it settles. In Web Shell, tell the user to return to Workflows and refresh the Saved tab if it is already open.
## Script contract
- Start with a literal metadata declaration:
```js
export const meta = {
name: 'Release readiness',
description: 'Inspect, validate, and summarize a release candidate',
};
```
- Use the sandbox globals `phase(title)`, `log(message)`, `agent(prompt, options?)`, `parallel(thunks)`, `pipeline(items, ...stages)`, `workflow(nameOrRef, args?)`, `args`, and `budget`. The `workflow-authoring` skill is the full reference for them — load it before writing anything beyond a trivial script.
- Scripts cannot import modules or access the filesystem, shell, environment, or network directly. Put required reads and actions in explicit agent prompts.
- Give every agent a complete, scoped prompt and a concise `label`. State whether it may edit files.
- Express real concurrency as `parallel([() => agent(...), () => agent(...)])`. Do not pass already-started promises to `parallel`.
- Keep dependent work sequential and pass prior results explicitly.
- Put variable user input in `args` instead of hard-coding one-off values.
- End every successful path with an explicit `return` of the final result. A trailing expression is not a return value.
- Do not use `node --check` for validation: valid workflow scripts may contain top-level `await` and `return` because the runtime wraps them in an async function.
## Updates
- Preserve unrelated behavior and metadata when editing an existing workflow.
- Do not overwrite an existing workflow with a different design unless the user requested that update.
- Do not delete or rename a workflow unless the user explicitly asks.
Pliki w paczce (2)
- SKILL.md 4 KB
- SKILL.test.ts 2 KB
Wersje
W bazie nie ma innych skilli o nazwie workflow-creator.
Migawka bazy z 13.11.2026 · wersja paczki 3e499c3aa9b6 (skrót SHA-256 całej paczki)
Pobrania w ostatnich 30 dniach: 0 · ranking
Zgłoś problem z tym skillem: szkodliwa treść, błędny opis albo prośba autora o usunięcie.
Podobne skille
- 95workflow-skill-creator
Zamienia ukończony przepływ pracy użytkownika w wielokrotnego użytku skill agenta. - 100workflow-skill-creator
Zamienia ukończony przepływ pracy użytkownika w wielokrotnego użytku skill dla agenta. - 100skill-creator
Tworzy i ulepsza pakiety skilli wielokrotnego użytku z czytelnymi metadanymi, skupionymi workflow i odpowiednimi granicami bezpieczeństwa. - 100skill-creator
Tworzy nowe pliki SKILL.md, ulepsza istniejące, projektuje opisy skilli tak, by trafnie się wyzwalały, i zamienia pokazany workflow w skill wielokrotnego użytku. - 96qwen-image-2-1-editing
Pisze prompty do edycji obrazów modelem Qwen Image 2.1. - 100codex-dynamic-workflows
Projektuje wieloagentowy przepływ pracy dla złożonego zadania, gdy potrzebna jest dynamiczna orkiestracja.