跳至正文
OpenAgentSkill
浏览已开放 · 目录记录日期 2026-11-21 · 自动更新和账户服务暂时关闭。
开发与测试

dailybot-conversation

Open (or idempotently reuse) a private Slack group DM (MPIM) that includes the Dailybot bot, then optionally post a message or report to it. Use when the developer wants to start a Slack group with specific teammates plus the bot — e.g. "open a group DM with Jane and Bob and send them the analysis report". Slack only, org-admin only. Distinct from dailybot-chat (which posts to existing channels/DMs) and dailybot-channels (which discovers report-channel UUIDs).

DailybotHQ · 已有 AI 审核记录

安装与使用

运行命令前先阅读来源与依赖说明。复制命令不会自动安装或执行。

npx skills add DailybotHQ/deepworkplan-skill --skill dailybot-conversation

技能说明


name: dailybot-conversation description: Open (or idempotently reuse) a private Slack group DM (MPIM) that includes the Dailybot bot, then optionally post a message or report to it. Use when the developer wants to start a Slack group with specific teammates plus the bot — e.g. "open a group DM with Jane and Bob and send them the analysis report". Slack only, org-admin only. Distinct from dailybot-chat (which posts to existing channels/DMs) and dailybot-channels (which discovers report-channel UUIDs). version: "3.13.0" documentation_url: https://www.dailybot.com/skill.md user-invocable: true metadata: {"openclaw":{"emoji":"👥","homepage":"https://dailybot.com","requires":{"anyBins":["dailybot","curl"]},"primaryEnv":"DAILYBOT_API_KEY","install":[{"id":"cli-install-script","kind":"download","url":"https://cli.dailybot.com/install.sh","label":"Install Dailybot CLI (official script — preferred on Linux/macOS)"},{"id":"pip","kind":"pip","package":"dailybot-cli","bins":["dailybot"],"label":"Install Dailybot CLI via pip (fallback if binary fails)"}]}} allowed-tools: Bash, Read, Grep, Glob

Dailybot Conversations

Requires dailybot-cli >= 3.9.0 (the skill-pack baseline; the dailybot conversation open command itself shipped in 3.2.0). If dailybot --version reports lower, ask the developer to run dailybot upgrade and continue with your primary task meanwhile. See ../SKILL.md § Required Dailybot CLI version.

You help developers open a private Slack group DM (MPIM) that includes the Dailybot bot plus one or more teammates, and — in the same step — optionally post a message or report to that group. Opening is idempotent: the same set of participants always returns the same channel, so "open it, or reuse the existing one" is a single call. This is the natural first half of "start a group with Jane and Bob and send them the report."

This is distinct from dailybot-chat (which sends to an already-known channel, DM, or team) and from dailybot-channels (which lists report-channel UUIDs for form/check-in authoring). If the developer already has a channel id and just wants to post, route to chat. If they want to create/obtain a group of people, start here.


When to Use

  • "Open a group DM with Jane and Bob" / "start a Slack group with the release team and the bot"
  • "Open a group with <user> and send them this report / analysis / summary"
  • "Get me a channel with these three people so the bot can post there"
  • Any flow that needs a group channel id before posting — this command returns it (creating the group if needed, reusing it if it already exists)

Do not use this for posting to an existing channel/DM (→ chat), for discovering report channels (→ channels), or on non-Slack orgs (the command returns a clear "Slack only" error).


Auth model & permissions

POST /v1/open-conversation/ accepts either an org API key (X-API-KEY) or a login Bearer token (dailybot login) — the CLI prefers the API key and falls back to the Bearer token, the same header logic as chat send. Two server-enforced gates:

GateRuleOn failure
PlatformSlack only406 open_conversation_not_supported → "Group conversations are only supported for Slack workspaces."
RoleOrganization admin only403 → "This command requires organization admin privileges."

Never re-implement these checks client-side; surface the server's decision and fall back to the non-blocking rule.


Step 1 — Verify Setup

Follow ../shared/auth.md, then confirm a credential exists:

dailybot status --auth >/dev/null 2>&1 || { echo "Run: dailybot login"; exit 3; }

If auth fails or the developer declines, skip and continue your primary task.


Step 2 — Resolve the Participants

Participants can be named three ways — the CLI resolves them for you:

You passFlagResolution
A user UUID-u <uuid>used as-is (no directory lookup)
An email-e me@example.com or -u me@example.comresolved via GET /v1/users/
A name-u "Jane Doe"resolved via GET /v1/users/ (unique match required)
  • --user / -u (alias --users) and --email / -e (alias --emails) are both repeatable and accept comma-separated values.
  • The org directory is fetched only when at least one identifier is not a bare UUID, so an all-UUID call skips the extra round-trip.
  • Duplicates are dropped (first occurrence wins); order is preserved.
  • Email/name resolution needs the directory to expose that person — email lookup is admin/manager-gated server-side. If a name is ambiguous, the CLI lists the matches so you can disambiguate. When unsure who the developer means, confirm before opening the group.

The bot is added automatically — you do not pass the bot as a participant. One human participant already makes a valid group with the bot.

Participant limit

Slack group DMs (MPIMs) support at most 8 total members. The Dailybot bot always occupies one slot, so you can pass at most 7 user UUIDs / emails / names. The CLI rejects more than 7 before making the API call; the server also validates and returns 400 conversation_too_many_participants if the limit is exceeded.


Step 3 — Open the Conversation (idempotent)

# By UUID (no directory lookup)
dailybot conversation open -u <uuid1> -u <uuid2>

# By name / email (resolved via the org directory)
dailybot conversation open -u "Jane Doe" -u bob@example.com

# Headless: capture the channel id for scripting / a follow-up send
CH=$(dailybot conversation open -u <uuid1> -u <uuid2> --json | jq -r .channel)

The response is { "channel": "<slack-conversation-id>" } (human output shows a panel with the channel + participant names). Idempotent — calling again with the

阅读完整来源 ↗