Before executing any

wecom-cli

command, you must first read and complete the public pre-checks in the

wecomcli-shared

skill.

• List recently viewed files in WeCom Disk
• Search for files or folders in WeCom Disk by keywords/type/creator/shared space
• Read basic information of WeCom Disk files
• Upload local files to a specified folder in WeCom Disk
• Download WeCom Disk files to local device
• Rename WeCom Disk files
• Create new folders in WeCom Disk

• Moving WeCom Disk files or folders → Inform users that this function is not supported yet, and suggest manual operation via the WeCom client
• Deleting/copying WeCom Disk files → Inform users that this function is not supported yet, and suggest manual operation via the WeCom client
• Deleting/renaming WeCom Disk folders (

  folder

  ), adjusting directory tree structure → Inform users that this function is not supported yet, and suggest manual operation via the WeCom client
• Creating/deleting shared spaces (

  space

  ), modifying space members and settings → Inform users that this function is not supported yet, and suggest manual operation via the WeCom client
• Granting a robot permission to a space / adding a robot to shared space members → WeCom Disk does not have this function, which cannot be achieved through any channel (including the client). Prohibit making such suggestions to users, and do not guide users to "contact the space administrator to authorize the robot"
• Modifying file sharing permissions, generating sharing links, revoking sharing, setting access passwords/validity periods → Inform users that this function is not supported yet, and suggest manual operation via the WeCom client
• WeCom Disk file version management (viewing historical versions, restoring old versions, comparing versions) → Inform users that this function is not supported yet
• Undoing/modifying uploaded files (overwrite upload, instant upload, resumable upload) → Inform users that this function is not supported yet; if replacement is needed, re-upload a new file via the "upload file" process
• Parsing the content of WeCom Disk files (text extraction, OCR, image-based Q&A, PDF/Word/Excel parsing, etc.) → This skill is responsible for downloading the file to local device and returning the

  file_path

• Transcribing video/audio files or generating subtitles → Inform users that this function is not supported yet
• Continuously monitoring WeCom Disk changes / real-time notifications for new files → Active monitoring is not possible; do not promise "to notify you when new files arrive", please ask users to initiate a query again later

https://drive.weixin.qq.com/s?k=...

url

get

download

https://doc.weixin.qq.com/<doc|sheet|smartsheet|smartpage>/...

wecomcli-doc

wecomcli-sheet

wecomcli-smartsheet

wecomcli-smartpage

doc

sheet

smartsheet

smartpage

wecomcli-doc-manage

Note:

doc.weixin.qq.com

/

page.weixin.qq.com

are domains for online documents, while

drive.weixin.qq.com

is the domain for WeCom Disk. Do not confuse them.

doc

sheet

ppt

collect

mind

flow

smartsheet

smartpage

journal

pdf

offline_word

offline_excel

offline_ppt

offline_pdf

image

videoaudio

design

offline_

Search both online and offline when ambiguous: When users mention "Excel", "Word", "PPT", "PDF", etc. without specifying online or offline, pass both online and offline versions in

file_types

(e.g.,

["sheet", "offline_excel"]

) to avoid omissions. For other types, pass the corresponding enumeration names as they are.

wecom-cli disk files search --json '{"keywords": ["Quarterly Report"], "search_type": "file", "sort_by": "modify_time", "sort_order": "desc", "limit": 10}'

keywords

keywords

creator_userids

search_type

file_types

creator_userids

userid

keywords

creator_userids

search_type

file_types

userid

wecomcli-contact

search_type

all

all

file

folder

space

keywords

creator_userids

search_type

file_types

file_types

doc

sheet

ppt

collect

mind

flow

smartsheet

smartpage

journal

pdf

offline_word

offline_excel

offline_ppt

offline_pdf

image

videoaudio

design

offline_

keywords

creator_userids

search_type

file_types

space_keywords

sort_by

best_match

best_match

modify_time

file_size

sort_order

desc

asc

desc

sort_by=modify_time

file_size

cursor

next_cursor

limit

has_more

next_cursor

true

next_cursor

files[].id

files[].type

file

folder

space

smartsheet

smartpage

sheet

word

ppt

flow

mind

journal

collect

files[].file_name

files[].file_size

type=file

files[].creator_userid

files[].space_id

files[].space_name

files[].folder_id

space_id

files[].folder_name

files[].path

space_name

folder_name

path

files[].create_time

YYYY-MM-DD HH:mm:ss

files[].update_time

YYYY-MM-DD HH:mm:ss

files[].docid

type=smartsheet

smartpage

sheet

word

ppt

collect

journal

files[].doc_url

files[].title_highlight

type=space

files[].text_highlight

type=space

Critical Constraint for Handling Online Document Matches: If the

type

returned by the search is

smartsheet

/

smartpage

/

sheet

/

word

/

ppt

/

journal

/

collect

/

mind

/

flow

, these are online collaborative documents (content stored in the cloud, not binary files). Prohibit using

disk files download

