remote-approval-config

Manage remote approval configurations across Feishu, DingTalk, and WeCom.

6|Updated Feb 26, 2026
One-click install
npx skills add https://github.com/Acosmi/CrabClaw --skill remote-approval-config
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: remote-approval-config
Source: https://github.com/Acosmi/CrabClaw/tree/main/docs/skills/tools/system/remote-approval-config
Command: npx skills add https://github.com/Acosmi/CrabClaw --skill remote-approval-config

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Manage remote approval configurations across Feishu, DingTalk, and WeCom via a dedicated gateway action.

Core Features & Use Cases

  • Centralized control of remote approval settings including enabled flags, callback URLs, and provider-specific patches.
  • Supports get to read current config and baseHash, set to update with hash validation, and test to verify provider connectivity.
  • Use Case: When your org needs to enable or disable remote approvals and validate connectivity across multiple providers from a single control point.

Quick Start

Query the current remote approval configuration with action=get to retrieve the latest baseHash, then apply updates with action=set using that baseHash.

Frequently Asked Questions about remote-approval-config

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

FAQPage Schema
How do I manage remote approval configurations across Feishu, DingTalk, and WeCom centrally?

You can manage remote approval configurations across Feishu, DingTalk, and WeCom centrally via a dedicated gateway action that controls enabled flags, callback URLs, and provider-specific patches from a single control point.

What is the best way to update remote approval settings without causing conflicts?

The best way to update remote approval settings safely is using the set action with baseHash validation, ensuring you first retrieve the latest baseHash via the get action to prevent configuration conflicts.

Can I test connectivity for remote approvals across multiple enterprise messaging providers?

Yes, you can test connectivity for remote approvals across multiple enterprise messaging providers using the dedicated test action to verify that your Feishu, DingTalk, and WeCom pipelines are correctly configured.

Does remote approval configuration support applying patches to specific providers?

Yes, remote approval configuration supports applying provider-specific patches, allowing you to customize enabled flags and callback URLs for individual providers like Feishu, DingTalk, or WeCom independently.

Why do I need a baseHash when setting remote approval configurations?

You need a baseHash when setting remote approval configurations to enable hash-based safe updates, ensuring that your set action does not overwrite changes made by others since your last get action.