wecomcli-preflight

Validates and repairs OpenClaw tool permission configuration before invoking wecom-cli operations.

287|46|Updated Feb 5, 2026
One-click install
npx skills add https://github.com/YanHaidao/wecom --skill wecomcli-preflight-yanhaidao
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: wecomcli-preflight
Source: https://github.com/YanHaidao/wecom/tree/main/skills/wecomcli-preflight
Command: npx skills add https://github.com/YanHaidao/wecom --skill wecomcli-preflight-yanhaidao

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Before any wecom-cli operation can run, the OpenClaw tool permission settings (tools.profile and tools.alsoAllow) must allow the WeCom plugin. This Skill performs that preflight check via shell commands and automatically fixes missing whitelist entries, avoiding the deadlock where an unwhitelisted tool is invisible to the agent. ## Core Features & Use Cases - Permission Detection: Reads tools.profile and tools.alsoAllow via the openclaw CLI to determine whether wecom-cli is permitted. - Automatic Repair: Appends the plugin ID to tools.alsoAllow while preserving existing entries, then prompts the user to restart the Gateway manually. - Failure Guidance: Provides manual fix instructions when automatic configuration fails or the OpenClaw CLI is unavailable. - Use Case: On the first wecom-cli call in a session, or after a permission-denied error, run this check to confirm or restore tool access before proceeding with messaging, contacts, or document operations. ## Quick Start Before calling wecom-cli for the first time, run the preflight check to verify and fix the OpenClaw tool whitelist configuration.

Frequently Asked Questions about wecomcli-preflight

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I fix wecom-cli tool not allowed errors in OpenClaw?

Run openclaw config get tools.alsoAllow to check the whitelist, then add the plugin ID with openclaw config set tools.alsoAllow '["wecom-openclaw-plugin"]'. Restart the Gateway with openclaw gateway restart for the change to take effect.

When should the wecom-cli preflight check run?

Run it on the first wecom-cli call in a session, or whenever a call returns tool not allowed, not permitted, or permission denied errors. Once a call succeeds in the session, the check can be skipped.

Does tools.profile full require a whitelist for wecom-cli?

No. When tools.profile is set to full, all tools including wecom-cli are unrestricted, so the alsoAllow whitelist check is skipped entirely and the original request proceeds directly.

Why does the skill not restart the Gateway automatically?

Restarting the Gateway interrupts all active connections including the current session, so the user might miss the confirmation message. The skill instead prints the restart command for the user to run manually.

Can I run wecom-cli directly with bash or npx if the tool is blocked?

No. The skill explicitly forbids bypassing the dedicated wecom-cli tool via exec, bash, shell, or npx. Permission or configuration problems must be reported and fixed through the whitelist instead.