Agent skill · Testing & QA

agent-testing-bot

Bot-channel end-to-end verification for LobeHub — drives the real native chat apps (Discord / Slack / Telegram / WeChat / Lark / QQ / iMessage) via osascript or the iMessage bridge, on macOS. Extends the generic agent-testing skill for bot surfaces. Triggers on 'test bot', 'bot test', 'test in discord', 'test in telegram', 'test in slack', 'test in wechat', 'test in weixin', 'test in lark', 'test in feishu', 'test in qq'.

LobeHub80,937★ · +310/wk · 1 repos on radarProfile →
claude-codeships scriptsNOASSERTION
Install
npx skills add lobehub/lobehub --skill agent-testing-bot --agent claude-code

Same command for any agent — swap --agent for codex, cursor, copilot.

Facts
Files in the skill folder: 16
SKILL.md size: 4 KB
Bundled scripts: yes
Path: .agents/skills/agent-testing-bot/SKILL.md
Open the folder on GitHub →
Where it comes from
Stars: 81,252 · +315 this week
Language: TypeScript
Read our review of the source →

Weekly change comes from our own snapshots, not the repository page — it measures attention, not adoption.

From the SKILL.md

# Agent Testing — Bot Channels (LobeHub project skill) This skill **extends** the generic `agent-testing` skill (installed alongside at `../agent-testing/`) to the bot-channel surfaces. It does NOT replace the core process: the same three phases apply — ```text PLAN (Steps 0–2) → EXECUTE (Steps 3–6) → FINISH (Step 7) ``` — and the same report + publish pipeline (`result.json` → `report-init.sh` → `lh acceptance run ingest … --source agent-testing`). Read the generic skill's `SKILL.md` for target grounding, the living logs, the Phase-1 approval gate, the report format, and teardown. This file only adds the bot-channel surface. For LobeHub environment/auth/probe specifics (dev server, seeded account, ports), the adapter is `.agents/acceptance/PROJECT.md`. ## When this surface applies | Change scope | Surface | Why | | ---------------------------------------------- | --------------------------------- | ------------------------------------------------ | | **Bot channels** (Discord / WeChat / Lark / …) | Native app via osascript / bridge | Only way to exercise the real channel end-to-end | Route here only when the behavior under test is a bot channel. For CLI / Web / Electron changes, u

What's inside
Steps it walks through
  1. When this surface applies
  2. Platforms
  3. Shared driver contract
  4. osascript prerequisites
  5. Screen-recording gate (macOS-only)
Ships with 15 files
  • discord/index.md
  • discord/test-discord-bot.sh
  • imessage/index.md
  • imessage/send-imessage-test.sh
  • imessage/test-imessage-bridge.sh
  • lark/index.md
  • lark/test-lark-bot.sh
  • qq/index.md
  • qq/test-qq-bot.sh
  • slack/index.md
  • slack/test-slack-bot.sh
  • telegram/index.md
  • telegram/test-telegram-bot.sh
  • wechat/index.md
  • wechat/test-wechat-bot.sh
More from lobehub
All skills →
About this skill
What does the agent-testing-bot skill do?

Bot-channel end-to-end verification for LobeHub — drives the real native chat apps (Discord / Slack / Telegram / WeChat / Lark / QQ / iMessage) via osascript or the iMessage bridge, on macOS. Extends the generic agent-testing skill for bot surfaces. Triggers on 'test bot', 'bot test', 'test in discord', 'test in telegram', 'test in slack', 'test in wechat', 'test in weixin', 'test in lark', 'test in feishu', 'test in qq'.

How do I install it?

Run `npx skills add lobehub/lobehub --skill agent-testing-bot --agent claude-code` — it drops the skill into your project so the agent can pick it up. Swap the --agent value for codex, cursor or copilot if you use one of those.

Where does this skill come from?

From lobehub/lobehub, a repository with 81,252 stars. We read it straight from the repository tree rather than a submitted listing, so what you see here is what is actually published.

Is a popular skill a good skill?

Not necessarily. Stars measure attention, not adoption — a repository can trend for a week and be abandoned. That is why we show the weekly change from our own snapshots next to the total, instead of a single flattering number.

Keep going