Local & CI companion to the AI Diff Reviewer GitHub Action (DailybotHQ/ai-diff-reviewer). Router for six capabilities — (1) review the current branch diff locally (same methodology as CI); (2) generate repo-tailored .review/extension.md overrides (generate-extension); (3) install and configure the Action, and answer…
★not rated 23▲
+2
changed 3d agoA238 tokens
originalMIT
Read the most recent AI Diff Reviewer review from the current branch's open PR, present the findings in the parent skill's local-review format (verdict, findings table, per-finding body, recommendation), and - with explicit consent - walk the developer through each finding to apply, defer, or skip. Multi-provider…
★not rated 23▲
+2
changed 3d agoC216 tokens
originalMIT
Generates a repo-tailored review-configuration file (.review/extension.md by default, or a full replacement prompt-file in advanced mode) by inspecting THIS codebase — stack, architecture, security surface, existing conventions, historical pain points — and producing concrete, code-anchored severity overrides. Uses…
★not rated 23▲
+2
changed 3d agoA167 tokens
originalMIT
Author a well-documented GitHub pull request — title and body — for the current branch, keeping the branch in sync with the remote base first. Fetches the base, merges origin/ into the current branch when it is behind, resolves merge conflicts, runs the repo's quick validation and pushes the current branch (never…
★not rated 23▲
+2
changed 3d agoD227 tokens
originalMIT
Interactive installer for the AI Diff Reviewer GitHub Action — walks the developer through 6 key decisions (provider, strictness, trigger mode, external-contributor policy, PR description mode, complexity labels), detects the repo's stack for sensible defaults, and writes a working .github/workflows/pr-review.yml…
★not rated 23▲
+2
changed 3d agoA180 tokens
originalMIT
Official Dailybot agent skill pack — report progress, check messages, send emails, announce agent status, complete check-ins, give kudos (to users or teams), resolve teams, run the full forms lifecycle (list, submit, update, transition between workflow states), author check-ins and forms from scratch (create/configure…
★not rated 23▲
+2
changed 3d agoC356 tokens
originalMIT
Ask the Dailybot AI a question from the terminal and read the answer, non-interactively. Runs headless — a single dailybot ask " " prints the assistant's reply to stdout (or structured JSON with --json), so an autonomous agent (Claude Code, CI, a bot) can query the Dailybot AI with only an API key. Use when the…
★not rated 23▲
+2
changed 3d agoA145 tokens
originalMIT
Discover the report channels (Slack/Teams/Discord/Google Chat) available to you via Dailybot, so their UUIDs can be attached to forms and check-ins with --report-channel. Use when the developer needs a channel UUID for form/check-in authoring.
★not rated 23▲
+2
changed 3d agoA58 tokens
originalMIT
Send and edit Dailybot bot messages on the team's connected chat platform (Slack, Microsoft Teams, Discord, Google Chat) — to user DMs, channels, or whole teams. Supports report-style threads (one headline + replies, in one call), interactive buttons (approval flows, workflow triggers, modals, callbacks), and editing…
★not rated 23▲
+2
changed 3d agoA104 tokens
originalMIT
Drive the full check-in lifecycle via Dailybot — list and complete pending check-ins, see pending/completed status for a day, inspect a check-in's questions and schedule, browse response history, edit or reset a submitted response, and backfill or future-date responses. Also authors check-ins — create and configure a…
★not rated 23▲
+2
changed 3d agoA164 tokens
originalMIT
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…
★not rated 23▲
+2
changed 3d agoA111 tokens
originalMIT
Send emails to a confirmed recipient via Dailybot on behalf of the agent. Use for notifications, summaries, follow-ups, or any communication the developer asks you to send. Always confirm recipients with the developer before sending — never guess addresses.
★not rated 23▲
+2
changed 3d agoA51 tokens
originalMIT
List, inspect, submit, update, and transition form responses via Dailybot — including forms with workflow states and audience-scoped permissions. Also authors forms — create and configure a form (workflow states, permissions, anonymous/public/approval, ChatOps command) and manage its questions (types, report titles…
★not rated 23▲
+2
changed 3d agoA125 tokens
originalMIT
STARTER TEMPLATE — do not consume this file in place. Copy it to .agents/skills/dailybot-custom/ /SKILL.md in your own repo, then customize. This is the bootstrap skeleton for authoring a per-form custom skill that the universal dailybot-forms resolver will load from .dailybot/profile.json.
★not rated 23▲
+2
changed 3d agoA76 tokens
originalMIT
Announce agent online/offline status to Dailybot and receive pending messages from the team. Use for long-running or scheduled agents to stay visible and pick up instructions.
★not rated 23▲
+2
changed 3d agoA37 tokens
originalMIT
Give kudos to a teammate or to an entire team via Dailybot to recognize their contributions. Use when the developer wants to thank or recognize one person, or recognize a whole team (e.g. "kudos al equipo Engineering"). Do not use for general progress reports — those go through dailybot-report.
★not rated 23▲
+2
changed 3d agoA67 tokens
originalMIT
Check for pending messages and instructions from your team via Dailybot. Use when starting a work session, when idle, or when asked what to work on next. Messages are instructions that should influence your work.
★not rated 23▲
+2
changed 3d agoA46 tokens
originalMIT
Report work progress to Dailybot. Activate after completing a discrete task or subtask, or after any batch of edits that modifies 3 or more files. Compose a standup-style update describing what changed and why.
★not rated 23▲
+2
changed 3d agoB47 tokens
originalMIT
Read and resolve teams visible to the authenticated user. Use when the developer references a team by name (for kudos targeting, member lookup, or routing context) and an agent needs to obtain its UUID. Other Dailybot skills (kudos, messages) delegate team-name resolution to this skill rather than duplicating the…
★not rated 23▲
+2
changed 3d agoA70 tokens
originalMIT
List, inspect, and trigger Dailybot workflows — enumerate the workflows configured for the organization, read one workflow's configuration, and fire API-triggerable workflows on demand. Use when the developer asks "list my workflows", "show workflows", "what's in the release workflow?", "trigger the deploy workflow"…
★not rated 23▲
+2
changed 3d agoA90 tokens
originalMIT
DeepWorkPlan — turn any repo AI-first and run Deep Work Plans. Routes to create, execute, refine, resume, status, verify, upgrade, and repo-onboarding sub-skills based on intent. Use when the developer wants to plan, execute, manage, or verify structured multi-task work, or make a repository AI-agent-ready.
DeepWorkPlan addon that safely upgrades a repo's dependencies — reasoning about the repo's ACTUAL package manager (npm/pnpm/yarn + ncu, pip/poetry/uv, cargo, go mod, bundler, composer, and more) rather than assuming npm — with a batched, validated, revertible workflow that detects the manager and manifests/lockfiles…
★not rated 23▲
+2
changed 3d agoA188 tokens
originalMIT
Optional DeepWorkPlan addon that gives a repo with a user-facing interface surface a DESIGN.md (under docs/, indexed from AGENTS.md) — a Markdown design-system file any coding agent reads to generate interface output consistent with the repo's OWN conventions. Covers three profiles detected independently from real…
★not rated 23▲
+2
changed 3d agoA287 tokens
originalMIT
Optional DeepWorkPlan addon that gives a repository a reproducible dev container through devcontainer-kit (the dck command, DailybotHQ/devcontainer-kit pinned at v1.0.1, interface 2) - a vendor-neutral thin integrator that detects the kit with dck doctor --json, offers the kit and its tag-pinned dck-dockerfile skill…
★not rated 23▲
+2
changed 3d agoA178 tokens
originalMIT
At most 3 mods per repository are shown here, and a mod shipped inside a plugin is left to that plugin's page — the rest are on their repository pages: