Token导航 LogoToken导航TokenDH.com
开发只读clawhub未标认证来源可访问clear审计通过

multi-account-config多帐户配置

Agent Skill

multi-account-config 用于补充开发相关能力,适合在 OpenClaw 中需要让 Agent 承接开发相关任务时使用。可结合来源仓库、安装命令和原始 README 继续核验具体用法。安装前建议确认权限范围、维护状态,以及是否会触发联网、命令执行或文件读写。

总安装

8,059

周安装

326

GitHub Stars

公开资料未说明

下载量

2,530
OpenClaw

安装说明

本站只整理中文说明和来源信息,不托管安装包,也不代用户安装。

GitHub

来源数

2

许可证

MIT-0

最后核验

2026-05-01

来源状态

来源可访问

安装方式

通过对话安装

复制提示词发给支持本地命令或 Skills 的 AI 助手,先确认命令和权限,再让它执行。

请帮我安装这个 Agent Skill:multi-account-config(多帐户配置)
来源仓库:https://github.com/devilsen/multi-account-config
安装命令:
openclaw skills install multi-account-config
安装前请先检查当前环境是否支持对应 CLI,并向我确认将要执行的命令、安装目录、联网范围和文件读写权限;确认后再执行。

命令行安装

复制命令到本机终端执行。该命令会通过 OpenClaw 从第三方来源获取 Skill;本站只展示命令,不托管安装包,也不自动执行。

ClawHubOpenClaw
openclaw skills install multi-account-config

简介

为 OpenClaw 配置多个消息平台帐户。当用户想要添加或配置 Telegram、WhatsApp、Discord 等其他帐户时使用

SKILL.md

name
multi-account-config
description
Configure multiple messaging platform accounts for OpenClaw. Use when the user wants to add or configure additional accounts for Telegram, WhatsApp, Discord, or other supported channels. Triggers on requests like "configure multiple accounts", "add another telegram bot", "setup multi-account", "add work account", etc.

Multi-Account Configuration

Guide users through configuring multiple accounts for messaging platforms in OpenClaw.

Supported Platforms

  • Telegram
  • WhatsApp
  • Discord
  • Slack
  • Signal
  • Other OpenClaw-supported channels

Workflow

Step 1: Identify Platform

Ask the user which platform they want to configure:

"你想配置哪个平台的多账号?支持的选项:Telegram、WhatsApp、Discord、Slack、Signal 等。"

Step 2: Collect Account Information

For each account, collect:

  1. Account ID/Name - A short identifier (e.g., "work", "personal", "friendA")
  2. Platform-specific credentials:

- Telegram: Bot Token (from @BotFather) - WhatsApp: Pairing code or existing credentials - Discord: Bot Token - Slack: Bot Token - Signal: Phone number

Suggest meaningful names based on use case:

  • "work" - 工作相关
  • "personal" - 个人使用
  • "side-project" - 副业项目
  • "family" - 家人群组

Step 3: Get Current Config

Use gateway config.get to retrieve current configuration.

Step 4: Build Updated Config

Structure the configuration following this pattern:

{
  "bindings": [
    {
      "agentId": "main",
      "match": {
        "channel": "<platform>",
        "accountId": "<account-id>"
      }
    }
  ],
  "channels": {
    "<platform>": {
      "enabled": true,
      "accounts": {
        "<account-id>": {
          "name": "<Display Name>",
          "enabled": true,
          "dmPolicy": "allowlist",
          "allowFrom": ["<user-id>"],
          "botToken": "<token>",
          "groupPolicy": "open",
          "streaming": "block"
        }
      }
    }
  }
}

Step 5: Apply Configuration

Use gateway config.patch to apply the new configuration.

Step 6: Verify

Confirm the configuration was applied successfully and provide next steps.

Configuration Schema Reference

Bindings

Each account needs a binding entry:

{
  "agentId": "main",
  "match": {
    "channel": "telegram",
    "accountId": "work"
  }
}

Account Properties

PropertyTypeDescription
namestringDisplay name for the account
enabledbooleanWhether the account is active
dmPolicystring"allowlist", "blocklist", or "open"
allowFromarrayList of allowed sender IDs (for allowlist)
botTokenstringPlatform-specific token
groupPolicystring"open", "closed", or "admin-only"
streamingstring"block" or "allow"

Example: Adding Telegram Work Account

User provides:

  • Platform: Telegram
  • Account name: work
  • Bot Token: 123456:ABC-DEF...

Configuration to add:

{
  "bindings": [
    {
      "agentId": "main",
      "match": {
        "channel": "telegram",
        "accountId": "work"
      }
    }
  ],
  "channels": {
    "telegram": {
      "enabled": true,
      "accounts": {
        "work": {
          "name": "Work",
          "enabled": true,
          "dmPolicy": "allowlist",
          "allowFrom": ["USER_ID"],
          "botToken": "123456:ABC-DEF...",
          "groupPolicy": "open",
          "streaming": "block"
        }
      }
    }
  }
}

Important Notes

  1. Preserve existing accounts - When adding new accounts, merge with existing config
  2. Get user ID from context - Use the current user's sender ID for allowFrom
  3. Validate tokens - Ensure tokens are complete and properly formatted
  4. Restart required - Configuration changes require gateway restart to take effect
  5. Security - Never log or expose tokens in responses

适合场景

01

OpenClaw 用户查找和安装 Skill 时

02

用户想查找某类 Agent Skill 时

03

需要根据任务场景推荐可安装能力包时

04

需要对比不同来源的安装命令和来源信息时

能力概览

能力 1

按任务关键词查找相关 Skills

能力 2

展示可复制的安装命令

能力 3

保留来源站点、仓库和原始说明,方便继续核验

能力 4

补充不同宿主或平台的使用分布数据

能力 5

展示第三方安全扫描或审计结果

安装后应在对应宿主中按原始 README 的触发条件使用;具体调用方式请以来源页面和 README 为准。

平台分布

OpenClaw

87.77%
按下载量换算2,221

安全审计

VirusTotal

通过

ClawScan

通过

Static analysis

通过

权限和风险

只读

该 Skill 主要提供规则、说明或参考内容,本身偏只读;真正读写文件、联网或执行命令仍取决于宿主 Agent 的任务。

安装前确认

本站仅展示第三方公开信息,不托管安装包,不提供自动安装或运行环境。安装前应自行审查源码、依赖和命令行为。当前只有一个来源,正式发布前建议补源仓库或其他目录站核验。

来源信息

继续浏览同类 Skills