WPS Knowledge Base

Problem

WPS Knowledge Base targets agent work where cloud notes, folders, and enterprise spaces are too fragmented for local search alone. It wraps the kwiki-cli Skills Hub API into command-line actions, so an assistant can respond to intents such as 'knowledge base', 'ask the knowledge base', or 'organize documents'.

How It Works

• Knowledge management: knowledge-view-list, knowledge-view-get, knowledge-view-share-link, and knowledge-view-update cover listing, inspecting, sharing, and editing spaces.
• AI Q&A: knowledge-view-ask targets one or more kuid values, aggregates text/event-stream SSE into a single JSON object by default, and supports --web-search, --switch-thinking, or --stream for raw output.
• File workflows: file-list, file-create, file-rename, file-move, file-upload, file-download, file-import, and file-convert handle traversal, creation, moving, uploading, downloading, cloud document import, and md -> otl conversion.
• Safety controls: write operations require a token; --account supports multiple profiles, OS keyring is preferred, and --dry-run can print the planned request for higher-risk commands.

Boundaries

This skill targets WPS/zhishi cloud knowledge bases, not the current editor workspace or local disk search. kuid prefixes such as 0s and 0l encode spaces versus files/folders, but personal and enterprise identifiers use different rules, so do not treat enterprise suffixes as drive_id. OTL smart documents cannot be downloaded via file-download, and deleted items move to a recovery window in the trash.