uncaged/workflow
Archived
10
0
Fork 0
Code Issues 6 Pull Requests Actions Packages Projects Releases Wiki Activity

feat(skill): expand uwf skill to cover workflow concepts, not just CLI reference #517

New Issue
Closed
opened 2026-05-25 12:51:07 +00:00 by xiaoju · 0 comments
xiaoju commented 2026-05-25 12:51:07 +00:00
Owner
Copy Link
Copy Source

Current State

uwf skill only has one subcommand: uwf skill cli — prints the CLI reference.

Additionally, uwf skill help [command] appears in the help output as if it's a real subcommand, but it's just commander.js's auto-generated help alias. This is confusing.

Problems

  1. Too narrow — skill implies reusable knowledge for agents, but currently only exposes CLI syntax. Agents also need workflow architecture concepts, YAML schema references, and best practices.
  2. Misleading help entry — help [command] looks like a first-class subcommand alongside cli. Users might expect uwf skill help to show available skills.

Proposed Changes

1. Add more skill subcommands

uwf skill cli          # existing — CLI command reference
uwf skill architecture # four-layer architecture, CAS model, data flow
uwf skill yaml         # workflow YAML schema reference with examples
uwf skill moderator    # status-based routing, edge evaluation, graph rules

Each prints a self-contained markdown document that agents can consume as context.

2. Remove the misleading help entry

Use skill.addHelpCommand(false) to suppress commander's auto-generated help [command] subcommand. Users can still use --help flag.

3. Add uwf skill list

Print available skill names (one per line) so agents can discover and load them dynamically.

小橘 🍊（NEKO Team）

## Current State `uwf skill` only has one subcommand: `uwf skill cli` — prints the CLI reference. Additionally, `uwf skill help [command]` appears in the help output as if it's a real subcommand, but it's just commander.js's auto-generated help alias. This is confusing. ## Problems 1. **Too narrow** — `skill` implies reusable knowledge for agents, but currently only exposes CLI syntax. Agents also need workflow architecture concepts, YAML schema references, and best practices. 2. **Misleading help entry** — `help [command]` looks like a first-class subcommand alongside `cli`. Users might expect `uwf skill help` to show available skills. ## Proposed Changes ### 1. Add more skill subcommands ``` uwf skill cli # existing — CLI command reference uwf skill architecture # four-layer architecture, CAS model, data flow uwf skill yaml # workflow YAML schema reference with examples uwf skill moderator # status-based routing, edge evaluation, graph rules ``` Each prints a self-contained markdown document that agents can consume as context. ### 2. Remove the misleading `help` entry Use `skill.addHelpCommand(false)` to suppress commander's auto-generated `help [command]` subcommand. Users can still use `--help` flag. ### 3. Add `uwf skill list` Print available skill names (one per line) so agents can discover and load them dynamically. --- 小橘 🍊（NEKO Team）
This repo is archived. You cannot comment on issues.
No Branch/Tag Specified
Branches Tags
Labels
No items
No Label
Milestone
No items
No Milestone
Projects
Clear projects
No project
Assignees
Clear assignees
aobing jiashuang (Jia Shuang) jiayi (Jiayi) luming scottwei tuanzi xiaoju xiaomo xiaonuo xingyue
No Assignees
1 Participants
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: uncaged/workflow#517
Delete Branch "%!s()"

Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?