(will fail or return an empty file), and it is not suitable to use

disk files get

. For

smartsheet

/

smartpage

/

sheet

/

word

, there are corresponding downstream skills to read the content; refer to the Cross-Skill Dependencies table at the end for routing; currently, no downstream skills or CLI can read the content of

ppt

/

journal

/

collect

/

mind

/

flow

. When users want to view the content of these types, directly inform them that content reading is not supported yet, and guide them to open the

doc_url

in the WeCom client. Only when

type=file

can the

id

be used as

file_id

to call

disk files download

to get the local file.

• Trigger Condition (Authoritative Description): Select at least one from

  keywords

  /

  creator_userids

  /

  search_type

  /

  file_types

  ;

  space_keywords

  is only an additional filtering condition and cannot trigger search alone. If all four are empty, ask the user for clarification in natural language before initiating the search. If the user only provides space keywords (e.g., "search in XX space"), ask for specific search content in natural language.
• Inform Truthfully if No Results Found: If no results are found after adjusting keywords/types multiple times, stop searching and inform the user truthfully whether "no files found" or "no such space found"; do not repeatedly change keywords to force a search.
• Optional Parameter Passing Strategy: Default to not passing, only pass when explicitly specified by the user:

  Parameter	When Not to Pass (Backend Default)	When to Pass (Explicitly Expressed by User)
  search_type	User says "search for xxx / find xxx / files / materials" without specifying the object type → Backend uses all	Explicitly says "only search folders / directories"→ folder ; "only search shared spaces / team spaces"→ space ; "only files, no folders"→ file
  sort_by	User has no sorting preference → Backend uses best_match	"Latest / recently modified / earliest"→ modify_time ; "Largest / smallest"→ file_size
  sort_order	Not required when sort_by=best_match	Use desc for new→old and asc for old→new when passing modify_time / file_size ; default to desc if not passed
  file_types	User says "documents / files / materials / resources" or business concepts (contracts / reports / meeting minutes) → No filtering, rely on keywords	User explicitly mentions specific formats (PPT / Excel / PDF / images / smart spreadsheets, etc.), add the corresponding enumerations to the array
  space_keywords	No space restriction	User says "search in XX space / XX team disk" → Fill in space name keywords (this interface does not accept space_id )

• Do Not Mix File Type Suffixes in

  keywords

  : When users say "search for Excel reports" or "find PPT plans", pass the file type suffixes (Excel/PPT/Word/PDF) to

  file_types

  for filtering, and only keep business keywords in

  keywords

  (e.g., "reports" / "plans"). Example: "Excel report" →

  keywords:["report"]

  +

  file_types:["sheet","offline_excel"]

  .
• Spoken Language → Enumeration Mapping for

  file_types

  : Refer to the "User Spoken Expression" column in the File Type Enumeration table above.
• Pagination Continuation: Use

  next_cursor

  as the

  cursor

  for the next call when

  has_more=true

  ; pass an empty string for

  cursor

  in the first call.
• Time Range Filtering Not Supported: This interface does not have

  begin_time

  /

  end_time

  fields; do not forge them. If users provide time ranges such as "last 3 days / last week / this month", first retrieve data with

  sort_by=modify_time

  ,

  sort_order=desc

  , then perform secondary filtering on the client side based on

  update_time

  .
• Result Summary Order Follows Sorting Direction: When

  sort_order=desc

  (default, new→old), summarize results for users from newest to oldest, do not reverse the order.

file_content_media

media_id

file_path

wecom-cli disk files upload --json '{"folder_id": "FOLDER_ID", "file_name": "Quarterly Report.pptx", "file_content_media": "mcxxx"}'

wecom-cli disk files upload --json '{"folder_id": "FOLDER_ID", "file_name": "Quarterly Report.pptx", "file_path": "/tmp/Quarterly Report.pptx"}'

folder_id

file_id

space_id

file_name

/ \ : * ? " < > |

file_path

file_name

file_content_media

file_content_media

media_id

mc

file_content_media

file_path

file_path

file_content_media

file_path

file.id

file.file_name

file.docid

type=smartsheet

smartpage

sheet

word

ppt

collect

journal

file.type

file.file_size

type=file

file.creator_userid

file.space_id

file.space_name

file.folder_id

file.folder_name

file.create_time

file.update_time

file.path

file.doc_url

file_content_media

media_id

media upload

1. Confirm

   folder_id

   : If not provided by the user, do not pass it to upload to the default space
2. Directly fill the existing

   media_id

   into

   file_content_media

   and call

   disk files upload

file_path

1. Can be used directly when the user explicitly provides a local file path (or a preceding skill returns a local

   file_path

   , such as the path after downloading via

   disk files download

   )
2. Confirm

   folder_id

   : If not provided by the user, do not pass it to upload to the default space
3. Directly fill the local path into

   file_path

   and call

   disk files upload

   (no need to go through

   wecomcli-media

   )

Mutually Exclusive: Only one of

file_content_media

