Setup
Set up the Dailybot plugin — install the CLI, authenticate, and configure the agent profile. Use on first install or when setup needs to be redone.From its SKILL.md
npx -y skills add DailybotHQ/dailybot-claude-plugin --skill setupAssembled from the repository path, not quoted from the project. Check it against their README if it does not work.
One thing to look at
- 1 stars1 stars. Stars are a popularity signal and not a quality one, but at this level it is likely that nobody has read this closely except its author, and you would be relying on your own review.
SKILL.md
1.9 KB, as published. Nobody here has run it
Dailybot Setup
Walk the user through first-time setup for the Dailybot plugin. This skill handles CLI installation, authentication, and agent profile configuration in one guided flow.
When to Use
- The user just installed the plugin and wants to get started
- The user says "set up Dailybot", "connect Dailybot", or "configure Dailybot"
- Another skill failed because the CLI is missing or auth is broken and the user wants to fix it
Setup Flow
Read and follow every step in ${CLAUDE_PLUGIN_ROOT}/shared/auth.md. That file covers:
- CLI installation — check if
dailybotis installed, guide throughpip install dailybot-cliif not - Authentication — OTP login flow, API key alternative, or self-registration
- Agent profile — ensure a default agent profile exists
Present one step at a time. Do not dump all instructions at once.
After Setup Completes
Once all three steps pass, confirm:
"Dailybot is ready. Here's what you can do:
/dailybot:report— send a progress update to your team/dailybot:messages— check for pending messages/dailybot:email— send an email through Dailybot/dailybot:health— announce agent statusProgress reports are also sent automatically when you complete significant work."
If Setup Fails
If any step fails and the user can't or won't resolve it:
- Tell them what's missing (CLI, auth, or profile)
- Let them know the plugin's skills won't work until setup is complete
- Offer to try again later — don't loop
Non-Blocking Rule
Setup should never block the user's primary work. If they came here from another task, get back to it after setup completes or is skipped.