chore(skills): sync vendored dailybot skill pack to v3.11.0#77
Conversation
## Summary Dogfood sync of .agents/skills/dailybot/ to DailybotHQ/agent-skill v3.11.0 — documents interactive chat buttons (approvals, workflow triggers, modals, callbacks) and workflow trigger, and raises the pack CLI floor to dailybot-cli >= 3.8.0. ## Change Log - Sync all vendored SKILL.md / shared docs to v3.11.0 - Bump pack version + CLI floor in AGENTS.md and skills_agents_catalog.md - docker/local/cli: raise the dev-container CLI floor to >=3.8.0 ## Risks - None at runtime — vendored docs + local dev tooling only; no source or packaging changes [skip release] Co-authored-by: Cursor <cursoragent@cursor.com>
AI review for
|
There was a problem hiding this comment.
Clean dogfood sync — approve. This is exactly the AGENTS.md §15.a case (a) skill-pack sync it claims to be: .agents/skills/dailybot/ → v3.11.0, baseline dailybot-cli >= 3.7.0 → >= 3.8.0, plus the catalog, AGENTS.md pack reference, and the local dev-container floor in docker/local/cli/Dockerfile. Per the repo review overrides I reviewed the sync intent and consistency rather than the upstream skill internals.
What I verified
- Version frontmatter is uniform. All 16
SKILL.mdfiles carryversion: "3.11.0"— no straggler left at3.10.3. - Baseline bump is complete and consistent. Every user-facing
Requires dailybot-cli >= 3.7.0line moved to>= 3.8.0(router, ask, channels, chat, checkin, conversation, email, env, forms, health, kudos, messages, report/hooks, teams, workflow, and the sharedauth.md/dashboard-urls.md/env-json.md/list-query-and-errors.mdreferences). - Historical “shipped in 3.7.0” facts are correctly preserved (e.g.
env-json.md“New in 3.7.0”,SKILL.md“per-repo credentials (from 3.7.0)”, thev3.7.2kudos-fix link). These are dated provenance, not baseline claims, and were rightly left untouched. - New content is internally coherent. The chat
Buttonsexpansion, the new error-code rows inlist-query-and-errors.md, and theworkflow triggersurface cross-reference each other consistently (--filter api_trigger,callback_workflow,workflow_not_triggerable,workflow_trigger_payload_invalid, thebutton_*codes). Dialogues renumber cleanly A–H and workflow steps 1–7 with no gaps or duplicates. - Docker floor coherence.
docker/local/cli/Dockerfilemoved from>=3.7.2to>=3.8.0, matching the new pack baseline. Thecurl … install.sh | … bashline is pre-existing (only theDAILYBOT_VERSIONenv var changed) and already documents its safety rationale, so it is not a newly-introduced pipe-to-shell path. [skip release]usage is correct for this diff shape per AGENTS.md §15.a case (a) — releasing would push the CLI past the pack's freshly-pinned floor and re-trigger the sync loop.
Findings table
| # | Severity | File | Summary |
|---|---|---|---|
| — | — | — | No blocking or warning-level issues found. |
Non-blocking observation (off-diff, not actionable here)
· .agents/skills/dailybot/SKILL.md:54 still reads “Thirteen coordinated capabilities” while the capability table below it has 14 rows. This line is not in this PR's diff and the mismatch pre-dates this sync (no capability row was added here — only the Workflows/Forms/env rows were reworded), so it is an upstream-pack artifact to fix at the source, not in this dogfood sync.
Recommendation: approve
Summary
.agents/skills/dailybot/toDailybotHQ/agent-skill**v3.11.0`workflow trigger/--filter api_triggerdailybot-cli >= 3.8.0(matches CLI 3.8.0 already onmain)AGENTS.md+.agents/docs/skills_agents_catalog.mddocker/local/cli/Dockerfileto>=3.8.0Why
[skip release]This is AGENTS.md §15.a case (a) — skill-pack dogfood sync only. Releasing would bump the CLI past the pack's pinned floor and re-trigger an infinite sync loop.
When squash-merging, put this on its own line in the squash commit body:
Test plan
.agents/skills/dailybot/, catalog,AGENTS.md, anddocker/local/cli/Dockerfile.agents/skills/dailybot/SKILL.mdfrontmatter showsversion: "3.11.0"and baseline>= 3.8.0workflow triggerauto-release.ymllogs "Release skipped on author request"Made with Cursor