and

file_path

can be selected, cannot pass both or neither. If the user provides neither

media_id

nor local file path, ask for clarification in natural language; do not fabricate a file through search/illusion.

wecom-cli disk files download --json '{"file_id": "FILE_ID"}'

file_id

file_id

url

url

file_id

url

file_id

url

file_id

url

file_path

file_content

size

• Only Applicable to Offline Binary Files: Only files with

  type=file

  (corresponding to

  offline_word

  /

  offline_excel

  /

  offline_ppt

  /

  offline_pdf

  /

  image

  /

  videoaudio

  /

  design

  in

  file_types

  ) can be downloaded to local device via this interface.
• Never Use Download for Online Documents: If the

  type

  returned by the search is

  smartsheet

  /

  smartpage

  /

  sheet

  /

  word

  /

  ppt

  /

  journal

  /

  collect

  /

  mind

  /

  flow

  , prohibit passing their

  id

  or

  doc_url

  as

  file_id

  /

  url

  to this interface, which will fail or return an invalid file. For

  smartsheet

  /

  smartpage

  /

  sheet

  /

  word

  , use the

  docid

  to route to the corresponding downstream document skills according to the Cross-Skill Dependencies table at the end to read content; currently, no downstream skills can read the content of

  ppt

  /

  journal

  /

  collect

  /

  mind

  /

  flow

  , directly inform users that this is not supported yet, and guide them to open the

  doc_url

  in the WeCom client.
• URL Format Identification: Only

  https://drive.weixin.qq.com/s?k=...

  is a WeCom Disk file sharing URL, which can be used as the

  url

  parameter;

  https://doc.weixin.qq.com/...

  /

  https://page.weixin.qq.com/...

  are online document links, prohibited from being passed to this interface.

wecom-cli disk files rename --json '{"file_id": "FILE_ID", "new_name": "New File Name.xlsx"}'

file_id

new_name

/ \ : * ? " < > |

status

"success"

This interface does not return a

file

object; to retrieve the latest metadata, call "Read File Information" again.

• File Name is Not

  file_id

  : When the user provides a file name/keyword, first use

  disk files search

  to get the

  file_id

  ; do not directly use the file name as

  file_id

  .
• Upload Material Source Constraint: Choose one of

  file_content_media

  and

  file_path

  for

  upload

  , one must be provided, cannot pass both.

  file_content_media

  must be a valid

  media_id

  (prefix

  mc

  ), do not construct or guess it;

  file_path

  can only be a real local file path explicitly provided by the user or returned by a preceding skill, do not fabricate it. If neither is available, ask for clarification in natural language; do not fabricate a file through search/illusion.
• Search Must Be Bounded: Adjust conditions once if necessary after a set of searches; stop and inform users "no results found" after 2~3 rounds of unsuccessful searches, and ask users to provide more accurate keywords/file types/creators; do not keep changing keywords to force a search.
• Convey CLI Errors as They Are: If the command returns a clear error code, inform users truthfully and provide alternative suggestions; do not bypass the CLI using curl/python or other general methods to force completion.
• Do Not Expose Internal IDs: Internal IDs such as

  creator_userid

  /

  space_id

  /

  folder_id

  /

  file_id

  /

  docid

  are only used for subsequent interface calls; prohibit directly displaying them to users; if need to display creator information for

  creator_userid

  , first resolve it to a name via

  wecomcli-contact

  .
• Ask for Clarification When Spaces/Folders Have the Same Name: If the search returns multiple spaces or folders with the same name, ask users to select the specific target in natural language; do not randomly select the first one or guess.
• Ask for Clarification When Parameters Are Missing / Multiple Candidates / Intent is Unclear: Ask users to clarify in natural language, do not guess.

list

search

• Display item by item using markdown unordered lists, prohibit using tables — display a maximum of 10 items.
• First line of each item: If the returned

  doc_url

  is not empty (online document), write it as a markdown link in the format

  - [File Name](doc_url)

  ; if

  doc_url

  is empty (offline files, folders, spaces, etc.), write it as

  - File Name

  , do not fabricate links. Secondary lines can display

  path

  /

  update_time

  / readable

  file_size

  (e.g.,

  2.4 MB

  ), separate fields with

  ·

  or spaces.
• Prohibit directly displaying raw JSON, internal IDs such as

  creator_userid

  /

  space_id

  /

  folder_id

  /

  id

  .

wecomcli-doc

type=word

doc

docid

wecom-cli doc 'contents get'

docid

a1_

b1_

wecomcli-smartpage

wecomcli-sheet

type=sheet

docid

wecomcli-sheet

wecomcli-smartsheet

type=smartsheet

docid

wecomcli-smartsheet

wecomcli-smartpage

type=smartpage

type=word

docid

a1_

b1_

docid

wecomcli-smartpage

wecomcli-doc-manage

wecomcli-doc-manage

rename

folder

When parameters are missing / multiple candidates / intent is unclear, ask users to clarify in natural language.