Agent skill

Wecomcli Doc Manage

by Pinvou in Pinvou/pinvou-agent

何时用:仅当用户明确指向企业微信文档的公共管理(搜索/改名/成员权限/加入规则)时使用;本地文件管理默认走本地工具。适用所有企微文档类型;新建 doc 走 wecomcli-doc、新建在线表格走 wecomcli-sheet、智能表格 CRUD 走 wecomcli-smartsheet、生成智能文档走 wecomcli-smartpage;「看过哪些文档/浏览历史」走本技能。

MITAuto-check passedDocuments & Office

Install Wecomcli Doc Manage

skills CLI
$ npx skills add Pinvou/pinvou-agent --skill wecomcli-doc-manage -a claude-code

Project install by default; add -g for ~/.claude/skills/.

GitHub CLI
$ gh skill install Pinvou/pinvou-agent wecomcli-doc-manage --agent claude-code

Project scope by default; add --scope user for a personal install. Needs GitHub CLI 2.90.0 or later (public preview).

Manual copy
$ git clone --depth 1 https://github.com/Pinvou/pinvou-agent.git skills-src && mkdir -p .claude/skills && cp -r skills-src/pinvou3-app/src-tauri/resources/common/bundle/wecom-skills/wecomcli-doc-manage .claude/skills/wecomcli-doc-manage && rm -rf skills-src

Use ~/.claude/skills/ instead of .claude/skills for a personal install. The folder must contain SKILL.md.

Claude Code skills documentation · loads skills from .claude/skills/

Facts

Skill name
wecomcli-doc-manage
GitHub stars
2.4k
Token cost
~1.7k tokens
SKILL.md length
427 words
Files
4 (incl. references)
Skills in repo
30
Repo updated
First seen
Licence
MIT

At a glance

