wecom-doc
- Repo stars 3,936
- Author updated Live
- Author repo openclaw-china
- Domain
- Documentation
- Compatible agents
-
- Claude Code
- Cursor
- Cline
- Codex
- Windsurf
- Gemini CLI
- +20
- Trust score
- 88 / 100 · community maintained
- Author / version / license
- @BytePioneer-AI · no license declared
- Token usage
- Lean
- Setup complexity
- Plug-and-play
- External API key
- Not required
- Operating systems
- macOS · Linux · Windows
- Runtime requirements
- No special requirements
- Permissions
-
- Read-only
- Write / modify
- Network behavior
- Local-only
- Install commands
- 26 variants
Profile is derived at build time from SKILL.md and install vectors. Subject to drift from author intent.
Heads up: 未限定 allowed-tools,默认拥有全部工具权限。
---
name: wecom-doc
description: 这个 skill 只负责通过 mcporter 调用企业微信文档 MCP,不要直接调用企业微信 Wedoc API。 先确认 mcporter 可执行。若未安装,提示用户安装;用户同意后执行:…
category: documentation
runtime: no special runtime
---
# wecom-doc output preview
## PART A: Task fit
- Use case: 这个 skill 只负责通过 mcporter 调用企业微信文档 MCP,不要直接调用企业微信 Wedoc API。 先确认 mcporter 可执行。若未安装,提示用户安装;用户同意后执行: npm install -g mcporter 安装完成后继续后续步骤,不要停在中间。 mcporter list wecom-doc --output json runs entirely locally. Works with Claude Code, Cursor, Cline and 23 more..
- Inputs: target material, constraints, expected output, and acceptance criteria.
- Evidence boundary: follow “使用时机 / 前置检查 / 1. 检查 mcporter” and do not present inference as author intent.
## PART B: Execution result
- **01** The card summarizes the use case; runtime output centers on “这个 skill 只负责通过 mcporter 调用企业微信文档 MCP,不要直接调用企业微信 Wedoc API。 先确认 mcporter 可执行。若未安装,提示用户安装;用户同意后执行: npm install -g mcporter 安装完成后继续后续步骤,不要停在中间。 mcporter list wecom-doc --output json runs entirely locally. Works with Claude Code, Cursor, Cline and 23 more.”.
- **02** When the source has headings, the agent prioritizes “使用时机 / 前置检查 / 1. 检查 mcporter” so the result follows the author’s structure.
- **03** Typical output includes task judgment, concrete steps, required commands or file edits, validation, and follow-up options.
- **04** Risk context follows the fingerprint: read files, write/modify files; mostly runs locally; usually needs no extra API key.
## Running Rules
- read files, write/modify files; mostly runs locally; usually needs no extra API key.
- Validate with a small sample before expanding scope.
- Return the result, validation criteria, and next iteration options. The source does not require a stable slash command. After installation, invoke the skill by name and describe the task.
Name target files or source material, expected output, forbidden changes, and whether network or shell access is allowed. Permission fingerprint: read files, write/modify files.
Start with a small task and check whether the result follows “使用时机 / 前置检查 / 1. 检查 mcporter”. Inspect diffs, logs, previews, or tests before expanding scope.
Confirm the final output includes a concrete result, evidence, and next action. If it stays generic, tighten inputs, boundaries, and acceptance criteria.
---
name: wecom-doc
description: 这个 skill 只负责通过 mcporter 调用企业微信文档 MCP,不要直接调用企业微信 Wedoc API。 先确认 mcporter 可执行。若未安装,提示用户安装;用户同意后执行:…
category: documentation
source: BytePioneer-AI/openclaw-china
---
# wecom-doc
## When to use
- 这个 skill 只负责通过 mcporter 调用企业微信文档 MCP,不要直接调用企业微信 Wedoc API。 先确认 mcporter 可执行。若未安装,提示用户安装;用户同意后执行: npm install -g mcport…
- Use it when the task has clear inputs, repeatable steps, and validation criteria.
## What to provide
- Target material, scope, expected result, and forbidden changes.
- Whether network, commands, file writes, or external services are allowed.
## Execution rules
- Organize steps around “使用时机 / 前置检查 / 1. 检查 mcporter” and keep inference separate from source facts.
- read files, write/modify files; mostly runs locally; usually needs no extra API key.
- Validate with a small sample before expanding the task.
## Output requirements
- Return the deliverable, key evidence, validation method, and next action.
- Mark missing information as unknown; do not invent commands, platforms, or dependencies. The author source anchors workflow facts; repository files anchor sources and commands; Fluxly only adds fit, limitations, and quality judgment.
skill "wecom-doc" {
input -> user goal + target files + boundaries + acceptance criteria
context -> 使用时机 / 前置检查 / 1. 检查 mcporter
rules -> SKILL.md triggers / order / output contract
runtime -> no special runtime | read files, write/modify files | mostly runs locally
guardrails -> usually needs no extra API key + small-sample validation + diff/log review
output -> copyable result + checklist + next iteration
} 企业微信文档 MCP
这个 skill 只负责通过 mcporter 调用企业微信文档 MCP,不要直接调用企业微信 Wedoc API。
使用时机
- 用户要创建企业微信文档
- 用户要创建企业微信智能表格
- 用户要编辑机器人创建的企微文档或智能表格
前置检查
1. 检查 mcporter
先确认 mcporter 可执行。若未安装,提示用户安装;用户同意后执行:
npm install -g mcporter
安装完成后继续后续步骤,不要停在中间。
2. 确认 wecom-doc MCP 已配置
先执行:
mcporter list wecom-doc --output json
如果已经能正常返回 tool 列表,直接进入调用阶段。
如果返回 server not found、unknown server 或类似错误,读取:
~/.openclaw/wecomConfig/config.json
检查是否存在 mcpConfig.doc.type 和 mcpConfig.doc.url。若存在,执行:
mcporter config add wecom-doc --type "<type>" --url "<url>"
添加完成后再次执行 mcporter list wecom-doc --output json 进行验证。
3. 自动配置失败时的引导
如果本地没有 mcpConfig.doc,说明当前 wecom 长连接还没成功拉到文档 MCP 配置。此时:
- 如果能读取到
channels.wecom.botId,提示用户去企业微信授权当前机器人文档权限 - 或让用户直接发送
StreamableHttp URL/JSON Config
当用户提供 URL 或 JSON Config 后,提取 url 并执行:
mcporter config add wecom-doc --type streamable-http --url "<url>"
配置完成后重新执行 mcporter list wecom-doc --output json,然后继续用户原始请求。
调用规则
- 所有请求必须通过
mcporter call wecom-doc.<tool> --args '{...}' --output json执行 - 先用
mcporter list wecom-doc --output json读取实际 tool 列表,不要硬编码 tool 名称和参数结构 create_doc返回的docid要保存在当前会话里,后续编辑操作依赖它- 如果用户要编辑已有文档,但当前会话里没有机器人创建时返回的
docid,直接输出:
仅支持对机器人创建的文档进行编辑
文档工作流
新建普通文档
- 调用
create_doc,传doc_type: 3 - 保存返回的
docid - 如需写内容,调用
edit_doc_content
新建智能表格
- 调用
create_doc,传doc_type: 10 - 保存返回的
docid - 根据需要继续调用智能表格相关 tool
错误处理
- 如果
mcporter call返回help_message,优先把其中面向用户的说明直接输出给用户 - 如果返回
850001,说明还需要用户提供配置或授权,按上面的配置引导继续处理 - 如果返回
daemon not running或connection refused,提示用户先执行:
mcporter daemon start
Decide Fit First
Design Intent
How To Use It
Boundaries And Review