wot-ui-cli

Original：🇨🇳 Chinese

Translated

For answering, using, and debugging @wot-ui/cli. Keywords: wot, @wot-ui/cli, CLI, MCP, doctor, usage, lint, list, info, doc, demo, token, changelog, extract, wot mcp. Applicable for command queries, parameter explanations, MCP integration, local debugging, data extraction, and open-wot repository maintenance.

12installs

Sourcewot-ui/open-wot

Added on2026-04-23

NPX Install

npx skill4agent add wot-ui/open-wot wot-ui-cli

SKILL.md Content (Chinese)

View Translation Comparison →

Wot UI CLI Skill

This skill is designed to enable Agents to prioritize answers based on the repository's README and actual command capabilities when handling issues related to

@wot-ui/cli

itself, rather than mistaking it for pure component library documentation.

Applicable Scenarios

Users ask how to use the
```
wot
```
command.

Users need to distinguish the purposes of

list

info

doc

demo

token

changelog

doctor

usage

lint

mcp

extract

Users want to integrate with MCP Server, or need configuration and debugging methods for
```
wot mcp
```
.
Users want to debug
```
@wot-ui/cli
```
in this repository, verify build artifacts, or re-extract data.
Users' issues are essentially open-wot repository maintenance problems, rather than pure wot-ui component usage issues.

Scope of Application

Focuses on the
```
@wot-ui/cli
```
toolkit and the development and maintenance process of the
```
open-wot
```
repository.
Covers command capabilities, general parameters, MCP, offline data sources, extraction processes, local debugging, and release package boundaries in key areas.
If the task is to generate
```
wd-*
```
page code, explain component props, or provide theme customization solutions, prioritize using the
```
wot-ui-v2
```
skill.

Recommended Process

First confirm whether the user is asking about the CLI tool itself, or using the CLI to query component knowledge.
If it's a command usage issue, answer by command category first: component knowledge, project analysis, MCP, data extraction, repository development.
If it's a repository maintenance issue, prioritize providing actual debugging commands in this repository rather than general discussions.
If component content is involved, guide or switch to the
```
wot-ui-v2
```
skill.

Command Groups

Component Knowledge Query

```
wot list
```
```
wot info <Component>
```
```
wot doc <Component>
```
```
wot demo <Component> [name]
```
```
wot token [Component]
```
```
wot changelog [version] [component]
```

Project Analysis

```
wot doctor [dir]
```
```
wot usage [dir]
```
```
wot lint [dir]
```

MCP

```
wot mcp
```

Data Extraction and Repository Maintenance

pnpm extract:cli --wot-dir ../wot-ui --output data/v2.json

```
pnpm extract:clone
```
```
pnpm exec tsx src/index.ts <command>
```
```
pnpm build
```
```
node dist/index.mjs <command>
```

Working Rules

The package name is
```
@wot-ui/cli
```
, and the actual executable command is
```
wot
```
.
When answering command-related questions, prioritize using the behaviors and parameters promised in the repository's README, and do not invent undeclared subcommands.
When answering local debugging questions, prioritize providing the source code entry:
```
pnpm exec tsx src/index.ts ...
```
.
When answering build artifact questions, provide
```
node dist/index.mjs ...
```
instead.
When answering MCP-related questions, explain that
```
wot mcp
```
uses stdio, and no interactive output in the terminal is usually a normal phenomenon.
When answering extraction logic questions, explain that data mainly comes from the markdown and SCSS source code of the upstream
```
wot-ui/wot-ui
```
.
When users ask about component knowledge but access it via the CLI, retain the semantic layer of "querying component knowledge through the CLI".

Reference Materials

Wot UI CLI Overview