何时用:仅当用户明确指向企业微信文档的公共管理(搜索/改名/成员权限/加入规则)时使用;本地文件管理默认走本地工具。适用所有企微文档类型;新建 doc 走 wecomcli-doc、新建在线表格走 wecomcli-sheet、智能表格 CRUD 走 wecomcli-smartsheet、生成智能文档走 wecomcli-smartpage;「看过哪些文档/浏览历史」走本技能。

  • Works in 4 steps: 对 query 做中英文分词,得到 token 列表(中文按词切分,英文按空格… → 判定"必传 token":从剩余 token… → 组装 keywords 数组:第 1 个元素是所有"必传… → …
  • Documents & Office work in your project
  • SKILL.md covers 核心概念, 适用范围, 接口路由表 and 接口详述, plus 1 more section
  • Instructions only: no scripts, shell commands, URLs or credentials in SKILL.md

What it does

Wecomcli Doc Manage is an agent skill from Pinvou/pinvou-agent. 何时用:仅当用户明确指向企业微信文档的公共管理(搜索/改名/成员权限/加入规则)时使用;本地文件管理默认走本地工具。适用所有企微文档类型;新建 doc 走 wecomcli-doc、新建在线表格走 wecomcli-sheet、智能表格 CRUD 走 wecomcli-smartsheet、生成智能文档走 wecomcli-smartpage;「看过哪些文档/浏览历史」走本技能。

Its SKILL.md is about 1.7k tokens, which your agent loads only when the skill is triggered. The skill folder holds 4 other files, including reference files (for example `references/doc-members-update.md`, `references/doc-names-update.md` and `references/doc-rules-update.md`).

It sits in Documents & Office. The repository describes itself as: Open-source desktop AI agent for tools, files, knowledge, workflows, and real deliverables. The licence is MIT.

When your agent uses it

  • Documents & Office work in your project

Example prompts

  • “/wecomcli-doc-manage”

Workflow steps

4 steps, taken from the first numbered list in SKILL.md.

  1. 对 query 做中英文分词,得到 token 列表(中文按词切分,英文按空格 / 大小写边界切分),并剔除"帮我"、"找下"、"文档"、"的"等口语化 / 通用 / 停用词。
  2. 判定"必传 token":从剩余 token 中挑出真正承载用户检索意图的核心词(通常是专有名词、产品名、功能名等强区分度词),其余作为辅助 token。
  3. 组装 keywords 数组:第 1 个元素是所有"必传 token"用空格拼接的串(只拼必传的,不要把全部 token 都塞进去),后续元素依次是各单独 token(必传 + 辅助)。例如 query "帮我找下产品的待办tool文档",分词后必传 token 为…
  4. 若必传 token 只有 1 个,第 1 个元素就是该 token 本身,不必重复追加。例如 query "周报" → keywords = ["周报"]。

What it can do on your machine

Read from SKILL.md and the folder at commit 7bba3ef. It shows what the files ask for, not the result of running them.

  • Tool permissions

    Pre-approves nothing: there is no allowed-tools line, so your agent's usual permission prompts apply.

    From allowed-tools in the SKILL.md frontmatter.

  • Runs code

    No scripts in the folder and no shell commands in SKILL.md (its code samples are bash).

    From the folder's file list and the shell code blocks in SKILL.md.

  • Network

    No URLs in SKILL.md.

    From URLs in SKILL.md, links to its own repository left out.

  • Credentials

    Names no API keys, tokens, secrets or passwords.

    From names ending in _API_KEY, _TOKEN, _SECRET, _KEY or _PASSWORD in SKILL.md.

Context cost

Wecomcli Doc Manage loads about 1.7k tokens when it runs, and up to ~2.3k if it reads all its reference files. Until then it costs about 53 tokens; SKILL.md has 427 words of instructions outside code blocks.

Always · name and description, kept in context so the agent knows when to use it
~53
When it runs · the whole SKILL.md, loaded when a task matches
~1.7k
With references · SKILL.md plus every file in references/, read only if the agent opens them
~2.3k

Estimates: characters ÷ 4, the usual rule of thumb; real counts depend on the model's tokenizer. Scripts and assets cost tokens only if the agent reads them.

Safety

Auto-check passed

The automated check found no risky patterns in SKILL.md.

Automated static check — not a guarantee. Review scripts before installing. It scans the text of SKILL.md for risky patterns (piping downloads into a shell, reading credential files, hidden Unicode, destructive commands); files beside SKILL.md are not scanned.

SKILL.md

The full file from Pinvou/pinvou-agent at commit 7bba3ef, republished under its MIT licence (© Pinvou). 427 words, ~1,732 tokens.

Download SKILL.mdSave it as .claude/skills/wecomcli-doc-manage/SKILL.md (or your agent's skills folder). This skill also uses 3 other files; get the full folder from GitHub.
name
wecomcli-doc-manage
description
何时用:仅当用户明确指向企业微信文档的公共管理(搜索/改名/成员权限/加入规则)时使用;本地文件管理默认走本地工具。适用所有企微文档类型;新建 doc 走 wecomcli-doc、新建在线表格走 wecomcli-sheet、智能表格 CRUD 走 wecomcli-smartsheet、生成智能文档走 wecomcli-smartpage;「看过哪些文档/浏览历史」走本技能。

执行任何 wecom-cli 命令前,必须先读取并完成 wecomcli-shared 技能的公共前置检查。

核心概念

  • 四种文档类型:在线文档 doc、在线表格 sheet、智能表格 smartsheet、智能文档 smartpage。doc_type 枚举在多接口中复用。
  • 搜索接口额外支持的类型:收集表 collect、PPT ppt、脑图 mind、流程图 flow、汇报 journal、PDF pdf。这些类型仅在「搜索文档」接口的 doc_types 过滤中可用,其他接口(改名、权限、加入规则等)不适用。

适用范围

适用:

  • 仅支持搜索 doc文档 / 在线表格 / 智能表格 / 智能文档 / PPT / 收集表 / 脑图 / 流程图 / 汇报 / PDF 文档类型
  • 仅支持修改 doc文档 / 在线表格 / 智能表格 / 智能文档 的名称
  • 仅支持添加 doc文档 / 在线表格 / 智能表格 / 智能文档 的成员权限
  • 仅支持设置 doc文档 / 在线表格 / 智能表格 / 智能文档 的加入规则

接口路由表

路由表第二列若是 references/xxx.md 链接 → 必须先用 read 读完该文件,再构造命令。

用户意图参考位置
搜索文档(包含最近浏览/创建)见下方「搜索文档」
修改文档名+names-update
添加文档成员 / 改权限+members-update
设置链接加入规则+rules-update

接口详述

搜索文档

按关键词与过滤条件(类型 / 创建者 / 浏览者-成员 / 时间窗 / 排序)搜索文档

关于"浏览者"与"成员":在本接口的搜索语义下二者等价——visitor_userids 命中的是"该 userid 作为浏览者/成员/相关者"的文档,用来表达"包含 X"、"X 参与的"、"与 X 相关的"、"X 作为成员的"均可。注意权限约束:无论传谁的 userid,最终结果只会返回当前调用者本人有权限访问的文档;他人有权限但你没权限的文档不会出现在结果中,因此本接口不能用于"窥探他人独占的文档列表"。

命令
bash
wecom-cli doc search --json '<JSON 参数>'
参数
字段类型必填默认值语义
keywordsstring[]是—关键词数组,OR 关系。仅按其他条件过滤时传空数组 []
search_scopestring否title_content搜索范围枚举:title(仅标题) / title_content(标题和内容,默认) / content(仅内容)
doc_typesstring[]否—限定类型,取值为 doc / sheet / smartsheet / smartpage / collect / ppt / mind / flow / journal / pdf 的子集
creator_useridsstring[]否—限定创建者 userid 列表(典型:传当前用户 userid 查"我最近创建")
visitor_useridsstring[]否—限定"浏览者 / 成员" userid 列表
created_after / created_beforestring否—创建时间窗,YYYY-MM-DD HH:mm:ss
opened_after / opened_beforestring否—最近打开时间窗,YYYY-MM-DD HH:mm:ss
sort_bystring否best_match排序枚举:best_match(默认) / create_time(创建时间) / modify_time(修改时间)
limitint否10返回上限,不超过 100
cursorstring否—分页游标;首次传空,后续取上页 next_cursor
返回
字段类型说明
has_moreboolean是否还有下一页;true 时用 next_cursor 续取
next_cursorstring下一页游标
docsarray结果文档列表,每项字段见下表

docs[] 单条文档字段:

字段类型说明
docidstring文档唯一 ID
doc_namestring文档名
doc_typestring文档类型
urlstring可访问的文档链接
creator_useridstring文档创建者 userid
create_time / modify_timestring创建 / 最近修改时间
title_highlight / text_highlightstring[]命中高亮片段
Show full SKILL.md (213 more words)Show less
使用规则
  • ppt / journal / collect / mind / flow 目前没有任何下游 skill 或 CLI 能读取正文,命中这些类型且用户要看内容时,直接告知暂不支持读取,引导用户用 doc_url 在企业微信客户端内打开查看。
  • 参数组合按意图分派(含必填约束):先判定用户意图,再按对应分支组装参数。禁止所有参数均不传或仅传空值(如 {})。
    • (a) 按内容找 → keywords(必填,不得为空数组) + search_scope=title_content + sort_by=best_match
    • (b) "我最近浏览 / 与我相关 / 我作为成员 / 包含我的文档" → visitor_userids=[<当前 userid>](必填,不得为空) + sort_by=best_match + opened_after(默认近 7 天)
    • (c) "包含某人为成员 / 某人参与 "(他人)→ visitor_userids=[<他人 userid>](必填,先经 wecomcli-contact 由姓名解析)+ sort_by=best_match;必须提醒用户:只会返回当前调用者有权限访问的那部分文档,对方独占且你无权访问的文档不会出现。
    • (d) "我最近创建" → creator_userids=[<当前 userid>](必填,不得为空) + created_* 时间窗 + sort_by=create_time + created_after(默认近 7 天)
    • 若意图不属于 (b)(c)(d),一律按 (a) 处理,keywords 必填。
  • userid(前缀 wo):用户提供的是姓名时通过 读取 wecomcli-contact 技能 解析为 userid;禁止把姓名当 userid 拼接,禁止凭记忆或猜测编造。
  • keywords 必须先分词再组装:当用户给出自然语言 query(如 "帮我找下产品的待办tool文档")时,禁止把整段 query 直接当成单个 keyword 传入。处理流程:
    1. 对 query 做中英文分词,得到 token 列表(中文按词切分,英文按空格 / 大小写边界切分),并剔除"帮我"、"找下"、"文档"、"的"等口语化 / 通用 / 停用词。
    2. 判定"必传 token":从剩余 token 中挑出真正承载用户检索意图的核心词(通常是专有名词、产品名、功能名等强区分度词),其余作为辅助 token。
    3. 组装 keywords 数组:第 1 个元素是所有"必传 token"用空格拼接的串(只拼必传的,不要把全部 token 都塞进去),后续元素依次是各单独 token(必传 + 辅助)。例如 query "帮我找下产品的待办tool文档",分词后必传 token 为 ["待办", "tool"],则 keywords = ["待办 tool", "待办", "tool"]。
    4. 若必传 token 只有 1 个,第 1 个元素就是该 token 本身,不必重复追加。例如 query "周报" → keywords = ["周报"]。
  • 多候选必须让用户确认:结果 >1 条时,按下方「结果展示规范」展示候选列表,等用户选定后再继续后续动作。
  • 无候选必须追问用户:结果 =0 条时,告知用户当前没有搜到文档,追问用户是否可以提供更多的关键词线索。

示例:用户 query "帮我找下产品的待办tool文档"

剔除"帮我 / 找下 / 的 / 文档"等通用词,剩余 ["产品", "待办", "tool"];判定核心检索意图为 "待办" 与 "tool",故必传 token 为 ["待办", "tool"],"产品" 作为辅助 token。

bash
wecom-cli doc search --json '{"keywords":["待办 tool","待办","tool","产品"],"search_scope":"title_content","limit":10}'
结果展示规范

向用户展示搜索结果(含单条与多候选)时严格遵守:

  • 用 markdown 无序列表逐条展示,禁止使用表格——最多展示10条结果,即使只有 2~3 条结果也用列表;表格会强制四列对齐,反而把 ID / 时间等噪声字段一起暴露。
  • 文档名必须是可点击链接:每条首行写成 - [doc_name](url),url 取接口返回的 url 字段原样使用。
  • 默认不展示创建者:creator_userid 是内部 ID,禁止以任何形式输出给用户。

跨技能依赖

依赖技能典型协作场景数据流向
wecomcli-contact添加文档成员时用户只给姓名,需先解析为 useridwecomcli-contact 的 contact users search → 返回 userid → 本 skill 的 doc members update 接口
需要读取、打开搜索到的docid

拿到 docid 只是第一步。读取/打开文档正文是另一类技能,必须按doc_types,先用 read 读取对应"内容技能"的 SKILL.md,再按其文档发命令:

  • doc(在线文档)→ wecomcli-doc 技能
  • smartpage(智能文档)→ wecomcli-smartpage 技能
  • sheet(在线表格)→ wecomcli-sheet 技能
  • smartsheet(智能表格)→ wecomcli-smartsheet 技能 严禁直接拼"读正文"的命令;首次读取正文前必须先用 read 读取上述对应内容技能的 SKILL.md,命令一律以该 SKILL.md 为准。

搜索多候选需确认 / 搜索意图类确认 / 必填参数(docid、权限角色等)缺失时,用简洁自然语言仅追问缺失或有歧义的信息;有候选项时在文字中列出供用户选择,不得自行猜测。

© Pinvou, MIT. Rendered from Markdown: HTML in the file is shown as text, images as links, and headings moved down two levels. Raw file

Files

SKILL.md and 3 other files (references) in pinvou3-app/src-tauri/resources/common/bundle/wecom-skills/wecomcli-doc-manage of Pinvou/pinvou-agent.

  • SKILL.md
  • references/doc-members-update.md
  • references/doc-names-update.md
  • references/doc-rules-update.md

Open the folder on GitHubat commit 7bba3ef

Compare with similar skills

Wecomcli Doc Manage next to the 5 skills that share the most tags, products or categories with it. Stars are the repository's; “used in” counts other GitHub owners with a copy.

Wecomcli Doc Manage compared with similar skills
SkillStarsUsed inTokensAuto-checkLicenceRepo updated
Wecomcli Doc Manage this skillPinvou/pinvou-agent2.4k—~1.7kAutomated safety check: PassMIT
Markdown Article FormatterJimLiu/baoyu-skills26k6 repos~3.5kAutomated safety check: PassMIT
MarkitdownImCa0/just-laws78214 repos~3.2kAutomated safety check: NotesMIT
Obsidian MarkdownAtmosphere/atmosphere3.8k20 repos~1.3kAutomated safety check: PassApache-2.0
DOCXrvdbreemen/OTGW-firmware20733 repos~4.3kAutomated safety check: PassProprietary
Gzh Designisjiamu/gzh-design-skill3.9k1 repos~2.2kAutomated safety check: PassAGPL-3.0

Similar skills

  • Markdown Article Formatter

    JimLiu/baoyu-skills

    Reformats plain text or Markdown articles with frontmatter, a title, a summary, headings, bold, lists and code blocks, and saves a separate formatted copy.

    26k GitHub starsUsed in 6 repos~3.5k tokens
    Documents & OfficeAuto-check passed
  • Markitdown

    ImCa0/just-laws

    Convert files and office documents to Markdown. An agent skill from ImCa0/just-laws.

    782 GitHub starsUsed in 14 repos~3.2k tokens
    Documents & OfficeAuto-check: notes
  • Obsidian Markdown

    Atmosphere/atmosphere

    Create and edit Obsidian Flavored Markdown with wikilinks, embeds, callouts, properties, and other Obsidian-specific syntax.

    3.8k GitHub starsUsed in 20 repos~1.3k tokens
    Documents & OfficeAuto-check passed
  • DOCX

    rvdbreemen/OTGW-firmware

    A skill your agent uses whenever the user wants to create, read, edit, or manipulate Word documents (.docx files).

    207 GitHub starsUsed in 33 repos~4.3k tokens
    Documents & OfficeAuto-check passed
  • Gzh Design

    isjiamu/gzh-design-skill

    微信公众号文章排版引擎,将 Markdown 转换为可直接粘贴到公众号编辑器的 HTML。主题风格从 references/theme-index.md 注册的自定义主题库中选取,自动章节编号、关键词下划线标记、引言卡片、目录导航、代码块、图片/GIF、作者签名。支持 Markdown / Word(.docx) / PDF / 纯文本输入(非 Markdown…

    3.9k GitHub starsUsed in 1 repo~2.2k tokens
    Documents & OfficeAuto-check passed
  • Reads, creates and edits Word .docx files with python-docx, and drops to raw OOXML for tracked changes, comments and byte-exact edits.

    41k GitHub stars~2.5k tokensUpdated yesterday
    Documents & OfficeAuto-check passed

More from Pinvou/pinvou-agent

All 30 skills in this repo
  • Tmeet Skill

    Pinvou/pinvou-agent

    何时用:用户明确要通过命令行操作腾讯会议(tmeet),或 Agent 遇到工具缺失/调用失败/能力不足想反馈平台时。OAuth 登录/登出/状态、会议管理(创建/更新/取消/查询/搜索/受邀者)、录制管理(列表/播放地址/智能纪要/转写/权限申请)、元宝纪要(按关键词/时间搜索、稳态/瞬态详情)、会议报告(参会人/等候室/导出明细/异步任务)、通讯录(仅限会议邀请/呼叫入会前置解析,严禁单独查…

    2.4k GitHub stars~4.8k tokensUpdated today
    Auto-check passed
  • Wecomcli Doc

    Pinvou/pinvou-agent

    何时用:仅当用户明确指定 doc/docx/word/在线文档/office文档或提供 doc.weixin.qq.com/doc/ 链接时使用;泛指「做个文档/写文档/整理成文档」默认走 wecomcli-smartpage 或本地工具,本技能不得抢占。doc 内容操作:新建、导入(.doc/.docx/.txt)、读取、追加、覆盖写入;结构化数据需求改用智能文档/智能表格;公共管理走…

    2.4k GitHub stars~1.1k tokensUpdated today
    Auto-check passed
  • Dws

    Pinvou/pinvou-agent

    【何时用:仅当用户明确指向钉钉/DingTalk(钉钉文档、钉钉日程等)时使用;泛指做文档/表格/待办/审批默认走本地工具,不要误用钉钉】用 dws CLI 管理钉钉:AI表格/AI搜问(找人首选)/目标管理(Agoal)/组织大脑/日历/通讯录/群聊与机器人消息/待办/审批/考勤/日志(日报周报)/DING消息/钉钉文档/云盘/Markdown文件/AI听记/邮箱/在线电子表格(axls)/知…

    2.4k GitHub stars~5.3k tokensUpdated today
    Auto-check passed
  • Lark Im

    Pinvou/pinvou-agent

    【何时用:仅当用户明确指向飞书/Lark(发到飞书、飞书文档等)时使用;泛指做个文档或PPT或表格或方案默认走本地工具,不要误用飞书】飞书即时通讯:收发消息和管理群聊。发送和回复消息、搜索聊天记录、管理群聊成员、上传下载图片和文件、管理表情回复、发送应用内/短信/电话加急、发送和处理交互卡片(Interactive…

    2.4k GitHub stars~5.9k tokensUpdated today
    Auto-check passed
  • Lark Sheets

    Pinvou/pinvou-agent

    【何时用:仅当用户明确指向飞书/Lark 电子表格;泛指做表格默认走本地工具】创建/操作飞书电子表格:工作表与行列结构、读写单元格(值/公式/样式/批注/图片)、查找替换、批量更新、图表/透视表/条件格式/筛选/迷你图/浮动图片。按名称搜索云空间表格文件改用 lark-drive 的 drive +search。doubao.com 的 /sheets/ URL 也走本 skill。不适用本地…

    2.4k GitHub stars~6.5k tokensUpdated today
    Auto-check passed
  • Lark Base

    Pinvou/pinvou-agent

    【何时用:仅当用户明确指向飞书/Lark(发到飞书、飞书文档等)时使用;泛指做个文档或PPT或表格或方案默认走本地工具,不要误用飞书】飞书多维表格(Base)操作:建表、字段、记录、视图、统计、公式/lookup、表单、仪表盘、BaseApp 应用模式(页面与组件)、Workspace 目录、workflow、角色权限、模板中心(模板分类/列表/搜索);遇到…

    2.4k GitHub stars~4k tokensUpdated today
    Auto-check passed

Questions about Wecomcli Doc Manage

What does Wecomcli Doc Manage do?

何时用:仅当用户明确指向企业微信文档的公共管理(搜索/改名/成员权限/加入规则)时使用;本地文件管理默认走本地工具。适用所有企微文档类型;新建 doc 走 wecomcli-doc、新建在线表格走 wecomcli-sheet、智能表格 CRUD 走 wecomcli-smartsheet、生成智能文档走 wecomcli-smartpage;「看过哪些文档/浏览历史」走本技能。. Wecomcli Doc Manage is an agent skill from Pinvou/pinvou-agent.

When should I use Wecomcli Doc Manage?

Wecomcli Doc Manage fits situations like: documents & Office work in your project.

How do I install Wecomcli Doc Manage in Claude Code?

Run `npx skills add Pinvou/pinvou-agent --skill wecomcli-doc-manage -a claude-code`. Or copy the skill folder (pinvou3-app/src-tauri/resources/common/bundle/wecom-skills/wecomcli-doc-manage in Pinvou/pinvou-agent) into .claude/skills/wecomcli-doc-manage in your project. Claude Code loads it when a task matches its description.

How do I install Wecomcli Doc Manage in Codex?

Run `npx skills add Pinvou/pinvou-agent --skill wecomcli-doc-manage -a codex`. Or copy the skill folder (pinvou3-app/src-tauri/resources/common/bundle/wecom-skills/wecomcli-doc-manage in Pinvou/pinvou-agent) into .agents/skills/wecomcli-doc-manage in your project. Codex loads it when a task matches its description.

Can I use Wecomcli Doc Manage in Cursor, Gemini CLI or GitHub Copilot?

Cursor, Gemini CLI, GitHub Copilot and OpenCode also load SKILL.md folders. With the skills CLI, run `npx skills add Pinvou/pinvou-agent --skill wecomcli-doc-manage -a cursor` (or -a gemini-cli, github-copilot or opencode for the others). To copy it by hand, put the folder in .cursor/skills/wecomcli-doc-manage, .gemini/skills/wecomcli-doc-manage, .github/skills/wecomcli-doc-manage and .opencode/skills/wecomcli-doc-manage in your project.

What does Wecomcli Doc Manage need to run?

SKILL.md names no scripts, command-line tools or credentials: Wecomcli Doc Manage is instructions for the agent only.

Does Wecomcli Doc Manage access the network?

SKILL.md contains no URLs. Any network use would come from the scripts or tools the agent runs. This is read from the text; nothing was executed.

Is Wecomcli Doc Manage safe to install?

Our automated static check of SKILL.md found no risky patterns, such as piping downloads into a shell, reading credential files or hidden Unicode. It is not a guarantee. Review the folder before installing.

What licence does Wecomcli Doc Manage use?

Wecomcli Doc Manage is published under the MIT licence (the repository's licence). It allows redistribution, so the full SKILL.md is shown on this page.

How many tokens does Wecomcli Doc Manage use?

About 1.7k tokens (SKILL.md is roughly 6.9k characters). Agents keep only the skill's name and description in context until a task matches; then they load SKILL.md in full. Its references folder adds about 554 tokens, read only when the agent opens those files.

What are the alternatives to Wecomcli Doc Manage?

Skills that share tags, products or a category with Wecomcli Doc Manage: Markdown Article Formatter (JimLiu/baoyu-skills, 26k stars), Markitdown (ImCa0/just-laws, 782 stars), Obsidian Markdown (Atmosphere/atmosphere, 3.8k stars) and DOCX (rvdbreemen/OTGW-firmware, 207 stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.

Who maintains Wecomcli Doc Manage?

Pinvou (a GitHub organization) maintains it in Pinvou/pinvou-agent, which has 2,401 GitHub stars. The repository holds 30 skills in this directory. The repository was last updated on October 9, 2026.

Source: Pinvou/pinvou-agent on GitHub. Facts on this page come from the repository at the commit we read; the author's words are quoted as theirs.