dailybot
Original:🇺🇸 English
Translated
1 scripts
Official Dailybot agent skill pack — report progress, check messages, send emails, and announce agent status. Routes to the right sub-skill based on intent. Use when the developer mentions Dailybot or wants to interact with their team.
7installs
Sourcedailybothq/agent-skill
Added on
NPX Install
npx skill4agent add dailybothq/agent-skill dailybotTags
Translated version includes tags in frontmatterSKILL.md Content
View Translation Comparison →Dailybot
Dailybot connects AI coding agents to their human team. This is a skill pack with four capabilities — each one lives in its own sub-skill with detailed instructions.
Your job: Determine which capability the developer needs, then read and follow the corresponding sub-skill.
documentation_url
vs. the skill pack
documentation_urlThe in frontmatter points to . That URL is the public API reference (HTTP endpoints and curl examples). It is not the GitHub skill pack (router, , sub-skills, ).
documentation_urlhttps://api.dailybot.com/skill.mdshared/setup.sh- OpenClaw: Install the pack with , or clone
openclaw skills install dailybotintohttps://github.com/DailybotHQ/agent-skill.<workspace>/skills/dailybot/ - skills.sh / npx: from any supported agent.
npx skills add DailybotHQ/agent-skill - Do not treat downloading only as a full install — agents need the complete repository or registry install.
api.dailybot.com/skill.md
Dailybot CLI: Before any API call, ensure the CLI exists (). If missing, follow the consent flow in — the universal install script ( with SHA-256 verification) handles macOS / Linux / WSL / Docker / CI by auto-detecting the OS internally. Native Windows users get a PowerShell variant. skips the interactive prompt for CI and power users. HTTP API with is the last-resort fallback when no CLI can run.
command -v dailybotshared/auth.mdcurl … install.shDAILYBOT_AUTO_YES=1DAILYBOT_API_KEYAvailable Skills
| Skill | Directory | What it does |
|---|---|---|
| Report | | Send progress updates after completing a task/subtask or editing 3+ files |
| Messages | | Check for pending messages and instructions from the team |
| Send emails to any address via Dailybot | |
| Health | | Announce agent online/offline status and receive messages |
Routing Rules
Match the developer's intent to the right skill and read that skill's SKILL.md to execute it. Do not answer directly — the sub-skill has the full workflow.
| Developer says... | Route to |
|---|---|
| "report this to Dailybot", "send a Dailybot update", "let my team know what we built" | Report → read |
| "check messages", "do I have messages?", "what should I work on?", "any instructions?" | Messages → read |
| "email this to Alice", "send an email", "send a summary to the team" | Email → read |
| "go online", "announce status", "health check", "check in with the team" | Health → read |
Auto-activation (no explicit request)
| Situation | Route to |
|---|---|
| You completed a task/subtask, or edited 3+ files | Report → read |
| Starting a long work session or idle for 15+ minutes | Health → read |
If the intent is ambiguous, default to Report — it's the most common use case.
Shared Resources
All sub-skills reference these shared files for common operations:
- — authentication (CLI login, API key, agent registration, profile setup)
shared/auth.md - — automated repo/branch/agent context detection
shared/context.sh - — HTTP API patterns for when the CLI is unavailable
shared/http-fallback.md
Per-Repo Opt-Out
Before any outbound call, sub-skills check for a file in
the working repository root. If present, the skill exits silently and no data
leaves the machine. See for the implementation and
for how developers turn this on.
.dailybot/disabledshared/context.shREADME.mdNon-Blocking Rule
All Dailybot operations must never block your primary work. If the CLI is missing, auth fails, the network is down, or any command errors:
- Warn the developer briefly
- Continue with the primary task
- Do not retry automatically
- Do not enter a diagnostic loop