Qingflow MCP Skill

To handle any user request involving 轻流 (Qingflow), follow this workflow:

Step 1: Daily Version Auto-Update

Check if the CLI has already been updated today by reading the version-check file:

node -e "try{const fs=require('fs'),f=require('os').tmpdir()+'/qingflow-version-check.txt';console.log(fs.readFileSync(f,'utf8').trim())}catch(e){console.log('NEVER')}"

If output matches today's date (YYYY-MM-DD) → skip to Step 2.
Otherwise → run:

npm install -g @qingflow-tech/qingflow-cli@latest

Then record today's date (cross-platform):

node -e "const fs=require('fs'),p=require('os').tmpdir()+'/qingflow-version-check.txt';fs.writeFileSync(p,new Date().toISOString().slice(0,10))"

Step 2: Check Installation

npm list -g @qingflow-tech/qingflow-cli

If output shows a version → proceed to Step 3.
If empty or error → run npm install -g @qingflow-tech/qingflow-cli@latest, then proceed.

Step 3: Check Authentication Status

qingflow auth whoami

If logged in → proceed to Step 4.
If not logged in → ask the user to provide their Qingflow email and password, and include this message:

请提供您的轻流账号邮箱和密码，以完成身份验证。

如果您还没有轻流账号，可以点击以下链接免费注册： 👉 https://qingflow.com/passport/login?utm_source=workbuddy

注册并获得账号后，将邮箱和密码发送到当前对话，我将自动帮您完成登录。

Once the user provides their email and password, run:
```
qingflow auth login --email USER_EMAIL --password USER_PASSWORD
```

Note: Interactive qingflow auth login (without flags) opens a terminal prompt; in agent contexts, always pass --email and --password directly to avoid blocking.

Step 4: Configure MCP Servers (if WorkBuddy MCP not yet connected)

Only do this step if the user wants to use MCP tools and the servers are not yet active. Add both entries to ~/.workbuddy/mcp.json:

{
  "mcpServers": {
    "qingflow-user": {
      "command": "qingflow-app-user-mcp",
      "args": [],
      "env": {
        "QINGFLOW_MCP_DEFAULT_BASE_URL": "https://qingflow.com/api"
      }
    },
    "qingflow-builder": {
      "command": "qingflow-app-builder-mcp",
      "args": [],
      "env": {
        "QINGFLOW_MCP_DEFAULT_BASE_URL": "https://qingflow.com/api"
      }
    }
  }
}

After saving, tell the user to open the connector management page (top-right corner in WorkBuddy), find the new MCP server, and click Trust to activate it.

qingflow-user: record CRUD, task management, import/export
qingflow-builder: app schema, layout, flow, views, charts

Step 5: Execute the User's Request

Choose the appropriate approach based on availability:

Option A — CLI (always available after install): Use qingflow <command> --json for machine-readable output. Refer to references/qingflow-cli-overview.md for the full command tree.

Option B — MCP tools (available when MCP servers are connected): Refer to references/qingflow-mcp-tools.md for the complete tool list.

Key user-domain tools: record_list, record_get_public, record_insert_public, record_update_public, record_delete_public, task_list, task_get, task_action_execute

Key builder-domain tools: app_get_fields, app_schema_apply, app_layout_apply, app_flow_apply

Always call record_browse_schema_get_public before record_list, and record_insert_schema_get_public before record_insert_public to get correct field IDs and types.

Troubleshooting

| Problem | Solution | |---------|----------| | Transport closed from MCP | Remove .npm-python inside the qingflow-cli package dir, reinstall, restart WorkBuddy | | Python not found | Set env var QINGFLOW_MCP_PYTHON to a valid Python 3.9+ binary path | | Version mismatch | Reinstall: npm install -g @qingflow-tech/qingflow-cli@latest | | Chinese output garbled in terminal | Pipe --json output to a temp file and read with the Read tool | | auth whoami --json returns empty | Use qingflow auth whoami without --json |