diff --git a/.agents/skills/dailybot/SKILL.md b/.agents/skills/dailybot/SKILL.md index 9753d31..37cff99 100644 --- a/.agents/skills/dailybot/SKILL.md +++ b/.agents/skills/dailybot/SKILL.md @@ -1,7 +1,7 @@ --- name: dailybot -description: 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 questions, workflow states, permissions, reminders, scheduling, AI settings, sharing), send/edit chat messages on the team's Slack/Teams/Discord/Google Chat (including report-style threads and sending as a user's identity), open (or reuse) a Slack group DM with the bot and post a report to it, ask the Dailybot AI a question headlessly, **and browse/read the workspace** — who am I / my org / a user's profile (`me` / `org` / `user get`), browse the kudos feed + the org-wide feed + wall of fame, and list/read workflows, all with shared pagination / search / date-range filters. Routes to the right sub-skill based on intent. Use when the developer mentions Dailybot or wants to interact with their team. -version: "3.4.0" +description: 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 questions, workflow states, permissions, reminders, scheduling, AI settings, sharing), send/edit chat messages on the team's Slack/Teams/Discord/Google Chat (including report-style threads and sending as a user's identity), open (or reuse) a Slack group DM with the bot and post a report to it, ask the Dailybot AI a question headlessly, **and browse/read the workspace** — who am I / my org / a user's profile (`me` / `org` / `user get`), browse the kudos feed + the org-wide feed + wall of fame, and list/read workflows — all with shared pagination / search / date-range filters. Also **manages per-repo API keys** through the opt-in `.dailybot/env.json` file (dailybot env add/use/show/list/remove/off/on — CLI 3.7.0+) so a developer can be "logged into different orgs in different repos" simultaneously. Routes to the right sub-skill based on intent. Use when the developer mentions Dailybot or wants to interact with their team. +version: "3.10.3" 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)"}]}} @@ -30,7 +30,8 @@ no network fetch is required** to know what to do. Run first-run setup in order: the `dailybot` CLI is the integration surface. If it is missing, follow [`shared/auth.md`](shared/auth.md) — it proposes the checksum-verified installer and installs **only after the developer confirms**. Confirm with - `dailybot --version` (minimum `>= 3.1.2` for the whole pack). + `dailybot --version` (minimum `>= 3.7.0` — the skill-pack baseline for + every sub-skill). 2. **Authenticate.** `dailybot login` (email OTP) **or** set `DAILYBOT_API_KEY` — see [`shared/auth.md`](shared/auth.md). Credentials are stored owner-only (`0600`) and masked in all output. @@ -67,6 +68,7 @@ Thirteen coordinated capabilities, with smart routing between them: | **Forms** | `dailybot-forms` | List, submit, update, or transition forms — including workflow-state forms with audience permissions (`form list` is now **org-scoped** by default, with `--mine` to narrow to your own; list + responses support pagination / search / date filters) — **plus authoring**: create/configure a form (workflow states, permissions, anonymous/public/approval, ChatOps command) and manage its questions | | **Workflows** | `dailybot-workflow` | Developer wants to **read** the org's workflows — `workflow list` (paginated/searchable) and `workflow get`. Read-only; writes are web-app only. Plan-gated | | **Report channels** | `dailybot-channels` | Discover report-channel UUIDs to attach to forms/check-ins with `--report-channel` | +| **Per-repo API keys** | `dailybot-env` | Configure `.dailybot/env.json` — an **opt-in, gitignored** file that carries API keys + URLs for one or more environments (live, local, staging) so the developer can be "logged into different orgs in different repos". `dailybot env add / use / show / list / remove / off / on`. CLI >= 3.7.0 | ## Install @@ -84,9 +86,10 @@ reporting, ships **inside this skill** — follow **[Start here (first run)](#st ## Required Dailybot CLI version -> **Minimum: `dailybot-cli >= 3.1.2`.** This is the baseline for the entire skill -> pack — every sub-skill assumes it. Install or upgrade to at least 3.1.2 before -> using any command below. +> **Baseline: `dailybot-cli >= 3.7.0`** for **every** sub-skill in the pack — +> one single floor, no per-sub-skill exceptions. Recommended install / upgrade +> target: **latest release** — `dailybot upgrade` (or `pip install +> --upgrade dailybot-cli`) always satisfies it. > > Requires **Python >= 3.10**. The wheel is `py3-none-any` (pure Python), MIT-licensed. > @@ -100,18 +103,25 @@ reporting, ships **inside this skill** — follow **[Start here (first run)](#st ### Why this minimum -`3.1.2` is the line in the sand: from this release on, the skill pack and the CLI -move together, and the pack no longer tracks per-feature version floors. If -`dailybot --version` reports below 3.1.2, the sub-skills may reference commands, -flags, or error codes that don't exist yet — ask the developer to run -`dailybot upgrade` (or `pip install --upgrade 'dailybot-cli>=3.1.2'`). +`3.7.0` is the release that completed the auth story this pack relies on: +the `env` sub-skill's `dailybot env` command group and `.dailybot/env.json` +per-repo credentials (with the wire-preference guarantee that a repo-local +key beats the global Bearer session), the hardened refuse-if-tracked guard, +and every earlier surface the pack documents (reporting, hooks, chat, forms +and check-in authoring, kudos, teams, workflows, `ask`, the shared list +query flags, and the machine-readable error codes). Pinning one single +floor keeps agent behavior predictable — no per-sub-skill version matrix. + +If `dailybot --version` reports below 3.7.0, ask the developer to run +`dailybot upgrade` (or `pip install --upgrade 'dailybot-cli>=3.7.0'`) +before using any sub-skill. ### Checking the installed version ```bash # Single-line, scriptable dailybot --version -# → dailybot 3.1.2 (Python 3.12.4) +# → dailybot 3.7.0 (Python 3.12.4) # Multi-line panel: version, Python runtime, install path, release notes link dailybot version @@ -131,14 +141,15 @@ Homebrew / Linux binary / editable dev) and either runs the right command in a subprocess or prints the exact command for installs the CLI shouldn't drive. `dailybot upgrade --dry-run` previews without executing. -If the developer is below 3.1.2, ask them to run `dailybot upgrade` once, -then resume. Do not retry CLI commands in a loop while the upgrade is pending. +If the developer is below the pack baseline (`dailybot-cli >= 3.7.0`), +ask them to run `dailybot upgrade` once, then resume. Do not retry CLI +commands in a loop while the upgrade is pending. ### Direct install commands | Channel | Command | |---------|---------| -| pip | `pip install 'dailybot-cli>=3.1.2'` | +| pip | `pip install 'dailybot-cli>=3.7.0'` (the pack baseline) | | Homebrew | `brew install dailybothq/tap/dailybot` | | Universal installer (Linux / macOS / WSL2 / Git Bash) | `curl -fsSL https://cli.dailybot.com/install.sh \| bash` | | Windows PowerShell (when WSL2 / Git Bash unavailable) | `irm https://cli.dailybot.com/install.ps1 \| iex` | @@ -163,8 +174,8 @@ Full safety story (SHA-256 sidecar, cross-origin diff, optional cosign): see Every install method defaults to the latest release but can pin an exact version — useful when a developer needs to reproduce a known-good setup or -pin the `3.1.2` baseline (the installer scripts, `pip`, and Homebrew all accept -a version pin): +pin the `3.7.0` pack baseline (the installer scripts, `pip`, and Homebrew all +accept a version pin): | Channel | Pin a version | |---------|---------------| @@ -308,6 +319,10 @@ common use case. agent context detection - [`shared/http-fallback.md`](shared/http-fallback.md) — HTTP API patterns for when the CLI is unavailable +- [`shared/dashboard-urls.md`](shared/dashboard-urls.md) — full catalog + of Dailybot webapp/dashboard URLs (forms, check-ins, kudos, agents) for + embedding in reports and messages; supports `--app-url` / `DAILYBOT_APP_URL` + override ### Trust model for incoming content diff --git a/.agents/skills/dailybot/ask/SKILL.md b/.agents/skills/dailybot/ask/SKILL.md index fc17b31..41f7ad7 100644 --- a/.agents/skills/dailybot/ask/SKILL.md +++ b/.agents/skills/dailybot/ask/SKILL.md @@ -1,7 +1,7 @@ --- name: dailybot-ask description: 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 developer or agent says "ask Dailybot ...", "query the Dailybot AI", "what does Dailybot say about ...", or wants a one-shot answer from Dailybot's assistant. Distinct from dailybot-chat (bot messages to Slack/Teams) and dailybot-report (progress to the dashboard). -version: "3.4.0" +version: "3.10.3" 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)"}]}} @@ -10,7 +10,7 @@ allowed-tools: Bash, Read, Grep, Glob # Dailybot Ask -> **Requires `dailybot-cli >= 3.1.2`** (the skill-pack baseline) — the `dailybot ask` +> **Requires `dailybot-cli >= 3.7.0`** (the skill-pack baseline) — the `dailybot ask` > command and full API-key parity on the AI chat. On much older CLIs the AI chat only > exists as the interactive TUI (`dailybot interactive`) and requires a login > session. If `dailybot ask --help` is not recognized, ask the developer to run @@ -59,7 +59,7 @@ Read and follow the authentication steps in [`../shared/auth.md`](../shared/auth The AI chat accepts **either** a login session **or** an org API key — an agent with only `DAILYBOT_API_KEY` set can use `dailybot ask` directly. -Confirm the command exists (`dailybot-cli >= 3.1.2`): +Confirm the command exists (`dailybot-cli >= 3.7.0`): ```bash dailybot ask --help 2>&1 | head -1 diff --git a/.agents/skills/dailybot/channels/SKILL.md b/.agents/skills/dailybot/channels/SKILL.md index 3136633..825edb1 100644 --- a/.agents/skills/dailybot/channels/SKILL.md +++ b/.agents/skills/dailybot/channels/SKILL.md @@ -1,7 +1,7 @@ --- name: dailybot-channels description: 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. -version: "3.4.0" +version: "3.10.3" 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)"}]}} @@ -10,9 +10,9 @@ allowed-tools: Bash, Read, Grep, Glob # Dailybot Report Channels -> **Requires `dailybot-cli >= 3.1.2`** (the skill-pack baseline). The `dailybot channels list` +> **Requires `dailybot-cli >= 3.7.0`** (the skill-pack baseline). The `dailybot channels list` > command is available at this floor. If `dailybot --version` reports below -> 3.1.2, ask the developer to run `dailybot upgrade`. See +> 3.7.0, ask the developer to run `dailybot upgrade`. See > [`../SKILL.md` § Required Dailybot CLI version](../SKILL.md#required-dailybot-cli-version). Report channels are the Slack / Microsoft Teams / Discord / Google Chat diff --git a/.agents/skills/dailybot/chat/SKILL.md b/.agents/skills/dailybot/chat/SKILL.md index d36d7cb..76a2218 100644 --- a/.agents/skills/dailybot/chat/SKILL.md +++ b/.agents/skills/dailybot/chat/SKILL.md @@ -1,7 +1,7 @@ --- name: dailybot-chat description: 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) and editing the parent or any reply afterward. Use when the developer says "send a message to my Slack channel", "ping the team in chat", "post the deploy report to #releases", or wants to update a previously sent bot message. Works headless for agents. -version: "3.4.0" +version: "3.10.3" 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)"}]}} @@ -10,7 +10,7 @@ allowed-tools: Bash, Read, Grep, Glob # Dailybot Chat -> **Requires `dailybot-cli >= 3.1.2`** (the skill-pack baseline). The `dailybot chat send` / `chat update` command group, the `--thread-message` flag (≤10 replies per call, each independently editable), the login-Bearer auth path on `/v1/send-message/` (send without an org API key), and `--send-as-user` / `--send-as-me` (admin-only) are all available. If `dailybot --version` is below 3.1.2, ask the developer to run `dailybot upgrade`. See [`../SKILL.md` § Required Dailybot CLI version](../SKILL.md#required-dailybot-cli-version) for install commands and version-check tooling. +> **Requires `dailybot-cli >= 3.7.0`** (the skill-pack baseline). The `dailybot chat send` / `chat update` command group, the `--thread-message` flag (≤10 replies per call, each independently editable), the login-Bearer auth path on `/v1/send-message/` (send without an org API key), and `--send-as-user` / `--send-as-me` (admin-only) are all available. If `dailybot --version` is below 3.7.0, ask the developer to run `dailybot upgrade`. See [`../SKILL.md` § Required Dailybot CLI version](../SKILL.md#required-dailybot-cli-version) for install commands and version-check tooling. You send **Dailybot bot messages** on the developer's behalf to the organization's connected chat platform (Slack, Microsoft Teams, Discord, Google Chat) — to user DMs, channels, or whole teams (expanded to member DMs server-side). This skill is the right surface for: diff --git a/.agents/skills/dailybot/checkin/SKILL.md b/.agents/skills/dailybot/checkin/SKILL.md index 4a71246..1a5b213 100644 --- a/.agents/skills/dailybot/checkin/SKILL.md +++ b/.agents/skills/dailybot/checkin/SKILL.md @@ -1,7 +1,7 @@ --- name: dailybot-checkin description: 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 check-in (schedule, participants, reminders, privacy, smart/AI) and manage its questions (types, report titles, variations, conditional logic). Works headless with an API key. Use when the developer asks to fill in their standup, answer daily questions, check what check-ins they have, edit or reset a check-in, review past responses, or create/configure a check-in. Do not use for free-text progress reports — those go through dailybot-report. -version: "3.4.0" +version: "3.10.3" 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)"}]}} @@ -285,11 +285,11 @@ prompts — handy for humans; agents should use the headless commands above. ## Step 3.7 — Authoring check-ins (create / configure / questions) -> **Requires `dailybot-cli >= 3.1.2`** (the skill-pack baseline). The authoring surface — `checkin create`, +> **Requires `dailybot-cli >= 3.7.0`** (the skill-pack baseline). The authoring surface — `checkin create`, > `checkin config`, `checkin archive`, the `checkin questions add|edit|delete|reorder` > group, resolving people by email, the smart/AI flags, and the **create requires > ≥ 1 question** rule (`questions_required`) — is all available. If -> `dailybot --version` is below 3.1.2, run `dailybot upgrade`. +> `dailybot --version` is below 3.7.0, run `dailybot upgrade`. Everything above **answers** a check-in. This section **builds** one. As of the authoring release, an agent can create a check-in from scratch, tune every @@ -297,10 +297,11 @@ scheduling / reminder / privacy / AI setting, manage its questions (including conditional jump logic), verify the result with a round-trip read, and archive it — all headless with an API key. -> **Role-gated.** Creating, configuring, or archiving a check-in and editing its -> questions are **admin/manager** operations server-side. With a plain-member -> credential these calls fail with a `401`/`403` — surface that to the developer -> and stop (don't retry). Answering check-ins (Steps 2–3.5) is not gated this way. +> **Role-gated.** Configuring, archiving a check-in, and editing its questions +> are **admin/manager** operations server-side. **Creating** a check-in is now +> allowed for **any authenticated member**. +> Update and delete remain admin/manager only. Answering check-ins (Steps 2–3.5) +> is not role-gated. ### Create in one shot vs. configure incrementally @@ -865,5 +866,6 @@ Check-in completion must **never block your primary work**. If the CLI is missin - [`../shared/auth.md`](../shared/auth.md) — authentication setup - [`../shared/http-fallback.md`](../shared/http-fallback.md) — HTTP API fallback patterns +- [`../shared/dashboard-urls.md`](../shared/dashboard-urls.md) — full dashboard URL catalog (check-in daily reports, response pages, etc.) - **Live API spec:** `https://api.dailybot.com/api/swagger/` - **Full agent API skill:** `https://www.dailybot.com/skill.md` diff --git a/.agents/skills/dailybot/conversation/SKILL.md b/.agents/skills/dailybot/conversation/SKILL.md index b6206fc..eb017a2 100644 --- a/.agents/skills/dailybot/conversation/SKILL.md +++ b/.agents/skills/dailybot/conversation/SKILL.md @@ -1,7 +1,7 @@ --- 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.4.0" +version: "3.10.3" 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)"}]}} @@ -10,11 +10,10 @@ allowed-tools: Bash, Read, Grep, Glob # Dailybot Conversations -> **Requires `dailybot-cli >= 3.2.0`** — the release that introduced the -> `dailybot conversation open` command (and `form list --mine`). The rest of the -> pack works from the `>= 3.1.2` baseline, but this sub-skill's command does not -> exist below 3.2.0: if `dailybot --version` reports lower, ask the developer to -> run `dailybot upgrade` and continue with your primary task meanwhile. See +> **Requires `dailybot-cli >= 3.7.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](../SKILL.md#required-dailybot-cli-version). You help developers **open a private Slack group DM (MPIM)** that includes the @@ -98,6 +97,14 @@ Participants can be named three ways — the CLI resolves them for you: > 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) @@ -170,6 +177,7 @@ Match on the machine-readable `code` (with `--json`), never the prose `detail`. |------|--------|------------------------| | 406 | `open_conversation_not_supported` | Org is not on Slack. Tell the developer group DMs are Slack-only; stop. | | 403 | — | Caller is not an org admin. Explain the command needs admin rights. | +| 400 | `conversation_too_many_participants` | More than 7 users passed (8 total including the bot). Reduce the list. | | 400 | `one_or_more_users_not_found` | A participant isn't an active org user. Re-check the names/UUIDs. | | 400 | `no_valid_users` | The list contained invalid UUIDs. Fix the identifiers. | | 400 | `params_validation_error` | `users_uuids` wasn't a list — a CLI usage error; re-run with `-u`. | @@ -231,4 +239,5 @@ automatically, and do not enter a diagnostic loop. - [`../teams/SKILL.md`](../teams/SKILL.md) — resolve a person's UUID by name - [`../shared/auth.md`](../shared/auth.md) — authentication setup - [`../shared/http-fallback.md`](../shared/http-fallback.md) — HTTP API fallback patterns +- [`../shared/dashboard-urls.md`](../shared/dashboard-urls.md) — full dashboard URL catalog - **Full agent API skill:** `https://www.dailybot.com/skill.md` diff --git a/.agents/skills/dailybot/email/SKILL.md b/.agents/skills/dailybot/email/SKILL.md index f08fb44..9770a81 100644 --- a/.agents/skills/dailybot/email/SKILL.md +++ b/.agents/skills/dailybot/email/SKILL.md @@ -1,7 +1,7 @@ --- name: dailybot-email description: 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. -version: "3.4.0" +version: "3.10.3" documentation_url: https://www.dailybot.com/skill.md user-invocable: false 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)"}]}} @@ -12,7 +12,7 @@ allowed-tools: Bash, Read, Grep, Glob You send emails on behalf of the developer's agent through Dailybot. Useful for notifications, summaries, follow-ups, weekly reports, or any communication that should be delivered as email. -> **Requires `dailybot-cli >= 3.1.2`** (the skill-pack baseline). See [`../SKILL.md` § Required Dailybot CLI version](../SKILL.md#required-dailybot-cli-version). +> **Requires `dailybot-cli >= 3.7.0`** (the skill-pack baseline). See [`../SKILL.md` § Required Dailybot CLI version](../SKILL.md#required-dailybot-cli-version). --- diff --git a/.agents/skills/dailybot/env/SKILL.md b/.agents/skills/dailybot/env/SKILL.md new file mode 100644 index 0000000..70a65d7 --- /dev/null +++ b/.agents/skills/dailybot/env/SKILL.md @@ -0,0 +1,168 @@ +--- +name: dailybot-env +description: Manage per-repo API key overrides in `.dailybot/env.json` — an opt-in, gitignored file that carries API keys + optional URLs for one or more environments (live, local, staging). One profile is active at a time; when set, it overrides `DAILYBOT_API_KEY`, `config.json`, and the login Bearer session for the enclosing repo. Use when the developer wants to be "logged into different orgs in different repos" simultaneously, needs a local dev key just for this project, or wants to toggle between staging and prod without touching global config or env vars. Requires CLI >= 3.7.0. +version: "3.10.3" +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 per-repo API key override (`env.json`) + +> **Requires `dailybot-cli >= 3.7.0`** — the `dailybot env` command group and the `.dailybot/env.json` loader are new in that release. If `dailybot --version` reports below 3.7.0, ask the developer to run `dailybot upgrade` before continuing. See [`../SKILL.md` § Required Dailybot CLI version](../SKILL.md#required-dailybot-cli-version). + +This sub-skill lets an agent configure and manage `/.dailybot/env.json` — an **opt-in, gitignored** file that pins API keys + URL overrides per environment (live, local, staging) for the enclosing repo. When a profile is *active*, it overrides `DAILYBOT_API_KEY`, `config.json`, and the login Bearer session **only for that repo**. + +> **The full workflow, schema, security rules, and worked examples live in [`../shared/env-json.md`](../shared/env-json.md).** Read it first — it is the single source of truth. This file is the routing entry-point and quick-reference. + +## When to use + +Route here when the developer says any of: + +- *"I want a local API key just for this project."* +- *"How do I test against staging without breaking my prod login?"* +- *"Can I be in org A in this repo and org B in another repo?"* +- *"Set up per-project Dailybot credentials for me."* +- *"Switch this repo to my localhost Dailybot instance."* + +**Do not** route here when: + +- The developer is in CI. Use `DAILYBOT_API_KEY` as an env var — leaves no on-disk secret. +- The developer wants team-shared *identity* (agent name, default metadata). That's `.dailybot/profile.json` — see [`../shared/repo-profile.md`](../shared/repo-profile.md). +- The developer has one Dailybot org and a working login session. `dailybot login` + global config is simpler. + +## Pre-flight — before writing anything + +1. **Confirm the CLI supports `env`** (>= 3.7.0): + + ```bash + dailybot env --help >/dev/null 2>&1 || { + echo "This feature requires dailybot-cli >= 3.7.0. Run: dailybot upgrade" >&2 + exit 1 + } + ``` + +2. **Ensure the repo's `.gitignore` covers `.dailybot/*`.** The Dailybot skill pack expects this pattern: + + ```gitignore + .dailybot/* + !.dailybot/profile.json + ``` + + If missing, add it (creating `.gitignore` if needed): + + ```bash + grep -q '^\.dailybot/\*' .gitignore 2>/dev/null || cat >> .gitignore <<'EOF' + + # Dailybot per-repo state (env.json contains API keys — never commit it) + .dailybot/* + !.dailybot/profile.json + EOF + ``` + + If the developer skips this step and later commits `env.json`, the CLI will refuse to load it and print an actionable error. `dailybot env add` also fires a soft warning when the file isn't gitignored yet. + +## The commands (quick reference) + +```bash +# CREATE a profile (creates the file if needed; first profile auto-becomes active) +dailybot env add --name NAME --key KEY [--api-url URL] [--app-url URL] + +# SWITCH active profile +dailybot env use NAME # switch active +dailybot env use "" # clear active (fall through to global auth) + +# INSPECT +dailybot env show # resolved profile (API key masked) +dailybot env list # all profiles, active marked + +# DELETE +dailybot env remove NAME [--yes] + +# KILL SWITCH (preserves active) +dailybot env off # disable the file +dailybot env on # re-enable +``` + +All API keys are masked in output (`sk_l****`). The CLI never echoes the full key back. + +## Common recipes + +### First-time setup for a local dev org + +```bash +dailybot env add \ + --name local \ + --key sk_local_xxxxxxxx \ + --api-url http://localhost:8000 \ + --app-url http://localhost:8090 + +dailybot env show # verify +``` + +Because this is the first profile, it becomes active automatically. Every subsequent `dailybot` command in this repo now talks to `http://localhost:8000`. Other repos are unaffected. + +### Toggle between staging and prod + +```bash +dailybot env add --name prod --key sk_prod_xxxx # first → auto-active +dailybot env add --name staging --key sk_staging_yyyy \ + --api-url https://staging-api.example.com + +dailybot env use staging # switch to staging for bug repro +# ... work in staging ... +dailybot env use prod # switch back +``` + +### Temporarily disable env.json without losing setup + +```bash +dailybot env off # env.json ignored; CLI falls through to global auth +# ... test something with your global login ... +dailybot env on # restores the previously active profile +``` + +`env off` sets `disabled: true` at the top level; `active` is preserved so `env on` instantly restores the previous selection. + +### Delete a profile + +```bash +dailybot env remove staging --yes +# If 'staging' was active, active is cleared and the CLI falls back to +# global auth until you run `dailybot env use ` again. +``` + +## Security — what an agent must never do + +1. **Never `cat` or otherwise print raw `env.json`.** It contains API keys. Use `dailybot env show` / `dailybot env list` — they mask. +2. **Never suggest committing `env.json`.** The CLI has a fatal `RepoEnvError` guard that fires on load if the file is tracked. +3. **Never write API keys into `.dailybot/profile.json`.** That is a hard error in the CLI. `env.json` is the ONLY sanctioned place inside `.dailybot/` for credentials. +4. **If the developer accidentally committed `env.json`**: tell them to rotate every key immediately (assume compromise), then `git rm --cached` + fix `.gitignore` + rewrite `env.json` with newly generated keys. Do NOT try to `git filter-repo` the leak away — assume the world has seen the keys. + +Full four-layer protection story (gitignore, `0o600`, fatal refuse-if-tracked, write-time gitignore warning): see [`../shared/env-json.md` § Security](../shared/env-json.md#security--non-negotiable-rules). + +## Interaction with existing auth (short version) + +| Existing flow | Effect when env.json is active in this repo | +|---|---| +| `dailybot login` | Still writes Bearer to `credentials.json`. env.json wins **inside this repo**. Other repos use the Bearer normally. | +| `dailybot logout` | Unaffected — only clears Bearer. env.json remains intact. | +| `dailybot config key=...` | Still works globally. env.json sits above it in precedence. | +| `DAILYBOT_API_KEY` env var | Still works. env.json beats it inside a repo. | +| `.dailybot/profile.json` | Orthogonal — still signs reports (identity). env.json provides credentials + URLs. Both can be present. | + +Precedence order (full table in [`../shared/env-json.md` § Auth resolution order](../shared/env-json.md#auth-resolution-order-updated-in-cli-370)). + +## Troubleshooting (quick reference) + +- **"The CLI is not using my env.json."** → `dailybot env show`; check `disabled`, `active`, and the walk-up path. Are you overriding with `--profile` / `--api-url` / `--app-url` flags? +- **"The CLI refuses to run and complains about tracked env.json."** → run the exact fix printed in the error message. Staged-but-uncommitted counts as tracked. (`dailybot hook *` commands print the error but still run and exit 0 — by design, per their harness contract.) +- **"I edited env.json by hand and now nothing works."** → `dailybot env show` surfaces schema warnings; if unrecoverable, delete the file and re-add profiles via `dailybot env add`. +- **"I set `disabled: "true"` and it's still active."** → `disabled` must be a JSON boolean; the CLI warns and treats a string as `false`. Use `dailybot env off`. + +## See also + +- [`../shared/env-json.md`](../shared/env-json.md) — full schema, precedence, security posture, worked examples. +- [`../shared/repo-profile.md`](../shared/repo-profile.md) — the sibling `profile.json` file (agent identity, tracked in git). +- [`../shared/auth.md`](../shared/auth.md) — general authentication flow (OTP login, API key alternatives, CLI installation). diff --git a/.agents/skills/dailybot/forms/SKILL.md b/.agents/skills/dailybot/forms/SKILL.md index d8db742..c472a13 100644 --- a/.agents/skills/dailybot/forms/SKILL.md +++ b/.agents/skills/dailybot/forms/SKILL.md @@ -1,7 +1,7 @@ --- name: dailybot-forms description: 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, variations, conditional logic). Use when the developer wants to see available forms, fill out a survey, continue an in-progress response, move a response between states, read prior responses, or create/configure a form. Do not use for daily check-ins — those go through dailybot-checkin. -version: "3.4.0" +version: "3.10.3" 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)"}]}} @@ -10,7 +10,7 @@ allowed-tools: Bash, Read, Grep, Glob # Dailybot Forms -> **Requires `dailybot-cli >= 3.1.2`** (the skill-pack baseline). The full forms lifecycle — `form list` / `submit` / `get` / `responses` / `response get` / `update` / `transition` / `delete` — plus the structured `--json` 4xx error shape are all available. If `dailybot --version` is below 3.1.2, ask the developer to run `dailybot upgrade`. See [`../SKILL.md` § Required Dailybot CLI version](../SKILL.md#required-dailybot-cli-version) for install commands and version-check tooling. +> **Requires `dailybot-cli >= 3.7.0`** (the skill-pack baseline). The full forms lifecycle — `form list` / `submit` / `get` / `responses` / `response get` / `update` / `transition` / `delete` — plus the structured `--json` 4xx error shape are all available. If `dailybot --version` is below 3.7.0, ask the developer to run `dailybot upgrade`. See [`../SKILL.md` § Required Dailybot CLI version](../SKILL.md#required-dailybot-cli-version) for install commands and version-check tooling. You help developers work with the full Dailybot forms lifecycle: list, inspect, submit, update, transition between workflow states, and read prior responses. Forms are custom questionnaires created by team leads — feedback surveys, retrospectives, release checklists, approval flows, or any structured data collection. Some forms are simple "fill once and done"; others have **workflow states** (e.g. `draft → review → released`) with audience-scoped permissions on who can edit and who can transition. @@ -109,7 +109,7 @@ The resolver step (4) is the customer-extension hook. See **Step 7 — Custom-sk dailybot form list --json ``` -Returns all forms visible to the logged-in user. **As of `dailybot-cli >= 3.2.0` this is org-scoped**: it lists every form the caller can see on the webapp list view — an org **admin sees all** the org's forms; a member sees forms flagged for the list view plus their own. (Before 3.2.0 the endpoint returned only the caller's *own* forms even for admins — a server-side bug; if a developer reports "I only see a handful of my forms," check `dailybot --version` and have them `dailybot upgrade`.) The shape is stable and machine-readable: +Returns all forms in the caller's organization. Every org member sees every org form; capabilities (editing, response visibility, state changes) are governed by each form's permissions. Pass `--mine` to narrow to only your own forms. (If a developer reports "I only see a handful of my forms," check `dailybot --version` and have them `dailybot upgrade` — older CLIs had a server-side visibility bug.) The shape is stable and machine-readable: ```json [ @@ -140,7 +140,7 @@ Returns all forms visible to the logged-in user. **As of `dailybot-cli >= 3.2.0` ### Pagination, search, and date filters -> **Note:** the shared list query flags below are part of the `dailybot-cli >= 3.1.2` baseline. Older CLIs +> **Note:** the shared list query flags below are part of the `dailybot-cli >= 3.7.0` baseline. Older CLIs > return the full list with no filtering. `form list` accepts the **full shared list query flag set** — pagination @@ -161,15 +161,68 @@ dailybot form list --all --json dailybot form list --page 2 --page-size 20 --json ``` -### Scope the list to your own forms — `--mine` (CLI >= 3.2.0) +### Filter by owner — `--mine` and `--owner` -Since the default is now org-scoped, pass **`--mine`** to narrow the result to -only the forms **you own** (it sends `owner=me` to the API). Useful when an admin -wants their personal forms out of the full org list. +Pass **`--mine`** to narrow the result to only the forms **you own**, or +**`--owner`** (repeatable) to filter by specific owners. `--owner` accepts +a UUID, email, or name — non-UUID values are resolved via the org directory. +The two flags can be combined (AND semantics with every other filter). ```bash # Only the forms I own: dailybot form list --mine --json + +# Forms owned by a specific person (by name): +dailybot form list --owner "Jane Doe" --json + +# Forms owned by two people (by UUID): +dailybot form list --owner --owner --json +``` + +> **Deprecation:** the `--filter me` scope is deprecated server-side. Use +> `--mine` or `--owner` instead — `--filter me` still works but maps to +> the legacy `filter=me` parameter. + +### Form owners picker — `form owners` + +A lightweight endpoint to discover which org members own at least one form, +without pulling the full member directory. + +```bash +dailybot form owners # table of owners +dailybot form owners --search jane # search by name/email +dailybot form owners --json # machine-readable +``` + +Each result has `uuid`, `full_name`, `image`, `role`, and optionally `email` +(email is only visible to admins/managers — the CLI must not assume it exists). + +### Server-side filtering, sorting, and archived forms + +| Flag | Values | Description | +|------|--------|-------------| +| `--filter` | `all`, `public`, `approval`, `workflow`, `archived` | Scope filter (server-side). `me` still works but is deprecated. | +| `--owner` | UUID, email, or name (repeatable) | Filter by form owner(s). Max 50. | +| `--order` | `alphabetical`, `recent`, `total` | Sort field (`total` = total response count). | +| `--ascending` / `--asc` | flag | Sort ascending (default: descending). | +| `--include-questions` | flag | Include question definitions in each form. | +| `--include-archived` | flag | Include archived forms (hidden by default). | + +```bash +# Workflow-enabled forms, sorted alphabetically ascending: +dailybot form list --filter workflow --order alphabetical --asc --json + +# Only forms with approval flow: +dailybot form list --filter approval --json + +# Public forms sorted by total responses: +dailybot form list --filter public --order total --json + +# Archived forms: +dailybot form list --filter archived --json + +# Include question definitions: +dailybot form list --include-questions --json ``` > **The envelope is unconditional.** `GET /v1/forms/` and the responses endpoint @@ -261,7 +314,7 @@ When the form has a workflow (`workflow.enabled: true`), the agent must understa ## Step 5.5 — Authoring forms (create / configure / questions) -> **Requires `dailybot-cli >= 3.1.2`** (the skill-pack baseline). The full authoring surface — `form create`, `form config` (workflow states, the three permission audiences, anonymous/public/brand/require-identity with `public_url`, approval + approvers, the ChatOps command), `form archive`, the `form questions add|edit|delete|reorder` group, resolving people by email, `--no-approvers`, the 3 report-channel cap, and the **create requires ≥ 1 question** rule (`questions_required`) — is all available. If `dailybot --version` is below 3.1.2, ask the developer to run `dailybot upgrade`. +> **Requires `dailybot-cli >= 3.7.0`** (the skill-pack baseline). The full authoring surface — `form create`, `form config` (workflow states, the three permission audiences, anonymous/public/brand/require-identity with `public_url`, approval + approvers, the ChatOps command), `form archive`, the `form questions add|edit|delete|reorder` group, resolving people by email, `--no-approvers`, the 3 report-channel cap, and the **create requires ≥ 1 question** rule (`questions_required`) — is all available. If `dailybot --version` is below 3.7.0, ask the developer to run `dailybot upgrade`. Everything above this point *reads* and *responds to* forms. This section *builds and reshapes* them. An agent with the right permissions can now create a form, wire up its workflow states, permission audiences, approval flow, and ChatOps command, and manage its questions — all end-to-end from the CLI, without opening the Dailybot webapp. @@ -758,7 +811,8 @@ Useful flags: |------|-------------| | `--latest` | Return only the most recent response visible to the caller. | | `--state STATE` | Filter to responses in a specific workflow state. Pass the **state key** (`draft`), not the label (`Draft`) — read the keys from `workflow.states[].key` on `form get`. Filtering is server-side. On a form with no workflow the API returns `400 invalid_workflow_state`. | -| `--search TEXT` | (alias `--grep`) Case-insensitive substring filter across responses. Max 256 chars (truncated client-side). | +| `--all` | List everyone's responses (requires VIEW_REPORTS permission — admin/owner only; a member receives 403). | +| `--search TEXT` | Search response content and submitter name/email. Max 256 chars. Does **not** search anonymous member identities (privacy preserved). | | `--json` | Machine-readable output (stable shape). | > **`form responses` search.** The `--search` / `--grep` flag @@ -770,6 +824,48 @@ Useful flags: > responses (admin/owner only), not every page. > See [`../shared/list-query-and-errors.md`](../shared/list-query-and-errors.md). +### Advanced response filters + +| Flag | Values | Description | +|------|--------|-------------| +| `--source` | CSV: `member`, `anonymous`, `automation`, `public` | Filter by submission origin (OR semantics within the group). | +| `--submitter` | CSV of UUIDs (max 50) | Filter by specific submitter user UUIDs. | +| `--flow-status` | `pending`, `approved`, `denied` | Approval flow status filter. Silently ignored if the form has no approval flow. | +| `--order` | `recent`, `oldest` | Sort by creation time. | +| `--ascending` / `--asc` | flag | Sort ascending (alias for `--order oldest`). | +| `--user UUID` | single UUID | Filter to one user's responses (admin/owner only). | +| `--from DATE` | YYYY-MM-DD | Responses on/after this date. | +| `--to DATE` | YYYY-MM-DD | Responses on/before this date. | + +**Submission sources** — every response belongs to exactly one bucket: + +| Source | Meaning | +|--------|---------| +| `member` | Identified org member submitted normally. | +| `anonymous` | Org member submitted anonymously (`collect_responses_anonymously=true`). | +| `automation` | Submitted via API/CLI with `--automation` (`is_dailybot_bot=true`). | +| `public` | Submitted via the public form URL by an external guest. | + +All filters compose with **AND** across groups and **OR** within each group: +`--source "member,automation" --flow-status pending --search "deploy"` → responses that are `(member OR automation) AND pending AND contain "deploy"`. + +```bash +# All automation submissions: +dailybot form responses --all --source automation --json + +# Multiple sources (OR): automation OR public: +dailybot form responses --all --source "automation,public" --json + +# Approval: only pending: +dailybot form responses --all --flow-status pending --json + +# Combined: member responses, approved, containing "sprint": +dailybot form responses --all --source member --flow-status approved --search "sprint" --json + +# Sorted oldest first in a date range: +dailybot form responses --all --order oldest --from 2026-07-01 --to 2026-07-10 --json +``` + ### JSON shape (single response) ```json @@ -971,6 +1067,36 @@ Always show the complete answer set before sending: | `--state` | `-s` | Optional initial state (workflow forms only). Defaults to the form's initial state. | | `--yes` | `-y` | Skip confirmation. | | `--json` | | Machine-readable JSON output. | +| `--automation` | | Submit as an automation — channel notifications show no submitter name. | +| `--anonymous` | | Submit anonymously — channel notifications show a random generated name. | +| `--guest-name` | | Guest submitter full name (used with `--automation` for third-party submissions). | +| `--guest-email` | | Guest submitter email (validated client-side). | +| `--source` | | Provenance label, max 512 chars (e.g. `workflow:release-pipeline`). Works with any mode. | + +> **`--automation` vs `--anonymous`:** Both are independent booleans. `--automation` hides the submitter entirely; `--anonymous` replaces them with a random name. When combined, `automation` takes precedence for the channel display. Neither flag affects who owns the response in the dashboard — it only controls the notification appearance. + +### Submission modes + +| Mode | Flags | Channel notification | +|------|-------|---------------------| +| Normal | (none) | Shows your name + avatar | +| Anonymous | `--anonymous` | Random generated name (e.g. "Purple Elephant") | +| Automation | `--automation` | No submitter shown | +| Automation + Guest | `--automation --guest-name "X" --guest-email "x@y"` | Guest name/email in body, no submitter avatar | +| Any + Source | `--source "label"` | Provenance label attached (works with any mode) | + +```bash +# Automation with guest identity and source tracking: +dailybot form submit \ + --content '{"":"done"}' --yes --automation \ + --guest-name "Release Bot" --guest-email "releases@example.com" \ + --source "workflow:production-deploy" +``` + +**Validation rules:** +- If the form has `require_email_and_name` enabled and you use `--automation`, both `--guest-name` and `--guest-email` are required (API returns `guest_user_required`). +- `--guest-email` is validated client-side for format. +- `--source` max length: 512 characters. After submit, **re-read `current_state` and `allowed_transitions` on the returned payload** to decide the next step. @@ -1012,11 +1138,12 @@ When the form is workflow-enabled and `allowed_transitions` is non-empty: dailybot form transition --yes ``` -> **Pass `to_state`, never `label`.** In `allowed_transitions`, `to_state` is the -> machine key (`released`) and `label` is display text (`Mark released`). The API -> matches on the key and answers `Unknown workflow state: 'Mark released'` -> otherwise. Read the key from the response payload rather than typing the state -> name you saw in the panel. +> **You can pass either `to_state` (machine key) or `label` (display text).** +> The CLI resolves labels to keys automatically — e.g. +> `"Mark released"` → `released`. In `allowed_transitions`, `to_state` is the +> machine key (`released`) and `label` is display text (`Mark released`). Both +> are accepted; the CLI performs a case-insensitive lookup and translates labels +> to keys before calling the API. On older CLIs, only the machine key works. Confirm with the developer before transitioning: @@ -1217,6 +1344,7 @@ Form operations must **never block your primary work**. If the CLI is missing, a - [`../shared/auth.md`](../shared/auth.md) — authentication setup - [`../shared/http-fallback.md`](../shared/http-fallback.md) — HTTP API fallback patterns +- [`../shared/dashboard-urls.md`](../shared/dashboard-urls.md) — full dashboard URL catalog (forms, check-ins, kudos, agents) - [`_custom-template/SKILL.md`](_custom-template/SKILL.md) — starter template for authoring a custom per-form skill (copy into `.agents/skills/dailybot-custom//` in your own repo) - **Live API spec:** `https://api.dailybot.com/api/swagger/` - **Full agent API skill:** `https://www.dailybot.com/skill.md` diff --git a/.agents/skills/dailybot/forms/_custom-template/SKILL.md b/.agents/skills/dailybot/forms/_custom-template/SKILL.md index ffe5bff..68fdbad 100644 --- a/.agents/skills/dailybot/forms/_custom-template/SKILL.md +++ b/.agents/skills/dailybot/forms/_custom-template/SKILL.md @@ -1,7 +1,7 @@ --- name: dailybot-custom-form-template description: 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. -version: "3.4.0" +version: "3.10.3" documentation_url: https://www.dailybot.com/skill.md user-invocable: false allowed-tools: Bash, Read, Grep, Glob diff --git a/.agents/skills/dailybot/health/SKILL.md b/.agents/skills/dailybot/health/SKILL.md index 455d75c..96b7bc2 100644 --- a/.agents/skills/dailybot/health/SKILL.md +++ b/.agents/skills/dailybot/health/SKILL.md @@ -1,7 +1,7 @@ --- name: dailybot-health description: 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. -version: "3.4.0" +version: "3.10.3" documentation_url: https://www.dailybot.com/skill.md user-invocable: false 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)"}]}} @@ -12,7 +12,7 @@ allowed-tools: Bash, Read, Grep, Glob You announce the agent's status (online, working, offline, degraded) to Dailybot so the team knows whether the agent is alive and what it's doing. Health check responses also deliver pending messages from the team. -> **Requires `dailybot-cli >= 3.1.2`** (the skill-pack baseline). See [`../SKILL.md` § Required Dailybot CLI version](../SKILL.md#required-dailybot-cli-version). +> **Requires `dailybot-cli >= 3.7.0`** (the skill-pack baseline). See [`../SKILL.md` § Required Dailybot CLI version](../SKILL.md#required-dailybot-cli-version). --- diff --git a/.agents/skills/dailybot/kudos/SKILL.md b/.agents/skills/dailybot/kudos/SKILL.md index 2ed887d..b0a4014 100644 --- a/.agents/skills/dailybot/kudos/SKILL.md +++ b/.agents/skills/dailybot/kudos/SKILL.md @@ -1,7 +1,7 @@ --- name: dailybot-kudos description: 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. -version: "3.4.0" +version: "3.10.3" 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)"}]}} @@ -10,7 +10,7 @@ allowed-tools: Bash, Read, Grep, Glob # Dailybot Kudos -> **Requires `dailybot-cli >= 3.1.2`** (the skill-pack baseline). Giving kudos to a user (`--to`) or a team (`--team`), and browsing kudos (`list` / `org` / `wall-of-fame`), are all available. If `dailybot --version` is below 3.1.2, ask the developer to run `dailybot upgrade`. See [`../SKILL.md` § Required Dailybot CLI version](../SKILL.md#required-dailybot-cli-version) for install commands and version-check tooling. +> **Requires `dailybot-cli >= 3.7.0`** (the skill-pack baseline). Giving kudos to a user (`--to`) or a team (`--team`), and browsing kudos (`list` / `org` / `wall-of-fame`), are all available. If `dailybot --version` is below 3.7.0, ask the developer to run `dailybot upgrade`. See [`../SKILL.md` § Required Dailybot CLI version](../SKILL.md#required-dailybot-cli-version) for install commands and version-check tooling. You help developers recognize teammates by sending kudos through Dailybot. Kudos are team-visible appreciation messages — the whole team sees them in Dailybot's recognition feed and in connected chat platforms (Slack, Teams, Discord). @@ -32,7 +32,7 @@ If the developer has only an API key, kudos still work — the CLI falls back to ## Browsing kudos (read) > **Baseline:** the three read commands below (`kudos list`, `kudos org`, -> `kudos wall-of-fame`) are part of the `dailybot-cli >= 3.1.2` baseline. +> `kudos wall-of-fame`) are part of the `dailybot-cli >= 3.7.0` baseline. Beyond *giving* kudos, an agent can **browse** the recognition feed and read org-wide stats. All three return the standard pagination envelope where @@ -93,6 +93,43 @@ Returns the recognition leaderboard — the top receiver, the top giver, and the ranked leaderboard entries. `--limit N` caps the number of leaderboard entries returned. +**Parse the payload carefully — three fields are commonly misread:** + +- Every person is **nested under a `user` key** — the name lives at + `top_receiver.user.full_name` (and likewise in `top_giver` and in every + leaderboard entry), **not** at a top-level `full_name`. +- `leaderboard` is itself a **paginated envelope** `{count, next, previous, + results}` — the ranked entries are in `leaderboard.results`, and the total + ranked members is `leaderboard.count` (do not count the envelope's keys). +- `leaderboard_summary` is the **caller's own standing**: `{position, total}`. + +```json +{ + "top_receiver": { "user": { "uuid": "…", "full_name": "…", "image": "…" }, + "kudos_received": 11, "kudos_given": 5, + "total_plus_kudos_received": 18, "total_plus_kudos_given": 2 }, + "top_giver": { "user": { "…": "…" }, "kudos_given": 14 }, + "dna_distribution": [ { "company_value": { "id": "…", "value": "…", "emoji": "…" }, + "count": 10, "percentage": 38.5 } ], + "leaderboard": { "count": 11, "next": false, "previous": false, + "results": [ { "position": 1, "user": { "…": "…" }, + "score": 11, "total_plus_kudos": 18 } ] }, + "leaderboard_summary": { "position": 1, "total": 11 } +} +``` + +`dna_distribution` breaks the kudos down by the org's company values. + +> **Version note:** the human (non-`--json`) rendering of this command was +> fixed in [`dailybot-cli` v3.7.2](https://github.com/DailybotHQ/cli/releases/tag/v3.7.2) +> ([DailybotHQ/cli#71](https://github.com/DailybotHQ/cli/pull/71), on +> [PyPI](https://pypi.org/project/dailybot-cli/)) — since that release it shows +> the full wall of fame: top receiver/giver with counts, the caller's position, +> the company-values distribution, and the ranked leaderboard table. Older CLI +> versions render an incomplete summary panel (dashes instead of names), so +> always prefer `--json` when parsing, and suggest `dailybot upgrade` if the +> developer sees dashes. + --- ## When to Use @@ -462,6 +499,7 @@ Sending kudos must **never block your primary work**. If the CLI is missing, aut - [`../shared/auth.md`](../shared/auth.md) — authentication setup - [`../shared/http-fallback.md`](../shared/http-fallback.md) — HTTP API fallback patterns +- [`../shared/dashboard-urls.md`](../shared/dashboard-urls.md) — full dashboard URL catalog (kudos detail, wall of fame, etc.) - [`../teams/SKILL.md`](../teams/SKILL.md) — team-name resolver (called by this skill) - **Live API spec:** `https://api.dailybot.com/api/swagger/` - **Full agent API skill:** `https://www.dailybot.com/skill.md` diff --git a/.agents/skills/dailybot/messages/SKILL.md b/.agents/skills/dailybot/messages/SKILL.md index a4b5e8a..7663b54 100644 --- a/.agents/skills/dailybot/messages/SKILL.md +++ b/.agents/skills/dailybot/messages/SKILL.md @@ -1,7 +1,7 @@ --- name: dailybot-messages description: 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. -version: "3.4.0" +version: "3.10.3" documentation_url: https://www.dailybot.com/skill.md user-invocable: false 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)"}]}} @@ -14,7 +14,7 @@ You check for pending messages and instructions from the developer's team. Messa This is the "what should I work on next?" skill. -> **Requires `dailybot-cli >= 3.1.2`** (the skill-pack baseline). See [`../SKILL.md` § Required Dailybot CLI version](../SKILL.md#required-dailybot-cli-version). +> **Requires `dailybot-cli >= 3.7.0`** (the skill-pack baseline). See [`../SKILL.md` § Required Dailybot CLI version](../SKILL.md#required-dailybot-cli-version). --- diff --git a/.agents/skills/dailybot/report/SKILL.md b/.agents/skills/dailybot/report/SKILL.md index a5b7e3c..c849f8f 100644 --- a/.agents/skills/dailybot/report/SKILL.md +++ b/.agents/skills/dailybot/report/SKILL.md @@ -1,7 +1,7 @@ --- name: dailybot-report description: 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. -version: "3.4.0" +version: "3.10.3" 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)"}]}} @@ -123,7 +123,7 @@ trigger in a previous session. #### Check whether hooks apply, and whether they are already installed -1. **CLI version.** Run `dailybot --version`. If it reports below `3.1.2` +1. **CLI version.** Run `dailybot --version`. If it reports below `3.7.0` (or the CLI is absent), the `dailybot hook` group does not exist — skip Step 0b silently and continue to Step 1. The Step 0a trigger alone still works. @@ -530,5 +530,6 @@ Reporting must **never block your primary work**. If the CLI is missing, auth fa - [`../shared/auth.md`](../shared/auth.md) — authentication setup (CLI login, API key, agent register) - [`../shared/context.sh`](../shared/context.sh) — automated context detection - [`../shared/http-fallback.md`](../shared/http-fallback.md) — HTTP API fallback patterns +- [`../shared/dashboard-urls.md`](../shared/dashboard-urls.md) — dashboard URL catalog (report detail pages, agent analytics, etc.) - **Live API spec:** `https://api.dailybot.com/api/swagger/` - **Full agent API skill:** `https://www.dailybot.com/skill.md` diff --git a/.agents/skills/dailybot/report/hooks.md b/.agents/skills/dailybot/report/hooks.md index faa4df3..5c76e12 100644 --- a/.agents/skills/dailybot/report/hooks.md +++ b/.agents/skills/dailybot/report/hooks.md @@ -12,7 +12,7 @@ in once, and from then on the harness re-arms the reminders in every future session, container, and repo. No human reminders, no reliance on the model's memory. -> **Requires `dailybot-cli >= 3.1.2`** (the skill-pack baseline). The `dailybot hook` command group +> **Requires `dailybot-cli >= 3.7.0`** (the skill-pack baseline). The `dailybot hook` command group > is available at this floor. > Check with `dailybot --version`; if older, ask the developer to run > `dailybot upgrade` once. Hooks installed against an older CLI fail @@ -163,7 +163,7 @@ the only remaining per-person step is `dailybot login`, and the | `soft_turn_threshold` | `8` (`5` in `continuous` mode when omitted) | Agent turns without a report before a soft nudge is eligible | Invalid `mode` values fall back to `"balanced"`; invalid `soft_turn_threshold` - values fall back to the mode default. (Part of the `dailybot-cli >= 3.1.2` + values fall back to the mode default. (Part of the `dailybot-cli >= 3.7.0` baseline; much older CLIs ignore `mode`/`soft_turn_threshold` and stay on the balanced defaults. @@ -182,7 +182,7 @@ the only remaining per-person step is `dailybot login`, and the | Symptom | Check | |---------|-------| -| Reminders never fire | Run `dailybot hook stop` manually after a commit — any output? Then check `dailybot --version` (>= 3.1.2), `.dailybot/disabled`, and the harness config actually contains the `dailybot hook` entries | +| Reminders never fire | Run `dailybot hook stop` manually after a commit — any output? Then check `dailybot --version` (>= 3.7.0), `.dailybot/disabled`, and the harness config actually contains the `dailybot hook` entries | | Reminder fires but mentions old history | Delete the repo's file under `~/.config/dailybot/ledger/` — the baseline re-anchors silently | | Too noisy | Raise `min_interval_minutes` in `.dailybot/profile.json`, or use `dailybot hook dismiss --minutes ` | | Not reminded often enough (research-heavy repo) | Set `"mode": "continuous"` (or lower `soft_turn_threshold` / `min_interval_minutes`) in `.dailybot/profile.json` | diff --git a/.agents/skills/dailybot/shared/auth.md b/.agents/skills/dailybot/shared/auth.md index 04ae92a..0a43e62 100644 --- a/.agents/skills/dailybot/shared/auth.md +++ b/.agents/skills/dailybot/shared/auth.md @@ -45,7 +45,7 @@ treat that as session-wide consent. > [!NOTE] > **Installing a specific version.** Both installers default to the latest -> release but accept a version pin (the skill-pack baseline is **`dailybot-cli >= 3.1.2`**): +> release but accept a version pin (the skill-pack baseline is **`dailybot-cli >= 3.7.0`**): > - `install.sh` — set `DAILYBOT_VERSION=` in the environment, or > pass `bash -s -- --version `. Example (drop it into the verified > snippet below, right before `bash /tmp/install.sh`): @@ -355,27 +355,88 @@ Dailybot → Settings → API Keys. --- -## 4. Auth model — API key *or* login, almost everywhere +## 4. Auth model — unified Bearer-first priority everywhere -As of the CLI's full-parity baseline (`dailybot-cli >= 3.1.2`, paired with the -matching API server rollout), **every authenticated CLI command accepts either -credential** — a Bearer login session **or** an org API key. The server resolves -the acting user from the API key's `owner`, so the two paths behave identically. -This is what lets an autonomous agent do **everything** with only -`DAILYBOT_API_KEY` set — including `dailybot ask` (the AI chat). +**All endpoints use the same auth priority: Bearer token first, API key +second** (unified in CLI 3.5.1). There is no longer a split where agent +endpoints preferred API key and user endpoints preferred Bearer — the CLI +now behaves consistently everywhere. The server accepts both credentials on +every `/v1/` endpoint, so the two paths are functionally identical. -| Scope | Accepted credentials | Used by | -|-------|----------------------|---------| -| **Agent endpoints** | API key (`X-API-KEY`) preferred, Bearer fallback | `dailybot agent update`, `dailybot agent health`, `dailybot agent email send` | -| **User / CLI / AI commands** | Bearer token preferred, API key fallback — **either works** | `dailybot status`, `update`, `checkin`, `form`, `kudos`, `team`, `user`, `chat`, `ask` (AI chat) | +One deliberate exception (CLI >= 3.7.0): when the API key resolves from a +repo's `.dailybot/env.json` active profile, the client sends `X-API-KEY` +**first** — the per-repo key must beat the global Bearer session even against +a server that would accept the Bearer, and the session token must never be +transmitted to the env.json server. The 401/403 alt-credential retry covers +the reverse direction. See [`env-json.md`](env-json.md). + +| Scope | Auth priority | Used by | +|-------|--------------------------------|---------| +| **All endpoints** | Bearer preferred → API key fallback | Every command: `agent update`, `form submit`, `kudos`, `chat send`, `ask`, etc. | | **Login lifecycle** | OTP / Bearer only | `dailybot login`, `dailybot logout` (revokes the session token) | -Both credentials can coexist — the CLI stores them separately, and a developer -can hold an API key and a Bearer session at the same time. The CLI prefers the -login session when present and falls back to the API key. +### Per-repo API key override (`.dailybot/env.json`) — CLI >= 3.7.0 + +Since `dailybot-cli >= 3.7.0`, the CLI also honours an **opt-in, gitignored** +per-repo file at `/.dailybot/env.json` that carries API keys + optional +URL overrides for one or more environments. When present with an *active* +profile, it sits **just below** explicit `--profile` / `--api-url` flags in +the auth-resolution order — above `agents.json`, above `DAILYBOT_API_KEY`, +above `config.json`, above the login Bearer. + +If the developer asks about "per-repo API keys", "staging vs prod", +"different orgs per project", or wants to override auth without touching +env vars, route them to [`shared/env-json.md`](env-json.md) — it has the +full schema, CLI commands (`dailybot env add / use / show / list / remove / +off / on`), security posture, and worked examples. + +`env.json` is orthogonal to `profile.json`: + +- `profile.json` = identity (tracked in git, team-shared). +- `env.json` = auth context (gitignored, per-developer). -> **Parity.** All user-scoped commands (`checkin`, `form`, `kudos`, `user`) and -> the AI chat accept an org API key **or** a Bearer login session. Only +Neither field overlaps. Both can be present. + +Both credentials can coexist — the CLI stores them separately, and a developer +can hold an API key and a Bearer session at the same time. + +### Automatic fallback on 401 or 403 + +When the primary credential is rejected (HTTP **401 or 403**), the CLI +automatically retries once with the alternative credential if available. +This is bidirectional: + +- **Bearer expired** → retries with API key +- **API key stale/revoked** → retries with Bearer session + +Both `_agent_request()` (agent-scoped endpoints) and `_request()` (all +user-scoped endpoints — `auth_status`, `checkin`, `form`, `kudos`, `chat`, +`ask`, `user`, `team`, ...) implement identical retry semantics. Login- +lifecycle endpoints (`request_code`, `verify_code`, `logout`, agent +registration) never retry because the credential IS the thing being +negotiated or invalidated. + +The retry covers three real-world cases at zero UX cost: + +1. **`env.json` active + stale Bearer.** Prod OTP session on disk, `cd` into + a repo whose `env.json` points at `http://localhost:8000` — the local + API rejects the Bearer (403), the retry uses the `env.json` API key, + the command succeeds. `dailybot status --auth` then reports + `Authenticated via API key` (not `login (OTP)`) — the report reflects + what actually worked, not what was tried first. +2. **Bearer expired** in normal single-org use → falls back to a locally + configured API key without a login prompt. +3. **API key revoked** while a valid login session exists → falls back to + the Bearer. + +Retrying on **403** in addition to 401 is required because Django/DRF +frequently returns 403 for rejected credentials (see +[DRF authentication docs](https://www.django-rest-framework.org/api-guide/authentication/#unauthorized-and-forbidden-responses)). +Relying on 401 alone leaves the local-Django + `env.json` case broken. + +> **Parity.** All commands — user-scoped (`checkin`, `form`, `kudos`, `user`), +> agent-scoped (`agent update`, `agent health`), and the AI chat (`ask`) — +> accept an org API key **or** a Bearer login session. Only > `dailybot logout` is Bearer-only. ### Checking session status @@ -405,29 +466,6 @@ automatically if it does not exist. ### Commands need *some* credential Every authenticated command works with **either** a login session or an API -key; they exit with a non-zero "not authenticated" code only when **neither** -is present. The single command that still requires a Bearer session is -`dailybot logout` (it revokes the session token itself). Guide the developer -through `dailybot login` or ask them to set `DAILYBOT_API_KEY`. - -### Config directory override - -The `DAILYBOT_CONFIG_DIR` environment variable overrides where all credential -and config files are stored (default: `~/.config/dailybot/`): - -```bash -export DAILYBOT_CONFIG_DIR=/tmp/my-sandbox-config -dailybot login --email me@example.com -``` - -This is useful for development sandboxes, CI environments, or testing -scenarios with isolated config directories. The directory is created -automatically if it does not exist. - -### User-scoped commands fail without a Bearer session - -If a developer tries to use `dailybot checkin`, `dailybot form`, -`dailybot kudos`, or `dailybot user` with only an API key and no login -session, the CLI exits with code `3` (not authenticated). Guide them -through `dailybot login` — these commands require the human's own -session, not an agent key. +key. Only `dailybot logout` requires a Bearer session (it revokes the session +token itself). If neither credential is present, the CLI exits with a clear +error suggesting `dailybot login` or setting `DAILYBOT_API_KEY`. diff --git a/.agents/skills/dailybot/shared/dashboard-urls.md b/.agents/skills/dailybot/shared/dashboard-urls.md new file mode 100644 index 0000000..7a9e4b4 --- /dev/null +++ b/.agents/skills/dailybot/shared/dashboard-urls.md @@ -0,0 +1,129 @@ +# Shared reference — Dailybot dashboard URLs + +> **Requires `dailybot-cli >= 3.7.0`** (the skill-pack baseline). The +> `--app-url` flag and `DAILYBOT_APP_URL` env var for configuring the dashboard +> base URL are available at this floor, as is the per-profile `app_url` in +> [`env-json.md`](env-json.md). + +This is the **single source of truth** for all dashboard (webapp) URLs that +agents can embed in reports, messages, or surface to the developer. Sub-skills +link here instead of repeating route tables. + +--- + +## 1. Base URL resolution + +The dashboard base URL resolves in this order: + +| Priority | Source | Example | +|----------|--------|---------| +| 1 | `--app-url` CLI flag | `dailybot --app-url http://localhost:8090 agent update …` | +| 2 | `DAILYBOT_APP_URL` env var | `export DAILYBOT_APP_URL=http://localhost:8090` | +| 3 | Default | `https://app.dailybot.com` | + +For **local development**, set the env var or pass the flag: + +```bash +export DAILYBOT_APP_URL=http://localhost:8090 +``` + +> **Do not hardcode staging or dev URLs** in committed code, docs, or skill +> files. Use the env var or flag for non-production environments. + +--- + +## 2. Route catalog + +All paths below are relative to the base URL. Replace `{placeholders}` with +actual UUIDs/IDs from API responses. Routes marked `[fullscreen]` open a +standalone page (no sidebar navigation). + +### Home + +| Description | Path | +|-------------|------| +| Main home | `/home` | + +### Forms + +| Description | Path | +|-------------|------| +| Forms home | `/forms/home` | +| Responses list | `/forms/{form_uuid}/responses` | +| Response detail | `/forms/{form_uuid}/responses/{response_uuid}` | +| Create form — questions `[fullscreen]` | `/forms/create/form-questions` | +| Create form — setup `[fullscreen]` | `/forms/create` | +| Fill form (public) `[fullscreen]` | `/forms/{form_uuid}/responses/create/` | +| Edit response `[fullscreen]` | `/forms/{form_uuid}/responses/update/{response_uuid}` | + +### Check-ins + +| Description | Path | +|-------------|------| +| Check-ins home | `/checkins/home` | +| Daily report | `/checkins/{checkin_uuid}/daily-report` | +| Daily report (date) | `/checkins/{checkin_uuid}/daily-report/{YYYY-MM-DD}` | +| Activity | `/checkins/{checkin_uuid}/activity` | +| Submit response `[fullscreen]` | `/checkins/response-daily/{checkin_uuid}/add/{YYYY-MM-DD}` | +| Edit response `[fullscreen]` | `/checkins/response-daily/{checkin_uuid}/edit/{YYYY-MM-DD}` | +| Create check-in `[fullscreen]` | `/checkins/create` | +| Edit — questions `[fullscreen]` | `/checkins/edit/{checkin_uuid}/questions` | +| Edit — frequency `[fullscreen]` | `/checkins/edit/{checkin_uuid}/frequency` | +| Edit — participants `[fullscreen]` | `/checkins/edit/{checkin_uuid}/participants` | +| Edit — reporting `[fullscreen]` | `/checkins/edit/{checkin_uuid}/reporting` | + +### Kudos + +| Description | Path | +|-------------|------| +| Kudos home | `/kudos/home` | +| Wall of fame | `/kudos/wall-of-fame` | +| Team values | `/kudos/team-values` | +| Send kudo `[fullscreen]` | `/kudos/send` | +| Kudo detail `[fullscreen]` | `/kudos/detail/{kudo_id}` | +| Company value detail `[fullscreen]` | `/kudos/company-values/{value_id}` | + +### Agents + +| Description | Path | +|-------------|------| +| Agents home | `/agents/home` | +| Reports | `/agents/reports` | +| Messages | `/agents/messages` | +| Analytics | `/agents/analytics/{tab}` (`agents`, `coauthors`, `insights`) | +| Agent detail | `/agents/{agent_uuid}` | +| Report detail | `/agents/report/{report_id}` | +| Co-author detail | `/agents/co-author/{coauthor_uuid}` | + +--- + +## 3. Building full URLs + +Combine the base URL + path. When the API returns a `url` field (e.g. in +`POST /v1/agent-reports/` → `{"url": "https://app.dailybot.com/agents/report/123"}`), +**prefer the server-returned URL** — it already includes the correct host. Only +construct URLs manually when the API does not return one (e.g. linking to a +form's responses page or a check-in's daily report). + +```python +# Example: construct a form responses URL +app_url = get_app_url() # resolves --app-url > env > default +form_uuid = "abc-123" +url = f"{app_url}/forms/{form_uuid}/responses" +``` + +--- + +## 4. When to surface dashboard URLs + +Agents should include dashboard links in reports and messages when: + +- **After submitting a form response** — link to the response detail page +- **After giving kudos** — link to the kudo detail or wall of fame +- **In agent progress reports** — the `View:` line already shows the report URL +- **When the developer asks** to "see it in the dashboard" or "open it in the web" +- **In chat messages** — as clickable links (Slack/Teams render them as hyperlinks) + +Do **not** surface dashboard URLs: +- When the developer is working offline or in a CI/headless context +- In error messages (errors should guide the user to CLI commands, not the web) diff --git a/.agents/skills/dailybot/shared/env-json.md b/.agents/skills/dailybot/shared/env-json.md new file mode 100644 index 0000000..c679e64 --- /dev/null +++ b/.agents/skills/dailybot/shared/env-json.md @@ -0,0 +1,453 @@ +# Per-repo API key override (`.dailybot/env.json`) + +> **Read this if the developer asks about "switching between orgs per repo", "local dev keys", "logging into a staging org just for this project", or setting up "different Dailybot environments" for testing.** This is a single source of truth for the `env.json` workflow — sub-skills link here instead of duplicating the rules. + +The Dailybot CLI (>= **3.7.0**) supports a per-repository file at `/.dailybot/env.json` that carries API keys + optional URL overrides for one or more environments (`live`, `local`, `staging`, ...). When a profile is *active*, it overrides `DAILYBOT_API_KEY`, `config.json`, and the login Bearer session **for the enclosing repo only** — enabling the developer to be "logged into different orgs in different repos" without touching global state or env vars. + +`env.json` is **opt-in, gitignored, and never required**. The CLI works exactly as before when the file is absent. + +--- + +## STOP — the one thing you MUST enforce as an agent + +**`.dailybot/env.json` must NEVER be committed to git. Ever. Under any circumstance.** + +If the developer's request involves creating, editing, sharing, moving, or explaining `env.json`, you must treat "keep it gitignored" as a non-negotiable invariant. Concretely, that means: + +- **NEVER** run or suggest `git add .dailybot/env.json` (or `git add -A` / `git add .` from a place that would sweep it in). The CLI's `add` command writes the file to disk — that is the *only* place it should ever exist. +- **NEVER** `cat`, `head`, `tail`, or otherwise print the raw file contents into the chat, into a report, into a PR body, or into any other artifact — API keys live inside. Use `dailybot env show` / `dailybot env list` which mask them. +- **NEVER** copy the file into `tmp/`, into a docs example, into a test fixture, or into any other tracked location. If you need to reference structure, use the placeholder schema shown in this doc (with `sk_local_xxxx`-style dummy keys). +- **NEVER** try to work around the CLI's fatal refuse-if-tracked guard (see § "Security — non-negotiable rules" below). If the CLI is blocking a command because `env.json` is tracked, the *only* correct answer is `git rm --cached .dailybot/env.json` + rotate the exposed keys — not `--no-verify`, not "temporarily untrack", not editing the guard away. +- **ALWAYS** verify the repo's `.gitignore` contains `.dailybot/*` before the developer's first `dailybot env add`. If it doesn't, add it (and commit that change) *first*. +- **ALWAYS** treat "the file was committed at some point in history" as a compromise: rotate every key in it via the Dailybot dashboard immediately, then follow the recovery recipe below. + +The rule is absolute because git history is forever. On a public repo the keys are burned the instant the push lands; on a private repo they still leak to every collaborator, every past fork, every CI cache, and every backup. `git revert` does not undo the exposure. **Rotate, don't revert.** + +The CLI enforces this same rule with four independent protections (gitignore convention, `0o600` permissions, a fatal load-time guard in the root `cli()` callback, and an advisory write-time `git check-ignore` warning). All of them must be in place. If any of them looks broken on the developer's machine, treat it as a bug worth reporting — do NOT paper over it. + +--- + +## When to reach for `env.json` + +Suggest it when the developer says any of: + +- *"I want a local key just for this project."* +- *"How do I test against staging without messing up my prod login?"* +- *"I need to be in org A in this repo and org B in another repo."* +- *"Can I have per-project Dailybot credentials?"* + +Do **not** suggest it when: + +- The developer is in CI. Recommend `DAILYBOT_API_KEY` as an env var instead — leaves no on-disk secret to clean up. +- The developer wants team-shared identity for the repo — that's [`profile.json`](repo-profile.md), not `env.json`. +- The developer has a single Dailybot org and a working login session. `dailybot login` + global config is simpler. + +--- + +## Distinction from `profile.json` (critical, do not confuse them) + +The two files live side-by-side in `.dailybot/` but serve **opposite roles**: + +| File | Committed? | Contains | Role | +|---|---|---|---| +| `.dailybot/profile.json` | **Yes** (tracked) | `name`, `default_metadata`, `report`, `vars` | **Identity** — how the agent signs reports (team-shared) | +| `.dailybot/env.json` | **No** (gitignored) | `api_key`, `api_url`, `app_url` per profile | **Auth context** — which org the CLI talks to (per-developer, per-machine) | + +Neither file overlaps on any field. Both can be present, and typically will be: `profile.json` pins the report signature ("this repo's reports come from `Core Hub Bot`"), while `env.json` picks which Dailybot org those reports get sent to on your machine right now. + +**Under NO circumstances** should you write API keys to `profile.json` — the CLI hard-errors with `RepoProfileError` when it detects a `key` field there. `env.json` is the ONLY sanctioned place inside `.dailybot/` for credentials. + +--- + +## Schema + +```json +{ + "disabled": false, + "active": "local org 1", + "profiles": [ + { + "name": "live", + "api_key": "sk_live_xxxxxxxx" + }, + { + "name": "local org 1", + "api_key": "sk_local_xxxxxxxx", + "api_url": "http://localhost:8000", + "app_url": "http://localhost:8090" + }, + { + "name": "staging", + "api_key": "sk_staging_xxxxxxxx", + "api_url": "https://staging-api.example.com", + "app_url": "https://staging-app.example.com" + } + ] +} +``` + +| Field | Type | Required? | Purpose | +|---|---|---|---| +| `disabled` | boolean | optional (default `false`) | Kill-switch. `true` ignores the whole file even if `active` points to a valid profile. Preserves `active` for one-command re-enable. Must be a **JSON boolean** — a hand-edited string like `"true"` is NOT honored: the CLI warns loudly and the file **stays active** (use `dailybot env off` instead). | +| `active` | string \| null | optional | Name of the profile to use. `null` / `""` / missing / unknown-name → file is *inert* and resolution falls through. Only one active at a time. | +| `profiles` | list of objects | **required** | Every configured environment. | +| `profiles[].name` | string | **required** | Unique per file. Human-friendly, may contain spaces. | +| `profiles[].api_key` | string | **required** | The API key for this environment. Plain-text on disk — gitignore is mandatory. | +| `profiles[].api_url` | string | optional | Overrides `DAILYBOT_API_URL` / `credentials.json` when this profile is active. Falls through to `https://api.dailybot.com` when absent. | +| `profiles[].app_url` | string | optional | Overrides `DAILYBOT_APP_URL` when this profile is active. Falls through to `https://app.dailybot.com` when absent. | + +Unknown keys are logged as a warning and ignored (forward-compatibility). snake_case only — camelCase is a schema violation. + +--- + +## CLI workflow (always prefer these commands over hand-editing) + +```bash +# First profile — creates the file at /.dailybot/env.json with 0o600 +# perms and auto-marks itself active. +dailybot env add \ + --name "local org 1" \ + --key sk_local_xxxxxxxx \ + --api-url http://localhost:8000 \ + --app-url http://localhost:8090 + +# Additional profiles — appended, active pointer unchanged. +dailybot env add --name live --key sk_live_yyyyyyyy +dailybot env add --name staging --key sk_staging_zzzzzzzz \ + --api-url https://staging-api.example.com + +# Switch which profile is active. +dailybot env use staging +dailybot env use "" # clear active → fall through to global auth + +# Inspect. +dailybot env show # resolved profile (API key masked) +dailybot env list # all profiles, active marked +# `env show` also prints an explicit "Disabled: no" row (since `disabled: +# false` is normalized away on write) and resolves defaulted API/Webapp URLs +# so the developer sees the concrete server the context points at. + +# Kill-switch — preserves `active` so `on` restores instantly. +dailybot env off +dailybot env on + +# Delete a profile. If it was the active one, active is cleared. +dailybot env remove staging --yes +``` + +The CLI ALWAYS masks API keys in output (`sk_l****` — first 4 chars + `****`). It never echoes the full key back. + +--- + +## Auth resolution order (updated in CLI 3.7.0) + +The full precedence for `api_key` / `api_url` / `app_url` when a repo has `env.json`: + +| # | Layer | Notes | +|---|---|---| +| 1 | `--profile` / `--api-url` / `--app-url` CLI flags | Per-invocation escape hatch — always wins | +| **2** | **`.dailybot/env.json` active profile** | **New in 3.7.0** — the whole innovation | +| 3 | `.dailybot/profile.json::profile` → `agents.json` | Existing repo profile → global agent profile chain | +| 4 | `agents.json` default profile | Global default | +| 5 | `DAILYBOT_API_KEY` env var | Session-level | +| 6 | `config.json::api_key` (from `dailybot config key=...`) | Persistent global | +| 7 | Login session Bearer token (`credentials.json::token`) | From `dailybot login` | + +When `env.json::disabled` is `true`, or `active` is empty/null/unknown, the file is transparently skipped and every resolver behaves as if the file didn't exist. + +Two precision notes (CLI >= 3.7.0): + +- **Layer 2 holds on the wire, not just in resolution.** When the key comes from `env.json`, the HTTP client sends `X-API-KEY` on the **first** attempt even if a Bearer login session exists — the per-repo key wins even against a server that would have accepted the Bearer, and the global session token is never transmitted to the env.json server. Keys from layers 5–6 keep the historical Bearer-first wire order. +- **Layer 1 vs layer 2 for `agent *` commands:** a keyed `agents.json` profile beats `env.json` only when selected with an explicit `--profile` flag. The same profile resolved implicitly (via `profile.json::profile` or as the `agents.json` default) yields to `env.json`. `dailybot agent profiles --resolve` always shows exactly what will be sent. + +--- + +## Security — non-negotiable rules + +`env.json` is one of two files (the other being `credentials.json` in the global config dir) where the CLI stores API keys in plain text. Inside a repo, extra care is required — four independent layers of protection back the "never commit" rule. + +### 1. Gitignore is mandatory (and automatic in most setups) + +Every Dailybot-aware repo should have this in its root `.gitignore`: + +```gitignore +.dailybot/* +!.dailybot/profile.json +``` + +The broad ignore covers `env.json` automatically. **`env.json` is NEVER excepted** — only `profile.json` is. The Dailybot CLI's own `.gitignore` uses this exact pattern. There is no legitimate reason to un-ignore `env.json` — not with `!.dailybot/env.json`, not with a per-machine dot-file trick, not with `git update-index --assume-unchanged` (that only defers the leak). + +### 2. Owner-only permissions (`0o600`) + +Every write via `dailybot env` creates the file with mode `0o600` **from the first byte** (`os.open(..., 0o600)` — there is no umask window where the keys sit world-readable), and every load re-chmods it defensively — even if the file was created by an editor or `cp` with a lax umask. + +### 3. Fatal refuse-if-tracked guard — fires at the ROOT of every CLI invocation + +The root `cli()` callback in `dailybot_cli/main.py` calls `load_repo_env()` on **every command invocation**. That function runs: + +```bash +git ls-files --error-unmatch .dailybot/env.json +``` + +If the file is tracked, `RepoEnvError` fires, `print_error()` writes to stderr, and `SystemExit(1)` aborts the process **before any subcommand runs**. "Tracked" includes **staged-but-uncommitted** — `git ls-files` reads the index, so a stray `git add -f` trips the guard before a commit ever happens. Sample stderr: + +``` +Error: /path/.dailybot/env.json is tracked by git. This file contains API keys and +must never be committed. Fix with: + git rm --cached .dailybot/env.json + # ensure your .gitignore ignores .dailybot/env.json + git commit -m 'chore: untrack .dailybot/env.json' +The CLI refuses to load env.json while it is tracked. +``` + +**No auth-consuming command bypasses this** — `dailybot status`, `dailybot user list`, `dailybot form list`, `dailybot agent update`, `dailybot env show`, `dailybot login`, `dailybot upgrade`, `dailybot uninstall`, everything is blocked. There is no silent fallback to global auth — the CLI refuses to operate until `env.json` is untracked. Exactly two carve-outs: + +- `dailybot --help` / `dailybot --version` — Click short-circuits them before the callback runs, so the developer can always read instructions. +- The `dailybot hook *` group — it prints the same error to stderr but **still runs and exits 0**, honoring its always-exit-0 harness contract (a tracked env.json must not break every agent session in the repo). Hook commands are local-only and never consume env.json auth, so nothing leaks through this path. + +Edge case: if the `git` binary is not on PATH but a `.git` directory exists in an ancestor, the guard cannot verify tracking — it degrades to a **loud warning** instead of a silent pass. Treat that warning as a prompt to check `.gitignore` manually. + +### 4. Write-time gitignore warning + +`dailybot env add` also runs `git check-ignore` after writing. If `env.json` is **not** covered by any ignore rule, a warning fires on stderr — non-fatal (a brand-new repo might not have a `.gitignore` yet) but very visible: + +``` +Warning: /path/.dailybot/env.json is NOT gitignored. This file contains API keys +and must never be committed. Add `.dailybot/*` (except `!.dailybot/profile.json`) +to your .gitignore before committing. +``` + +### If the developer accidentally committed `env.json` + +Treat it as a compromise — the world has seen the keys the instant the push landed. Recovery: + +1. **Rotate every key in the file immediately** at Dailybot → Settings → API Keys. The old keys must be considered burned. +2. `git rm --cached .dailybot/env.json && git commit -m 'chore: untrack .dailybot/env.json'` +3. Verify `.gitignore` covers `.dailybot/*` (add it if missing) — otherwise the very next `dailybot env add` will re-stage the file. +4. Rewrite `env.json` locally with the freshly rotated keys via `dailybot env add ...`. +5. If the repo has been pushed anywhere (public or private), follow [GitHub's guide to removing sensitive data](https://docs.github.com/en/authentication/keeping-your-account-and-data-secure/removing-sensitive-data-from-a-repository) — but do NOT skip step 1. Rotation is what actually contains the exposure; history rewrite is cosmetic and does not undo the leak. + +Do NOT try to `git filter-repo` the leaked file out and call it done — assume compromise and rotate first, rewrite history second. + +### Quick full audit an agent can run on demand + +If the developer asks "is my env.json really safe?", run this end-to-end check: + +```bash +ROOT="$(git rev-parse --show-toplevel 2>/dev/null || pwd)" +ENV_FILE="$ROOT/.dailybot/env.json" + +echo "--- 1) Does the file exist? ---" +[ -f "$ENV_FILE" ] && echo "yes: $ENV_FILE" || echo "no (nothing to audit)" + +echo "--- 2) Is it gitignored? ---" +(cd "$ROOT" && git check-ignore -v .dailybot/env.json) || echo "NOT IGNORED (fix .gitignore)" + +echo "--- 3) Is it accidentally tracked? ---" +(cd "$ROOT" && git ls-files --error-unmatch .dailybot/env.json 2>/dev/null) \ + && echo "TRACKED (SECURITY VIOLATION — rotate keys + git rm --cached)" \ + || echo "not tracked (good)" + +echo "--- 4) File permissions ---" +[ -f "$ENV_FILE" ] && stat -c '%a %n' "$ENV_FILE" 2>/dev/null || stat -f '%A %N' "$ENV_FILE" +# Expect 600. + +echo "--- 5) CLI resolution ---" +dailybot env show # masks API keys; confirms the CLI is reading the file +``` + +Any of 2/3/4 tripping = actionable finding. + +--- + +## Detection pre-flight (when an agent is helping a developer manage keys) + +Only run this if the developer's request explicitly touches per-repo auth. Do not preemptively read env.json for every session — it contains secrets and there's no benefit to loading it if you're not being asked about it. + +```bash +ROOT="$(git rev-parse --show-toplevel 2>/dev/null || pwd)" +ENV_FILE="$ROOT/.dailybot/env.json" + +if [ -f "$ENV_FILE" ]; then + echo "REPO_ENV_EXISTS=1" + # NEVER cat this file — it contains API keys. Use the CLI's show/list + # subcommands which mask keys automatically: + dailybot env show 2>&1 +else + echo "REPO_ENV_EXISTS=" +fi +``` + +Rules: + +- **Never `cat`, `head`, or otherwise print the raw file** — API keys are inside. Use `dailybot env show` / `dailybot env list` which mask them. +- **Never suggest committing `env.json`** — the CLI will refuse to load it once it's tracked. +- **Never write API keys into `profile.json`** — that's a hard error. +- If the developer asks "what env am I in?", use `dailybot env show` (masked) — do not read the file directly. + +--- + +## Worked examples + +### Example 1 — First-time setup for a local dev org + +Developer: *"I need to test against my local Dailybot instance for this project without breaking my prod login."* + +```bash +# 1. Confirm CLI >= 3.7.0 (env command exists). +dailybot env --help >/dev/null 2>&1 || { + echo "This feature requires dailybot-cli >= 3.7.0. Run: dailybot upgrade" >&2 +} + +# 2. Ensure the gitignore covers .dailybot/* (create if needed). +grep -q '^\.dailybot/\*' .gitignore 2>/dev/null || { + cat >> .gitignore <<'EOF' + +# Dailybot per-repo state (env.json contains API keys — never commit it) +.dailybot/* +!.dailybot/profile.json +EOF +} + +# 3. Add the local profile. It becomes active automatically because it's the first. +dailybot env add \ + --name local \ + --key sk_local_xxxxxxxx \ + --api-url http://localhost:8000 \ + --app-url http://localhost:8090 + +# 4. Verify. +dailybot env show +``` + +Every subsequent `dailybot` command in this repo now talks to `http://localhost:8000` with the local key. In every other repo, the prod login remains untouched. + +### Example 2 — Toggling between staging and prod for QA + +Developer: *"I want to reproduce a staging bug, then switch back to prod."* + +```bash +dailybot env add --name prod --key sk_prod_xxxx # first → auto-active +dailybot env add --name staging --key sk_staging_yyyy \ + --api-url https://staging-api.example.com + +# Switch to staging for the bug repro session. +dailybot env use staging + +# ... reproduce the bug ... + +# Switch back. +dailybot env use prod +``` + +### Example 3 — Temporarily disabling env.json to test global auth + +Developer: *"I want to see what would happen with my global config for a minute, but don't lose my env.json setup."* + +```bash +dailybot env off # env.json ignored, CLI falls through to global auth +# ... test something ... +dailybot env on # restores the previously active profile +``` + +`env off` sets `disabled: true` at the top level — the `active` selection is preserved so `env on` restores it instantly. + +Verification pattern the developer can run to prove the toggle actually works: + +```bash +dailybot env show # Active env.json Profile: local +dailybot status --auth # → Authenticated via API key (local org) + +dailybot env off +dailybot env show # env.json is disabled (active would be: local) +dailybot status --auth # → Authenticated via login (OTP) (falls back to Bearer) + +dailybot env on +dailybot env show # Active env.json Profile: local (restored) +dailybot status --auth # → Authenticated via API key (local org again) +``` + +If step 2 does not fall back — i.e., the CLI keeps using the env.json profile after `env off` — that's a bug; report it. + +### Example 4 — Removing an environment cleanly + +```bash +dailybot env remove staging --yes +# If 'staging' was the active profile, active is cleared and the CLI +# falls back to global auth until you run `dailybot env use ` again. +``` + +--- + +## Interaction with existing auth flows + +- **`dailybot login` still works.** It writes to `~/.config/dailybot/credentials.json` (Bearer session). If `env.json` is active for a repo, that key wins over the Bearer for that repo. In other repos (or when `env.json` is disabled/inert), the Bearer takes over normally. +- **`dailybot logout` is unaffected.** It only clears the Bearer session. Your `env.json` remains intact. +- **`dailybot config key=...` still works.** It writes to `~/.config/dailybot/config.json`. `env.json` sits above it in the precedence order. +- **`DAILYBOT_API_KEY` still works.** For CI or one-off overrides. `env.json` beats it inside a repo; outside a repo (or when disabled), the env var wins. +- **Repo `profile.json` is orthogonal.** It still governs the *display name* and `default_metadata` for reports. `env.json` provides *credentials + URLs*. Both can be present. + +### env.json key first + transparent alt-credential retry (auto) + +When the resolved API key comes from `env.json`, the CLI's HTTP client sends it on the **first** attempt — the global Bearer session never reaches the env.json server. This is what makes the "logged into prod, `cd` into a local-dev repo" case Just Work in one round-trip: + +``` + + client.auth_status() + | + | Attempt 1: X-API-KEY -> http://localhost:8000 + | 200 OK (prod Bearer never leaves the machine) + | + + returns local org data (silently) +``` + +Backing that up, the client automatically retries every user-scoped and agent-scoped call **once** with the alternative credential when the server answers 401 or 403 — in either direction (stale env.json key → Bearer, stale Bearer → API key). + +Retry semantics: + +- Triggers on **HTTP 401 or 403** (Django/DRF answers 403 for rejected credentials just as often as 401; both are treated as "credential problem, try the other one"). +- Fires **at most once per call** with the alternative credential — a double rejection surfaces as a normal auth error. +- **Login-lifecycle endpoints do NOT retry** — `dailybot login`, `dailybot logout`, and the agent-registration challenge always report the truth of what happened (the credential IS what's being negotiated there, or invalidated). +- **`dailybot status --auth` inspects the auth mode after the call** and reports which credential actually succeeded on the wire (`Authenticated via API key` vs `Authenticated via login (OTP)`), so the developer always sees the truth. +- **`dailybot login` inside a repo with an active env.json profile warns first** — login persists the resolved `api_url` into the GLOBAL `~/.config/dailybot/credentials.json`, so the CLI names the profile and the server and suggests `dailybot env off` before proceeding. + +Ships with the same CLI floor as `env.json` itself. + +--- + +## Troubleshooting + +**"The CLI is not using my env.json."** +1. `dailybot env show` — is it reporting the profile you expect? +2. Look at `disabled`, `active`, and the walk-up path. `env show` prints the resolved file path — is it the one you edited? +3. Are you running with `--profile` / `--api-url` / `--app-url`? Flags win. +4. Did you edit the file directly? Check the JSON — the CLI's `env` commands validate on write, but hand-edits can produce invalid JSON that the loader rejects with a parse warning (printed to stdout, once per process) before falling back to global auth. + +**"The CLI refuses to run and complains about tracked env.json."** +Run the fix printed in the error. This is the fatal refuse-if-tracked guard doing its job. (Exception: `dailybot hook *` commands print the error but still run and exit 0 — that is by design, not a hole; see § Security above.) + +**"I set `disabled` to `"true"` by hand and the file is still active."** +`disabled` must be a JSON boolean (`true`, no quotes). The CLI warns about the string and treats it as `false` so a typo never silently changes which org you talk to. Run `dailybot env off` instead of hand-editing. + +**"I edited env.json by hand and now nothing works."** +`dailybot env show` will surface schema warnings. If unrecoverable, delete the file and re-add profiles via `dailybot env add`. + +**"I want the same profile across many repos without duplicating it."** +That's what `~/.config/dailybot/agents.json` (global profiles) is for — see `dailybot agent configure`. `env.json` is intentionally per-repo. + +--- + +## Version compatibility + +- Requires **`dailybot-cli >= 3.7.0`**. Older CLIs never look at `.dailybot/env.json` and treat it as harmless clutter. +- The Dailybot agent skill pack targeting this doc requires the same floor. +- If a developer is on an older CLI, offer to upgrade first: `dailybot upgrade` (auto-detects install method). + +--- + +## See also + +- [`shared/auth.md`](auth.md) — the general authentication flow (OTP login, API key alternatives, CLI installation). +- [`shared/repo-profile.md`](repo-profile.md) — the sibling file `profile.json` (agent identity, committed). +- [CLI configuration reference](https://github.com/DailybotHQ/cli/blob/main/docs/CONFIGURATION.md#repo-level-env-override-dailybotenvjson) — canonical schema + precedence + security posture. +- [CLI auth-resolution order](https://github.com/DailybotHQ/cli/blob/main/AGENTS.md#14-auth-resolution-order-do-not-break) — the per-field precedence the CLI implements. +- [CLI security posture](https://github.com/DailybotHQ/cli/blob/main/docs/SECURITY.md) — the four-layer protection for `env.json`. diff --git a/.agents/skills/dailybot/shared/list-query-and-errors.md b/.agents/skills/dailybot/shared/list-query-and-errors.md index d1d5d34..c48cec8 100644 --- a/.agents/skills/dailybot/shared/list-query-and-errors.md +++ b/.agents/skills/dailybot/shared/list-query-and-errors.md @@ -1,10 +1,10 @@ # Shared reference — list query flags, pagination, and machine-readable errors -> **Requires `dailybot-cli >= 3.1.2`** (the skill-pack baseline). Everything on this page — the shared +> **Requires `dailybot-cli >= 3.7.0`** (the skill-pack baseline). Everything on this page — the shared > list query flags, the `{count, next, previous, results}` pagination envelope, > the `Showing X of N` footer, the machine-readable error `code` dispatch, and > the API-key / Bearer parity + free-plan gating rules — is available at this -> floor. If `dailybot --version` is below 3.1.2, ask the developer to run +> floor. If `dailybot --version` is below 3.7.0, ask the developer to run > `dailybot upgrade`. This is the **single source of truth** for behavior shared across every @@ -27,7 +27,7 @@ that flag already means "every author's responses", not "every page"). | `--page-size N` | | Items per page. **Max 100** — larger values are clamped client-side. Passing it alone returns that one page, not the whole list. | | `--all` | | Fetch **every** page and concatenate the results. Mutually exclusive with `--limit`. | | `--limit N` | | Stop after the first `N` items (across pages). Mutually exclusive with `--all`. | -| `--search TEXT` | `--grep TEXT` | Case-insensitive substring filter. **Max 256 chars** — longer queries are truncated client-side before the request. | +| `--search TEXT` | `--grep TEXT` | Case-insensitive substring filter. **Max 256 chars** — longer queries are rejected client-side with an error before the request is made. | | `--since YYYY-MM-DD` | | Start of a date range (inclusive). | | `--until YYYY-MM-DD` | | End of a date range (inclusive). | | `--date YYYY-MM-DD` | | A single day (shorthand for `--since D --until D`). | @@ -151,7 +151,7 @@ In `--json` mode the error surfaces as `{ error, status, code, detail }`. | `code` | Meaning | What to do | |--------|---------|------------| | `target_user_inactive` | The targeted user is deactivated. | Pick an active user. | -| `search_query_too_long` | `--search` exceeded the limit. | The CLI truncates to 256 chars client-side; if you see this, shorten the query. | +| `search_query_too_long` | `--search` exceeded the 256-char limit. | The query is rejected client-side before the request. If you hit this server-side, shorten the query. | | `invalid_date_range` | `--since`/`--until` are malformed or reversed. | Fix the dates (`YYYY-MM-DD`, since ≤ until). | | `invalid_user_identifier` | `--user` was given an email or a name. | `--user` takes **only a UUID**. Get it from `dailybot user list --json`. (Caught client-side before the request.) | | `invalid_workflow_state` | On `form responses --state`: the form has no workflow. On `form create` / `form config --state`: the `"Label:#color"` spec is malformed. | Two meanings, one code — read which command you ran. For the filter, drop `--state` (or pick a workflow form). | @@ -160,6 +160,8 @@ In `--json` mode the error surfaces as `{ error, status, code, detail }`. | `send_as_user_not_found` | The `--send-as-user` UUID doesn't resolve to a user. | Confirm the user exists (`dailybot user list`). | | `invalid_kudos_filter` | `kudos list --filter` got an unrecognized value. | Use `received` or `given` (the CLI also accepts `KUDOS_RECEIVED` / `KUDOS_GIVEN`). | | `send_message_validation_error` | `chat send` payload is missing content or otherwise invalid. | Read the `detail` — it names the problem (e.g. no message/buttons/image). | +| `invalid_owner_user_id` | `--owner` value isn't a valid UUID (after resolution). | Fix the UUID or name. | +| `too_many_owner_user_ids` | More than 50 `--owner` values. | Narrow the filter — max 50 owners per request. | ### 429 — rate limit diff --git a/.agents/skills/dailybot/shared/repo-profile.md b/.agents/skills/dailybot/shared/repo-profile.md index 4c4abc1..9dc0ff4 100644 --- a/.agents/skills/dailybot/shared/repo-profile.md +++ b/.agents/skills/dailybot/shared/repo-profile.md @@ -10,7 +10,7 @@ This pre-flight closes that gap. Run it once per turn (or once per work session ## The rule (one line) -> Before constructing any `dailybot ` command line, walk up from `$PWD` looking for a `.dailybot/` directory. If `.dailybot/profile.json` exists in the closest ancestor, **omit from your command every flag the profile already provides**. +> Before constructing any `dailybot ` command line, walk up from `$PWD` looking for a `.dailybot/` directory. If `.dailybot/profile.json` exists in the closest ancestor, **omit from your command every flag the profile already provides**. (If `.dailybot/env.json` also exists, the CLI reads it automatically for credentials + URL overrides — see [`shared/env-json.md`](env-json.md); do not attempt to override its keys from the command line.) What "already provides" means concretely: @@ -147,12 +147,24 @@ This applies to: `dailybot-report`, `dailybot-chat`, `dailybot-kudos`, `dailybot ## What about `.dailybot/` files other than `profile.json`? -The schema may grow. Today the only file the CLI reads from `.dailybot/` is `profile.json`. If you find other files in `.dailybot/`, do not act on them — just leave them alone. A future skill-pack release will add specific guidance for any new file. +Since CLI **3.7.0**, `.dailybot/` also supports an **opt-in, gitignored** file called `env.json` that carries per-repo API keys + URLs for one or more environments. It is orthogonal to `profile.json` — different purpose, different lifecycle, different security posture: + +| File | Committed? | Purpose | +|---|---|---| +| `.dailybot/profile.json` | **Yes** (tracked) | *Identity* — how reports get signed (team-shared) | +| `.dailybot/env.json` | **No** (gitignored) | *Auth context* — which org the CLI talks to (per-developer) | + +If the developer asks about per-repo API keys, staging/local dev orgs, or "logging into different orgs in different repos", route them to [`shared/env-json.md`](env-json.md) instead — that file has the full workflow, security rules, and CLI commands. + +Do **not** attempt to read `env.json` directly (`cat` etc.) from an agent context — it contains API keys. Use `dailybot env show` / `dailybot env list`, which mask them automatically. + +Any other file you find in `.dailybot/` is out of scope for this skill pack — leave it alone. --- ## See also - [`shared/auth.md`](./auth.md) — full authentication / profile resolution model (Bearer token, API key, profile slug, env var). +- [`shared/env-json.md`](./env-json.md) — the sibling `env.json` file (per-repo API keys + URLs, gitignored, CLI 3.7.0+). - [CLI auth-resolution order](https://github.com/DailybotHQ/cli/blob/main/AGENTS.md#14-auth-resolution-order-do-not-break) — the per-field precedence the CLI implements (this doc is the agent-side mirror). - [CLI configuration reference](https://github.com/DailybotHQ/cli/blob/main/docs/CONFIGURATION.md) — the full `.dailybot/profile.json` schema, security rules, and migration notes. diff --git a/.agents/skills/dailybot/teams/SKILL.md b/.agents/skills/dailybot/teams/SKILL.md index 17e871c..dae65ca 100644 --- a/.agents/skills/dailybot/teams/SKILL.md +++ b/.agents/skills/dailybot/teams/SKILL.md @@ -1,7 +1,7 @@ --- name: dailybot-teams description: 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 logic. -version: "3.4.0" +version: "3.10.3" 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)"}]}} @@ -10,7 +10,7 @@ allowed-tools: Bash, Read, Grep, Glob # Dailybot Teams -> **Requires `dailybot-cli >= 3.1.2`** (the skill-pack baseline). `dailybot team list`, `dailybot team get`, and the account-context commands `dailybot me` / `org` / `user get` are all available. If `dailybot --version` is below 3.1.2, ask the developer to run `dailybot upgrade`. See [`../SKILL.md` § Required Dailybot CLI version](../SKILL.md#required-dailybot-cli-version) for install commands and version-check tooling. +> **Requires `dailybot-cli >= 3.7.0`** (the skill-pack baseline). `dailybot team list`, `dailybot team get`, and the account-context commands `dailybot me` / `org` / `user get` are all available. If `dailybot --version` is below 3.7.0, ask the developer to run `dailybot upgrade`. See [`../SKILL.md` § Required Dailybot CLI version](../SKILL.md#required-dailybot-cli-version) for install commands and version-check tooling. You help agents resolve and read teams visible to the logged-in user. Teams are how Dailybot groups people inside an organization — they're the targets for team-scoped kudos, the routing context for some messages, and the source of truth for "who's in X?". @@ -170,7 +170,7 @@ Returns the team plus its membership when `--with-members` is set. Useful when t ## Step 4.5 — Read a single user, and your own account context -> **Baseline:** `user get`, `me`, and `org` are part of the `dailybot-cli >= 3.1.2` baseline. +> **Baseline:** `user get`, `me`, and `org` are part of the `dailybot-cli >= 3.7.0` baseline. The org directory has always been readable in bulk via `dailybot user list` (names + UUIDs; emails hidden as PII). You can also read diff --git a/.agents/skills/dailybot/workflow/SKILL.md b/.agents/skills/dailybot/workflow/SKILL.md index 90ce0d3..9a052b3 100644 --- a/.agents/skills/dailybot/workflow/SKILL.md +++ b/.agents/skills/dailybot/workflow/SKILL.md @@ -1,7 +1,7 @@ --- name: dailybot-workflow description: List and inspect Dailybot workflows (read-only) — enumerate the workflows configured for the organization and read one workflow's configuration. Use when the developer asks "list my workflows", "show workflows", or "what's in the release workflow?". Writes are done in the Dailybot web app; this skill only reads. Plan-gated feature. -version: "3.4.0" +version: "3.10.3" 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)"}]}} @@ -10,9 +10,9 @@ allowed-tools: Bash, Read, Grep, Glob # Dailybot Workflows (read-only) -> **Requires `dailybot-cli >= 3.1.2`** (the skill-pack baseline). The `dailybot workflow list` / +> **Requires `dailybot-cli >= 3.7.0`** (the skill-pack baseline). The `dailybot workflow list` / > `dailybot workflow get` command group is available. If -> `dailybot --version` reports below 3.1.2, ask the developer to run +> `dailybot --version` reports below 3.7.0, ask the developer to run > `dailybot upgrade`. See [`../SKILL.md` § Required Dailybot CLI version](../SKILL.md#required-dailybot-cli-version) > for install commands and version-check tooling. diff --git a/.agents/skills/deepworkplan/SKILL.md b/.agents/skills/deepworkplan/SKILL.md index cdca71c..ae5e2f4 100644 --- a/.agents/skills/deepworkplan/SKILL.md +++ b/.agents/skills/deepworkplan/SKILL.md @@ -1,7 +1,7 @@ --- name: deepworkplan description: DeepWorkPlan — turn any repo AI-first and run Deep Work Plans. Routes to create, execute, refine, resume, status, verify, 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. -version: "2.16.0" +version: "2.16.1" documentation_url: https://deepworkplan.com user-invocable: true allowed-tools: Bash, Read, Grep, Glob, Edit, Write diff --git a/.agents/skills/deepworkplan/addons/README.md b/.agents/skills/deepworkplan/addons/README.md index f45a226..2a936e5 100644 --- a/.agents/skills/deepworkplan/addons/README.md +++ b/.agents/skills/deepworkplan/addons/README.md @@ -61,7 +61,7 @@ An addon MAY additionally ship per-stack presets, examples, or migration notes. | Addon | Folder | Status | |-------|--------|--------| | Devcontainer support | [`addons/devcontainer/`](devcontainer/SKILL.md) | **Authored** — compose-based `.devcontainer/` + `docker/` with AI-CLI persistence, `dailybot-project-network`, `DOCKER_DEV_ENV=vscode`, project-identity precedence, public-OSS variant, 7 reasoning presets. | -| Dailybot integration | [`addons/dailybot/`](dailybot/SKILL.md) | **Authored** — opt-in install of the Dailybot agent skill (**3.4.0**) / CLI (**>= 3.1.2**), auth **deferred** to the Dailybot skill's own consent flow, **four lifecycle events** (kickoff, significant task, blocked, completion) wired as optional best-effort reports via the `report` sub-skill, optional deterministic hook enforcement, and access to the full 13-capability Dailybot skill when invoked directly. The core methodology has **zero** Dailybot dependency. | +| Dailybot integration | [`addons/dailybot/`](dailybot/SKILL.md) | **Authored** — opt-in install of the Dailybot agent skill (**3.10.3**) / CLI (**>= 3.7.0**), auth **deferred** to the Dailybot skill's own consent flow, **four lifecycle events** (kickoff, significant task, blocked, completion) wired as optional best-effort reports via the `report` sub-skill, optional deterministic hook enforcement, and access to the full 14-capability Dailybot skill when invoked directly. The core methodology has **zero** Dailybot dependency. | | Dependency upgrade | [`addons/dependency-upgrade/`](dependency-upgrade/SKILL.md) | **Authored** — opt-in, **package-manager-agnostic** dependency upgrades: detect the repo's real manager (npm/pnpm/yarn + ncu, pip/poetry/uv, cargo, go mod, bundler, composer…), classify by semver, upgrade in safe batches, run the repo's **real** validation gate after each batch, revert a failing batch, summarize. Installs a `/lib-upgrade` delegator into the repo's `.agents/commands/` only when accepted. | | Design system | [`addons/design-system/`](design-system/SKILL.md) | **Authored** — opt-in, **interface-surface-scoped** `DESIGN.md` at `docs/DESIGN.md` (indexed from `AGENTS.md`; root only if no `docs/` tree), covering three profiles in one file: **visual-ui** (design tokens from CSS vars / Tailwind config / token files / component styles; WCAG AA contrast), **cli-output** (semantic terminal styles, output components, TTY/`NO_COLOR` degradation), and **conversational** (voice & register, message anatomy, per-platform rendering with plain-text fallbacks). Reason about the repo's **real** design source — never a brand file — and reconcile an existing `DESIGN.md` instead of clobbering it. Offered by `onboard` **only when an interface surface is detected**: visual-ui is default-on when detected; cli-output and conversational are recommended when detected, always asked, never auto-applied. | diff --git a/.agents/skills/deepworkplan/addons/dailybot/SKILL.md b/.agents/skills/deepworkplan/addons/dailybot/SKILL.md index 0113d1d..8660571 100644 --- a/.agents/skills/deepworkplan/addons/dailybot/SKILL.md +++ b/.agents/skills/deepworkplan/addons/dailybot/SKILL.md @@ -1,7 +1,7 @@ --- name: deepworkplan-addon-dailybot -description: Optional DeepWorkPlan addon that connects an AI-first repo to the developer's Dailybot team — installing (with consent) the Dailybot agent skill (DailybotHQ/agent-skill, currently 3.4.0) and/or the Dailybot CLI (DailybotHQ/cli, >= 3.1.2), wiring the plan lifecycle into best-effort agent updates - kickoff when a plan starts, significant task completions, a blocked report when an unattended run halts, and a milestone on plan completion - with payloads derived from the plan's state layer, and optionally committing the Dailybot skill's deterministic hook enforcement (dailybot hook lifecycle hooks) so the agent harness itself reminds agents about unreported work. Opt-in, never required, never blocks the work, reconciles existing setups instead of clobbering them, and defers all auth to the Dailybot skill's own consent flow. Use when the developer or team already uses Dailybot and wants DWP progress visible to humans. -version: "2.16.0" +description: Optional DeepWorkPlan addon that connects an AI-first repo to the developer's Dailybot team — installing (with consent) the Dailybot agent skill (DailybotHQ/agent-skill, currently 3.10.3) and/or the Dailybot CLI (DailybotHQ/cli, >= 3.7.0), wiring the plan lifecycle into best-effort agent updates - kickoff when a plan starts, significant task completions, a blocked report when an unattended run halts, and a milestone on plan completion - with payloads derived from the plan's state layer, and optionally committing the Dailybot skill's deterministic hook enforcement (dailybot hook lifecycle hooks) so the agent harness itself reminds agents about unreported work. Opt-in, never required, never blocks the work, reconciles existing setups instead of clobbering them, and defers all auth to the Dailybot skill's own consent flow. Use when the developer or team already uses Dailybot and wants DWP progress visible to humans. +version: "2.16.1" documentation_url: https://deepworkplan.com user-invocable: true allowed-tools: Bash, Read, Grep, Glob, Edit, Write @@ -17,11 +17,11 @@ be AI-first, and it **never blocks** the actual work. > ## The rule that overrides everything: this addon DEFERS, it does not reinvent > -> The official **Dailybot agent skill** (currently **3.4.0**) already owns +> The official **Dailybot agent skill** (currently **3.10.3**) already owns > install, consent, auth, context detection, the writing style, and the -> non-blocking guarantee. It exposes **13 coordinated capabilities** (report, +> non-blocking guarantee. It exposes **14 coordinated capabilities** (report, > ask, messages, email, chat, conversations, health, check-ins, kudos, teams, -> forms, workflows, report channels) — but **this addon's job is narrow**: (1) +> forms, workflows, report channels, per-repo API keys) — but **this addon's job is narrow**: (1) > **offer** to install the Dailybot skill/CLI through their own consent flows, > and (2) **wire** the optional **report** sub-skill into DWP `execute`/plan > lifecycle. It MUST NOT duplicate, bypass, or weaken any Dailybot consent or @@ -80,18 +80,18 @@ without their explicit acceptance** — and where the Dailybot skill's own conse flow applies, defer to it rather than prompting yourself. - **Dailybot agent skill** (the recommended path — it brings the consent/auth - flow and the full 13-capability pack; currently **3.4.0**): + flow and the full 14-capability pack; currently **3.10.3**): - `npx skills add DailybotHQ/agent-skill` (cross-agent, recommended), or - `npx skills update dailybot` when already installed, or - OpenClaw native: `openclaw skills install dailybot`, or - `git clone https://github.com/DailybotHQ/agent-skill.git` + run its `setup.sh`. - **Dailybot CLI** (the underlying bridge, from - [`DailybotHQ/cli`](https://github.com/DailybotHQ/cli); minimum **`>= 3.1.2`** + [`DailybotHQ/cli`](https://github.com/DailybotHQ/cli); minimum **`>= 3.7.0`** for the whole skill pack; the skill installs it on first use via its own SHA-256-verified consent flow — you generally do **not** install it separately, but these are the supported paths if asked): - Verified install via the Dailybot skill's `shared/auth.md` (preferred), or - - `pip install 'dailybot-cli>=3.1.2'` (Python 3.10+), or + - `pip install 'dailybot-cli>=3.7.0'` (Python 3.10+), or - `brew install dailybothq/tap/dailybot` (macOS), or - `curl -fsSL https://cli.dailybot.com/install.sh | bash` — **only** with the checksum/consent verification the Dailybot skill documents (never run @@ -151,7 +151,7 @@ This is the integration value. Reasoning guidance is in ### Step 3b — Offer deterministic hook enforcement (OPT-IN, defer to the Dailybot skill) The lifecycle wiring above is prompt-layer: it relies on the model remembering -to report. With `dailybot-cli` **>= 3.1.2** (included in the current **3.4.0** +to report. With `dailybot-cli` **>= 3.7.0** (included in the current **3.10.3** skill pack), the Dailybot skill ships **deterministic hook enforcement** (`report/hooks.md`): harness lifecycle hooks (`dailybot hook session-start | activity | post-commit | stop | dismiss`) backed by a local per-repo report @@ -160,7 +160,7 @@ end of turn — even in long unattended sessions where prompt instructions decay This is the strongest version of the visibility this addon exists for. - **Offer it** (consent-gated, show the exact config before writing) when - `dailybot --version` reports **>= 3.1.2**: commit the repo-level hook config — + `dailybot --version` reports **>= 3.7.0**: commit the repo-level hook config — Claude Code `.claude/settings.json` (or `.agents/settings.json` where `.claude → .agents`), Cursor `.cursor/hooks.json` (or via `.cursor → .agents`), other harnesses per the @@ -179,14 +179,14 @@ This is the strongest version of the visibility this addon exists for. deterministic backstop when a lifecycle event was missed. A hook reminder mid-plan is answered with either a lifecycle-appropriate report or `dailybot hook dismiss` — never ignored, never blocking. -- **Degrade gracefully.** CLI below 3.1.2 → skip this step (the Step 3 wiring +- **Degrade gracefully.** CLI below 3.7.0 → skip this step (the Step 3 wiring stands alone) and mention `dailybot upgrade` once. The `dailybot hook` commands are local-only and always exit 0, so installing them cannot violate the never-block rule; they also respect `.dailybot/disabled`. ### Step 4 — Validate (SPEC §Validation) Run the validation checklist and report: whether the skill/CLI is present (skill -**>= 3.4.0** recommended, CLI **>= 3.1.2**), that auth was deferred (not +**>= 3.10.3** recommended, CLI **>= 3.7.0**), that auth was deferred (not reinvented), that the report step is wired as **optional + non-blocking**, whether hook enforcement was offered/installed, the identity source if any, and any deferred items. diff --git a/.agents/skills/deepworkplan/addons/dailybot/SPEC.md b/.agents/skills/deepworkplan/addons/dailybot/SPEC.md index e2d5d15..f32cb05 100644 --- a/.agents/skills/deepworkplan/addons/dailybot/SPEC.md +++ b/.agents/skills/deepworkplan/addons/dailybot/SPEC.md @@ -30,9 +30,9 @@ baseline AI-first conformance. > machine-readable state layer (`PLAN_STATE.md`). All events remain opt-in, > conditional, and non-blocking; the completion milestone is unchanged. > -> **Additive in 2.3.0.** Version gates align with the Dailybot agent skill **3.4.0** -> and `dailybot-cli` **>= 3.1.2** (unified floor — hooks, chat, authoring, and -> browse/read surface ship together). §3.5 documents the paired skill's full +> **Additive in 2.3.0.** Version gates align with the Dailybot agent skill **3.10.3** +> and `dailybot-cli` **>= 3.7.0** (unified floor — hooks, chat, authoring, the +> browse/read surface, and the per-repo `.dailybot/env.json` auth added in CLI 3.7.0 ship together). §3.5 documents the paired skill's full > capability surface; this addon still wires only the `report` sub-skill. ## 1. Conventions @@ -88,7 +88,7 @@ with explicit acceptance, and each reconciled if already present (§7): Dailybot skill's `shared/auth.md` (cross-origin diff against the GitHub source + `.sha256` sidecar match, optional cosign). The addon **MUST NOT** recommend piping the script to a shell **unverified**, **or** - - `pip install 'dailybot-cli>=3.1.2'` (Python 3.10+), **or** + - `pip install 'dailybot-cli>=3.7.0'` (Python 3.10+), **or** - `brew install dailybothq/tap/dailybot` (macOS), **or** - Windows PowerShell: `irm https://cli.dailybot.com/install.ps1 | iex` (when WSL2 / Git Bash unavailable). @@ -108,8 +108,8 @@ with explicit acceptance, and each reconciled if already present (§7): ### 3.4 Optional harness hook enforcement -- When `dailybot-cli` is **>= 3.1.2** (the unified floor for the current skill - pack, currently **3.4.0**), the addon **SHOULD** offer — and **MAY**, with +- When `dailybot-cli` is **>= 3.7.0** (the unified floor for the current skill + pack, currently **3.10.3**), the addon **SHOULD** offer — and **MAY**, with explicit acceptance, commit — repo-level harness hook configs whose entries invoke the `dailybot hook` lifecycle commands (`session-start`, `activity`, `post-commit`, `stop`, `dismiss`), e.g. Claude Code `.claude/settings.json` @@ -122,7 +122,7 @@ with explicit acceptance, and each reconciled if already present (§7): - The addon **MUST NOT** write hook configs without explicit acceptance, and **MUST** merge into existing config files — never overwrite (§7). Existing `dailybot hook` entries **MUST** be preserved, not duplicated. -- When the CLI is below 3.1.2, the addon **MUST** skip this offer (the §5 +- When the CLI is below 3.7.0, the addon **MUST** skip this offer (the §5 wiring stands alone) and **MAY** suggest `dailybot upgrade` once. - The committed `.dailybot/profile.json` **MAY** include `"report": {"mode": "continuous"}` for research/docs-heavy repos so non-commit @@ -130,12 +130,13 @@ with explicit acceptance, and each reconciled if already present (§7): ### 3.5 Paired Dailybot skill — full capability surface (informational) -The Dailybot agent skill (currently **3.4.0**, source +The Dailybot agent skill (currently **3.10.3**, source [`DailybotHQ/agent-skill`](https://github.com/DailybotHQ/agent-skill)) exposes -**13 coordinated sub-skills**: report, ask, messages, email, chat, +**14 coordinated sub-skills**: report, ask, messages, email, chat, conversations, health, check-ins (complete + authoring), kudos (give + browse), teams (list/resolve + `me`/`org`/`user get`), forms (lifecycle + authoring), -workflows (read-only list/get), and report channels. **This addon wires only the +workflows (read-only list/get), report channels, and per-repo API keys +(`.dailybot/env.json` via `dailybot env`). **This addon wires only the `report` sub-skill** into DWP plan execution (§5). The other capabilities are available when the developer invokes the Dailybot skill directly — the addon **MUST NOT** wire them into DWP execution unless the developer explicitly asks. @@ -285,10 +286,10 @@ A repo is **conformant to this addon** when **all** hold (after acceptance): - `SKILL.md` (the onboarding hook + flow), `templates/INTEGRATION.md` (reasoning aid) - `../README.md` (addon mechanism), [`../../spec/ADDONS.md`](../../spec/ADDONS.md) (concept + pointer) - Dailybot skill: [`DailybotHQ/agent-skill`](https://github.com/DailybotHQ/agent-skill) - — `SKILL.md` (currently **3.4.0**), `shared/auth.md`, `TRUST.md`, + — `SKILL.md` (currently **3.10.3**), `shared/auth.md`, `TRUST.md`, `report/SKILL.md`, `report/hooks.md`, `report/triggers.md` - Dailybot CLI: [`DailybotHQ/cli`](https://github.com/DailybotHQ/cli), PyPI `dailybot-cli` - — minimum **>= 3.1.2**; `docs/AGENT_HOOKS.md` (the `dailybot hook` command group + — minimum **>= 3.7.0**; `docs/AGENT_HOOKS.md` (the `dailybot hook` command group + report ledger) - [`../../spec/PLAN_STATE.md`](../../spec/PLAN_STATE.md) (the state layer the payloads derive from), `../../spec/AGENT_PROTOCOL.md` §7 (unattended profile + stop conditions) diff --git a/.agents/skills/deepworkplan/addons/dailybot/templates/INTEGRATION.md b/.agents/skills/deepworkplan/addons/dailybot/templates/INTEGRATION.md index c31f1d8..4f25c1c 100644 --- a/.agents/skills/deepworkplan/addons/dailybot/templates/INTEGRATION.md +++ b/.agents/skills/deepworkplan/addons/dailybot/templates/INTEGRATION.md @@ -57,7 +57,7 @@ skill's own `shared/auth.md` flow. | Want | Offer | |------|-------| | **Dailybot skill** (recommended — brings consent/auth + `report`) | `npx skills add DailybotHQ/agent-skill` · OpenClaw `openclaw skills install dailybot` · `git clone https://github.com/DailybotHQ/agent-skill.git` + `./setup.sh` | -| **Dailybot CLI only** (developer explicitly wants the binary) | `pip install 'dailybot-cli>=3.1.2'` (Py 3.10+) · `brew install dailybothq/tap/dailybot` (macOS) · verified install via `shared/auth.md` · Windows: `irm https://cli.dailybot.com/install.ps1 \| iex` | +| **Dailybot CLI only** (developer explicitly wants the binary) | `pip install 'dailybot-cli>=3.7.0'` (Py 3.10+) · `brew install dailybothq/tap/dailybot` (macOS) · verified install via `shared/auth.md` · Windows: `irm https://cli.dailybot.com/install.ps1 \| iex` | > Prefer installing the **skill** — it owns the SHA-256-verified CLI install and > the OTP/API-key auth flow. Only surface the raw CLI commands when the developer @@ -146,17 +146,17 @@ Decision notes: --- -## 4b. Offer deterministic hook enforcement (CLI >= 3.1.2) +## 4b. Offer deterministic hook enforcement (CLI >= 3.7.0) The §4 wiring is prompt-layer — it relies on the model remembering. When -`dailybot-cli` is **>= 3.1.2** (the unified floor for the current skill pack, -currently **3.4.0**), also offer (opt-in, show the exact config first) to commit +`dailybot-cli` is **>= 3.7.0** (the unified floor for the current skill pack, +currently **3.10.3**), also offer (opt-in, show the exact config first) to commit the repo-level harness hook config so the harness itself reminds the agent about unreported work at end of turn: ```bash # Version gate — only offer when the CLI meets the floor -dailybot --version # >= 3.1.2 (hooks, chat, authoring, browse/read) +dailybot --version # >= 3.7.0 (hooks, chat, authoring, browse/read) dailybot version --check # confirms whether an upgrade is available ``` @@ -180,7 +180,7 @@ other harnesses per its table. Decision notes: `"report": {"min_interval_minutes": 30, "nudge": false}` turns reminders off for the repo while keeping manual reporting; `"mode": "continuous"` nudges non-commit work (research, docs, plans) sooner in research-heavy repos. -- **Older CLI:** below 3.1.2 → skip the offer, suggest `dailybot upgrade` once, +- **Older CLI:** below 3.7.0 → skip the offer, suggest `dailybot upgrade` once, and let the §4 wiring stand alone. --- diff --git a/.agents/skills/deepworkplan/addons/dependency-upgrade/SKILL.md b/.agents/skills/deepworkplan/addons/dependency-upgrade/SKILL.md index c718a08..9e9ae99 100644 --- a/.agents/skills/deepworkplan/addons/dependency-upgrade/SKILL.md +++ b/.agents/skills/deepworkplan/addons/dependency-upgrade/SKILL.md @@ -1,7 +1,7 @@ --- name: deepworkplan-addon-dependency-upgrade description: Optional 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, classifies upgrades (patch/minor/major), upgrades in safe batches, runs the repo's real validation gate after each batch, reverts a failing batch, and summarizes. Opt-in, never required, reconciles with the repo's existing tooling. Use when the developer wants to bring dependencies up to date without breaking the build. -version: "2.16.0" +version: "2.16.1" documentation_url: https://deepworkplan.com user-invocable: true allowed-tools: Bash, Read, Grep, Glob, Edit, Write diff --git a/.agents/skills/deepworkplan/addons/design-system/SKILL.md b/.agents/skills/deepworkplan/addons/design-system/SKILL.md index d1d1567..064ba32 100644 --- a/.agents/skills/deepworkplan/addons/design-system/SKILL.md +++ b/.agents/skills/deepworkplan/addons/design-system/SKILL.md @@ -1,7 +1,7 @@ --- name: deepworkplan-addon-design-system description: 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 files — visual-ui (rendered web/mobile/desktop UI), cli-output (styled terminal output — semantic colors, panels, spinners, prompts, TTY/NO_COLOR degradation), and conversational (chat/email messaging — voice and register, message anatomy, per-platform rendering). Reasons about the repo's ACTUAL design source (CSS custom properties, Tailwind config, token files, component styles, a CLI display/theme module, or message-composition helpers) rather than copying a brand file; checks contrast (WCAG AA), color-is-not-the-only-carrier, plain-text fallbacks, and token integrity. The visual-ui profile is default-on when detected (applied in trust mode, strongly recommended in guided mode); cli-output and conversational are recommended when detected and always asked about, never auto-applied. Never offered for a repo with no interface surface (pure library, headless service, infra-only); never required for baseline conformance; reconciles an existing DESIGN.md instead of clobbering it. Use when the developer wants agents to produce on-brand, consistent interface output — visual UI, terminal output, or outbound messages. -version: "2.16.0" +version: "2.16.1" documentation_url: https://deepworkplan.com user-invocable: true allowed-tools: Bash, Read, Grep, Glob, Edit, Write diff --git a/.agents/skills/deepworkplan/addons/devcontainer/SKILL.md b/.agents/skills/deepworkplan/addons/devcontainer/SKILL.md index 21e5052..0cc2299 100644 --- a/.agents/skills/deepworkplan/addons/devcontainer/SKILL.md +++ b/.agents/skills/deepworkplan/addons/devcontainer/SKILL.md @@ -1,7 +1,7 @@ --- name: deepworkplan-addon-devcontainer description: Optional DeepWorkPlan addon that adds (or reconciles) a compose-based devcontainer to a repo — base image and supporting services reasoned from the detected stack, with persistent AI-CLI auth, the dailybot-project-network, the DOCKER_DEV_ENV=vscode convention, and project-identity precedence. Opt-in, never required, reconciles existing setups instead of clobbering them. Use when the developer wants a reproducible isolated dev container for an AI-first repo. -version: "2.16.0" +version: "2.16.1" documentation_url: https://deepworkplan.com user-invocable: true allowed-tools: Bash, Read, Grep, Glob, Edit, Write diff --git a/.agents/skills/deepworkplan/author/SKILL.md b/.agents/skills/deepworkplan/author/SKILL.md index 089ec6f..52d2eb0 100644 --- a/.agents/skills/deepworkplan/author/SKILL.md +++ b/.agents/skills/deepworkplan/author/SKILL.md @@ -1,7 +1,7 @@ --- name: deepworkplan-author description: Author or update reusable skills, agents, and commands in the current repo — reason about the repo's .agents/ layout, follow the Open Agent Skills frontmatter contract, and keep the .agents/docs/ catalog in sync. Use when a developer wants to create or evolve the repo's agent kit (skills, agents, commands), or runs /skill-create or /agent-create. -version: "2.16.0" +version: "2.16.1" documentation_url: https://deepworkplan.com user-invocable: true allowed-tools: Bash, Read, Grep, Glob, Edit, Write diff --git a/.agents/skills/deepworkplan/create/SKILL.md b/.agents/skills/deepworkplan/create/SKILL.md index 7aa1945..3361ad5 100644 --- a/.agents/skills/deepworkplan/create/SKILL.md +++ b/.agents/skills/deepworkplan/create/SKILL.md @@ -1,7 +1,7 @@ --- name: deepworkplan-create description: Create a Deep Work Plan. Gather context, draft, and refine into a single final plan under .dwp/plans/, with a refined draft staged in .dwp/drafts/. Use when the developer wants a new structured multi-task plan. -version: "2.16.0" +version: "2.16.1" documentation_url: https://deepworkplan.com user-invocable: true allowed-tools: Bash, Read, Grep, Glob, Edit, Write diff --git a/.agents/skills/deepworkplan/execute/SKILL.md b/.agents/skills/deepworkplan/execute/SKILL.md index 607d660..27ff61a 100644 --- a/.agents/skills/deepworkplan/execute/SKILL.md +++ b/.agents/skills/deepworkplan/execute/SKILL.md @@ -1,7 +1,7 @@ --- name: deepworkplan-execute description: Execute an existing Deep Work Plan task-by-task, run each task's validation, and log progress. Use when the developer wants to run or continue executing a plan in .dwp/plans/. -version: "2.16.0" +version: "2.16.1" documentation_url: https://deepworkplan.com user-invocable: true allowed-tools: Bash, Read, Grep, Glob, Edit, Write diff --git a/.agents/skills/deepworkplan/onboard/SKILL.md b/.agents/skills/deepworkplan/onboard/SKILL.md index c44e5ee..4e38c34 100644 --- a/.agents/skills/deepworkplan/onboard/SKILL.md +++ b/.agents/skills/deepworkplan/onboard/SKILL.md @@ -1,7 +1,7 @@ --- name: deepworkplan-onboard description: Make a repository AI-first by reasoning about its stack and archetype, then generating adapted AGENTS.md, docs/, per-module docs, .agents/, and the .claude/.cursor to .agents symlinks. Offers opt-in addons. Use when the developer wants to onboard or AI-enable a repo. -version: "2.16.0" +version: "2.16.1" documentation_url: https://deepworkplan.com user-invocable: true allowed-tools: Bash, Read, Grep, Glob, Edit, Write @@ -518,14 +518,14 @@ auto-install it for everyone**. If accepted: read that addon's `SKILL.md` and ru its flow — detect whether the Dailybot skill/CLI is already present (reconcile-don't-clobber), offer the **opt-in** install paths (Dailybot agent skill via `npx skills add DailybotHQ/agent-skill` / `npx skills update dailybot` -/ OpenClaw / git clone + `setup.sh`, or the Dailybot CLI **>= 3.1.2**), **defer +/ OpenClaw / git clone + `setup.sh`, or the Dailybot CLI **>= 3.7.0**), **defer all authentication** to the Dailybot skill's own consent flow (`shared/auth.md` — `dailybot login` or `DAILYBOT_API_KEY`; never reinvent or store credentials), wire the **four lifecycle events** (kickoff, significant task, blocked, completion) as optional progress reports via the dailybot `report` sub-skill, and **MAY** offer deterministic hook enforcement (`dailybot hook`, CLI >= -3.1.2). The paired Dailybot skill (**3.4.0**) exposes 13 capabilities (chat, -check-ins, forms authoring, ask AI, and more); this addon wires only **report** +3.7.0). The paired Dailybot skill (**3.10.3**) exposes 14 capabilities (chat, +check-ins, forms authoring, ask AI, per-repo API keys, and more); this addon wires only **report** into DWP execution. Every report is strictly **best-effort and never blocks** the work if Dailybot is absent, unauthenticated, or unreachable. The core DeepWorkPlan methodology has **zero Dailybot dependency** — this addon is purely diff --git a/.agents/skills/deepworkplan/refine/SKILL.md b/.agents/skills/deepworkplan/refine/SKILL.md index 833f6ce..015fe6b 100644 --- a/.agents/skills/deepworkplan/refine/SKILL.md +++ b/.agents/skills/deepworkplan/refine/SKILL.md @@ -1,7 +1,7 @@ --- name: deepworkplan-refine description: Refine a Deep Work Plan draft or modify an existing final plan. Use when the developer wants to adjust scope, tasks, or details of a draft in .dwp/drafts/ or a plan in .dwp/plans/. -version: "2.16.0" +version: "2.16.1" documentation_url: https://deepworkplan.com user-invocable: true allowed-tools: Bash, Read, Grep, Glob, Edit, Write diff --git a/.agents/skills/deepworkplan/resume/SKILL.md b/.agents/skills/deepworkplan/resume/SKILL.md index 695dd2f..3da0055 100644 --- a/.agents/skills/deepworkplan/resume/SKILL.md +++ b/.agents/skills/deepworkplan/resume/SKILL.md @@ -1,7 +1,7 @@ --- name: deepworkplan-resume description: Resume an interrupted Deep Work Plan from its recorded progress state. Use when the developer wants to continue a plan in .dwp/plans/ that was paused or interrupted mid-execution. -version: "2.16.0" +version: "2.16.1" documentation_url: https://deepworkplan.com user-invocable: true allowed-tools: Bash, Read, Grep, Glob, Edit, Write diff --git a/.agents/skills/deepworkplan/spec/ADDONS.md b/.agents/skills/deepworkplan/spec/ADDONS.md index 36cf701..d934689 100644 --- a/.agents/skills/deepworkplan/spec/ADDONS.md +++ b/.agents/skills/deepworkplan/spec/ADDONS.md @@ -136,16 +136,16 @@ is fully conformant with **zero** addons installed. - Scope: an **opt-in** connection to the developer's **Dailybot team**. When accepted, it offers (never forces) install of the **Dailybot agent skill** - (`npx skills add DailybotHQ/agent-skill`, currently **3.4.0**; OpenClaw, or - git clone + `setup.sh`) and/or the **Dailybot CLI** (`dailybot-cli >= 3.1.2`, + (`npx skills add DailybotHQ/agent-skill`, currently **3.10.3**; OpenClaw, or + git clone + `setup.sh`) and/or the **Dailybot CLI** (`dailybot-cli >= 3.7.0`, via pip, Homebrew, the SHA-256-verified `cli.dailybot.com/install.sh`, or Windows PowerShell); **defers all authentication** to the Dailybot skill's own consent flow (`shared/auth.md` — `dailybot login` or `DAILYBOT_API_KEY`); wires **four lifecycle events** (kickoff, significant task, blocked, completion) as **optional, best-effort, never-blocking** progress reports via the dailybot `report` sub-skill; and **MAY** commit deterministic hook enforcement - (`dailybot hook` lifecycle hooks, CLI >= 3.1.2). The paired Dailybot skill - exposes 13 capabilities (chat, check-ins, forms authoring, ask AI, and more); + (`dailybot hook` lifecycle hooks, CLI >= 3.7.0). The paired Dailybot skill + exposes 14 capabilities (chat, check-ins, forms authoring, ask AI, per-repo API keys, and more); this addon wires only **report** into DWP execution. - **Vendor-neutral guardrail:** the core DeepWorkPlan methodology has **zero** Dailybot dependency. This addon **MUST NOT** be auto-installed for everyone — diff --git a/.agents/skills/deepworkplan/status/SKILL.md b/.agents/skills/deepworkplan/status/SKILL.md index 2e34554..9430ae0 100644 --- a/.agents/skills/deepworkplan/status/SKILL.md +++ b/.agents/skills/deepworkplan/status/SKILL.md @@ -1,7 +1,7 @@ --- name: deepworkplan-status description: Report the status of a Deep Work Plan — completed tasks, what's left, and blockers — without executing. Use when the developer asks for plan status or what remains. -version: "2.16.0" +version: "2.16.1" documentation_url: https://deepworkplan.com user-invocable: true allowed-tools: Bash, Read, Grep, Glob, Edit, Write diff --git a/.agents/skills/deepworkplan/verify/SKILL.md b/.agents/skills/deepworkplan/verify/SKILL.md index 8acde1f..f8d08e7 100644 --- a/.agents/skills/deepworkplan/verify/SKILL.md +++ b/.agents/skills/deepworkplan/verify/SKILL.md @@ -1,7 +1,7 @@ --- name: deepworkplan-verify description: Verify that a repository is DeepWorkPlan-conformant (AI-first) and that its plans are well-formed, producing an objective pass/fail report. Use when the developer asks to verify, audit, or check conformance of a repo or a plan. -version: "2.16.0" +version: "2.16.1" documentation_url: https://deepworkplan.com user-invocable: true allowed-tools: Bash, Read, Grep, Glob diff --git a/docker/local/dwpwebsite/Dockerfile b/docker/local/dwpwebsite/Dockerfile index 599951c..31965b7 100644 --- a/docker/local/dwpwebsite/Dockerfile +++ b/docker/local/dwpwebsite/Dockerfile @@ -100,7 +100,7 @@ RUN corepack pnpm add -g @openai/codex # avoiding the click 8.x conflict with the system-provided python3-click. # Binary lands in ~/.local/bin (already on PATH); auth/config lives in # ~/.config/dailybot, persisted across rebuilds via the dailybot_data volume. -RUN curl -fsSL https://cli.dailybot.com/install.sh | DAILYBOT_VERSION='>=3.2.1' bash +RUN curl -fsSL https://cli.dailybot.com/install.sh | DAILYBOT_VERSION='>=3.7.3' bash # Configure Git for node user (can be overridden by mounted .gitconfig) RUN git config --global init.defaultBranch main \ diff --git a/src/content/kit/de/dailybot.md b/src/content/kit/de/dailybot.md index 9189521..f4be502 100644 --- a/src/content/kit/de/dailybot.md +++ b/src/content/kit/de/dailybot.md @@ -1,6 +1,6 @@ --- title: Dailybot -description: "Optionales DWP-Addon: verbindet den Plan mit einem Dailybot-Team, optionale Hooks und die Agent-Skill 3.4.0 (Chat, Check-ins, Formulare, Ask AI und mehr)." +description: "Optionales DWP-Addon: verbindet den Plan mit einem Dailybot-Team, optionale Hooks und die Agent-Skill 3.10.3 (Chat, Check-ins, Formulare, Ask AI und mehr)." kind: addon lang: de order: 2 @@ -23,7 +23,7 @@ Die zentrale Deep Work Plan-Methodik hat **null** Dailybot-Abhängigkeit. Ein Re ## Was dieses Addon verbindet (bewusst eng gefasst) -Das DWP-Dailybot-Addon **erfindet** Dailybot nicht neu. Es verbindet die Planausführung mit der dailybot-**`report`**-Sub-Skill und committet optional Harness-Hooks. Alles andere — Installation, Einwilligung, Authentifizierung, Schreibstil — wird an die offizielle [Dailybot-Agent-Skill](https://github.com/DailybotHQ/agent-skill) (aktuell **3.4.0**) **delegiert**. +Das DWP-Dailybot-Addon **erfindet** Dailybot nicht neu. Es verbindet die Planausführung mit der dailybot-**`report`**-Sub-Skill und committet optional Harness-Hooks. Alles andere — Installation, Einwilligung, Authentifizierung, Schreibstil — wird an die offizielle [Dailybot-Agent-Skill](https://github.com/DailybotHQ/agent-skill) (aktuell **3.10.3**) **delegiert**. ### Vier Lifecycle-Ereignisse @@ -40,7 +40,7 @@ Payloads leiten sich von der State-Schicht des Plans (`state.json`) ab, wenn vor ### Optionale Hook-Durchsetzung -Mit `dailybot-cli >= 3.1.2` **kann** das Addon Repo-Level-Harness-Hooks committen (`dailybot hook session-start | activity | post-commit | stop | dismiss`), gestützt durch ein lokales Repo-Ledger. Der Harness erinnert den Agenten am Ende des Turns, wenn ein Lifecycle-Ereignis verpasst wurde — kritisch für lange unbeaufsichtigte Sessions, in denen Prompt-Anweisungen verblassen. +Mit `dailybot-cli >= 3.7.0` **kann** das Addon Repo-Level-Harness-Hooks committen (`dailybot hook session-start | activity | post-commit | stop | dismiss`), gestützt durch ein lokales Repo-Ledger. Der Harness erinnert den Agenten am Ende des Turns, wenn ein Lifecycle-Ereignis verpasst wurde — kritisch für lange unbeaufsichtigte Sessions, in denen Prompt-Anweisungen verblassen. Ein erfolgreicher Lifecycle-Report **setzt** das Hook-Ledger zurück, sodass die beiden Schichten nie doppelt berichten. Hook-Befehle lesen nur lokalen State und beenden immer mit `0`. @@ -73,7 +73,7 @@ Das Addon **bietet** Installationspfade; die Dailybot-Skill besitzt Einwilligung | **Bestehende Skill aktualisieren** | `npx skills update dailybot` | | **OpenClaw** | `openclaw skills install dailybot` | | **Git clone** | `git clone https://github.com/DailybotHQ/agent-skill.git` + `./setup.sh` | -| **Dailybot CLI** (Minimum `>= 3.1.2`) | Von der Skill bei erster Nutzung via verifiziertem `shared/auth.md` installiert; oder `pip install 'dailybot-cli>=3.1.2'`, Homebrew oder Installer mit Prüfsumme unter [cli.dailybot.com](https://cli.dailybot.com) | +| **Dailybot CLI** (Minimum `>= 3.7.0`) | Von der Skill bei erster Nutzung via verifiziertem `shared/auth.md` installiert; oder `pip install 'dailybot-cli>=3.7.0'`, Homebrew oder Installer mit Prüfsumme unter [cli.dailybot.com](https://cli.dailybot.com) | Versionen prüfen: `dailybot --version` und `dailybot version --check`. Upgrade: `dailybot upgrade`. @@ -82,13 +82,14 @@ Versionen prüfen: `dailybot --version` und `dailybot version --check`. Upgrade: Dieses Addon **fordert niemals** E-Mail, OTP oder API-Keys an und **speichert niemals** Credentials. Authentifizierung gehört zur Dailybot-Skill [`shared/auth.md`](https://github.com/DailybotHQ/agent-skill/blob/main/skills/dailybot/shared/auth.md): - `dailybot login` (E-Mail-OTP), oder -- `DAILYBOT_API_KEY` / `dailybot config key=...` +- `DAILYBOT_API_KEY` / `dailybot config key=...`, oder +- eine optionale, gitignorierte `.dailybot/env.json`-Datei mit Per-Repo-Keys (`dailybot env add/use`, CLI `>= 3.7.0`), damit ein Entwickler in verschiedenen Repos bei verschiedenen Organisationen angemeldet sein kann. -Wird Auth abgelehnt oder ist nicht verfügbar, wird Reporting still übersprungen — die Arbeit geht weiter. +Die Auth-Auflösung ist **Bearer-first**: ein Session-Token hat Vorrang, mit einem transparenten Bearer→API-Key-Retry bei `401`/`403`, sodass ein veraltetes Token niemals einen gültigen Key blockiert. Wird Auth abgelehnt oder ist nicht verfügbar, wird Reporting still übersprungen — die Arbeit geht weiter. -## Die gepaarte Dailybot-Skill — 13 Fähigkeiten (3.4.0) +## Die gepaarte Dailybot-Skill — 14 Fähigkeiten (3.10.3) -Die Installation der Dailybot-Agent-Skill bringt weit mehr als das DWP-Addon verbindet. Das offizielle Skill-Paket (Skill **3.4.0**, CLI **>= 3.1.2**, aktuelle Veröffentlichung **3.2.1**) exponiert **13 koordinierte Sub-Skills**: +Die Installation der Dailybot-Agent-Skill bringt weit mehr als das DWP-Addon verbindet. Das offizielle Skill-Paket (Skill **3.10.3**, CLI-Baseline **>= 3.7.0**, aktuelle Veröffentlichung **3.7.3**) exponiert **14 koordinierte Sub-Skills**: | Sub-Skill | Was sie tut | |-----------|--------------| @@ -102,9 +103,10 @@ Die Installation der Dailybot-Agent-Skill bringt weit mehr als das DWP-Addon ver | **Check-ins** | Standups abschließen; Check-ins **autorisieren** (Zeitplan, Teilnehmer, Fragen, Erinnerungen, KI-Einstellungen) | | **Kudos** | Teamkollegen oder ganze Teams anerkennen; Anerkennungs-Feed, Org-Feed, Wall of Fame durchsuchen | | **Teams** | Teams listen, Mitglieder inspizieren, Namen zu UUIDs auflösen; `me`, `org`, Benutzerprofile | -| **Formulare** | Formulare listen, einreichen, aktualisieren, transitionieren; Formulare **autorisieren** (Workflow-States, Berechtigungen, ChatOps) | +| **Formulare** | Formulare listen (jetzt standardmäßig **org-weit**, mit `--mine` und `--owner` zum Eingrenzen), einreichen, aktualisieren, transitionieren; Formulare **autorisieren** (Workflow-States, Berechtigungen, ChatOps); Pagination, Suche und Datumsfilter | | **Workflows** | Org-Workflows lesen (`workflow list` / `workflow get`; nur lesen) | | **Report-Kanäle** | Kanal-UUIDs für Formulare oder Check-ins entdecken | +| **Per-Repo-API-Keys** | `.dailybot/env.json` verwalten — eine optionale, gitignorierte Datei mit API-Keys + URLs pro Umgebung (`dailybot env add / use / show / list / remove / off / on`, CLI `>= 3.7.0`) | **Das DWP-Addon verbindet nur `report` mit der Planausführung.** Rufen Sie die Dailybot-Skill direkt für alles andere auf — z. B. Deploy-Zusammenfassung in `#releases` posten, Standup abschließen oder die Dailybot-KI bitten, Check-in-Trends zusammenzufassen. diff --git a/src/content/kit/en/dailybot.md b/src/content/kit/en/dailybot.md index 668babb..c382360 100644 --- a/src/content/kit/en/dailybot.md +++ b/src/content/kit/en/dailybot.md @@ -1,6 +1,6 @@ --- title: Dailybot -description: "Opt-in DWP addon: connect plan lifecycle to a Dailybot team, optional hook enforcement, and the full Dailybot agent skill 3.4.0 (chat, check-ins, forms, ask AI, and more)." +description: "Opt-in DWP addon: connect plan lifecycle to a Dailybot team, optional hook enforcement, and the full Dailybot agent skill 3.10.3 (chat, check-ins, forms, ask AI, and more)." kind: addon lang: en order: 2 @@ -23,7 +23,7 @@ The core Deep Work Plan methodology has **zero** Dailybot dependency. A reposito ## What this addon wires (narrow by design) -The DWP Dailybot addon does **not** reinvent Dailybot. It connects plan execution to the dailybot **`report`** sub-skill and optionally commits harness hooks. Everything else — install, consent, authentication, writing style — is **deferred** to the official [Dailybot agent skill](https://github.com/DailybotHQ/agent-skill) (currently **3.4.0**). +The DWP Dailybot addon does **not** reinvent Dailybot. It connects plan execution to the dailybot **`report`** sub-skill and optionally commits harness hooks. Everything else — install, consent, authentication, writing style — is **deferred** to the official [Dailybot agent skill](https://github.com/DailybotHQ/agent-skill) (currently **3.10.3**). ### Four lifecycle events @@ -40,7 +40,7 @@ Payloads derive from the plan's state layer (`state.json`) when present: `comple ### Optional hook enforcement -With `dailybot-cli >= 3.1.2`, the addon **may** commit repo-level harness hooks (`dailybot hook session-start | activity | post-commit | stop | dismiss`) backed by a local per-repo ledger. The harness reminds the agent at end of turn when a lifecycle event was missed — critical for long unattended sessions where prompt instructions decay. +With `dailybot-cli >= 3.7.0`, the addon **may** commit repo-level harness hooks (`dailybot hook session-start | activity | post-commit | stop | dismiss`) backed by a local per-repo ledger. The harness reminds the agent at end of turn when a lifecycle event was missed — critical for long unattended sessions where prompt instructions decay. A successful lifecycle report **resets** the hook ledger, so the two layers never double-report. Hook commands read local state only and always exit `0`. @@ -73,7 +73,7 @@ The addon **offers** install paths; the Dailybot skill owns consent and verifica | **Update existing skill** | `npx skills update dailybot` | | **OpenClaw** | `openclaw skills install dailybot` | | **Git clone** | `git clone https://github.com/DailybotHQ/agent-skill.git` + `./setup.sh` | -| **Dailybot CLI** (minimum `>= 3.1.2`) | Installed by the skill on first use via verified `shared/auth.md`; or `pip install 'dailybot-cli>=3.1.2'`, Homebrew, or the checksum-verified installer at [cli.dailybot.com](https://cli.dailybot.com) | +| **Dailybot CLI** (minimum `>= 3.7.0`) | Installed by the skill on first use via verified `shared/auth.md`; or `pip install 'dailybot-cli>=3.7.0'`, Homebrew, or the checksum-verified installer at [cli.dailybot.com](https://cli.dailybot.com) | Check versions: `dailybot --version` and `dailybot version --check`. Upgrade: `dailybot upgrade`. @@ -82,13 +82,14 @@ Check versions: `dailybot --version` and `dailybot version --check`. Upgrade: `d This addon **never** prompts for email, OTP, or API keys, and **never** stores credentials. Authentication is owned by the Dailybot skill's [`shared/auth.md`](https://github.com/DailybotHQ/agent-skill/blob/main/skills/dailybot/shared/auth.md): - `dailybot login` (email OTP), or -- `DAILYBOT_API_KEY` / `dailybot config key=...` +- `DAILYBOT_API_KEY` / `dailybot config key=...`, or +- an opt-in, gitignored `.dailybot/env.json` per-repo key file (`dailybot env add/use`, CLI `>= 3.7.0`) so a developer can be signed into different orgs in different repos. -If auth is declined or unavailable, reporting is skipped silently — work continues. +Auth resolution is **Bearer-first**: a session token takes priority, with a transparent Bearer→API-key retry on `401`/`403` so a stale token never blocks a valid key. If auth is declined or unavailable, reporting is skipped silently — work continues. -## The paired Dailybot skill — 13 capabilities (3.4.0) +## The paired Dailybot skill — 14 capabilities (3.10.3) -Installing the Dailybot agent skill brings far more than the DWP addon wires. The official skill pack (skill **3.4.0**, CLI **>= 3.1.2**, current publish **3.2.1**) exposes **13 coordinated sub-skills**: +Installing the Dailybot agent skill brings far more than the DWP addon wires. The official skill pack (skill **3.10.3**, CLI baseline **>= 3.7.0**, current publish **3.7.3**) exposes **14 coordinated sub-skills**: | Sub-skill | What it does | |-----------|--------------| @@ -102,9 +103,10 @@ Installing the Dailybot agent skill brings far more than the DWP addon wires. Th | **Check-ins** | Complete standups; **author** check-ins (schedule, participants, questions, reminders, AI settings) | | **Kudos** | Recognize teammates or whole teams; browse recognition feed, org feed, wall of fame | | **Teams** | List teams, inspect members, resolve names to UUIDs; `me`, `org`, user profiles | -| **Forms** | List, submit, update, transition forms; **author** forms (workflow states, permissions, ChatOps) | +| **Forms** | List (now **org-scoped** by default, with `--mine` and `--owner` to narrow), submit, update, transition forms; **author** forms (workflow states, permissions, ChatOps); pagination, search, and date filters | | **Workflows** | Read org workflows (`workflow list` / `workflow get`; read-only) | | **Report channels** | Discover channel UUIDs for forms or check-ins | +| **Per-repo API keys** | Manage `.dailybot/env.json` — an opt-in, gitignored file of API keys + URLs per environment (`dailybot env add / use / show / list / remove / off / on`, CLI `>= 3.7.0`) | **The DWP addon wires only `report` into plan execution.** Invoke the Dailybot skill directly for everything else — for example, post a deploy summary to `#releases`, complete a standup, or ask the Dailybot AI to summarize check-in trends. diff --git a/src/content/kit/es/dailybot.md b/src/content/kit/es/dailybot.md index de8072b..8e31c85 100644 --- a/src/content/kit/es/dailybot.md +++ b/src/content/kit/es/dailybot.md @@ -1,6 +1,6 @@ --- title: Dailybot -description: "Addon DWP opcional: conecta el plan con un equipo Dailybot, hooks opcionales y la skill de agente 3.4.0 (chat, check-ins, formularios, ask AI y más)." +description: "Addon DWP opcional: conecta el plan con un equipo Dailybot, hooks opcionales y la skill de agente 3.10.3 (chat, check-ins, formularios, ask AI y más)." kind: addon lang: es order: 2 @@ -23,7 +23,7 @@ La metodología central de Deep Work Plan tiene **cero** dependencia de Dailybot ## Qué conecta este addon (deliberadamente acotado) -El addon Dailybot de DWP **no** reinventa Dailybot. Conecta la ejecución del plan con la sub-skill **`report`** de dailybot y, opcionalmente, confirma hooks del harness. Todo lo demás — instalación, consentimiento, autenticación, estilo de redacción — se **delega** a la [skill de agente Dailybot](https://github.com/DailybotHQ/agent-skill) oficial (actualmente **3.4.0**). +El addon Dailybot de DWP **no** reinventa Dailybot. Conecta la ejecución del plan con la sub-skill **`report`** de dailybot y, opcionalmente, confirma hooks del harness. Todo lo demás — instalación, consentimiento, autenticación, estilo de redacción — se **delega** a la [skill de agente Dailybot](https://github.com/DailybotHQ/agent-skill) oficial (actualmente **3.10.3**). ### Cuatro eventos del ciclo de vida @@ -40,7 +40,7 @@ Las cargas útiles se derivan de la capa de estado del plan (`state.json`) cuand ### Refuerzo opcional mediante hooks -Con `dailybot-cli >= 3.1.2`, el addon **puede** confirmar hooks del harness a nivel de repo (`dailybot hook session-start | activity | post-commit | stop | dismiss`) respaldados por un registro local por repo. El harness recuerda al agente al final del turno cuando se omitió un evento del ciclo de vida — crítico para sesiones largas sin supervisión donde las instrucciones del prompt se diluyen. +Con `dailybot-cli >= 3.7.0`, el addon **puede** confirmar hooks del harness a nivel de repo (`dailybot hook session-start | activity | post-commit | stop | dismiss`) respaldados por un registro local por repo. El harness recuerda al agente al final del turno cuando se omitió un evento del ciclo de vida — crítico para sesiones largas sin supervisión donde las instrucciones del prompt se diluyen. Un reporte de ciclo de vida exitoso **reinicia** el registro de hooks, de modo que las dos capas nunca reportan en doble. Los comandos de hooks solo leen estado local y siempre terminan con `0`. @@ -73,7 +73,7 @@ El addon **ofrece** rutas de instalación; la skill de Dailybot es dueña del co | **Actualizar skill existente** | `npx skills update dailybot` | | **OpenClaw** | `openclaw skills install dailybot` | | **Git clone** | `git clone https://github.com/DailybotHQ/agent-skill.git` + `./setup.sh` | -| **Dailybot CLI** (mínimo `>= 3.1.2`) | Instalada por la skill en el primer uso vía `shared/auth.md` verificado; o `pip install 'dailybot-cli>=3.1.2'`, Homebrew, o el instalador con checksum verificado en [cli.dailybot.com](https://cli.dailybot.com) | +| **Dailybot CLI** (mínimo `>= 3.7.0`) | Instalada por la skill en el primer uso vía `shared/auth.md` verificado; o `pip install 'dailybot-cli>=3.7.0'`, Homebrew, o el instalador con checksum verificado en [cli.dailybot.com](https://cli.dailybot.com) | Comprueba versiones: `dailybot --version` y `dailybot version --check`. Actualiza: `dailybot upgrade`. @@ -82,13 +82,14 @@ Comprueba versiones: `dailybot --version` y `dailybot version --check`. Actualiz Este addon **nunca** pide correo, OTP ni claves API, y **nunca** almacena credenciales. La autenticación la gestiona [`shared/auth.md`](https://github.com/DailybotHQ/agent-skill/blob/main/skills/dailybot/shared/auth.md) de la skill de Dailybot: - `dailybot login` (OTP por correo), o -- `DAILYBOT_API_KEY` / `dailybot config key=...` +- `DAILYBOT_API_KEY` / `dailybot config key=...`, o +- un archivo de claves por repo `.dailybot/env.json`, opcional e ignorado por git (`dailybot env add/use`, CLI `>= 3.7.0`), para que un desarrollador pueda estar autenticado en distintas organizaciones en distintos repos. -Si se rechaza la autenticación o no está disponible, el reporte se omite en silencio — el trabajo continúa. +La resolución de autenticación es **Bearer primero**: un token de sesión tiene prioridad, con un reintento transparente de Bearer→clave API ante `401`/`403`, de modo que un token caducado nunca bloquea una clave válida. Si se rechaza la autenticación o no está disponible, el reporte se omite en silencio — el trabajo continúa. -## La skill emparejada de Dailybot — 13 capacidades (3.4.0) +## La skill emparejada de Dailybot — 14 capacidades (3.10.3) -Instalar la skill de agente Dailybot aporta mucho más de lo que conecta el addon de DWP. El paquete oficial de skills (skill **3.4.0**, CLI **>= 3.1.2**, publicación actual **3.2.1**) expone **13 sub-skills coordinadas**: +Instalar la skill de agente Dailybot aporta mucho más de lo que conecta el addon de DWP. El paquete oficial de skills (skill **3.10.3**, CLI base **>= 3.7.0**, publicación actual **3.7.3**) expone **14 sub-skills coordinadas**: | Sub-skill | Qué hace | |-----------|--------------| @@ -102,9 +103,10 @@ Instalar la skill de agente Dailybot aporta mucho más de lo que conecta el addo | **Check-ins** | Completar standups; **autorar** check-ins (programación, participantes, preguntas, recordatorios, ajustes de IA) | | **Kudos** | Reconocer compañeros o equipos enteros; explorar feed de reconocimiento, feed de la org, muro de la fama | | **Equipos** | Listar equipos, inspeccionar miembros, resolver nombres a UUIDs; `me`, `org`, perfiles de usuario | -| **Formularios** | Listar, enviar, actualizar, transicionar formularios; **autorar** formularios (estados de workflow, permisos, ChatOps) | +| **Formularios** | Listar (ahora **con alcance de org** por defecto, con `--mine` y `--owner` para acotar), enviar, actualizar, transicionar formularios; **autorar** formularios (estados de workflow, permisos, ChatOps); paginación, búsqueda y filtros por fecha | | **Workflows** | Leer workflows de la org (`workflow list` / `workflow get`; solo lectura) | | **Canales de reporte** | Descubrir UUIDs de canal para formularios o check-ins | +| **Claves API por repo** | Gestionar `.dailybot/env.json` — un archivo opcional e ignorado por git con claves API + URLs por entorno (`dailybot env add / use / show / list / remove / off / on`, CLI `>= 3.7.0`) | **El addon de DWP solo conecta `report` a la ejecución del plan.** Invoca la skill de Dailybot directamente para todo lo demás — por ejemplo, publicar un resumen de despliegue en `#releases`, completar un standup o pedir a la IA de Dailybot que resuma tendencias de check-ins. diff --git a/src/content/kit/fr/dailybot.md b/src/content/kit/fr/dailybot.md index 08705d8..98384d2 100644 --- a/src/content/kit/fr/dailybot.md +++ b/src/content/kit/fr/dailybot.md @@ -1,6 +1,6 @@ --- title: Dailybot -description: "Addon DWP optionnel : connecte le plan à une équipe Dailybot, hooks optionnels et la skill agent 3.4.0 (chat, check-ins, formulaires, ask AI et plus)." +description: "Addon DWP optionnel : connecte le plan à une équipe Dailybot, hooks optionnels et la skill agent 3.10.3 (chat, check-ins, formulaires, ask AI et plus)." kind: addon lang: fr order: 2 @@ -23,7 +23,7 @@ La méthodologie centrale de Deep Work Plan a **zéro** dépendance à Dailybot. ## Ce que cet addon connecte (volontairement restreint) -L'addon Dailybot de DWP **ne** réinvente pas Dailybot. Il connecte l'exécution du plan à la sous-skill **`report`** de dailybot et committe éventuellement des hooks du harness. Tout le reste — installation, consentement, authentification, style d'écriture — est **reporté** à la [skill agent Dailybot](https://github.com/DailybotHQ/agent-skill) officielle (actuellement **3.4.0**). +L'addon Dailybot de DWP **ne** réinvente pas Dailybot. Il connecte l'exécution du plan à la sous-skill **`report`** de dailybot et committe éventuellement des hooks du harness. Tout le reste — installation, consentement, authentification, style d'écriture — est **reporté** à la [skill agent Dailybot](https://github.com/DailybotHQ/agent-skill) officielle (actuellement **3.10.3**). ### Quatre événements du cycle de vie @@ -40,7 +40,7 @@ Les charges utiles dérivent de la couche d'état du plan (`state.json`) lorsqu' ### Application optionnelle par hooks -Avec `dailybot-cli >= 3.1.2`, l'addon **peut** committer des hooks de harness au niveau du dépôt (`dailybot hook session-start | activity | post-commit | stop | dismiss`) soutenus par un registre local par dépôt. Le harness rappelle à l'agent en fin de tour lorsqu'un événement du cycle de vie a été manqué — critique pour les longues sessions sans surveillance où les instructions du prompt s'affaiblissent. +Avec `dailybot-cli >= 3.7.0`, l'addon **peut** committer des hooks de harness au niveau du dépôt (`dailybot hook session-start | activity | post-commit | stop | dismiss`) soutenus par un registre local par dépôt. Le harness rappelle à l'agent en fin de tour lorsqu'un événement du cycle de vie a été manqué — critique pour les longues sessions sans surveillance où les instructions du prompt s'affaiblissent. Un rapport de cycle de vie réussi **réinitialise** le registre des hooks, de sorte que les deux couches ne rapportent jamais en double. Les commandes de hooks ne lisent que l'état local et se terminent toujours avec `0`. @@ -73,7 +73,7 @@ L'addon **propose** des chemins d'installation ; la skill Dailybot possède le c | **Mettre à jour la skill existante** | `npx skills update dailybot` | | **OpenClaw** | `openclaw skills install dailybot` | | **Git clone** | `git clone https://github.com/DailybotHQ/agent-skill.git` + `./setup.sh` | -| **Dailybot CLI** (minimum `>= 3.1.2`) | Installée par la skill à la première utilisation via `shared/auth.md` vérifié ; ou `pip install 'dailybot-cli>=3.1.2'`, Homebrew, ou l'installateur avec somme de contrôle sur [cli.dailybot.com](https://cli.dailybot.com) | +| **Dailybot CLI** (minimum `>= 3.7.0`) | Installée par la skill à la première utilisation via `shared/auth.md` vérifié ; ou `pip install 'dailybot-cli>=3.7.0'`, Homebrew, ou l'installateur avec somme de contrôle sur [cli.dailybot.com](https://cli.dailybot.com) | Vérifiez les versions : `dailybot --version` et `dailybot version --check`. Mise à niveau : `dailybot upgrade`. @@ -82,13 +82,14 @@ Vérifiez les versions : `dailybot --version` et `dailybot version --check`. Mis Cet addon **ne demande jamais** d'e-mail, d'OTP ni de clés API, et **ne stocke jamais** de credentials. L'authentification appartient à [`shared/auth.md`](https://github.com/DailybotHQ/agent-skill/blob/main/skills/dailybot/shared/auth.md) de la skill Dailybot : - `dailybot login` (OTP par e-mail), ou -- `DAILYBOT_API_KEY` / `dailybot config key=...` +- `DAILYBOT_API_KEY` / `dailybot config key=...`, ou +- un fichier de clés par dépôt `.dailybot/env.json`, optionnel et gitignoré (`dailybot env add/use`, CLI `>= 3.7.0`), pour qu'un développeur puisse être connecté à différentes orgs dans différents dépôts. -Si l'auth est refusée ou indisponible, le reporting est ignoré silencieusement — le travail continue. +La résolution de l'auth est **Bearer d'abord** : un jeton de session est prioritaire, avec une nouvelle tentative transparente Bearer→clé API sur `401`/`403` pour qu'un jeton périmé ne bloque jamais une clé valide. Si l'auth est refusée ou indisponible, le reporting est ignoré silencieusement — le travail continue. -## La skill jumelée Dailybot — 13 capacités (3.4.0) +## La skill jumelée Dailybot — 14 capacités (3.10.3) -Installer la skill agent Dailybot apporte bien plus que ce que l'addon DWP connecte. Le pack officiel de skills (skill **3.4.0**, CLI **>= 3.1.2**, publication actuelle **3.2.1**) expose **13 sous-skills coordonnées** : +Installer la skill agent Dailybot apporte bien plus que ce que l'addon DWP connecte. Le pack officiel de skills (skill **3.10.3**, CLI de référence **>= 3.7.0**, publication actuelle **3.7.3**) expose **14 sous-skills coordonnées** : | Sous-skill | Ce qu'elle fait | |-----------|--------------| @@ -102,9 +103,10 @@ Installer la skill agent Dailybot apporte bien plus que ce que l'addon DWP conne | **Check-ins** | Compléter les standups ; **autoriser** les check-ins (planification, participants, questions, rappels, paramètres IA) | | **Kudos** | Reconnaître des coéquipiers ou des équipes entières ; parcourir le fil de reconnaissance, fil org, mur de la renommée | | **Équipes** | Lister les équipes, inspecter les membres, résoudre les noms en UUIDs ; `me`, `org`, profils utilisateur | -| **Formulaires** | Lister, soumettre, mettre à jour, faire transitionner les formulaires ; **autoriser** les formulaires (états de workflow, permissions, ChatOps) | +| **Formulaires** | Lister (désormais **à portée org** par défaut, avec `--mine` et `--owner` pour restreindre), soumettre, mettre à jour, faire transitionner les formulaires ; **autoriser** les formulaires (états de workflow, permissions, ChatOps) ; pagination, recherche et filtres de date | | **Workflows** | Lire les workflows org (`workflow list` / `workflow get` ; lecture seule) | | **Canaux de rapport** | Découvrir les UUIDs de canal pour formulaires ou check-ins | +| **Clés API par dépôt** | Gérer `.dailybot/env.json` — un fichier optionnel et gitignoré de clés API + URLs par environnement (`dailybot env add / use / show / list / remove / off / on`, CLI `>= 3.7.0`) | **L'addon DWP ne connecte que `report` à l'exécution du plan.** Invoquez la skill Dailybot directement pour tout le reste — par exemple publier un résumé de déploiement dans `#releases`, compléter un standup ou demander à l'IA Dailybot de résumer les tendances de check-ins. diff --git a/src/content/kit/hi/dailybot.md b/src/content/kit/hi/dailybot.md index 009f4eb..8520190 100644 --- a/src/content/kit/hi/dailybot.md +++ b/src/content/kit/hi/dailybot.md @@ -1,6 +1,6 @@ --- title: Dailybot -description: "ऑप्ट-इन DWP ऐडऑन: योजना जीवनचक्र को Dailybot टीम से जोड़ें, वैकल्पिक हुक प्रवर्तन, और पूर्ण Dailybot एजेंट स्किल 3.4.0 (चैट, चेक-इन, फ़ॉर्म, Ask AI, और अधिक)।" +description: "ऑप्ट-इन DWP ऐडऑन: योजना जीवनचक्र को Dailybot टीम से जोड़ें, वैकल्पिक हुक प्रवर्तन, और पूर्ण Dailybot एजेंट स्किल 3.10.3 (चैट, चेक-इन, फ़ॉर्म, Ask AI, और अधिक)।" kind: addon lang: hi order: 2 @@ -23,7 +23,7 @@ Deep Work Plan निष्पादन को एक **Dailybot टीम** स ## यह ऐडऑन क्या जोड़ता है (जानबूझकर संकीर्ण) -DWP Dailybot ऐडऑन Dailybot को **दोबारा नहीं बनाता**। यह योजना निष्पादन को dailybot **`report`** sub-skill से जोड़ता है और वैकल्पिक रूप से harness हुक कमिट करता है। बाकी सब — इंस्टॉल, सहमति, authentication, लेखन शैली — आधिकारिक [Dailybot agent skill](https://github.com/DailybotHQ/agent-skill) (वर्तमान में **3.4.0**) को **सौंपा** जाता है। +DWP Dailybot ऐडऑन Dailybot को **दोबारा नहीं बनाता**। यह योजना निष्पादन को dailybot **`report`** sub-skill से जोड़ता है और वैकल्पिक रूप से harness हुक कमिट करता है। बाकी सब — इंस्टॉल, सहमति, authentication, लेखन शैली — आधिकारिक [Dailybot agent skill](https://github.com/DailybotHQ/agent-skill) (वर्तमान में **3.10.3**) को **सौंपा** जाता है। ### चार जीवनचक्र घटनाएँ @@ -40,7 +40,7 @@ Payload योजना की state परत (`state.json`) से निक ### वैकल्पिक हुक प्रवर्तन -`dailybot-cli >= 3.1.2` के साथ, ऐडऑन **रिपॉज़िटरी-स्तर harness हुक** (`dailybot hook session-start | activity | post-commit | stop | dismiss`) कमिट **कर सकता** है, जो स्थानीय per-repo बहीखाते द्वारा समर्थित हैं। Harness टर्न के अंत में याद दिलाता है जब कोई जीवनचक्र घटना छूट गई — लंबे unattended सत्रों के लिए महत्वपूर्ण जहाँ प्रॉम्प्ट निर्देश कमज़ोर पड़ जाते हैं। +`dailybot-cli >= 3.7.0` के साथ, ऐडऑन **रिपॉज़िटरी-स्तर harness हुक** (`dailybot hook session-start | activity | post-commit | stop | dismiss`) कमिट **कर सकता** है, जो स्थानीय per-repo बहीखाते द्वारा समर्थित हैं। Harness टर्न के अंत में याद दिलाता है जब कोई जीवनचक्र घटना छूट गई — लंबे unattended सत्रों के लिए महत्वपूर्ण जहाँ प्रॉम्प्ट निर्देश कमज़ोर पड़ जाते हैं। सफल जीवनचक्र रिपोर्ट हुक बहीखाते को **रीसेट** करती है, इसलिए दो परतें कभी दोहरी रिपोर्ट नहीं करतीं। हुक कमांड केवल स्थानीय स्थिति पढ़ते हैं और हमेशा `0` से समाप्त होते हैं। @@ -73,7 +73,7 @@ Payload योजना की state परत (`state.json`) से निक | **मौजूदा स्किल अपडेट** | `npx skills update dailybot` | | **OpenClaw** | `openclaw skills install dailybot` | | **Git clone** | `git clone https://github.com/DailybotHQ/agent-skill.git` + `./setup.sh` | -| **Dailybot CLI** (न्यूनतम `>= 3.1.2`) | स्किल द्वारा पहले उपयोग पर `shared/auth.md` के माध्यम से; या `pip install 'dailybot-cli>=3.1.2'`, Homebrew, या [cli.dailybot.com](https://cli.dailybot.com) पर checksum-verified installer | +| **Dailybot CLI** (न्यूनतम `>= 3.7.0`) | स्किल द्वारा पहले उपयोग पर `shared/auth.md` के माध्यम से; या `pip install 'dailybot-cli>=3.7.0'`, Homebrew, या [cli.dailybot.com](https://cli.dailybot.com) पर checksum-verified installer | संस्करण जाँचें: `dailybot --version` और `dailybot version --check`। अपग्रेड: `dailybot upgrade`। @@ -82,13 +82,14 @@ Payload योजना की state परत (`state.json`) से निक यह ऐडऑन **कभी** email, OTP, या API keys नहीं माँगता, और **कभी** credentials संग्रहीत नहीं करता। Authentication Dailybot स्किल के [`shared/auth.md`](https://github.com/DailybotHQ/agent-skill/blob/main/skills/dailybot/shared/auth.md) का स्वामी है: - `dailybot login` (email OTP), या -- `DAILYBOT_API_KEY` / `dailybot config key=...` +- `DAILYBOT_API_KEY` / `dailybot config key=...`, या +- एक ऑप्ट-इन, gitignored `.dailybot/env.json` per-repo key फ़ाइल (`dailybot env add/use`, CLI `>= 3.7.0`) ताकि एक डेवलपर अलग-अलग रिपॉज़िटरी में अलग-अलग orgs में साइन-इन रह सके। -यदि auth अस्वीकृत या अनुपलब्ध हो, रिपोर्टिंग चुपचाप छोड़ दी जाती है — कार्य जारी रहता है। +Auth resolution **Bearer-first** है: session token को प्राथमिकता मिलती है, `401`/`403` पर पारदर्शी Bearer→API-key retry के साथ, ताकि कोई बासी token किसी वैध key को कभी अवरुद्ध न करे। यदि auth अस्वीकृत या अनुपलब्ध हो, रिपोर्टिंग चुपचाप छोड़ दी जाती है — कार्य जारी रहता है। -## जोड़ी गई Dailybot स्किल — 13 क्षमताएँ (3.4.0) +## जोड़ी गई Dailybot स्किल — 14 क्षमताएँ (3.10.3) -Dailybot agent skill इंस्टॉल करने से DWP ऐडऑन से कहीं अधिक मिलता है। आधिकारिक स्किल पैक (स्किल **3.4.0**, CLI **>= 3.1.2**, वर्तमान publish **3.2.1**) **13 समन्वित sub-skills** प्रदान करता है: +Dailybot agent skill इंस्टॉल करने से DWP ऐडऑन से कहीं अधिक मिलता है। आधिकारिक स्किल पैक (स्किल **3.10.3**, CLI बेसलाइन **>= 3.7.0**, वर्तमान publish **3.7.3**) **14 समन्वित sub-skills** प्रदान करता है: | Sub-skill | क्या करता है | |-----------|--------------| @@ -102,9 +103,10 @@ Dailybot agent skill इंस्टॉल करने से DWP ऐडऑन | **Check-ins** | standup पूरे करें; चेक-इन **लेखन** (शेड्यूल, प्रतिभागी, प्रश्न, reminders, AI सेटिंग) | | **Kudos** | साथियों या पूरे टीमों को पहचानें; recognition feed, org feed, wall of fame ब्राउज़ करें | | **Teams** | टीमें सूचीबद्ध करें, सदस्यों का निरीक्षण करें, नामों को UUID में resolve करें; `me`, `org`, user profiles | -| **Forms** | फ़ॉर्म सूचीबद्ध, submit, update, transition करें; फ़ॉर्म **लेखन** (workflow states, permissions, ChatOps) | +| **Forms** | फ़ॉर्म सूचीबद्ध करें (अब डिफ़ॉल्ट रूप से **org-scoped**, संकीर्ण करने के लिए `--mine` और `--owner` के साथ), submit, update, transition करें; फ़ॉर्म **लेखन** (workflow states, permissions, ChatOps); pagination, search, और date filters | | **Workflows** | org workflows पढ़ें (`workflow list` / `workflow get`; read-only) | | **Report channels** | फ़ॉर्म या चेक-इन के लिए channel UUID खोजें | +| **Per-repo API keys** | `.dailybot/env.json` प्रबंधित करें — प्रति environment API keys + URLs की एक ऑप्ट-इन, gitignored फ़ाइल (`dailybot env add / use / show / list / remove / off / on`, CLI `>= 3.7.0`) | **DWP ऐडऑन केवल `report` को योजना निष्पादन में जोड़ता है।** बाकी सब के लिए Dailybot स्किल सीधे invoke करें — उदाहरण: `#releases` पर deploy सारांश पोस्ट करें, standup पूरा करें, या Dailybot AI से चेक-इन ट्रेंड सारांश माँगें। diff --git a/src/content/kit/id/dailybot.md b/src/content/kit/id/dailybot.md index 33f605f..72d7542 100644 --- a/src/content/kit/id/dailybot.md +++ b/src/content/kit/id/dailybot.md @@ -1,6 +1,6 @@ --- title: Dailybot -description: "Addon DWP opt-in: menghubungkan siklus hidup rencana ke tim Dailybot, penegakan hook opsional, dan skill agen Dailybot lengkap 3.4.0 (chat, check-in, formulir, ask AI, dan lainnya)." +description: "Addon DWP opt-in: menghubungkan siklus hidup rencana ke tim Dailybot, penegakan hook opsional, dan skill agen Dailybot lengkap 3.10.3 (chat, check-in, formulir, ask AI, dan lainnya)." kind: addon lang: id order: 2 @@ -23,7 +23,7 @@ Metodologi Deep Work Plan inti memiliki **nol** ketergantungan pada Dailybot. Re ## Yang dihubungkan addon ini (sengaja sempit) -Addon DWP Dailybot **tidak** menciptakan ulang Dailybot. Addon ini menghubungkan eksekusi rencana ke sub-skill dailybot **`report`** dan secara opsional meng-commit hook harness. Segala hal lain — instalasi, persetujuan, autentikasi, gaya penulisan — **ditunda** ke [skill agen Dailybot](https://github.com/DailybotHQ/agent-skill) resmi (saat ini **3.4.0**). +Addon DWP Dailybot **tidak** menciptakan ulang Dailybot. Addon ini menghubungkan eksekusi rencana ke sub-skill dailybot **`report`** dan secara opsional meng-commit hook harness. Segala hal lain — instalasi, persetujuan, autentikasi, gaya penulisan — **ditunda** ke [skill agen Dailybot](https://github.com/DailybotHQ/agent-skill) resmi (saat ini **3.10.3**). ### Empat peristiwa siklus hidup @@ -40,7 +40,7 @@ Payload berasal dari lapisan status rencana (`state.json`) jika ada: `completed` ### Penegakan hook opsional -Dengan `dailybot-cli >= 3.1.2`, addon **dapat** meng-commit hook harness tingkat repo (`dailybot hook session-start | activity | post-commit | stop | dismiss`) yang didukung ledger lokal per repo. Harness mengingatkan agen di akhir giliran ketika peristiwa siklus hidup terlewat — penting untuk sesi panjang tanpa pengawasan di mana instruksi prompt memudar. +Dengan `dailybot-cli >= 3.7.0`, addon **dapat** meng-commit hook harness tingkat repo (`dailybot hook session-start | activity | post-commit | stop | dismiss`) yang didukung ledger lokal per repo. Harness mengingatkan agen di akhir giliran ketika peristiwa siklus hidup terlewat — penting untuk sesi panjang tanpa pengawasan di mana instruksi prompt memudar. Laporan siklus hidup yang berhasil **mereset** ledger hook, sehingga kedua lapisan tidak pernah melaporkan ganda. Perintah hook hanya membaca status lokal dan selalu keluar dengan `0`. @@ -73,7 +73,7 @@ Addon **menawarkan** jalur instalasi; skill Dailybot mengelola persetujuan dan v | **Perbarui skill yang ada** | `npx skills update dailybot` | | **OpenClaw** | `openclaw skills install dailybot` | | **Git clone** | `git clone https://github.com/DailybotHQ/agent-skill.git` + `./setup.sh` | -| **Dailybot CLI** (minimum `>= 3.1.2`) | Diinstal oleh skill saat penggunaan pertama melalui `shared/auth.md` terverifikasi; atau `pip install 'dailybot-cli>=3.1.2'`, Homebrew, atau installer terverifikasi checksum di [cli.dailybot.com](https://cli.dailybot.com) | +| **Dailybot CLI** (minimum `>= 3.7.0`) | Diinstal oleh skill saat penggunaan pertama melalui `shared/auth.md` terverifikasi; atau `pip install 'dailybot-cli>=3.7.0'`, Homebrew, atau installer terverifikasi checksum di [cli.dailybot.com](https://cli.dailybot.com) | Periksa versi: `dailybot --version` dan `dailybot version --check`. Upgrade: `dailybot upgrade`. @@ -82,13 +82,14 @@ Periksa versi: `dailybot --version` dan `dailybot version --check`. Upgrade: `da Addon ini **tidak pernah** meminta email, OTP, atau API key, dan **tidak pernah** menyimpan kredensial. Autentikasi dimiliki oleh [`shared/auth.md`](https://github.com/DailybotHQ/agent-skill/blob/main/skills/dailybot/shared/auth.md) skill Dailybot: - `dailybot login` (email OTP), atau -- `DAILYBOT_API_KEY` / `dailybot config key=...` +- `DAILYBOT_API_KEY` / `dailybot config key=...`, atau +- file key per repo `.dailybot/env.json` yang opt-in dan di-gitignore (`dailybot env add/use`, CLI `>= 3.7.0`) sehingga seorang pengembang dapat masuk ke org yang berbeda di repo yang berbeda. -Jika autentikasi ditolak atau tidak tersedia, pelaporan dilewati secara diam-diam — pekerjaan berlanjut. +Resolusi auth bersifat **Bearer-first**: token sesi diprioritaskan, dengan retry transparan Bearer→API-key pada `401`/`403` sehingga token basi tidak pernah memblokir key yang valid. Jika autentikasi ditolak atau tidak tersedia, pelaporan dilewati secara diam-diam — pekerjaan berlanjut. -## Skill Dailybot yang dipasangkan — 13 kemampuan (3.4.0) +## Skill Dailybot yang dipasangkan — 14 kemampuan (3.10.3) -Menginstal skill agen Dailybot membawa jauh lebih banyak daripada yang dihubungkan addon DWP. Paket skill resmi (skill **3.4.0**, CLI **>= 3.1.2**, publish saat ini **3.2.1**) mengekspos **13 sub-skill terkoordinasi**: +Menginstal skill agen Dailybot membawa jauh lebih banyak daripada yang dihubungkan addon DWP. Paket skill resmi (skill **3.10.3**, baseline CLI **>= 3.7.0**, publish saat ini **3.7.3**) mengekspos **14 sub-skill terkoordinasi**: | Sub-skill | Fungsinya | |-----------|--------------| @@ -102,9 +103,10 @@ Menginstal skill agen Dailybot membawa jauh lebih banyak daripada yang dihubungk | **Check-ins** | Selesaikan standup; **author** check-in (jadwal, peserta, pertanyaan, pengingat, pengaturan AI) | | **Kudos** | Kenali rekan tim atau seluruh tim; jelajahi feed pengakuan, feed org, wall of fame | | **Teams** | Daftar tim, periksa anggota, selesaikan nama ke UUID; `me`, `org`, profil pengguna | -| **Forms** | Daftar, kirim, perbarui, transisi formulir; **author** formulir (status workflow, izin, ChatOps) | +| **Forms** | Daftar (kini **bercakupan org** secara default, dengan `--mine` dan `--owner` untuk mempersempit), kirim, perbarui, transisi formulir; **author** formulir (status workflow, izin, ChatOps); paginasi, pencarian, dan filter tanggal | | **Workflows** | Baca workflow org (`workflow list` / `workflow get`; hanya baca) | | **Report channels** | Temukan UUID channel untuk formulir atau check-in | +| **Per-repo API keys** | Kelola `.dailybot/env.json` — file API key + URL per environment yang opt-in dan di-gitignore (`dailybot env add / use / show / list / remove / off / on`, CLI `>= 3.7.0`) | **Addon DWP hanya menghubungkan `report` ke eksekusi rencana.** Panggil skill Dailybot langsung untuk segala hal lain — misalnya, posting ringkasan deploy ke `#releases`, selesaikan standup, atau minta AI Dailybot merangkum tren check-in. diff --git a/src/content/kit/it/dailybot.md b/src/content/kit/it/dailybot.md index 8fd707c..668de7f 100644 --- a/src/content/kit/it/dailybot.md +++ b/src/content/kit/it/dailybot.md @@ -1,6 +1,6 @@ --- title: Dailybot -description: "Addon DWP opt-in: collega il ciclo di vita del piano a un team Dailybot, enforcement opzionale degli hook e la skill agente Dailybot completa 3.4.0 (chat, check-in, moduli, ask AI e altro)." +description: "Addon DWP opt-in: collega il ciclo di vita del piano a un team Dailybot, enforcement opzionale degli hook e la skill agente Dailybot completa 3.10.3 (chat, check-in, moduli, ask AI e altro)." kind: addon lang: it order: 2 @@ -23,7 +23,7 @@ La metodologia Deep Work Plan di base ha **zero** dipendenze da Dailybot. Un rep ## Cosa collega questo addon (volutamente ristretto) -L'addon DWP Dailybot **non** reinventa Dailybot. Collega l'esecuzione del piano alla sub-skill dailybot **`report`** e opzionalmente committa gli hook del harness. Tutto il resto — installazione, consenso, autenticazione, stile di scrittura — è **delegato** alla [skill agente Dailybot](https://github.com/DailybotHQ/agent-skill) ufficiale (attualmente **3.4.0**). +L'addon DWP Dailybot **non** reinventa Dailybot. Collega l'esecuzione del piano alla sub-skill dailybot **`report`** e opzionalmente committa gli hook del harness. Tutto il resto — installazione, consenso, autenticazione, stile di scrittura — è **delegato** alla [skill agente Dailybot](https://github.com/DailybotHQ/agent-skill) ufficiale (attualmente **3.10.3**). ### Quattro eventi del ciclo di vita @@ -40,7 +40,7 @@ I payload derivano dal layer di stato del piano (`state.json`) quando presente: ### Enforcement opzionale degli hook -Con `dailybot-cli >= 3.1.2`, l'addon **può** committare hook del harness a livello di repository (`dailybot hook session-start | activity | post-commit | stop | dismiss`) supportati da un registro locale per repository. Il harness ricorda all'agente a fine turno quando un evento del ciclo di vita è stato perso — critico per le lunghe sessioni non presidiate in cui le istruzioni del prompt si diluiscono. +Con `dailybot-cli >= 3.7.0`, l'addon **può** committare hook del harness a livello di repository (`dailybot hook session-start | activity | post-commit | stop | dismiss`) supportati da un registro locale per repository. Il harness ricorda all'agente a fine turno quando un evento del ciclo di vita è stato perso — critico per le lunghe sessioni non presidiate in cui le istruzioni del prompt si diluiscono. Un report del ciclo di vita riuscito **azzera** il registro degli hook, così i due livelli non raddoppiano mai i report. I comandi degli hook leggono solo stato locale ed escono sempre con `0`. @@ -73,7 +73,7 @@ L'addon **offre** percorsi di installazione; la skill Dailybot gestisce consenso | **Aggiorna skill esistente** | `npx skills update dailybot` | | **OpenClaw** | `openclaw skills install dailybot` | | **Git clone** | `git clone https://github.com/DailybotHQ/agent-skill.git` + `./setup.sh` | -| **Dailybot CLI** (minimo `>= 3.1.2`) | Installata dalla skill al primo utilizzo tramite `shared/auth.md` verificato; oppure `pip install 'dailybot-cli>=3.1.2'`, Homebrew o l'installer con checksum verificato su [cli.dailybot.com](https://cli.dailybot.com) | +| **Dailybot CLI** (minimo `>= 3.7.0`) | Installata dalla skill al primo utilizzo tramite `shared/auth.md` verificato; oppure `pip install 'dailybot-cli>=3.7.0'`, Homebrew o l'installer con checksum verificato su [cli.dailybot.com](https://cli.dailybot.com) | Verifica versioni: `dailybot --version` e `dailybot version --check`. Aggiornamento: `dailybot upgrade`. @@ -82,13 +82,14 @@ Verifica versioni: `dailybot --version` e `dailybot version --check`. Aggiorname Questo addon **non** chiede mai email, OTP o API key e **non** memorizza credenziali. L'autenticazione è gestita da [`shared/auth.md`](https://github.com/DailybotHQ/agent-skill/blob/main/skills/dailybot/shared/auth.md) della skill Dailybot: - `dailybot login` (email OTP), oppure -- `DAILYBOT_API_KEY` / `dailybot config key=...` +- `DAILYBOT_API_KEY` / `dailybot config key=...`, oppure +- un file di chiavi per repository `.dailybot/env.json` opt-in ed escluso da git (`dailybot env add/use`, CLI `>= 3.7.0`) così che uno sviluppatore possa essere autenticato in org diverse in repository diversi. -Se l'autenticazione viene rifiutata o non è disponibile, il reporting viene saltato in silenzio — il lavoro continua. +La risoluzione dell'auth è **Bearer-first**: un token di sessione ha la priorità, con un retry trasparente Bearer→API-key su `401`/`403` così che un token scaduto non blocchi mai una chiave valida. Se l'autenticazione viene rifiutata o non è disponibile, il reporting viene saltato in silenzio — il lavoro continua. -## La skill Dailybot abbinata — 13 capacità (3.4.0) +## La skill Dailybot abbinata — 14 capacità (3.10.3) -Installare la skill agente Dailybot porta molto più di quanto l'addon DWP collega. Il pacchetto skill ufficiale (skill **3.4.0**, CLI **>= 3.1.2**, publish corrente **3.2.1**) espone **13 sub-skill coordinate**: +Installare la skill agente Dailybot porta molto più di quanto l'addon DWP collega. Il pacchetto skill ufficiale (skill **3.10.3**, CLI baseline **>= 3.7.0**, publish corrente **3.7.3**) espone **14 sub-skill coordinate**: | Sub-skill | Cosa fa | |-----------|--------------| @@ -102,9 +103,10 @@ Installare la skill agente Dailybot porta molto più di quanto l'addon DWP colle | **Check-ins** | Completa standup; **author** check-in (pianificazione, partecipanti, domande, promemoria, impostazioni AI) | | **Kudos** | Riconosce colleghi o interi team; sfoglia feed di riconoscimenti, feed org, wall of fame | | **Teams** | Elenca team, ispeziona membri, risolve nomi in UUID; `me`, `org`, profili utente | -| **Forms** | Elenca, invia, aggiorna, transiziona moduli; **author** moduli (stati workflow, permessi, ChatOps) | +| **Forms** | Elenca (ora **con ambito org** di default, con `--mine` e `--owner` per restringere), invia, aggiorna, transiziona moduli; **author** moduli (stati workflow, permessi, ChatOps); paginazione, ricerca e filtri per data | | **Workflows** | Legge workflow org (`workflow list` / `workflow get`; sola lettura) | | **Report channels** | Scopre UUID dei canali per moduli o check-in | +| **Per-repo API keys** | Gestisce `.dailybot/env.json` — un file opt-in ed escluso da git di API key + URL per ambiente (`dailybot env add / use / show / list / remove / off / on`, CLI `>= 3.7.0`) | **L'addon DWP collega solo `report` all'esecuzione del piano.** Invoca la skill Dailybot direttamente per tutto il resto — ad esempio, pubblica un riepilogo deploy su `#releases`, completa uno standup o chiedi all'AI Dailybot di riassumere le tendenze dei check-in. diff --git a/src/content/kit/ja/dailybot.md b/src/content/kit/ja/dailybot.md index 34330c5..541a7c3 100644 --- a/src/content/kit/ja/dailybot.md +++ b/src/content/kit/ja/dailybot.md @@ -1,6 +1,6 @@ --- title: Dailybot -description: "オプトインの DWP アドオン：プランライフサイクルを Dailybot チームに接続し、オプションのフック強制と、完全な Dailybot エージェントスキル 3.4.0（チャット、チェックイン、フォーム、Ask AI など）を提供します。" +description: "オプトインの DWP アドオン：プランライフサイクルを Dailybot チームに接続し、オプションのフック強制と、完全な Dailybot エージェントスキル 3.10.3（チャット、チェックイン、フォーム、Ask AI など）を提供します。" kind: addon lang: ja order: 2 @@ -23,7 +23,7 @@ Deep Work Plan の実行を **Dailybot チーム**に接続し、エージェン ## このアドオンが接続するもの（意図的に狭い設計） -DWP Dailybot アドオンは Dailybot を**再発明しません**。プラン実行を dailybot **`report`** サブスキルに接続し、オプションで harness フックをコミットします。それ以外——インストール、同意、認証、文体——はすべて公式 [Dailybot エージェントスキル](https://github.com/DailybotHQ/agent-skill)（現在 **3.4.0**）に**委譲**されます。 +DWP Dailybot アドオンは Dailybot を**再発明しません**。プラン実行を dailybot **`report`** サブスキルに接続し、オプションで harness フックをコミットします。それ以外——インストール、同意、認証、文体——はすべて公式 [Dailybot エージェントスキル](https://github.com/DailybotHQ/agent-skill)（現在 **3.10.3**）に**委譲**されます。 ### 4 つのライフサイクルイベント @@ -40,7 +40,7 @@ DWP `create` / `execute` 中、アドオンは**4 つのベストエフォート ### オプションのフック強制 -`dailybot-cli >= 3.1.2` で、アドオンはリポジトリレベルの harness フック（`dailybot hook session-start | activity | post-commit | stop | dismiss`）を**コミットしてもよい**。ローカルのリポジトリごとの台帳で支えられる。ライフサイクルイベントを見逃したとき、harness がターン終了時にエージェントにリマインド——プロンプト指示が薄れる長時間の無人セッションで重要。 +`dailybot-cli >= 3.7.0` で、アドオンはリポジトリレベルの harness フック（`dailybot hook session-start | activity | post-commit | stop | dismiss`）を**コミットしてもよい**。ローカルのリポジトリごとの台帳で支えられる。ライフサイクルイベントを見逃したとき、harness がターン終了時にエージェントにリマインド——プロンプト指示が薄れる長時間の無人セッションで重要。 成功したライフサイクルレポートはフック台帳を**リセット**するため、二重レポートは起きない。フックコマンドはローカル状態のみを読み、常に `0` で終了。 @@ -73,7 +73,7 @@ DWP `create` / `execute` 中、アドオンは**4 つのベストエフォート | **既存スキルの更新** | `npx skills update dailybot` | | **OpenClaw** | `openclaw skills install dailybot` | | **Git クローン** | `git clone https://github.com/DailybotHQ/agent-skill.git` + `./setup.sh` | -| **Dailybot CLI**（最低 `>= 3.1.2`） | 初回利用時にスキルが検証済み `shared/auth.md` 経由でインストール；または `pip install 'dailybot-cli>=3.1.2'`、Homebrew、または [cli.dailybot.com](https://cli.dailybot.com) のチェックサム検証インストーラー | +| **Dailybot CLI**（最低 `>= 3.7.0`） | 初回利用時にスキルが検証済み `shared/auth.md` 経由でインストール；または `pip install 'dailybot-cli>=3.7.0'`、Homebrew、または [cli.dailybot.com](https://cli.dailybot.com) のチェックサム検証インストーラー | バージョン確認：`dailybot --version` と `dailybot version --check`。アップグレード：`dailybot upgrade`。 @@ -81,14 +81,15 @@ DWP `create` / `execute` 中、アドオンは**4 つのベストエフォート このアドオンはメール、OTP、API キーを**決して**求めず、認証情報を**決して**保存しない。認証は Dailybot スキルの [`shared/auth.md`](https://github.com/DailybotHQ/agent-skill/blob/main/skills/dailybot/shared/auth.md) が所有： -- `dailybot login`（メール OTP）、または -- `DAILYBOT_API_KEY` / `dailybot config key=...` +- `dailybot login`（メール OTP）、 +- `DAILYBOT_API_KEY` / `dailybot config key=...`、または +- オプトインで gitignore された `.dailybot/env.json` のリポジトリごとのキーファイル（`dailybot env add/use`、CLI `>= 3.7.0`）——開発者はリポジトリごとに異なる組織にサインインできる。 -認証が拒否または利用不可の場合、レポートは静かにスキップ——作業は継続。 +認証解決は **Bearer 優先**：セッショントークンが優先され、`401`/`403` 時に透過的な Bearer→API キーのリトライを行うため、古いトークンが有効なキーをブロックすることはない。認証が拒否または利用不可の場合、レポートは静かにスキップ——作業は継続。 -## ペアの Dailybot スキル——13 の能力（3.4.0） +## ペアの Dailybot スキル——14 の能力（3.10.3） -Dailybot エージェントスキルのインストールは、DWP アドオンが接続する以上のものをもたらす。公式スキルパック（スキル **3.4.0**、CLI **>= 3.1.2**、現在の公開 **3.2.1**）は**13 の協調サブスキル**を公開： +Dailybot エージェントスキルのインストールは、DWP アドオンが接続する以上のものをもたらす。公式スキルパック（スキル **3.10.3**、CLI ベースライン **>= 3.7.0**、現在の公開 **3.7.3**）は**14 の協調サブスキル**を公開： | サブスキル | 機能 | |------------|------| @@ -102,9 +103,10 @@ Dailybot エージェントスキルのインストールは、DWP アドオン | **Check-ins** | スタンドアップ完了；チェックインの**作成**（スケジュール、参加者、質問、リマインダー、AI 設定） | | **Kudos** | チームメイトまたはチーム全体を表彰；認識フィード、組織フィード、殿堂を閲覧 | | **Teams** | チーム一覧、メンバー確認、名前から UUID 解決；`me`、`org`、ユーザープロフィール | -| **Forms** | フォームの一覧、送信、更新、遷移；フォームの**作成**（ワークフロー状態、権限、ChatOps） | +| **Forms** | フォームの一覧（デフォルトで**組織スコープ**、`--mine` と `--owner` で絞り込み）、送信、更新、遷移；フォームの**作成**（ワークフロー状態、権限、ChatOps）；ページネーション、検索、日付フィルター | | **Workflows** | 組織ワークフローの読み取り（`workflow list` / `workflow get`；読み取り専用） | | **Report channels** | フォームやチェックイン用のチャンネル UUID を発見 | +| **Per-repo API keys** | `.dailybot/env.json` を管理——環境ごとの API キー + URL のオプトインで gitignore されたファイル（`dailybot env add / use / show / list / remove / off / on`、CLI `>= 3.7.0`） | **DWP アドオンは `report` のみをプラン実行に接続。** それ以外は Dailybot スキルを直接呼び出す——例：`#releases` にデプロイ概要を投稿、スタンドアップ完了、Dailybot AI にチェックイントレンドの要約を依頼。 diff --git a/src/content/kit/ko/dailybot.md b/src/content/kit/ko/dailybot.md index 3eb7ed6..04d668b 100644 --- a/src/content/kit/ko/dailybot.md +++ b/src/content/kit/ko/dailybot.md @@ -1,6 +1,6 @@ --- title: Dailybot -description: "옵트인 DWP 애드온: 플랜 라이프사이클을 Dailybot 팀에 연결하고, 선택적 훅 강제 및 전체 Dailybot 에이전트 스킬 3.4.0(채팅, 체크인, 폼, Ask AI 등)을 제공합니다." +description: "옵트인 DWP 애드온: 플랜 라이프사이클을 Dailybot 팀에 연결하고, 선택적 훅 강제 및 전체 Dailybot 에이전트 스킬 3.10.3(채팅, 체크인, 폼, Ask AI 등)을 제공합니다." kind: addon lang: ko order: 2 @@ -23,7 +23,7 @@ Deep Work Plan 실행을 **Dailybot 팀**에 연결하여 사람들이 에이전 ## 이 애드온이 연결하는 것(의도적으로 좁은 설계) -DWP Dailybot 애드온은 Dailybot을 **재발명하지 않습니다**. 플랜 실행을 dailybot **`report`** 서브스킬에 연결하고 선택적으로 harness 훅을 커밋합니다. 나머지 — 설치, 동의, 인증, 작성 스타일 — 는 모두 공식 [Dailybot 에이전트 스킬](https://github.com/DailybotHQ/agent-skill)(현재 **3.4.0**)에 **위임**됩니다. +DWP Dailybot 애드온은 Dailybot을 **재발명하지 않습니다**. 플랜 실행을 dailybot **`report`** 서브스킬에 연결하고 선택적으로 harness 훅을 커밋합니다. 나머지 — 설치, 동의, 인증, 작성 스타일 — 는 모두 공식 [Dailybot 에이전트 스킬](https://github.com/DailybotHQ/agent-skill)(현재 **3.10.3**)에 **위임**됩니다. ### 네 가지 라이프사이클 이벤트 @@ -40,7 +40,7 @@ DWP `create` / `execute` 중 애드온은 **네 가지 최선 노력 에이전 ### 선택적 훅 강제 -`dailybot-cli >= 3.1.2`에서 애드온은 저장소 수준 harness 훅(`dailybot hook session-start | activity | post-commit | stop | dismiss`)을 **커밋할 수 있음**. 로컬 저장소별 원장으로 지원. 라이프사이클 이벤트를 놓쳤을 때 harness가 턴 종료 시 에이전트에게 알림 — 프롬프트 지시가 약해지는 긴 무인 세션에 중요. +`dailybot-cli >= 3.7.0`에서 애드온은 저장소 수준 harness 훅(`dailybot hook session-start | activity | post-commit | stop | dismiss`)을 **커밋할 수 있음**. 로컬 저장소별 원장으로 지원. 라이프사이클 이벤트를 놓쳤을 때 harness가 턴 종료 시 에이전트에게 알림 — 프롬프트 지시가 약해지는 긴 무인 세션에 중요. 성공한 라이프사이클 보고는 훅 원장을 **재설정**하므로 두 계층이 이중 보고하지 않음. 훅 명령은 로컬 상태만 읽고 항상 `0`으로 종료. @@ -73,7 +73,7 @@ DWP `create` / `execute` 중 애드온은 **네 가지 최선 노력 에이전 | **기존 스킬 업데이트** | `npx skills update dailybot` | | **OpenClaw** | `openclaw skills install dailybot` | | **Git 클론** | `git clone https://github.com/DailybotHQ/agent-skill.git` + `./setup.sh` | -| **Dailybot CLI**(최소 `>= 3.1.2`) | 첫 사용 시 스킬이 검증된 `shared/auth.md`를 통해 설치; 또는 `pip install 'dailybot-cli>=3.1.2'`, Homebrew, 또는 [cli.dailybot.com](https://cli.dailybot.com)의 체크섬 검증 설치 프로그램 | +| **Dailybot CLI**(최소 `>= 3.7.0`) | 첫 사용 시 스킬이 검증된 `shared/auth.md`를 통해 설치; 또는 `pip install 'dailybot-cli>=3.7.0'`, Homebrew, 또는 [cli.dailybot.com](https://cli.dailybot.com)의 체크섬 검증 설치 프로그램 | 버전 확인: `dailybot --version` 및 `dailybot version --check`. 업그레이드: `dailybot upgrade`. @@ -82,13 +82,14 @@ DWP `create` / `execute` 중 애드온은 **네 가지 최선 노력 에이전 이 애드온은 이메일, OTP 또는 API 키를 **절대** 요청하지 않고 자격 증명을 **절대** 저장하지 않습니다. 인증은 Dailybot 스킬의 [`shared/auth.md`](https://github.com/DailybotHQ/agent-skill/blob/main/skills/dailybot/shared/auth.md)가 소유: - `dailybot login`(이메일 OTP), 또는 -- `DAILYBOT_API_KEY` / `dailybot config key=...` +- `DAILYBOT_API_KEY` / `dailybot config key=...`, 또는 +- 옵트인, gitignore된 `.dailybot/env.json` 저장소별 키 파일(`dailybot env add/use`, CLI `>= 3.7.0`) — 개발자가 서로 다른 저장소에서 서로 다른 조직에 로그인할 수 있게 함. -인증이 거부되거나 사용 불가하면 보고는 조용히 건너뜀 — 작업은 계속됨. +인증 해석은 **Bearer 우선**입니다: 세션 토큰이 우선하며, `401`/`403` 시 투명한 Bearer→API 키 재시도로 오래된 토큰이 유효한 키를 절대 차단하지 않습니다. 인증이 거부되거나 사용 불가하면 보고는 조용히 건너뜀 — 작업은 계속됨. -## 페어링된 Dailybot 스킬 — 13가지 기능(3.4.0) +## 페어링된 Dailybot 스킬 — 14가지 기능(3.10.3) -Dailybot 에이전트 스킬 설치는 DWP 애드온이 연결하는 것 이상을 제공합니다. 공식 스킬 팩(스킬 **3.4.0**, CLI **>= 3.1.2**, 현재 게시 **3.2.1**)은 **13개의 조율된 서브스킬**을 노출: +Dailybot 에이전트 스킬 설치는 DWP 애드온이 연결하는 것 이상을 제공합니다. 공식 스킬 팩(스킬 **3.10.3**, CLI 기준 **>= 3.7.0**, 현재 게시 **3.7.3**)은 **14개의 조율된 서브스킬**을 노출: | 서브스킬 | 기능 | |----------|------| @@ -102,9 +103,10 @@ Dailybot 에이전트 스킬 설치는 DWP 애드온이 연결하는 것 이상 | **Check-ins** | 스탠드업 완료; 체크인 **작성**(일정, 참가자, 질문, 알림, AI 설정) | | **Kudos** | 팀원 또는 전체 팀 인정; 인정 피드, 조직 피드, 명예의 전당 탐색 | | **Teams** | 팀 목록, 멤버 조회, 이름을 UUID로 해석; `me`, `org`, 사용자 프로필 | -| **Forms** | 폼 목록, 제출, 업데이트, 전환; 폼 **작성**(워크플로 상태, 권한, ChatOps) | +| **Forms** | 폼 목록(이제 기본적으로 **조직 범위**, `--mine` 및 `--owner`로 범위 좁히기), 제출, 업데이트, 전환; 폼 **작성**(워크플로 상태, 권한, ChatOps); 페이지네이션, 검색, 날짜 필터 | | **Workflows** | 조직 워크플로 읽기(`workflow list` / `workflow get`; 읽기 전용) | | **Report channels** | 폼 또는 체크인용 채널 UUID 발견 | +| **Per-repo API keys** | `.dailybot/env.json` 관리 — 환경별 API 키 + URL의 옵트인, gitignore된 파일(`dailybot env add / use / show / list / remove / off / on`, CLI `>= 3.7.0`) | **DWP 애드온은 `report`만 플랜 실행에 연결합니다.** 나머지는 Dailybot 스킬을 직접 호출 — 예: `#releases`에 배포 요약 게시, 스탠드업 완료, Dailybot AI에 체크인 트렌드 요약 요청. diff --git a/src/content/kit/pl/dailybot.md b/src/content/kit/pl/dailybot.md index e900f6c..ff4d8da 100644 --- a/src/content/kit/pl/dailybot.md +++ b/src/content/kit/pl/dailybot.md @@ -1,6 +1,6 @@ --- title: Dailybot -description: "Opcjonalny addon DWP: połącz cykl życia planu z zespołem Dailybot, opcjonalne wymuszanie hooków oraz pełny skill agenta Dailybot 3.4.0 (czat, check-iny, formularze, Ask AI i więcej)." +description: "Opcjonalny addon DWP: połącz cykl życia planu z zespołem Dailybot, opcjonalne wymuszanie hooków oraz pełny skill agenta Dailybot 3.10.3 (czat, check-iny, formularze, Ask AI i więcej)." kind: addon lang: pl order: 2 @@ -23,7 +23,7 @@ Podstawowa metodyka Deep Work Plan ma **zero** zależności od Dailybot. Repozyt ## Co ten addon łączy (celowo wąsko) -Addon DWP Dailybot **nie wymyśla** Dailybot na nowo. Łączy wykonanie planu z sub-skillem dailybot **`report`** i opcjonalnie commituje hooki harnessa. Reszta — instalacja, zgoda, uwierzytelnianie, styl pisania — jest **delegowana** do oficjalnego [skilla agenta Dailybot](https://github.com/DailybotHQ/agent-skill) (obecnie **3.4.0**). +Addon DWP Dailybot **nie wymyśla** Dailybot na nowo. Łączy wykonanie planu z sub-skillem dailybot **`report`** i opcjonalnie commituje hooki harnessa. Reszta — instalacja, zgoda, uwierzytelnianie, styl pisania — jest **delegowana** do oficjalnego [skilla agenta Dailybot](https://github.com/DailybotHQ/agent-skill) (obecnie **3.10.3**). ### Cztery zdarzenia cyklu życia @@ -40,7 +40,7 @@ Payloady pochodzą z warstwy stanu planu (`state.json`), gdy jest obecna: `compl ### Opcjonalne wymuszanie hooków -Przy `dailybot-cli >= 3.1.2` addon **może** zacommitować hooki harnessa na poziomie repo (`dailybot hook session-start | activity | post-commit | stop | dismiss`) wspierane lokalnym rejestrem per-repo. Harness przypomina agentowi na końcu tury, gdy zdarzenie cyklu życia zostało pominięte — kluczowe dla długich sesji bez nadzoru, gdzie instrukcje promptu słabną. +Przy `dailybot-cli >= 3.7.0` addon **może** zacommitować hooki harnessa na poziomie repo (`dailybot hook session-start | activity | post-commit | stop | dismiss`) wspierane lokalnym rejestrem per-repo. Harness przypomina agentowi na końcu tury, gdy zdarzenie cyklu życia zostało pominięte — kluczowe dla długich sesji bez nadzoru, gdzie instrukcje promptu słabną. Udany raport cyklu życia **resetuje** rejestr hooków, więc obie warstwy nigdy nie raportują podwójnie. Polecenia hooków czytają tylko stan lokalny i zawsze kończą się kodem `0`. @@ -73,7 +73,7 @@ Addon **proponuje** ścieżki instalacji; skill Dailybot odpowiada za zgodę i w | **Aktualizacja istniejącego skilla** | `npx skills update dailybot` | | **OpenClaw** | `openclaw skills install dailybot` | | **Git clone** | `git clone https://github.com/DailybotHQ/agent-skill.git` + `./setup.sh` | -| **Dailybot CLI** (minimum `>= 3.1.2`) | Instalowany przez skill przy pierwszym użyciu przez `shared/auth.md`; lub `pip install 'dailybot-cli>=3.1.2'`, Homebrew lub installer ze sprawdzonym checksum na [cli.dailybot.com](https://cli.dailybot.com) | +| **Dailybot CLI** (minimum `>= 3.7.0`) | Instalowany przez skill przy pierwszym użyciu przez `shared/auth.md`; lub `pip install 'dailybot-cli>=3.7.0'`, Homebrew lub installer ze sprawdzonym checksum na [cli.dailybot.com](https://cli.dailybot.com) | Sprawdź wersje: `dailybot --version` i `dailybot version --check`. Aktualizacja: `dailybot upgrade`. @@ -82,13 +82,14 @@ Sprawdź wersje: `dailybot --version` i `dailybot version --check`. Aktualizacja Ten addon **nigdy** nie pyta o e-mail, OTP ani klucze API i **nigdy** nie przechowuje poświadczeń. Uwierzytelnianie należy do skilla Dailybot [`shared/auth.md`](https://github.com/DailybotHQ/agent-skill/blob/main/skills/dailybot/shared/auth.md): - `dailybot login` (OTP e-mail), lub -- `DAILYBOT_API_KEY` / `dailybot config key=...` +- `DAILYBOT_API_KEY` / `dailybot config key=...`, lub +- opcjonalny, gitignorowany plik kluczy per-repo `.dailybot/env.json` (`dailybot env add/use`, CLI `>= 3.7.0`), aby programista mógł być zalogowany do różnych organizacji w różnych repozytoriach. -Jeśli auth zostanie odrzucone lub jest niedostępne, raportowanie jest cicho pomijane — praca trwa dalej. +Rozwiązywanie auth działa w trybie **Bearer-first**: token sesji ma priorytet, z przezroczystym ponowieniem Bearer→klucz API przy `401`/`403`, więc nieaktualny token nigdy nie blokuje ważnego klucza. Jeśli auth zostanie odrzucone lub jest niedostępne, raportowanie jest cicho pomijane — praca trwa dalej. -## Sparowany skill Dailybot — 13 możliwości (3.4.0) +## Sparowany skill Dailybot — 14 możliwości (3.10.3) -Instalacja skilla agenta Dailybot daje znacznie więcej niż łączy addon DWP. Oficjalny pakiet skilli (skill **3.4.0**, CLI **>= 3.1.2**, bieżąca publikacja **3.2.1**) udostępnia **13 skoordynowanych sub-skilli**: +Instalacja skilla agenta Dailybot daje znacznie więcej niż łączy addon DWP. Oficjalny pakiet skilli (skill **3.10.3**, CLI baza **>= 3.7.0**, bieżąca publikacja **3.7.3**) udostępnia **14 skoordynowanych sub-skilli**: | Sub-skill | Co robi | |-----------|--------------| @@ -102,9 +103,10 @@ Instalacja skilla agenta Dailybot daje znacznie więcej niż łączy addon DWP. | **Check-ins** | Uzupełnianie standupów; **tworzenie** check-inów (harmonogram, uczestnicy, pytania, przypomnienia, ustawienia AI) | | **Kudos** | Docenianie współpracowników lub całych zespołów; przeglądanie feedu uznania, feedu org, wall of fame | | **Teams** | Listowanie zespołów, inspekcja członków, rozwiązywanie nazw do UUID; `me`, `org`, profile użytkowników | -| **Forms** | Listowanie, wysyłanie, aktualizacja, przejścia formularzy; **tworzenie** formularzy (stany workflow, uprawnienia, ChatOps) | +| **Forms** | Listowanie (teraz domyślnie **w zakresie org**, z `--mine` i `--owner` do zawężenia), wysyłanie, aktualizacja, przejścia formularzy; **tworzenie** formularzy (stany workflow, uprawnienia, ChatOps); paginacja, wyszukiwanie i filtry dat | | **Workflows** | Odczyt workflow org (`workflow list` / `workflow get`; tylko do odczytu) | | **Report channels** | Odkrywanie UUID kanałów dla formularzy lub check-inów | +| **Klucze API per-repo** | Zarządzanie `.dailybot/env.json` — opcjonalnym, gitignorowanym plikiem kluczy API + URL na środowisko (`dailybot env add / use / show / list / remove / off / on`, CLI `>= 3.7.0`) | **Addon DWP łączy tylko `report` z wykonaniem planu.** Wywołuj skill Dailybot bezpośrednio dla wszystkiego innego — np. opublikuj podsumowanie wdrożenia na `#releases`, uzupełnij standup lub poproś AI Dailybot o podsumowanie trendów check-inów. diff --git a/src/content/kit/pt/dailybot.md b/src/content/kit/pt/dailybot.md index 7d803f9..8111615 100644 --- a/src/content/kit/pt/dailybot.md +++ b/src/content/kit/pt/dailybot.md @@ -1,6 +1,6 @@ --- title: Dailybot -description: "Addon opcional do DWP: conecta o plano a uma equipa Dailybot, hooks opcionais e a skill de agente 3.4.0 (chat, check-ins, formulários, ask AI e mais)." +description: "Addon opcional do DWP: conecta o plano a uma equipa Dailybot, hooks opcionais e a skill de agente 3.10.3 (chat, check-ins, formulários, ask AI e mais)." kind: addon lang: pt order: 2 @@ -23,7 +23,7 @@ A metodologia central do Deep Work Plan tem **zero** dependência do Dailybot. U ## O que este addon liga (deliberadamente restrito) -O addon Dailybot do DWP **não** reinventa o Dailybot. Liga a execução do plano à sub-skill **`report`** do dailybot e, opcionalmente, confirma hooks do harness. Todo o resto — instalação, consentimento, autenticação, estilo de escrita — é **adiado** para a [skill de agente Dailybot](https://github.com/DailybotHQ/agent-skill) oficial (atualmente **3.4.0**). +O addon Dailybot do DWP **não** reinventa o Dailybot. Liga a execução do plano à sub-skill **`report`** do dailybot e, opcionalmente, confirma hooks do harness. Todo o resto — instalação, consentimento, autenticação, estilo de escrita — é **adiado** para a [skill de agente Dailybot](https://github.com/DailybotHQ/agent-skill) oficial (atualmente **3.10.3**). ### Quatro eventos do ciclo de vida @@ -40,7 +40,7 @@ As cargas úteis derivam da camada de estado do plano (`state.json`) quando pres ### Reforço opcional por hooks -Com `dailybot-cli >= 3.1.2`, o addon **pode** confirmar hooks do harness ao nível do repositório (`dailybot hook session-start | activity | post-commit | stop | dismiss`) apoiados por um registo local por repositório. O harness lembra o agente no fim do turno quando um evento do ciclo de vida foi omitido — crítico para sessões longas sem supervisão em que as instruções do prompt se diluem. +Com `dailybot-cli >= 3.7.0`, o addon **pode** confirmar hooks do harness ao nível do repositório (`dailybot hook session-start | activity | post-commit | stop | dismiss`) apoiados por um registo local por repositório. O harness lembra o agente no fim do turno quando um evento do ciclo de vida foi omitido — crítico para sessões longas sem supervisão em que as instruções do prompt se diluem. Um relatório de ciclo de vida bem-sucedido **reinicia** o registo de hooks, para que as duas camadas nunca reportem em duplicado. Os comandos de hooks só leem estado local e terminam sempre com `0`. @@ -73,7 +73,7 @@ O addon **oferece** caminhos de instalação; a skill Dailybot é dona do consen | **Atualizar skill existente** | `npx skills update dailybot` | | **OpenClaw** | `openclaw skills install dailybot` | | **Git clone** | `git clone https://github.com/DailybotHQ/agent-skill.git` + `./setup.sh` | -| **Dailybot CLI** (mínimo `>= 3.1.2`) | Instalada pela skill no primeiro uso via `shared/auth.md` verificado; ou `pip install 'dailybot-cli>=3.1.2'`, Homebrew, ou o instalador com checksum verificado em [cli.dailybot.com](https://cli.dailybot.com) | +| **Dailybot CLI** (mínimo `>= 3.7.0`) | Instalada pela skill no primeiro uso via `shared/auth.md` verificado; ou `pip install 'dailybot-cli>=3.7.0'`, Homebrew, ou o instalador com checksum verificado em [cli.dailybot.com](https://cli.dailybot.com) | Verifique versões: `dailybot --version` e `dailybot version --check`. Atualize: `dailybot upgrade`. @@ -82,13 +82,14 @@ Verifique versões: `dailybot --version` e `dailybot version --check`. Atualize: Este addon **nunca** pede email, OTP ou chaves API, e **nunca** armazena credenciais. A autenticação é gerida por [`shared/auth.md`](https://github.com/DailybotHQ/agent-skill/blob/main/skills/dailybot/shared/auth.md) da skill Dailybot: - `dailybot login` (OTP por email), ou -- `DAILYBOT_API_KEY` / `dailybot config key=...` +- `DAILYBOT_API_KEY` / `dailybot config key=...`, ou +- um ficheiro opcional de chaves por repositório `.dailybot/env.json`, ignorado pelo git (`dailybot env add/use`, CLI `>= 3.7.0`), para que um programador possa estar autenticado em orgs diferentes em repositórios diferentes. -Se a autenticação for recusada ou indisponível, o relatório é ignorado silenciosamente — o trabalho continua. +A resolução de autenticação é **Bearer-first**: um token de sessão tem prioridade, com uma nova tentativa transparente de Bearer→chave API em `401`/`403`, para que um token expirado nunca bloqueie uma chave válida. Se a autenticação for recusada ou indisponível, o relatório é ignorado silenciosamente — o trabalho continua. -## A skill emparelhada Dailybot — 13 capacidades (3.4.0) +## A skill emparelhada Dailybot — 14 capacidades (3.10.3) -Instalar a skill de agente Dailybot traz muito mais do que o addon DWP liga. O pacote oficial de skills (skill **3.4.0**, CLI **>= 3.1.2**, publicação atual **3.2.1**) expõe **13 sub-skills coordenadas**: +Instalar a skill de agente Dailybot traz muito mais do que o addon DWP liga. O pacote oficial de skills (skill **3.10.3**, base da CLI **>= 3.7.0**, publicação atual **3.7.3**) expõe **14 sub-skills coordenadas**: | Sub-skill | O que faz | |-----------|--------------| @@ -102,9 +103,10 @@ Instalar a skill de agente Dailybot traz muito mais do que o addon DWP liga. O p | **Check-ins** | Completar standups; **autorar** check-ins (agendamento, participantes, perguntas, lembretes, definições de IA) | | **Kudos** | Reconhecer colegas ou equipas inteiras; explorar feed de reconhecimento, feed da org, mural da fama | | **Equipas** | Listar equipas, inspecionar membros, resolver nomes para UUIDs; `me`, `org`, perfis de utilizador | -| **Formulários** | Listar, submeter, atualizar, transicionar formulários; **autorar** formulários (estados de workflow, permissões, ChatOps) | +| **Formulários** | Listar (agora **com âmbito de org** por omissão, com `--mine` e `--owner` para restringir), submeter, atualizar, transicionar formulários; **autorar** formulários (estados de workflow, permissões, ChatOps); paginação, pesquisa e filtros por data | | **Workflows** | Ler workflows da org (`workflow list` / `workflow get`; só leitura) | | **Canais de relatório** | Descobrir UUIDs de canal para formulários ou check-ins | +| **Chaves API por repositório** | Gerir `.dailybot/env.json` — um ficheiro opcional, ignorado pelo git, de chaves API + URLs por ambiente (`dailybot env add / use / show / list / remove / off / on`, CLI `>= 3.7.0`) | **O addon DWP liga apenas `report` à execução do plano.** Invoque a skill Dailybot diretamente para todo o resto — por exemplo, publicar um resumo de deploy em `#releases`, completar um standup ou pedir à IA Dailybot para resumir tendências de check-ins. diff --git a/src/content/kit/ru/dailybot.md b/src/content/kit/ru/dailybot.md index a6bb3a4..e897b1d 100644 --- a/src/content/kit/ru/dailybot.md +++ b/src/content/kit/ru/dailybot.md @@ -1,6 +1,6 @@ --- title: Dailybot -description: "Опциональный аддон DWP: подключение жизненного цикла плана к команде Dailybot, опциональное принудительное применение хуков и полный навык агента Dailybot 3.4.0 (чат, чек-ины, формы, Ask AI и др.)." +description: "Опциональный аддон DWP: подключение жизненного цикла плана к команде Dailybot, опциональное принудительное применение хуков и полный навык агента Dailybot 3.10.3 (чат, чек-ины, формы, Ask AI и др.)." kind: addon lang: ru order: 2 @@ -23,7 +23,7 @@ order: 2 ## Что подключает этот аддон (намеренно узкий дизайн) -Аддон DWP Dailybot **не** переизобретает Dailybot. Он подключает выполнение плана к поднавыку dailybot **`report`** и опционально коммитит harness-хуки. Всё остальное — установка, согласие, аутентификация, стиль написания — **отложено** до официального [навыка агента Dailybot](https://github.com/DailybotHQ/agent-skill) (сейчас **3.4.0**). +Аддон DWP Dailybot **не** переизобретает Dailybot. Он подключает выполнение плана к поднавыку dailybot **`report`** и опционально коммитит harness-хуки. Всё остальное — установка, согласие, аутентификация, стиль написания — **отложено** до официального [навыка агента Dailybot](https://github.com/DailybotHQ/agent-skill) (сейчас **3.10.3**). ### Четыре события жизненного цикла @@ -40,7 +40,7 @@ order: 2 ### Опциональное принудительное применение хуков -При `dailybot-cli >= 3.1.2` аддон **может** закоммитить harness-хуки на уровне репозитория (`dailybot hook session-start | activity | post-commit | stop | dismiss`), поддерживаемые локальной книгой учёта на репозиторий. Harness напоминает агенту в конце хода, когда пропущено событие жизненного цикла — критично для длинных безнадзорных сессий, где инструкции в промпте ослабевают. +При `dailybot-cli >= 3.7.0` аддон **может** закоммитить harness-хуки на уровне репозитория (`dailybot hook session-start | activity | post-commit | stop | dismiss`), поддерживаемые локальной книгой учёта на репозиторий. Harness напоминает агенту в конце хода, когда пропущено событие жизненного цикла — критично для длинных безнадзорных сессий, где инструкции в промпте ослабевают. Успешный отчёт жизненного цикла **сбрасывает** книгу хуков, поэтому два слоя никогда не дублируют отчёты. Команды хуков читают только локальное состояние и всегда завершаются с кодом `0`. @@ -73,7 +73,7 @@ order: 2 | **Обновление существующего навыка** | `npx skills update dailybot` | | **OpenClaw** | `openclaw skills install dailybot` | | **Git clone** | `git clone https://github.com/DailybotHQ/agent-skill.git` + `./setup.sh` | -| **Dailybot CLI** (минимум `>= 3.1.2`) | Устанавливается навыком при первом использовании через проверенный `shared/auth.md`; или `pip install 'dailybot-cli>=3.1.2'`, Homebrew, или установщик с проверкой контрольной суммы на [cli.dailybot.com](https://cli.dailybot.com) | +| **Dailybot CLI** (минимум `>= 3.7.0`) | Устанавливается навыком при первом использовании через проверенный `shared/auth.md`; или `pip install 'dailybot-cli>=3.7.0'`, Homebrew, или установщик с проверкой контрольной суммы на [cli.dailybot.com](https://cli.dailybot.com) | Проверка версий: `dailybot --version` и `dailybot version --check`. Обновление: `dailybot upgrade`. @@ -82,13 +82,14 @@ order: 2 Этот аддон **никогда** не запрашивает email, OTP или API-ключи и **никогда** не хранит учётные данные. Аутентификацией владеет [`shared/auth.md`](https://github.com/DailybotHQ/agent-skill/blob/main/skills/dailybot/shared/auth.md) навыка Dailybot: - `dailybot login` (email OTP), или -- `DAILYBOT_API_KEY` / `dailybot config key=...` +- `DAILYBOT_API_KEY` / `dailybot config key=...`, или +- опциональный, gitignore-нутый файл ключей на репозиторий `.dailybot/env.json` (`dailybot env add/use`, CLI `>= 3.7.0`), чтобы разработчик мог быть авторизован в разных организациях в разных репозиториях. -Если аутентификация отклонена или недоступна, отчётность пропускается молча — работа продолжается. +Разрешение аутентификации работает по принципу **Bearer-first**: токен сессии имеет приоритет, с прозрачным повтором Bearer→API-ключ при `401`/`403`, чтобы устаревший токен никогда не блокировал валидный ключ. Если аутентификация отклонена или недоступна, отчётность пропускается молча — работа продолжается. -## Парный навык Dailybot — 13 возможностей (3.4.0) +## Парный навык Dailybot — 14 возможностей (3.10.3) -Установка навыка агента Dailybot даёт гораздо больше, чем подключает аддон DWP. Официальный пакет навыков (навык **3.4.0**, CLI **>= 3.1.2**, текущая публикация **3.2.1**) раскрывает **13 согласованных поднавыков**: +Установка навыка агента Dailybot даёт гораздо больше, чем подключает аддон DWP. Официальный пакет навыков (навык **3.10.3**, базовый CLI **>= 3.7.0**, текущая публикация **3.7.3**) раскрывает **14 согласованных поднавыков**: | Поднавык | Назначение | |----------|------------| @@ -102,9 +103,10 @@ order: 2 | **Check-ins** | Завершение стендапов; **создание** чек-инов (расписание, участники, вопросы, напоминания, настройки AI) | | **Kudos** | Признание товарищей или целых команд; просмотр ленты признаний, организационной ленты, зала славы | | **Teams** | Список команд, просмотр участников, разрешение имён в UUID; `me`, `org`, профили пользователей | -| **Forms** | Список, отправка, обновление, переход форм; **создание** форм (состояния workflow, разрешения, ChatOps) | +| **Forms** | Список (теперь **в области организации** по умолчанию, с `--mine` и `--owner` для сужения), отправка, обновление, переход форм; **создание** форм (состояния workflow, разрешения, ChatOps); пагинация, поиск и фильтры по датам | | **Workflows** | Чтение организационных workflow (`workflow list` / `workflow get`; только чтение) | | **Report channels** | Обнаружение UUID каналов для форм или чек-инов | +| **API-ключи на репозиторий** | Управление `.dailybot/env.json` — опциональным, gitignore-нутым файлом API-ключей + URL по окружениям (`dailybot env add / use / show / list / remove / off / on`, CLI `>= 3.7.0`) | **Аддон DWP подключает только `report` к выполнению плана.** Вызывайте навык Dailybot напрямую для всего остального — например, опубликовать сводку деплоя в `#releases`, завершить стендап или попросить AI Dailybot обобщить тренды чек-инов. diff --git a/src/content/kit/th/dailybot.md b/src/content/kit/th/dailybot.md index 925914e..b48c78d 100644 --- a/src/content/kit/th/dailybot.md +++ b/src/content/kit/th/dailybot.md @@ -1,6 +1,6 @@ --- title: Dailybot -description: "DWP addon แบบ opt-in: เชื่อม lifecycle ของแผนกับทีม Dailybot การบังคับใช้ hook แบบเลือกได้ และ Dailybot agent skill 3.4.0 ครบชุด (แชท check-in ฟอร์ม Ask AI และอื่นๆ)" +description: "DWP addon แบบ opt-in: เชื่อม lifecycle ของแผนกับทีม Dailybot การบังคับใช้ hook แบบเลือกได้ และ Dailybot agent skill 3.10.3 ครบชุด (แชท check-in ฟอร์ม Ask AI และอื่นๆ)" kind: addon lang: th order: 2 @@ -23,7 +23,7 @@ order: 2 ## สิ่งที่ addon นี้เชื่อม (ออกแบบให้แคบโดยเจตนา) -DWP Dailybot addon **ไม่สร้าง** Dailybot ใหม่ มันเชื่อมการดำเนินแผนกับ sub-skill dailybot **`report`** และอาจ commit hook ของ harness ส่วนอื่น — การติดตั้ง ความยินยอม authentication สไตล์การเขียน — **มอบหมาย** ให้ [Dailybot agent skill](https://github.com/DailybotHQ/agent-skill) อย่างเป็นทางการ (ปัจจุบัน **3.4.0**) +DWP Dailybot addon **ไม่สร้าง** Dailybot ใหม่ มันเชื่อมการดำเนินแผนกับ sub-skill dailybot **`report`** และอาจ commit hook ของ harness ส่วนอื่น — การติดตั้ง ความยินยอม authentication สไตล์การเขียน — **มอบหมาย** ให้ [Dailybot agent skill](https://github.com/DailybotHQ/agent-skill) อย่างเป็นทางการ (ปัจจุบัน **3.10.3**) ### สี่เหตุการณ์ lifecycle @@ -40,7 +40,7 @@ Payload มาจากชั้น state ของแผน (`state.json`) เ ### การบังคับใช้ hook แบบเลือกได้ -ด้วย `dailybot-cli >= 3.1.2` addon **อาจ** commit hook ของ harness ระดับรีโพ (`dailybot hook session-start | activity | post-commit | stop | dismiss`) สนับสนุนโดย ledger ต่อรีโพในเครื่อง Harness เตือนเอเจนต์ปลายเทิร์นเมื่อพลาดเหตุการณ์ lifecycle — สำคัญสำหรับเซสชันยาวที่ไม่มีคนดูแล ซึ่งคำสั่งใน prompt จางลง +ด้วย `dailybot-cli >= 3.7.0` addon **อาจ** commit hook ของ harness ระดับรีโพ (`dailybot hook session-start | activity | post-commit | stop | dismiss`) สนับสนุนโดย ledger ต่อรีโพในเครื่อง Harness เตือนเอเจนต์ปลายเทิร์นเมื่อพลาดเหตุการณ์ lifecycle — สำคัญสำหรับเซสชันยาวที่ไม่มีคนดูแล ซึ่งคำสั่งใน prompt จางลง รายงาน lifecycle สำเร็จ **รีเซ็ต** ledger ของ hook ดังนั้นสองชั้นไม่รายงานซ้ำ คำสั่ง hook อ่านเฉพาะ state ในเครื่องและจบด้วย `0` เสมอ @@ -73,7 +73,7 @@ Addon **เสนอ** เส้นทางติดตั้ง skill Dailybot | **อัปเดต skill ที่มี** | `npx skills update dailybot` | | **OpenClaw** | `openclaw skills install dailybot` | | **Git clone** | `git clone https://github.com/DailybotHQ/agent-skill.git` + `./setup.sh` | -| **Dailybot CLI** (ขั้นต่ำ `>= 3.1.2`) | ติดตั้งโดย skill ครั้งแรกผ่าน `shared/auth.md`; หรือ `pip install 'dailybot-cli>=3.1.2'` Homebrew หรือ installer ที่ตรวจ checksum ที่ [cli.dailybot.com](https://cli.dailybot.com) | +| **Dailybot CLI** (ขั้นต่ำ `>= 3.7.0`) | ติดตั้งโดย skill ครั้งแรกผ่าน `shared/auth.md`; หรือ `pip install 'dailybot-cli>=3.7.0'` Homebrew หรือ installer ที่ตรวจ checksum ที่ [cli.dailybot.com](https://cli.dailybot.com) | ตรวจเวอร์ชัน: `dailybot --version` และ `dailybot version --check` อัปเกรด: `dailybot upgrade` @@ -82,13 +82,14 @@ Addon **เสนอ** เส้นทางติดตั้ง skill Dailybot Addon นี้ **ไม่** ถาม email OTP หรือ API keys และ **ไม่** เก็บ credentials Authentication เป็นของ skill Dailybot [`shared/auth.md`](https://github.com/DailybotHQ/agent-skill/blob/main/skills/dailybot/shared/auth.md): - `dailybot login` (email OTP) หรือ -- `DAILYBOT_API_KEY` / `dailybot config key=...` +- `DAILYBOT_API_KEY` / `dailybot config key=...` หรือ +- ไฟล์คีย์ต่อรีโพ `.dailybot/env.json` แบบ opt-in ที่ถูก gitignore (`dailybot env add/use`, CLI `>= 3.7.0`) เพื่อให้นักพัฒนาลงชื่อเข้าใช้ org ต่างกันในรีโพต่างกันได้ -หาก auth ถูกปฏิเสธหรือไม่พร้อม การรายงานจะข้ามเงียบๆ — งานดำเนินต่อ +การแก้ปัญหา auth เป็นแบบ **Bearer-first**: session token มีความสำคัญก่อน พร้อม retry แบบโปร่งใสจาก Bearer→API-key เมื่อเจอ `401`/`403` เพื่อไม่ให้ token ที่หมดอายุบล็อกคีย์ที่ใช้ได้ หาก auth ถูกปฏิเสธหรือไม่พร้อม การรายงานจะข้ามเงียบๆ — งานดำเนินต่อ -## Dailybot skill คู่กัน — 13 ความสามารถ (3.4.0) +## Dailybot skill คู่กัน — 14 ความสามารถ (3.10.3) -การติดตั้ง Dailybot agent skill ได้มากกว่าที่ DWP addon เชื่อม ชุด skill อย่างเป็นทางการ (skill **3.4.0** CLI **>= 3.1.2** publish ปัจจุบัน **3.2.1**) เปิด **13 sub-skill ที่ประสานกัน**: +การติดตั้ง Dailybot agent skill ได้มากกว่าที่ DWP addon เชื่อม ชุด skill อย่างเป็นทางการ (skill **3.10.3** CLI baseline **>= 3.7.0** publish ปัจจุบัน **3.7.3**) เปิด **14 sub-skill ที่ประสานกัน**: | Sub-skill | ทำอะไร | |-----------|--------------| @@ -102,9 +103,10 @@ Addon นี้ **ไม่** ถาม email OTP หรือ API keys แล | **Check-ins** | ทำ standup เสร็จ; **เขียน** check-in (ตาราง ผู้เข้าร่วม คำถาม การเตือน การตั้งค่า AI) | | **Kudos** | ยกย่องเพื่อนร่วมทีมหรือทั้งทีม; เรียกดู recognition feed org feed wall of fame | | **Teams** | แสดงรายการทีม ตรวจสมาชิก แปลงชื่อเป็น UUID; `me`, `org`, โปรไฟล์ผู้ใช้ | -| **Forms** | แสดงรายการ submit อัปเดต transition ฟอร์ม; **เขียน** ฟอร์ม (สถานะ workflow สิทธิ์ ChatOps) | +| **Forms** | แสดงรายการ (ตอนนี้ **org-scoped** โดยค่าเริ่มต้น พร้อม `--mine` และ `--owner` เพื่อจำกัด) submit อัปเดต transition ฟอร์ม; **เขียน** ฟอร์ม (สถานะ workflow สิทธิ์ ChatOps); pagination การค้นหา และตัวกรองวันที่ | | **Workflows** | อ่าน org workflows (`workflow list` / `workflow get`; read-only) | | **Report channels** | ค้นหา UUID ช่องสำหรับฟอร์มหรือ check-in | +| **Per-repo API keys** | จัดการ `.dailybot/env.json` — ไฟล์ opt-in ที่ถูก gitignore ของ API key + URL ต่อ environment (`dailybot env add / use / show / list / remove / off / on`, CLI `>= 3.7.0`) | **DWP addon เชื่อมเฉพาะ `report` เข้ากับการดำเนินแผน** เรียก skill Dailybot โดยตรงสำหรับอย่างอื่น — เช่น โพสต์สรุป deploy ไป `#releases` ทำ standup หรือขอให้ AI Dailybot สรุปแนวโน้ม check-in diff --git a/src/content/kit/tr/dailybot.md b/src/content/kit/tr/dailybot.md index d909125..3462e85 100644 --- a/src/content/kit/tr/dailybot.md +++ b/src/content/kit/tr/dailybot.md @@ -1,6 +1,6 @@ --- title: Dailybot -description: "Opt-in DWP eklentisi: plan yaşam döngüsünü bir Dailybot ekibine bağlar, isteğe bağlı hook zorlaması ve tam Dailybot agent skill 3.4.0 (sohbet, check-in'ler, formlar, ask AI ve daha fazlası)." +description: "Opt-in DWP eklentisi: plan yaşam döngüsünü bir Dailybot ekibine bağlar, isteğe bağlı hook zorlaması ve tam Dailybot agent skill 3.10.3 (sohbet, check-in'ler, formlar, ask AI ve daha fazlası)." kind: addon lang: tr order: 2 @@ -23,7 +23,7 @@ Temel Deep Work Plan metodolojisinin Dailybot'a **sıfır** bağımlılığı va ## Bu eklentinin bağladıkları (kasıtlı olarak dar) -DWP Dailybot eklentisi Dailybot'u **yeniden icat etmez**. Plan yürütmesini dailybot **`report`** alt-skill'ine bağlar ve isteğe bağlı olarak harness hook'larını commit'ler. Geri kalan her şey — kurulum, onay, kimlik doğrulama, yazım stili — resmi [Dailybot agent skill](https://github.com/DailybotHQ/agent-skill)'e (şu an **3.4.0**) **ertelenir**. +DWP Dailybot eklentisi Dailybot'u **yeniden icat etmez**. Plan yürütmesini dailybot **`report`** alt-skill'ine bağlar ve isteğe bağlı olarak harness hook'larını commit'ler. Geri kalan her şey — kurulum, onay, kimlik doğrulama, yazım stili — resmi [Dailybot agent skill](https://github.com/DailybotHQ/agent-skill)'e (şu an **3.10.3**) **ertelenir**. ### Dört yaşam döngüsü olayı @@ -40,7 +40,7 @@ Payload'lar mevcut olduğunda planın durum katmanından (`state.json`) türetil ### İsteğe bağlı hook zorlaması -`dailybot-cli >= 3.1.2` ile eklenti depo düzeyinde harness hook'larını (`dailybot hook session-start | activity | post-commit | stop | dismiss`) yerel depo başına ledger ile destekleyerek **commit edebilir**. Harness, bir yaşam döngüsü olayı kaçırıldığında tur sonunda agent'ı hatırlatır — prompt talimatlarının zayıfladığı uzun gözetimsiz oturumlar için kritik. +`dailybot-cli >= 3.7.0` ile eklenti depo düzeyinde harness hook'larını (`dailybot hook session-start | activity | post-commit | stop | dismiss`) yerel depo başına ledger ile destekleyerek **commit edebilir**. Harness, bir yaşam döngüsü olayı kaçırıldığında tur sonunda agent'ı hatırlatır — prompt talimatlarının zayıfladığı uzun gözetimsiz oturumlar için kritik. Başarılı bir yaşam döngüsü raporu hook ledger'ını **sıfırlar**, böylece iki katman asla çift rapor vermez. Hook komutları yalnızca yerel durumu okur ve her zaman `0` ile çıkar. @@ -73,7 +73,7 @@ Eklenti kurulum yollarını **sunar**; Dailybot skill onay ve doğrulamayı yön | **Mevcut skill'i güncelle** | `npx skills update dailybot` | | **OpenClaw** | `openclaw skills install dailybot` | | **Git clone** | `git clone https://github.com/DailybotHQ/agent-skill.git` + `./setup.sh` | -| **Dailybot CLI** (minimum `>= 3.1.2`) | İlk kullanımda skill tarafından doğrulanmış `shared/auth.md` ile kurulur; veya `pip install 'dailybot-cli>=3.1.2'`, Homebrew veya [cli.dailybot.com](https://cli.dailybot.com)'daki checksum doğrulanmış yükleyici | +| **Dailybot CLI** (minimum `>= 3.7.0`) | İlk kullanımda skill tarafından doğrulanmış `shared/auth.md` ile kurulur; veya `pip install 'dailybot-cli>=3.7.0'`, Homebrew veya [cli.dailybot.com](https://cli.dailybot.com)'daki checksum doğrulanmış yükleyici | Sürümleri kontrol et: `dailybot --version` ve `dailybot version --check`. Yükseltme: `dailybot upgrade`. @@ -82,13 +82,14 @@ Sürümleri kontrol et: `dailybot --version` ve `dailybot version --check`. Yük Bu eklenti **asla** e-posta, OTP veya API anahtarı istemez ve kimlik bilgilerini **saklamaz**. Kimlik doğrulama Dailybot skill'in [`shared/auth.md`](https://github.com/DailybotHQ/agent-skill/blob/main/skills/dailybot/shared/auth.md) dosyasına aittir: - `dailybot login` (e-posta OTP) veya -- `DAILYBOT_API_KEY` / `dailybot config key=...` +- `DAILYBOT_API_KEY` / `dailybot config key=...` veya +- opt-in, gitignore'lanmış bir `.dailybot/env.json` depo başına anahtar dosyası (`dailybot env add/use`, CLI `>= 3.7.0`); böylece bir geliştirici farklı depolarda farklı org'larda oturum açmış olabilir. -Kimlik doğrulama reddedilirse veya kullanılamazsa raporlama sessizce atlanır — çalışma devam eder. +Kimlik doğrulama çözümü **Bearer-first**'tür: bir oturum token'ı önceliklidir ve `401`/`403` durumunda şeffaf bir Bearer→API-anahtarı yeniden denemesiyle eski bir token asla geçerli bir anahtarı engellemez. Kimlik doğrulama reddedilirse veya kullanılamazsa raporlama sessizce atlanır — çalışma devam eder. -## Eşleşen Dailybot skill — 13 yetenek (3.4.0) +## Eşleşen Dailybot skill — 14 yetenek (3.10.3) -Dailybot agent skill kurmak, DWP eklentisinin bağladığından çok daha fazlasını getirir. Resmi skill paketi (skill **3.4.0**, CLI **>= 3.1.2**, güncel yayın **3.2.1**) **13 koordineli alt-skill** sunar: +Dailybot agent skill kurmak, DWP eklentisinin bağladığından çok daha fazlasını getirir. Resmi skill paketi (skill **3.10.3**, CLI baseline **>= 3.7.0**, güncel yayın **3.7.3**) **14 koordineli alt-skill** sunar: | Alt-skill | Ne yapar | |-----------|--------------| @@ -102,9 +103,10 @@ Dailybot agent skill kurmak, DWP eklentisinin bağladığından çok daha fazlas | **Check-ins** | Standup'ları tamamla; check-in'leri **author** et (zamanlama, katılımcılar, sorular, hatırlatıcılar, AI ayarları) | | **Kudos** | Ekip arkadaşlarını veya tüm ekipleri tanı; tanınma akışı, org akışı, wall of fame'e göz at | | **Teams** | Ekipleri listele, üyeleri incele, adları UUID'lere çöz; `me`, `org`, kullanıcı profilleri | -| **Forms** | Formları listele, gönder, güncelle, geçiş yap; formları **author** et (workflow durumları, izinler, ChatOps) | +| **Forms** | Listele (artık varsayılan olarak **org kapsamlı**, daraltmak için `--mine` ve `--owner`), gönder, güncelle, geçiş yap; formları **author** et (workflow durumları, izinler, ChatOps); sayfalama, arama ve tarih filtreleri | | **Workflows** | Org workflow'larını oku (`workflow list` / `workflow get`; salt okunur) | | **Report channels** | Formlar veya check-in'ler için kanal UUID'lerini keşfet | +| **Per-repo API keys** | `.dailybot/env.json`'ı yönet — ortam başına API anahtarları + URL'lerden oluşan opt-in, gitignore'lanmış bir dosya (`dailybot env add / use / show / list / remove / off / on`, CLI `>= 3.7.0`) | **DWP eklentisi yalnızca `report`'u plan yürütmesine bağlar.** Geri kalan her şey için Dailybot skill'i doğrudan çağırın — örneğin `#releases`'e deploy özeti gönderin, standup tamamlayın veya Dailybot AI'dan check-in trendlerini özetlemesini isteyin. diff --git a/src/content/kit/uk/dailybot.md b/src/content/kit/uk/dailybot.md index 696c0a6..2e9d49e 100644 --- a/src/content/kit/uk/dailybot.md +++ b/src/content/kit/uk/dailybot.md @@ -1,6 +1,6 @@ --- title: Dailybot -description: "Опційний DWP-аддон: підключення життєвого циклу плану до команди Dailybot, опційне примусове виконання хуків і повний агентський скіл Dailybot 3.4.0 (чат, чек-іни, форми, Ask AI тощо)." +description: "Опційний DWP-аддон: підключення життєвого циклу плану до команди Dailybot, опційне примусове виконання хуків і повний агентський скіл Dailybot 3.10.3 (чат, чек-іни, форми, Ask AI тощо)." kind: addon lang: uk order: 2 @@ -23,7 +23,7 @@ order: 2 ## Що підключає цей аддон (навмисно вузько) -DWP-аддон Dailybot **не перевинаходжує** Dailybot. Він підключає виконання плану до sub-skill dailybot **`report`** і опційно комітить хуки harness. Усе інше — встановлення, згода, автентифікація, стиль написання — **делегується** офіційному [агентському скілу Dailybot](https://github.com/DailybotHQ/agent-skill) (зараз **3.4.0**). +DWP-аддон Dailybot **не перевинаходжує** Dailybot. Він підключає виконання плану до sub-skill dailybot **`report`** і опційно комітить хуки harness. Усе інше — встановлення, згода, автентифікація, стиль написання — **делегується** офіційному [агентському скілу Dailybot](https://github.com/DailybotHQ/agent-skill) (зараз **3.10.3**). ### Чотири події життєвого циклу @@ -40,7 +40,7 @@ Payload походять із шару стану плану (`state.json`), я ### Опційне примусове виконання хуків -З `dailybot-cli >= 3.1.2` аддон **може** закомітити хуки harness на рівні репозиторію (`dailybot hook session-start | activity | post-commit | stop | dismiss`), підтримані локальним реєстром per-repo. Harness нагадує агенту в кінці ходу, коли подію життєвого циклу пропущено — критично для довгих незахищених сесій, де інструкції промпту слабшають. +З `dailybot-cli >= 3.7.0` аддон **може** закомітити хуки harness на рівні репозиторію (`dailybot hook session-start | activity | post-commit | stop | dismiss`), підтримані локальним реєстром per-repo. Harness нагадує агенту в кінці ходу, коли подію життєвого циклу пропущено — критично для довгих незахищених сесій, де інструкції промпту слабшають. Успішний звіт життєвого циклу **скидає** реєстр хуків, тож два шари ніколи не дублюють звіти. Команди хуків читають лише локальний стан і завжди завершуються кодом `0`. @@ -73,7 +73,7 @@ Payload походять із шару стану плану (`state.json`), я | **Оновлення наявного скілу** | `npx skills update dailybot` | | **OpenClaw** | `openclaw skills install dailybot` | | **Git clone** | `git clone https://github.com/DailybotHQ/agent-skill.git` + `./setup.sh` | -| **Dailybot CLI** (мінімум `>= 3.1.2`) | Встановлюється скілом при першому використанні через `shared/auth.md`; або `pip install 'dailybot-cli>=3.1.2'`, Homebrew чи installer з перевіркою checksum на [cli.dailybot.com](https://cli.dailybot.com) | +| **Dailybot CLI** (мінімум `>= 3.7.0`) | Встановлюється скілом при першому використанні через `shared/auth.md`; або `pip install 'dailybot-cli>=3.7.0'`, Homebrew чи installer з перевіркою checksum на [cli.dailybot.com](https://cli.dailybot.com) | Перевірка версій: `dailybot --version` і `dailybot version --check`. Оновлення: `dailybot upgrade`. @@ -82,13 +82,14 @@ Payload походять із шару стану плану (`state.json`), я Цей аддон **ніколи** не запитує email, OTP чи API keys і **ніколи** не зберігає облікові дані. Автентифікацією володіє скіл Dailybot [`shared/auth.md`](https://github.com/DailybotHQ/agent-skill/blob/main/skills/dailybot/shared/auth.md): - `dailybot login` (email OTP), або -- `DAILYBOT_API_KEY` / `dailybot config key=...` +- `DAILYBOT_API_KEY` / `dailybot config key=...`, або +- опційний, доданий до gitignore файл ключів per-repo `.dailybot/env.json` (`dailybot env add/use`, CLI `>= 3.7.0`), щоб розробник міг бути залогінений у різні організації в різних репозиторіях. -Якщо auth відхилено або недоступно, звітування тихо пропускається — робота триває. +Розв'язання auth — **Bearer-first**: токен сесії має пріоритет, із прозорим повтором Bearer→API-key на `401`/`403`, тож застарілий токен ніколи не блокує дійсний ключ. Якщо auth відхилено або недоступно, звітування тихо пропускається — робота триває. -## Парний скіл Dailybot — 13 можливостей (3.4.0) +## Парний скіл Dailybot — 14 можливостей (3.10.3) -Встановлення агентського скілу Dailybot дає набагато більше, ніж підключає DWP-аддон. Офіційний пакет скілів (скіл **3.4.0**, CLI **>= 3.1.2**, поточна публікація **3.2.1**) надає **13 координованих sub-skill**: +Встановлення агентського скілу Dailybot дає набагато більше, ніж підключає DWP-аддон. Офіційний пакет скілів (скіл **3.10.3**, базовий CLI **>= 3.7.0**, поточна публікація **3.7.3**) надає **14 координованих sub-skill**: | Sub-skill | Що робить | |-----------|--------------| @@ -102,9 +103,10 @@ Payload походять із шару стану плану (`state.json`), я | **Check-ins** | Завершення standup; **авторство** check-in (розклад, учасники, питання, нагадування, налаштування AI) | | **Kudos** | Визнання колег або цілих команд; перегляд recognition feed, org feed, wall of fame | | **Teams** | Список команд, перегляд учасників, resolve імен у UUID; `me`, `org`, профілі користувачів | -| **Forms** | Список, submit, update, transition форм; **авторство** форм (стани workflow, дозволи, ChatOps) | +| **Forms** | Список (тепер **org-scoped** за замовчуванням, з `--mine` і `--owner` для звуження), submit, update, transition форм; **авторство** форм (стани workflow, дозволи, ChatOps); пагінація, пошук і фільтри за датою | | **Workflows** | Читання org workflows (`workflow list` / `workflow get`; лише read-only) | | **Report channels** | Виявлення UUID каналів для форм або check-in | +| **Per-repo API keys** | Керування `.dailybot/env.json` — опційним, доданим до gitignore файлом API keys + URL на кожне середовище (`dailybot env add / use / show / list / remove / off / on`, CLI `>= 3.7.0`) | **DWP-аддон підключає лише `report` до виконання плану.** Викликайте скіл Dailybot безпосередньо для всього іншого — наприклад, опублікуйте підсумок деплою в `#releases`, завершіть standup або попросіть AI Dailybot підсумувати тренди check-in. diff --git a/src/content/kit/vi/dailybot.md b/src/content/kit/vi/dailybot.md index 074bab4..0f8a2e4 100644 --- a/src/content/kit/vi/dailybot.md +++ b/src/content/kit/vi/dailybot.md @@ -1,6 +1,6 @@ --- title: Dailybot -description: "Addon DWP opt-in: kết nối vòng đời kế hoạch với nhóm Dailybot, thực thi hook tùy chọn và skill agent Dailybot đầy đủ 3.4.0 (chat, check-in, biểu mẫu, ask AI và hơn thế nữa)." +description: "Addon DWP opt-in: kết nối vòng đời kế hoạch với nhóm Dailybot, thực thi hook tùy chọn và skill agent Dailybot đầy đủ 3.10.3 (chat, check-in, biểu mẫu, ask AI và hơn thế nữa)." kind: addon lang: vi order: 2 @@ -23,7 +23,7 @@ Phương pháp Deep Work Plan cốt lõi có **không** phụ thuộc Dailybot. ## Addon này kết nối gì (cố ý hẹp) -Addon DWP Dailybot **không** tái phát minh Dailybot. Nó kết nối thực thi kế hoạch với sub-skill dailybot **`report`** và tùy chọn commit hook harness. Mọi thứ khác — cài đặt, đồng ý, xác thực, phong cách viết — được **hoãn** sang [skill agent Dailybot](https://github.com/DailybotHQ/agent-skill) chính thức (hiện tại **3.4.0**). +Addon DWP Dailybot **không** tái phát minh Dailybot. Nó kết nối thực thi kế hoạch với sub-skill dailybot **`report`** và tùy chọn commit hook harness. Mọi thứ khác — cài đặt, đồng ý, xác thực, phong cách viết — được **hoãn** sang [skill agent Dailybot](https://github.com/DailybotHQ/agent-skill) chính thức (hiện tại **3.10.3**). ### Bốn sự kiện vòng đời @@ -40,7 +40,7 @@ Payload lấy từ lớp trạng thái kế hoạch (`state.json`) khi có: `com ### Thực thi hook tùy chọn -Với `dailybot-cli >= 3.1.2`, addon **có thể** commit hook harness cấp repo (`dailybot hook session-start | activity | post-commit | stop | dismiss`) được hỗ trợ bởi sổ cái cục bộ theo repo. Harness nhắc agent ở cuối lượt khi sự kiện vòng đời bị bỏ lỡ — quan trọng cho phiên dài không giám sát mà hướng dẫn prompt suy yếu. +Với `dailybot-cli >= 3.7.0`, addon **có thể** commit hook harness cấp repo (`dailybot hook session-start | activity | post-commit | stop | dismiss`) được hỗ trợ bởi sổ cái cục bộ theo repo. Harness nhắc agent ở cuối lượt khi sự kiện vòng đời bị bỏ lỡ — quan trọng cho phiên dài không giám sát mà hướng dẫn prompt suy yếu. Báo cáo vòng đời thành công **đặt lại** sổ cái hook, nên hai lớp không bao giờ báo cáo trùng. Lệnh hook chỉ đọc trạng thái cục bộ và luôn thoát `0`. @@ -73,7 +73,7 @@ Addon **đề xuất** đường cài đặt; skill Dailybot sở hữu đồng | **Cập nhật skill hiện có** | `npx skills update dailybot` | | **OpenClaw** | `openclaw skills install dailybot` | | **Git clone** | `git clone https://github.com/DailybotHQ/agent-skill.git` + `./setup.sh` | -| **Dailybot CLI** (tối thiểu `>= 3.1.2`) | Skill cài ở lần dùng đầu qua `shared/auth.md` đã xác minh; hoặc `pip install 'dailybot-cli>=3.1.2'`, Homebrew hoặc trình cài đã xác minh checksum tại [cli.dailybot.com](https://cli.dailybot.com) | +| **Dailybot CLI** (tối thiểu `>= 3.7.0`) | Skill cài ở lần dùng đầu qua `shared/auth.md` đã xác minh; hoặc `pip install 'dailybot-cli>=3.7.0'`, Homebrew hoặc trình cài đã xác minh checksum tại [cli.dailybot.com](https://cli.dailybot.com) | Kiểm tra phiên bản: `dailybot --version` và `dailybot version --check`. Nâng cấp: `dailybot upgrade`. @@ -82,13 +82,14 @@ Kiểm tra phiên bản: `dailybot --version` và `dailybot version --check`. N Addon này **không bao giờ** nhắc email, OTP hay API key và **không bao giờ** lưu thông tin xác thực. Xác thực thuộc về [`shared/auth.md`](https://github.com/DailybotHQ/agent-skill/blob/main/skills/dailybot/shared/auth.md) của skill Dailybot: - `dailybot login` (email OTP), hoặc -- `DAILYBOT_API_KEY` / `dailybot config key=...` +- `DAILYBOT_API_KEY` / `dailybot config key=...`, hoặc +- một file khóa theo repo `.dailybot/env.json` opt-in, được gitignore (`dailybot env add/use`, CLI `>= 3.7.0`) để một nhà phát triển có thể đăng nhập vào các tổ chức khác nhau trong các repo khác nhau. -Nếu xác thực bị từ chối hoặc không có, báo cáo bị bỏ qua im lặng — công việc tiếp tục. +Phân giải xác thực theo **Bearer-first**: token phiên được ưu tiên, với việc thử lại Bearer→API-key minh bạch khi gặp `401`/`403` nên token cũ không bao giờ chặn một khóa hợp lệ. Nếu xác thực bị từ chối hoặc không có, báo cáo bị bỏ qua im lặng — công việc tiếp tục. -## Skill Dailybot đi kèm — 13 khả năng (3.4.0) +## Skill Dailybot đi kèm — 14 khả năng (3.10.3) -Cài skill agent Dailybot mang lại nhiều hơn nhiều so với addon DWP kết nối. Gói skill chính thức (skill **3.4.0**, CLI **>= 3.1.2**, bản publish hiện tại **3.2.1**) mở **13 sub-skill phối hợp**: +Cài skill agent Dailybot mang lại nhiều hơn nhiều so với addon DWP kết nối. Gói skill chính thức (skill **3.10.3**, CLI cơ sở **>= 3.7.0**, bản publish hiện tại **3.7.3**) mở **14 sub-skill phối hợp**: | Sub-skill | Chức năng | |-----------|--------------| @@ -102,9 +103,10 @@ Cài skill agent Dailybot mang lại nhiều hơn nhiều so với addon DWP k | **Check-ins** | Hoàn thành standup; **author** check-in (lịch, người tham gia, câu hỏi, nhắc nhở, cài đặt AI) | | **Kudos** | Ghi nhận đồng đội hoặc cả nhóm; duyệt feed ghi nhận, feed org, wall of fame | | **Teams** | Liệt kê nhóm, xem thành viên, phân giải tên thành UUID; `me`, `org`, hồ sơ người dùng | -| **Forms** | Liệt kê, gửi, cập nhật, chuyển trạng thái biểu mẫu; **author** biểu mẫu (trạng thái workflow, quyền, ChatOps) | +| **Forms** | Liệt kê (nay **theo phạm vi org** mặc định, với `--mine` và `--owner` để thu hẹp), gửi, cập nhật, chuyển trạng thái biểu mẫu; **author** biểu mẫu (trạng thái workflow, quyền, ChatOps); phân trang, tìm kiếm và lọc theo ngày | | **Workflows** | Đọc workflow org (`workflow list` / `workflow get`; chỉ đọc) | | **Report channels** | Khám phá UUID kênh cho biểu mẫu hoặc check-in | +| **Per-repo API keys** | Quản lý `.dailybot/env.json` — một file opt-in, được gitignore chứa API key + URL theo môi trường (`dailybot env add / use / show / list / remove / off / on`, CLI `>= 3.7.0`) | **Addon DWP chỉ kết nối `report` vào thực thi kế hoạch.** Gọi skill Dailybot trực tiếp cho mọi thứ khác — ví dụ đăng tóm tắt deploy lên `#releases`, hoàn thành standup hoặc nhờ AI Dailybot tóm tắt xu hướng check-in. diff --git a/src/content/kit/zh/dailybot.md b/src/content/kit/zh/dailybot.md index a3282cc..56f37f8 100644 --- a/src/content/kit/zh/dailybot.md +++ b/src/content/kit/zh/dailybot.md @@ -1,6 +1,6 @@ --- title: Dailybot -description: "可选 DWP 附加组件：将计划生命周期连接到 Dailybot 团队，可选钩子强制层，以及完整的 Dailybot 代理技能 3.4.0（聊天、签到、表单、Ask AI 等）。" +description: "可选 DWP 附加组件：将计划生命周期连接到 Dailybot 团队，可选钩子强制层，以及完整的 Dailybot 代理技能 3.10.3（聊天、签到、表单、Ask AI 等）。" kind: addon lang: zh order: 2 @@ -23,7 +23,7 @@ order: 2 ## 此附加组件接入的内容（刻意保持精简） -DWP Dailybot 附加组件**不会**重新发明 Dailybot。它将计划执行连接到 dailybot **`report`** 子技能，并可选择提交 harness 钩子。其余一切——安装、同意、认证、书写风格——均**延后**至官方 [Dailybot 代理技能](https://github.com/DailybotHQ/agent-skill)（当前 **3.4.0**）。 +DWP Dailybot 附加组件**不会**重新发明 Dailybot。它将计划执行连接到 dailybot **`report`** 子技能，并可选择提交 harness 钩子。其余一切——安装、同意、认证、书写风格——均**延后**至官方 [Dailybot 代理技能](https://github.com/DailybotHQ/agent-skill)（当前 **3.10.3**）。 ### 四个生命周期事件 @@ -40,7 +40,7 @@ DWP Dailybot 附加组件**不会**重新发明 Dailybot。它将计划执行连 ### 可选钩子强制层 -使用 `dailybot-cli >= 3.1.2` 时，此附加组件**可以**提交仓库级 harness 钩子（`dailybot hook session-start | activity | post-commit | stop | dismiss`），由本地每仓库台账支撑。当遗漏生命周期事件时，harness 在回合结束时提醒代理——对提示词指令逐渐失效的长时间无人值守会话至关重要。 +使用 `dailybot-cli >= 3.7.0` 时，此附加组件**可以**提交仓库级 harness 钩子（`dailybot hook session-start | activity | post-commit | stop | dismiss`），由本地每仓库台账支撑。当遗漏生命周期事件时，harness 在回合结束时提醒代理——对提示词指令逐渐失效的长时间无人值守会话至关重要。 成功的生命周期报告会**重置**钩子台账，因此两层机制不会重复报告。钩子命令仅读取本地状态并始终以 `0` 退出。 @@ -73,7 +73,7 @@ DWP Dailybot 附加组件**不会**重新发明 Dailybot。它将计划执行连 | **更新现有技能** | `npx skills update dailybot` | | **OpenClaw** | `openclaw skills install dailybot` | | **Git 克隆** | `git clone https://github.com/DailybotHQ/agent-skill.git` + `./setup.sh` | -| **Dailybot CLI**（最低 `>= 3.1.2`） | 首次使用时由技能通过已验证的 `shared/auth.md` 安装；或 `pip install 'dailybot-cli>=3.1.2'`、Homebrew，或 [cli.dailybot.com](https://cli.dailybot.com) 上的校验和验证安装器 | +| **Dailybot CLI**（最低 `>= 3.7.0`） | 首次使用时由技能通过已验证的 `shared/auth.md` 安装；或 `pip install 'dailybot-cli>=3.7.0'`、Homebrew，或 [cli.dailybot.com](https://cli.dailybot.com) 上的校验和验证安装器 | 检查版本：`dailybot --version` 和 `dailybot version --check`。升级：`dailybot upgrade`。 @@ -82,13 +82,14 @@ DWP Dailybot 附加组件**不会**重新发明 Dailybot。它将计划执行连 此附加组件**从不**提示输入电子邮件、OTP 或 API 密钥，也**从不**存储凭据。认证由 Dailybot 技能的 [`shared/auth.md`](https://github.com/DailybotHQ/agent-skill/blob/main/skills/dailybot/shared/auth.md) 负责： - `dailybot login`（电子邮件 OTP），或 -- `DAILYBOT_API_KEY` / `dailybot config key=...` +- `DAILYBOT_API_KEY` / `dailybot config key=...`，或 +- 可选的、被 gitignore 忽略的 `.dailybot/env.json` 每仓库密钥文件（`dailybot env add/use`，CLI `>= 3.7.0`），使开发者能够在不同仓库中登录不同组织。 -若拒绝认证或认证不可用，则静默跳过报告——工作继续进行。 +认证解析采用 **Bearer 优先**：会话令牌优先，并在遇到 `401`/`403` 时透明地从 Bearer→API 密钥重试，因此过期令牌绝不会阻塞有效密钥。若拒绝认证或认证不可用，则静默跳过报告——工作继续进行。 -## 配套的 Dailybot 技能——13 项能力（3.4.0） +## 配套的 Dailybot 技能——14 项能力（3.10.3） -安装 Dailybot 代理技能带来的远不止 DWP 附加组件所接入的内容。官方技能包（技能 **3.4.0**，CLI **>= 3.1.2**，当前发布 **3.2.1**）暴露 **13 个协调子技能**： +安装 Dailybot 代理技能带来的远不止 DWP 附加组件所接入的内容。官方技能包（技能 **3.10.3**，CLI 基线 **>= 3.7.0**，当前发布 **3.7.3**）暴露 **14 个协调子技能**： | 子技能 | 功能 | |--------|------| @@ -102,9 +103,10 @@ DWP Dailybot 附加组件**不会**重新发明 Dailybot。它将计划执行连 | **Check-ins** | 完成站会；**编写**签到（日程、参与者、问题、提醒、AI 设置） | | **Kudos** | 表彰队友或整个团队；浏览认可动态、组织动态、荣誉墙 | | **Teams** | 列出团队、查看成员、将名称解析为 UUID；`me`、`org`、用户资料 | -| **Forms** | 列出、提交、更新、流转表单；**编写**表单（工作流状态、权限、ChatOps） | +| **Forms** | 列出（现默认**组织范围**，可用 `--mine` 和 `--owner` 收窄）、提交、更新、流转表单；**编写**表单（工作流状态、权限、ChatOps）；分页、搜索与日期筛选 | | **Workflows** | 读取组织工作流（`workflow list` / `workflow get`；只读） | | **Report channels** | 发现用于表单或签到的频道 UUID | +| **Per-repo API keys** | 管理 `.dailybot/env.json`——一个可选的、被 gitignore 忽略的、按环境组织的 API 密钥 + URL 文件（`dailybot env add / use / show / list / remove / off / on`，CLI `>= 3.7.0`） | **DWP 附加组件仅将 `report` 接入计划执行。** 直接调用 Dailybot 技能处理其余一切——例如，向 `#releases` 发布部署摘要、完成站会，或请 Dailybot AI 总结签到趋势。 diff --git a/src/content/pages/de/init.md b/src/content/pages/de/init.md index f429ff8..8058188 100644 --- a/src/content/pages/de/init.md +++ b/src/content/pages/de/init.md @@ -134,7 +134,7 @@ design-system) und bieten Sie jedes als explizites Opt-in an. Ein Repository ist mit **null** Addons vollständig konform — installieren Sie sie niemals automatisch. - **Devcontainer-Unterstützung** — ein reproduzierbarer, isolierter Dev-Container mit persistenter AI-CLI-Authentifizierung. -- **Dailybot-Integration** — vier Lifecycle-Events (Kickoff, bedeutende Aufgabe, Blockiert, Abschluss) als Best-Effort-Fortschrittsberichte für Teams, die Dailybot bereits nutzen, mit optionaler autonomer Hook-Durchsetzung (`dailybot-cli >= 3.1.2`). Die Installation der gepaarten Dailybot-Agenten-Skill (3.4.0) bietet zusätzlich Chat, Check-ins, Formular-Erstellung, KI-Abfrage und mehr — das Addon verbindet lediglich die Berichterstattung mit der DWP-Ausführung. Die zentrale Methodik hat keine Dailybot-Abhängigkeit. +- **Dailybot-Integration** — vier Lifecycle-Events (Kickoff, bedeutende Aufgabe, Blockiert, Abschluss) als Best-Effort-Fortschrittsberichte für Teams, die Dailybot bereits nutzen, mit optionaler autonomer Hook-Durchsetzung (`dailybot-cli >= 3.7.0`). Die Installation der gepaarten Dailybot-Agenten-Skill (3.10.3) bietet zusätzlich Chat, Check-ins, Formular-Erstellung, KI-Abfrage, Per-Repo-API-Keys und mehr — das Addon verbindet lediglich die Berichterstattung mit der DWP-Ausführung. Die zentrale Methodik hat keine Dailybot-Abhängigkeit. - **Dependency-Upgrade** — paketmanager-agnostische, chargenweise, validierte, rücknehmbare Upgrades. Wenn angenommen, installiert es den `/lib-upgrade`-Befehl. - **Design System** — optionale `docs/DESIGN.md` nur für Repositories mit einer erkannten Interface-Oberfläche diff --git a/src/content/pages/en/init.md b/src/content/pages/en/init.md index 7ed7d48..8da7b9f 100644 --- a/src/content/pages/en/init.md +++ b/src/content/pages/en/init.md @@ -147,7 +147,7 @@ design-system) and offer each as an explicit opt-in. A repository is fully confo addons — never auto-install them. - **Devcontainer support** — a reproducible, isolated dev container with persistent AI-CLI auth. -- **Dailybot integration** — four lifecycle events (kickoff, significant task, blocked, completion) as best-effort progress reports for teams already using Dailybot, with optional autonomous hook enforcement (`dailybot-cli >= 3.1.2`). Installing the paired Dailybot agent skill (3.4.0) also exposes chat, check-ins, forms authoring, ask AI, and more — the addon wires only reporting into DWP execution. The core methodology has zero Dailybot dependency. +- **Dailybot integration** — four lifecycle events (kickoff, significant task, blocked, completion) as best-effort progress reports for teams already using Dailybot, with optional autonomous hook enforcement (`dailybot-cli >= 3.7.0`). Installing the paired Dailybot agent skill (3.10.3) also exposes chat, check-ins, forms authoring, ask AI, per-repo API keys, and more — the addon wires only reporting into DWP execution. The core methodology has zero Dailybot dependency. - **Dependency upgrade** — package-manager-agnostic, batched, validated, revertible upgrades. When accepted, it installs the `/lib-upgrade` command. - **Design system** — opt-in `docs/DESIGN.md` for repos with a detected interface surface only diff --git a/src/content/pages/en/kit.md b/src/content/pages/en/kit.md index 8dc2870..7f012bd 100644 --- a/src/content/pages/en/kit.md +++ b/src/content/pages/en/kit.md @@ -49,7 +49,7 @@ and a generic fallback. Optional capabilities the onboard flow can layer onto a repo — never part of the AI-first baseline: - **Devcontainer** — a reproducible, isolated dev container with persistent AI-CLI auth. -- **Dailybot** — plan-lifecycle reporting (kickoff, significant task, blocked, completion) for teams using Dailybot, plus access to the full Dailybot agent skill (3.4.0: chat, check-ins, forms, ask AI, and more). +- **Dailybot** — plan-lifecycle reporting (kickoff, significant task, blocked, completion) for teams using Dailybot, plus access to the full Dailybot agent skill (3.10.3: chat, check-ins, forms, ask AI, per-repo API keys, and more). - **Dependency upgrade** — package-manager-agnostic, batched, validated, revertible upgrades. - **Design system** — an interface-scoped `DESIGN.md` (at `docs/DESIGN.md`, referenced from `AGENTS.md`) reasoned from the repo's real design source, with profiles for visual UI, styled CLI output, and conversational messaging, so agents generate on-brand interface output; the visual profile is default-on when a design system is detected, the CLI and conversational profiles are recommended when detected and always asked about. diff --git a/src/content/pages/es/init.md b/src/content/pages/es/init.md index caf65e3..e7b0560 100644 --- a/src/content/pages/es/init.md +++ b/src/content/pages/es/init.md @@ -149,7 +149,7 @@ design-system) y ofrece cada uno como una opción explícita. Un repositorio es - **Soporte de devcontainer** — un contenedor de desarrollo reproducible y aislado con autenticación de CLI de IA persistente. -- **Integración con Dailybot** — cuatro eventos del ciclo de vida (kickoff, tarea significativa, bloqueado, finalización) como informes de progreso de mejor esfuerzo para equipos que ya usan Dailybot, con refuerzo autónomo opcional mediante hooks (`dailybot-cli >= 3.1.2`). La instalación del skill de agente Dailybot emparejado (3.4.0) también expone chat, check-ins, autoría de formularios, preguntar a la IA y más — el addon solo conecta reportes con la ejecución de DWP. La metodología central no tiene dependencia de Dailybot. +- **Integración con Dailybot** — cuatro eventos del ciclo de vida (kickoff, tarea significativa, bloqueado, finalización) como informes de progreso de mejor esfuerzo para equipos que ya usan Dailybot, con refuerzo autónomo opcional mediante hooks (`dailybot-cli >= 3.7.0`). La instalación del skill de agente Dailybot emparejado (3.10.3) también expone chat, check-ins, autoría de formularios, preguntar a la IA, claves API por repo y más — el addon solo conecta reportes con la ejecución de DWP. La metodología central no tiene dependencia de Dailybot. - **Actualización de dependencias** — actualizaciones independientes del gestor de paquetes, por lotes, validadas y revertibles. Cuando se acepta, instala el comando `/lib-upgrade`. - **Design system** — `docs/DESIGN.md` opcional para repos con una superficie de interfaz detectada diff --git a/src/content/pages/fr/init.md b/src/content/pages/fr/init.md index 424cbcb..0549276 100644 --- a/src/content/pages/fr/init.md +++ b/src/content/pages/fr/init.md @@ -147,7 +147,7 @@ design-system) et proposez chacun comme un choix explicite. Un dépôt est pleinement conforme avec **zéro** addon — ne les installez jamais automatiquement. - **Prise en charge du devcontainer** — un conteneur de développement reproductible et isolé avec une auth de CLI IA persistante. -- **Intégration Dailybot** — quatre événements du cycle de vie (kickoff, tâche significative, bloqué, achèvement) comme rapports de progression au mieux pour les équipes utilisant déjà Dailybot, avec une couche facultative d’application autonome des hooks (`dailybot-cli >= 3.1.2`). L’installation du skill d’agent Dailybot apparié (3.4.0) expose aussi le chat, les check-ins, la création de formulaires, la consultation IA et plus — l’addon ne raccorde que le reporting à l’exécution DWP. La méthodologie de base n’a aucune dépendance à Dailybot. +- **Intégration Dailybot** — quatre événements du cycle de vie (kickoff, tâche significative, bloqué, achèvement) comme rapports de progression au mieux pour les équipes utilisant déjà Dailybot, avec une couche facultative d’application autonome des hooks (`dailybot-cli >= 3.7.0`). L’installation du skill d’agent Dailybot apparié (3.10.3) expose aussi le chat, les check-ins, la création de formulaires, la consultation IA, les clés API par dépôt et plus — l’addon ne raccorde que le reporting à l’exécution DWP. La méthodologie de base n’a aucune dépendance à Dailybot. - **Mise à jour des dépendances** — des mises à jour indépendantes du gestionnaire de paquets, par lots, validées et réversibles. Lorsqu’elle est acceptée, elle installe la commande `/lib-upgrade`. - **Design system** — `docs/DESIGN.md` optionnel, proposé uniquement pour les dépôts dotés d’une surface diff --git a/src/content/pages/hi/init.md b/src/content/pages/hi/init.md index 74c798d..7cfe98f 100644 --- a/src/content/pages/hi/init.md +++ b/src/content/pages/hi/init.md @@ -142,7 +142,7 @@ onboard सब-स्किल (`/deepworkplan-onboard`) आमंत्रि **शून्य** ऐडऑन के साथ पूर्णतः अनुरूप होती है — इन्हें कभी स्वतः-स्थापित न करें। - **Devcontainer समर्थन** — स्थायी AI-CLI प्रमाणन वाला एक पुनरुत्पाद्य, पृथक dev container। -- **Dailybot एकीकरण** — चार जीवनचक्र ईवेंट (किकऑफ़, महत्वपूर्ण कार्य, अवरुद्ध, पूर्णता) पहले से Dailybot का उपयोग करने वाली टीमों के लिए सर्वोत्तम-प्रयास प्रगति रिपोर्ट के रूप में, वैकल्पिक स्वायत्त हुक प्रवर्तन (`dailybot-cli >= 3.1.2`) के साथ। जोड़ी गई Dailybot एजेंट स्किल (3.4.0) स्थापित करने से चैट, चेक-इन, फ़ॉर्म ऑथरिंग, AI से पूछना और अन्य सुविधाएँ भी उपलब्ध होती हैं — ऐडऑन केवल रिपोर्टिंग को DWP निष्पादन से जोड़ता है। मूल पद्धति की Dailybot पर शून्य निर्भरता है। +- **Dailybot एकीकरण** — चार जीवनचक्र ईवेंट (किकऑफ़, महत्वपूर्ण कार्य, अवरुद्ध, पूर्णता) पहले से Dailybot का उपयोग करने वाली टीमों के लिए सर्वोत्तम-प्रयास प्रगति रिपोर्ट के रूप में, वैकल्पिक स्वायत्त हुक प्रवर्तन (`dailybot-cli >= 3.7.0`) के साथ। जोड़ी गई Dailybot एजेंट स्किल (3.10.3) स्थापित करने से चैट, चेक-इन, फ़ॉर्म ऑथरिंग, AI से पूछना, per-repo API keys और अन्य सुविधाएँ भी उपलब्ध होती हैं — ऐडऑन केवल रिपोर्टिंग को DWP निष्पादन से जोड़ता है। मूल पद्धति की Dailybot पर शून्य निर्भरता है। - **Dependency upgrade** — पैकेज-मैनेजर-निरपेक्ष, बैच-आधारित, सत्यापित, वापस लेने योग्य अपग्रेड। स्वीकार किए जाने पर, यह `/lib-upgrade` कमांड स्थापित करता है। - **Design system** — केवल पता लगाई गई इंटरफ़ेस सतह वाली रिपॉज़िटरी के लिए ऑप्ट-इन `docs/DESIGN.md` diff --git a/src/content/pages/id/init.md b/src/content/pages/id/init.md index c34e530..57043c8 100644 --- a/src/content/pages/id/init.md +++ b/src/content/pages/id/init.md @@ -146,7 +146,7 @@ design-system) dan tawarkan masing-masing sebagai opt-in eksplisit. Sebuah repos konforman dengan **nol** addon — jangan pernah memasangnya secara otomatis. - **Dukungan devcontainer** — kontainer pengembangan yang terisolasi dan dapat direproduksi dengan autentikasi AI-CLI yang persisten. -- **Integrasi Dailybot** — empat peristiwa siklus hidup (kickoff, tugas signifikan, terblokir, penyelesaian) sebagai pelaporan kemajuan secara best-effort untuk tim yang sudah memakai Dailybot, dengan penegakan hook otonom opsional (`dailybot-cli >= 3.1.2`). Memasang skill agent Dailybot yang dipasangkan (3.4.0) juga membuka chat, check-in, penulisan form, tanya AI, dan lainnya — addon ini hanya menghubungkan pelaporan ke eksekusi DWP. Metodologi inti tidak memiliki ketergantungan apa pun pada Dailybot. +- **Integrasi Dailybot** — empat peristiwa siklus hidup (kickoff, tugas signifikan, terblokir, penyelesaian) sebagai pelaporan kemajuan secara best-effort untuk tim yang sudah memakai Dailybot, dengan penegakan hook otonom opsional (`dailybot-cli >= 3.7.0`). Memasang skill agent Dailybot yang dipasangkan (3.10.3) juga membuka chat, check-in, penulisan form, tanya AI, API key per repo, dan lainnya — addon ini hanya menghubungkan pelaporan ke eksekusi DWP. Metodologi inti tidak memiliki ketergantungan apa pun pada Dailybot. - **Dependency upgrade** — peningkatan yang agnostik terhadap package manager, terkelompok, tervalidasi, dan dapat dikembalikan. Ketika diterima, ia memasang command `/lib-upgrade`. - **Design system** — `docs/DESIGN.md` opsional hanya untuk repositori dengan permukaan antarmuka yang diff --git a/src/content/pages/it/init.md b/src/content/pages/it/init.md index 577a1d0..3113b90 100644 --- a/src/content/pages/it/init.md +++ b/src/content/pages/it/init.md @@ -146,7 +146,7 @@ design-system) e proponi ciascuno come opt-in esplicito. Un repository è pienam **zero** addon — non installarli mai automaticamente. - **Supporto devcontainer** — un dev container riproducibile e isolato con autenticazione AI-CLI persistente. -- **Integrazione Dailybot** — quattro eventi del ciclo di vita (kickoff, attività significativa, bloccato, completamento) come report best-effort di progressi per i team che già usano Dailybot, con livello opzionale di enforcement autonomo degli hook (`dailybot-cli >= 3.1.2`). L'installazione della skill agente Dailybot abbinata (3.4.0) espone anche chat, check-in, authoring di form, domande all'AI e altro — l'addon collega solo il reporting all'esecuzione DWP. La metodologia di base ha zero dipendenze da Dailybot. +- **Integrazione Dailybot** — quattro eventi del ciclo di vita (kickoff, attività significativa, bloccato, completamento) come report best-effort di progressi per i team che già usano Dailybot, con livello opzionale di enforcement autonomo degli hook (`dailybot-cli >= 3.7.0`). L'installazione della skill agente Dailybot abbinata (3.10.3) espone anche chat, check-in, authoring di form, domande all'AI, API key per repository e altro — l'addon collega solo il reporting all'esecuzione DWP. La metodologia di base ha zero dipendenze da Dailybot. - **Dependency upgrade** — aggiornamenti indipendenti dal package manager, a lotti, validati e annullabili. Quando accettato, installa il comando `/lib-upgrade`. - **Design system** — un `docs/DESIGN.md` opt-in solo per i repository con una superficie di interfaccia diff --git a/src/content/pages/ja/init.md b/src/content/pages/ja/init.md index 989b2f2..4ffe9ef 100644 --- a/src/content/pages/ja/init.md +++ b/src/content/pages/ja/init.md @@ -89,7 +89,7 @@ onboard サブスキル（`/deepworkplan-onboard`）を呼び出します。実 ベースラインのオンボーディング後、四つのアドオン（devcontainer、Dailybot、dependency-upgrade、design-system）を列挙し、それぞれを明示的なオプトインとして提案します。リポジトリは**ゼロ**のアドオンで完全に適合します。決して自動でインストールしないでください。 - **Devcontainer サポート** — 永続的な AI CLI 認証を備えた、再現可能で隔離された開発コンテナ。 -- **Dailybot 連携** — 四つのライフサイクルイベント（キックオフ、重要なタスク、ブロック、完了）を、すでに Dailybot を使っているチームのための最善努力での進捗報告として、任意で自律的なフック強制層（`dailybot-cli >= 3.1.2`）付きで提供します。ペアの Dailybot エージェントスキル（3.4.0）をインストールすると、チャット、チェックイン、フォーム作成、AI への質問なども利用可能になります。このアドオンは DWP 実行へのレポーティングの接続のみを行います。中核となる方法論は Dailybot への依存がゼロです。 +- **Dailybot 連携** — 四つのライフサイクルイベント（キックオフ、重要なタスク、ブロック、完了）を、すでに Dailybot を使っているチームのための最善努力での進捗報告として、任意で自律的なフック強制層（`dailybot-cli >= 3.7.0`）付きで提供します。ペアの Dailybot エージェントスキル（3.10.3）をインストールすると、チャット、チェックイン、フォーム作成、AI への質問、リポジトリごとの API キーなども利用可能になります。このアドオンは DWP 実行へのレポーティングの接続のみを行います。中核となる方法論は Dailybot への依存がゼロです。 - **Dependency upgrade** — パッケージマネージャー非依存で、バッチ化され、検証され、取り消し可能な更新。受け入れられると、`/lib-upgrade` コマンドをインストールします。 - **Design system** — 検出されたインターフェイス面を持つリポジトリのみを対象とした、オプトインの `docs/DESIGN.md`（純粋なライブラリ、ヘッドレスサービス、インフラ専用リポジトリには提案されません）。三つのプロファイルが一つのファイルに重ねられます：visual-ui（検出時にデフォルトでオン）、cli-output、conversational — 後者二つは常に尋ねられ、自動適用されることはありません。 diff --git a/src/content/pages/ko/init.md b/src/content/pages/ko/init.md index 2835dc1..7fb0677 100644 --- a/src/content/pages/ko/init.md +++ b/src/content/pages/ko/init.md @@ -139,7 +139,7 @@ onboard 하위 스킬(`/deepworkplan-onboard`)을 호출하세요. 실제 리포 적합합니다 — 결코 자동 설치하지 마세요. - **Devcontainer 지원** — 영속적 AI-CLI 인증을 갖춘 재현 가능하고 격리된 개발 컨테이너. -- **Dailybot 연동** — 네 가지 라이프사이클 이벤트(kickoff, 중요 작업, 블로킹, 완료)를 이미 Dailybot을 사용하는 팀을 위한 최선 노력 기반의 진행 보고로 제공하며, 선택적 자율 훅 강제(`dailybot-cli >= 3.1.2`). 페어링된 Dailybot 에이전트 스킬(3.4.0)을 설치하면 채팅, 체크인, 폼 작성, AI 질의 등도 노출됩니다 — 이 애드온은 DWP 실행에 보고만 연결합니다. 핵심 방법론은 Dailybot 의존성이 전혀 없습니다. +- **Dailybot 연동** — 네 가지 라이프사이클 이벤트(kickoff, 중요 작업, 블로킹, 완료)를 이미 Dailybot을 사용하는 팀을 위한 최선 노력 기반의 진행 보고로 제공하며, 선택적 자율 훅 강제(`dailybot-cli >= 3.7.0`). 페어링된 Dailybot 에이전트 스킬(3.10.3)을 설치하면 채팅, 체크인, 폼 작성, AI 질의, 저장소별 API 키 등도 노출됩니다 — 이 애드온은 DWP 실행에 보고만 연결합니다. 핵심 방법론은 Dailybot 의존성이 전혀 없습니다. - **Dependency upgrade** — 패키지 관리자 비종속, 배치 단위, 검증되고 되돌릴 수 있는 업그레이드. 채택되면 `/lib-upgrade` 명령을 설치합니다. - **Design system** — 감지된 인터페이스 표면이 있는 리포지토리에만 제공되는 선택형 `docs/DESIGN.md` diff --git a/src/content/pages/pl/init.md b/src/content/pages/pl/init.md index 13bd435..1433e32 100644 --- a/src/content/pages/pl/init.md +++ b/src/content/pages/pl/init.md @@ -141,7 +141,7 @@ Po onboardingu bazowym wymień cztery dodatki (devcontainer, Dailybot, dependenc w pełni zgodne przy **zerowej** liczbie dodatków — nigdy nie instaluj ich automatycznie. - **Wsparcie devcontainera** — odtwarzalny, izolowany kontener deweloperski z trwałym uwierzytelnianiem AI-CLI. -- **Integracja z Dailybot** — cztery zdarzenia cyklu życia (kickoff, istotne zadanie, blokada, zakończenie) jako raporty postępu w trybie najlepszego wysiłku dla zespołów już korzystających z Dailybot, z opcjonalnym autonomicznym wymuszaniem hooków (`dailybot-cli >= 3.1.2`). Instalacja sparowanego skilla agenta Dailybot (3.4.0) udostępnia również czat, check-iny, tworzenie formularzy, pytanie AI i więcej — dodatek łączy jedynie raportowanie z wykonywaniem DWP. Podstawowa metodyka nie ma żadnej zależności od Dailybot. +- **Integracja z Dailybot** — cztery zdarzenia cyklu życia (kickoff, istotne zadanie, blokada, zakończenie) jako raporty postępu w trybie najlepszego wysiłku dla zespołów już korzystających z Dailybot, z opcjonalnym autonomicznym wymuszaniem hooków (`dailybot-cli >= 3.7.0`). Instalacja sparowanego skilla agenta Dailybot (3.10.3) udostępnia również czat, check-iny, tworzenie formularzy, pytanie AI, klucze API per-repo i więcej — dodatek łączy jedynie raportowanie z wykonywaniem DWP. Podstawowa metodyka nie ma żadnej zależności od Dailybot. - **Dependency upgrade** — aktualizacje niezależne od menedżera pakietów: partiami, zwalidowane i odwracalne. Po zaakceptowaniu instaluje komendę `/lib-upgrade`. - **Design system** — opcjonalny `docs/DESIGN.md` tylko dla repozytoriów z wykrytą powierzchnią interfejsu diff --git a/src/content/pages/pt/init.md b/src/content/pages/pt/init.md index 67e866e..d8237a8 100644 --- a/src/content/pages/pt/init.md +++ b/src/content/pages/pt/init.md @@ -144,7 +144,7 @@ design-system) e ofereça cada um como uma escolha explícita. Um repositório totalmente conforme com **zero** addons — nunca os instale automaticamente. - **Suporte a devcontainer** — um dev container reproduzível e isolado com auth de CLI de IA persistente. -- **Integração com a Dailybot** — quatro eventos do ciclo de vida (kickoff, tarefa significativa, bloqueado, conclusão) como relatórios de progresso best-effort para equipes que já usam a Dailybot, com reforço autônomo opcional via hooks (`dailybot-cli >= 3.1.2`). A instalação da skill de agente Dailybot emparelhada (3.4.0) também expõe chat, check-ins, criação de formulários, consulta à IA e mais — o addon conecta apenas os relatórios à execução DWP. A metodologia central tem zero dependência da Dailybot. +- **Integração com a Dailybot** — quatro eventos do ciclo de vida (kickoff, tarefa significativa, bloqueado, conclusão) como relatórios de progresso best-effort para equipes que já usam a Dailybot, com reforço autônomo opcional via hooks (`dailybot-cli >= 3.7.0`). A instalação da skill de agente Dailybot emparelhada (3.10.3) também expõe chat, check-ins, criação de formulários, consulta à IA, chaves API por repositório e mais — o addon conecta apenas os relatórios à execução DWP. A metodologia central tem zero dependência da Dailybot. - **Atualização de dependências** — atualizações independentes do gerenciador de pacotes, em lotes, validadas e reversíveis. Quando aceita, ela instala o comando `/lib-upgrade`. - **Design system** — `docs/DESIGN.md` opcional para repos com uma superfície de interface detectada diff --git a/src/content/pages/ru/init.md b/src/content/pages/ru/init.md index 9e1c8c1..26db0a3 100644 --- a/src/content/pages/ru/init.md +++ b/src/content/pages/ru/init.md @@ -145,7 +145,7 @@ design-system) и предложите каждое как явное согла и с **нулём** дополнений — никогда не устанавливайте их автоматически. - **Поддержка Devcontainer** — воспроизводимый, изолированный dev-контейнер с устойчивой аутентификацией AI-CLI. -- **Интеграция Dailybot** — четыре события жизненного цикла (kickoff, значимая задача, блокировка, завершение) как отчётность о прогрессе по принципу best-effort для команд, уже использующих Dailybot, с опциональным автономным обеспечением хуков (`dailybot-cli >= 3.1.2`). Установка парного навыка агента Dailybot (3.4.0) также открывает чат, чек-ины, создание форм, вопросы к AI и многое другое — дополнение подключает только отчётность к выполнению DWP. Основная методология имеет ноль зависимости от Dailybot. +- **Интеграция Dailybot** — четыре события жизненного цикла (kickoff, значимая задача, блокировка, завершение) как отчётность о прогрессе по принципу best-effort для команд, уже использующих Dailybot, с опциональным автономным обеспечением хуков (`dailybot-cli >= 3.7.0`). Установка парного навыка агента Dailybot (3.10.3) также открывает чат, чек-ины, создание форм, вопросы к AI, API-ключи на репозиторий и многое другое — дополнение подключает только отчётность к выполнению DWP. Основная методология имеет ноль зависимости от Dailybot. - **Dependency upgrade** — независимые от менеджера пакетов, партийные, проверяемые, обратимые обновления. При принятии оно устанавливает команду `/lib-upgrade`. - **Design system** — опциональный `docs/DESIGN.md` только для репозиториев с обнаруженной diff --git a/src/content/pages/th/init.md b/src/content/pages/th/init.md index 097c21f..49b9937 100644 --- a/src/content/pages/th/init.md +++ b/src/content/pages/th/init.md @@ -140,7 +140,7 @@ git clone https://github.com/DailybotHQ/deepworkplan-skill.git && cd deepworkpla สอดคล้องอย่างสมบูรณ์โดยมีส่วนเสริม **ศูนย์** อย่าง — อย่าติดตั้งมันอัตโนมัติ - **Devcontainer support** — dev container ที่ทำซ้ำได้และแยกตัว พร้อม auth ของ AI-CLI ที่คงอยู่ -- **Dailybot integration** — สี่เหตุการณ์วงจรชีวิต (kickoff, งานสำคัญ, ถูกบล็อก, เสร็จสิ้น) เป็นรายงานความคืบหน้าแบบเต็มความสามารถสำหรับทีมที่ใช้ Dailybot อยู่แล้ว พร้อมการบังคับใช้ hook อัตโนมัติแบบเลือกได้ (`dailybot-cli >= 3.1.2`) การติดตั้ง skill เอเจนต์ Dailybot ที่จับคู่มา (3.4.0) ยังเปิดให้ใช้แชท เช็คอิน สร้างฟอร์ม ถาม AI และอื่น ๆ — ส่วนเสริมเชื่อมเฉพาะการรายงานเข้ากับการดำเนินการ DWP ระเบียบวิธีหลักไม่มีการพึ่งพิง Dailybot ใด ๆ +- **Dailybot integration** — สี่เหตุการณ์วงจรชีวิต (kickoff, งานสำคัญ, ถูกบล็อก, เสร็จสิ้น) เป็นรายงานความคืบหน้าแบบเต็มความสามารถสำหรับทีมที่ใช้ Dailybot อยู่แล้ว พร้อมการบังคับใช้ hook อัตโนมัติแบบเลือกได้ (`dailybot-cli >= 3.7.0`) การติดตั้ง skill เอเจนต์ Dailybot ที่จับคู่มา (3.10.3) ยังเปิดให้ใช้แชท เช็คอิน สร้างฟอร์ม ถาม AI per-repo API keys และอื่น ๆ — ส่วนเสริมเชื่อมเฉพาะการรายงานเข้ากับการดำเนินการ DWP ระเบียบวิธีหลักไม่มีการพึ่งพิง Dailybot ใด ๆ - **Dependency upgrade** — การอัปเกรดที่เป็นกลางต่อตัวจัดการแพ็กเกจ ทำเป็นชุด ตรวจสอบแล้ว และย้อนกลับได้ เมื่อ ยอมรับ มันจะติดตั้งคำสั่ง `/lib-upgrade` - **Design system** — `docs/DESIGN.md` แบบเลือกเข้าร่วมสำหรับ repo ที่ตรวจพบว่ามีพื้นผิวอินเทอร์เฟซเท่านั้น diff --git a/src/content/pages/tr/init.md b/src/content/pages/tr/init.md index 7e823b1..91a5582 100644 --- a/src/content/pages/tr/init.md +++ b/src/content/pages/tr/init.md @@ -148,7 +148,7 @@ tümüyle uyumludur — onları asla otomatik kurmayın. - **Devcontainer desteği** — kalıcı AI-CLI kimlik doğrulaması içeren, yeniden üretilebilir, yalıtılmış bir geliştirme konteyneri. -- **Dailybot entegrasyonu** — dört yaşam döngüsü olayı (kickoff, önemli görev, engellendi, tamamlandı) olarak zaten Dailybot kullanan ekipler için en iyi çabayla ilerleme raporlaması; isteğe bağlı otonom kanca zorlama (`dailybot-cli >= 3.1.2`). Eşleştirilmiş Dailybot ajan skill’inin (3.4.0) kurulması ayrıca sohbet, check-in’ler, form yazarlığı, AI’ye sorma ve daha fazlasını açar — eklenti yalnızca raporlamayı DWP yürütmesine bağlar. Çekirdek metodolojinin Dailybot’a hiçbir bağımlılığı yoktur. +- **Dailybot entegrasyonu** — dört yaşam döngüsü olayı (kickoff, önemli görev, engellendi, tamamlandı) olarak zaten Dailybot kullanan ekipler için en iyi çabayla ilerleme raporlaması; isteğe bağlı otonom kanca zorlama (`dailybot-cli >= 3.7.0`). Eşleştirilmiş Dailybot ajan skill’inin (3.10.3) kurulması ayrıca sohbet, check-in’ler, form yazarlığı, AI’ye sorma, depo başına API anahtarları ve daha fazlasını açar — eklenti yalnızca raporlamayı DWP yürütmesine bağlar. Çekirdek metodolojinin Dailybot’a hiçbir bağımlılığı yoktur. - **Dependency upgrade** — paket yöneticisinden bağımsız, gruplanmış, doğrulanmış, geri alınabilir yükseltmeler. Kabul edildiğinde, `/lib-upgrade` komutunu kurar. - **Design system** — yalnızca saptanan arayüz yüzeyi olan depolar için isteğe bağlı `docs/DESIGN.md` diff --git a/src/content/pages/uk/init.md b/src/content/pages/uk/init.md index c24987e..0246804 100644 --- a/src/content/pages/uk/init.md +++ b/src/content/pages/uk/init.md @@ -142,7 +142,7 @@ git clone https://github.com/DailybotHQ/deepworkplan-skill.git && cd deepworkpla повністю відповідний з **нульовою** кількістю add-on — ніколи не встановлюйте їх автоматично. - **Підтримка Devcontainer** — відтворюваний, ізольований dev-контейнер зі стійкою автентифікацією AI-CLI. -- **Інтеграція з Dailybot** — чотири події життєвого циклу (kickoff, значуще завдання, блокування, завершення) як звіти про прогрес за принципом найкращих зусиль для команд, що вже використовують Dailybot, з опціональним автономним примусовим виконанням хуків (`dailybot-cli >= 3.1.2`). Встановлення парного скілу агента Dailybot (3.4.0) також відкриває чат, чек-іни, створення форм, запитання до AI та інше — add-on підключає лише звітування до виконання DWP. Базова методологія не має жодної залежності від Dailybot. +- **Інтеграція з Dailybot** — чотири події життєвого циклу (kickoff, значуще завдання, блокування, завершення) як звіти про прогрес за принципом найкращих зусиль для команд, що вже використовують Dailybot, з опціональним автономним примусовим виконанням хуків (`dailybot-cli >= 3.7.0`). Встановлення парного скілу агента Dailybot (3.10.3) також відкриває чат, чек-іни, створення форм, запитання до AI, per-repo API keys та інше — add-on підключає лише звітування до виконання DWP. Базова методологія не має жодної залежності від Dailybot. - **Оновлення залежностей** — незалежні від менеджера пакетів, партіями, перевірені, відкочувані оновлення. Коли прийнято, воно встановлює команду `/lib-upgrade`. - **Design system** — опціональний `docs/DESIGN.md` лише для репозиторіїв із виявленою інтерфейсною поверхнею diff --git a/src/content/pages/vi/init.md b/src/content/pages/vi/init.md index 8b7dcc2..7d9a39f 100644 --- a/src/content/pages/vi/init.md +++ b/src/content/pages/vi/init.md @@ -144,7 +144,7 @@ Sau khi khởi tạo nền tảng, hãy liệt kê bốn addon (devcontainer, Da hoàn toàn tuân thủ với **không** cần addon nào — đừng bao giờ tự động cài chúng. - **Hỗ trợ devcontainer** — một dev container tái lập được, cô lập, với xác thực AI-CLI bền vững. -- **Tích hợp Dailybot** — bốn sự kiện vòng đời (kickoff, tác vụ quan trọng, bị chặn, hoàn tất) dưới dạng báo cáo tiến độ theo nỗ lực tối đa cho các đội đã dùng Dailybot, với lớp hook tự hành tùy chọn (`dailybot-cli >= 3.1.2`). Cài skill agent Dailybot đi kèm (3.4.0) cũng mở ra chat, check-in, tạo biểu mẫu, hỏi AI và nhiều hơn — addon chỉ đấu nối phần báo cáo vào quá trình thực thi DWP. Phương pháp luận lõi không có phụ thuộc nào vào Dailybot. +- **Tích hợp Dailybot** — bốn sự kiện vòng đời (kickoff, tác vụ quan trọng, bị chặn, hoàn tất) dưới dạng báo cáo tiến độ theo nỗ lực tối đa cho các đội đã dùng Dailybot, với lớp hook tự hành tùy chọn (`dailybot-cli >= 3.7.0`). Cài skill agent Dailybot đi kèm (3.10.3) cũng mở ra chat, check-in, tạo biểu mẫu, hỏi AI, API key theo repo và nhiều hơn — addon chỉ đấu nối phần báo cáo vào quá trình thực thi DWP. Phương pháp luận lõi không có phụ thuộc nào vào Dailybot. - **Nâng cấp phụ thuộc** — nâng cấp độc lập với trình quản lý gói, theo lô, được kiểm chứng, hoàn nguyên được. Khi được chấp nhận, nó cài command `/lib-upgrade`. - **Design system** — `docs/DESIGN.md` tự nguyện dành cho các repo có bề mặt giao diện được phát hiện diff --git a/src/content/pages/zh/init.md b/src/content/pages/zh/init.md index f25a3aa..d8bbabc 100644 --- a/src/content/pages/zh/init.md +++ b/src/content/pages/zh/init.md @@ -128,7 +128,7 @@ git clone https://github.com/DailybotHQ/deepworkplan-skill.git && cd deepworkpla 在不带**任何**附加组件时即完全符合规范——绝不自动安装它们。 - **Devcontainer 支持** —— 一个可复现、隔离的开发容器，具备持久的 AI-CLI 认证。 -- **Dailybot 集成** —— 四个生命周期事件（启动、重要任务、阻塞、完成）作为面向已在使用 Dailybot 的团队的尽力而为式进展报告，并可选启用自主的钩子强制层（`dailybot-cli >= 3.1.2`）。安装配套的 Dailybot 代理技能（3.4.0）还会暴露聊天、签到、表单创建、AI 询问等功能——该附加组件仅将报告接入 DWP 执行。核心方法论对 Dailybot 零依赖。 +- **Dailybot 集成** —— 四个生命周期事件（启动、重要任务、阻塞、完成）作为面向已在使用 Dailybot 的团队的尽力而为式进展报告，并可选启用自主的钩子强制层（`dailybot-cli >= 3.7.0`）。安装配套的 Dailybot 代理技能（3.10.3）还会暴露聊天、签到、表单创建、AI 询问、每仓库 API 密钥等功能——该附加组件仅将报告接入 DWP 执行。核心方法论对 Dailybot 零依赖。 - **Dependency upgrade** —— 包管理器无关、分批次、经验证、可回退的升级。被 采纳时，它会安装 `/lib-upgrade` 命令。 - **Design system** —— 可选的 `docs/DESIGN.md`，仅面向具备被检测到的界面表面的仓库 diff --git a/src/content/spec/de/addons.md b/src/content/spec/de/addons.md index abeb883..d801c9f 100644 --- a/src/content/spec/de/addons.md +++ b/src/content/spec/de/addons.md @@ -41,8 +41,8 @@ Eine Compose-basierte `.devcontainer/` + `docker/`-Einrichtung, aus dem erkannte Eine optionale Verbindung zum **Dailybot-Team** des Entwicklers für Agenten-Fortschrittssichtbarkeit. - **Kit-Seite:** [Dailybot](/kit/dailybot) — vollständige Fähigkeitsreferenz -- **Was das DWP-Addon verdrahtet:** vier Plan-Lifecycle-Reports (Kickoff, signifikante Aufgabe, blockiert, Abschluss) via dailybot-`report`-Sub-Skill; optionale deterministische Hook-Durchsetzung (`dailybot hook`, CLI `>= 3.1.2`) -- **Gepaarte Skill:** Installation von [DailybotHQ/agent-skill](https://github.com/DailybotHQ/agent-skill) (aktuell **3.4.0**) exponiert **13 Fähigkeiten** — Chat in Slack/Teams/Discord/Google Chat, Check-ins, Formular-Autorisierung, Ask AI, Kudos, E-Mail und mehr. Das DWP-Addon verdrahtet nur **report**; andere Fähigkeiten werden direkt über die Dailybot-Skill aufgerufen +- **Was das DWP-Addon verdrahtet:** vier Plan-Lifecycle-Reports (Kickoff, signifikante Aufgabe, blockiert, Abschluss) via dailybot-`report`-Sub-Skill; optionale deterministische Hook-Durchsetzung (`dailybot hook`, CLI `>= 3.7.0`) +- **Gepaarte Skill:** Installation von [DailybotHQ/agent-skill](https://github.com/DailybotHQ/agent-skill) (aktuell **3.10.3**) exponiert **14 Fähigkeiten** — Chat in Slack/Teams/Discord/Google Chat, Check-ins, Formular-Autorisierung, Ask AI, Kudos, Per-Repo-API-Keys (`.dailybot/env.json`), E-Mail und mehr. Das DWP-Addon verdrahtet nur **report**; andere Fähigkeiten werden direkt über die Dailybot-Skill aufgerufen - **Auth:** vollständig an die Dailybot-Skill delegiert (`dailybot login` oder `DAILYBOT_API_KEY`); dieses Addon speichert niemals Credentials - **Vendor-neutrale Leitplanke:** zentrales DWP hat **null** Dailybot-Abhängigkeit; niemals für alle automatisch installieren - **Wann angeboten:** Entwickler oder Team nutzt bereits Dailybot oder fragt explizit nach Team-Reporting diff --git a/src/content/spec/en/addons.md b/src/content/spec/en/addons.md index ecfe01a..a2b96f5 100644 --- a/src/content/spec/en/addons.md +++ b/src/content/spec/en/addons.md @@ -41,8 +41,8 @@ A compose-based `.devcontainer/` + `docker/` setup reasoned from the detected st An opt-in connection to the developer's **Dailybot team** for agent progress visibility. - **Kit page:** [Dailybot](/kit/dailybot) — full capability reference -- **What the DWP addon wires:** four plan-lifecycle reports (kickoff, significant task, blocked, completion) via the dailybot `report` sub-skill; optional deterministic hook enforcement (`dailybot hook`, CLI `>= 3.1.2`) -- **Paired skill:** installing [DailybotHQ/agent-skill](https://github.com/DailybotHQ/agent-skill) (currently **3.4.0**) exposes **13 capabilities** — chat on Slack/Teams/Discord/Google Chat, check-ins, forms authoring, ask AI, kudos, email, and more. The DWP addon wires only **report**; other capabilities are invoked through the Dailybot skill directly +- **What the DWP addon wires:** four plan-lifecycle reports (kickoff, significant task, blocked, completion) via the dailybot `report` sub-skill; optional deterministic hook enforcement (`dailybot hook`, CLI `>= 3.7.0`) +- **Paired skill:** installing [DailybotHQ/agent-skill](https://github.com/DailybotHQ/agent-skill) (currently **3.10.3**) exposes **14 capabilities** — chat on Slack/Teams/Discord/Google Chat, check-ins, forms authoring, ask AI, kudos, per-repo API keys (`.dailybot/env.json`), email, and more. The DWP addon wires only **report**; other capabilities are invoked through the Dailybot skill directly - **Auth:** fully deferred to the Dailybot skill (`dailybot login` or `DAILYBOT_API_KEY`); this addon never stores credentials - **Vendor-neutral guardrail:** core DWP has **zero** Dailybot dependency; never auto-install for everyone - **When offered:** developer or team already uses Dailybot, or explicitly asks for team reporting diff --git a/src/content/spec/es/addons.md b/src/content/spec/es/addons.md index aef4a47..85bb45e 100644 --- a/src/content/spec/es/addons.md +++ b/src/content/spec/es/addons.md @@ -41,8 +41,8 @@ Una configuración `.devcontainer/` + `docker/` basada en compose, razonada a pa Una conexión opcional al **equipo de Dailybot** del desarrollador para visibilidad del avance del agente. - **Página del kit:** [Dailybot](/kit/dailybot) — referencia completa de capacidades -- **Qué conecta el addon de DWP:** cuatro reportes del ciclo de vida del plan (inicio, tarea significativa, bloqueado, finalización) vía la sub-skill `report` de dailybot; refuerzo determinístico opcional mediante hooks (`dailybot hook`, CLI `>= 3.1.2`) -- **Skill emparejada:** instalar [DailybotHQ/agent-skill](https://github.com/DailybotHQ/agent-skill) (actualmente **3.4.0**) expone **13 capacidades** — chat en Slack/Teams/Discord/Google Chat, check-ins, autoría de formularios, ask AI, kudos, correo y más. El addon de DWP solo conecta **report**; el resto de capacidades se invocan directamente mediante la skill de Dailybot +- **Qué conecta el addon de DWP:** cuatro reportes del ciclo de vida del plan (inicio, tarea significativa, bloqueado, finalización) vía la sub-skill `report` de dailybot; refuerzo determinístico opcional mediante hooks (`dailybot hook`, CLI `>= 3.7.0`) +- **Skill emparejada:** instalar [DailybotHQ/agent-skill](https://github.com/DailybotHQ/agent-skill) (actualmente **3.10.3**) expone **14 capacidades** — chat en Slack/Teams/Discord/Google Chat, check-ins, autoría de formularios, ask AI, kudos, claves API por repo (`.dailybot/env.json`), correo y más. El addon de DWP solo conecta **report**; el resto de capacidades se invocan directamente mediante la skill de Dailybot - **Auth:** totalmente delegada a la skill de Dailybot (`dailybot login` o `DAILYBOT_API_KEY`); este addon nunca almacena credenciales - **Salvaguarda neutral respecto al proveedor:** el DWP central tiene **cero** dependencia de Dailybot; nunca instalar automáticamente para todos - **Cuándo se ofrece:** el desarrollador o el equipo ya usan Dailybot, o piden explícitamente reportes al equipo diff --git a/src/content/spec/fr/addons.md b/src/content/spec/fr/addons.md index eb56451..e40163d 100644 --- a/src/content/spec/fr/addons.md +++ b/src/content/spec/fr/addons.md @@ -41,8 +41,8 @@ Une configuration `.devcontainer/` + `docker/` basée sur compose, raisonnée à Une connexion optionnelle à l'**équipe Dailybot** du développeur pour la visibilité de la progression des agents. - **Page kit :** [Dailybot](/kit/dailybot) — référence complète des capacités -- **Ce que l'addon DWP connecte :** quatre rapports du cycle de vie du plan (kickoff, tâche significative, bloqué, achèvement) via la sous-skill `report` de dailybot ; application déterministe optionnelle par hooks (`dailybot hook`, CLI `>= 3.1.2`) -- **Skill jumelée :** installer [DailybotHQ/agent-skill](https://github.com/DailybotHQ/agent-skill) (actuellement **3.4.0**) expose **13 capacités** — chat sur Slack/Teams/Discord/Google Chat, check-ins, autorisation de formulaires, ask AI, kudos, e-mail et plus. L'addon DWP ne connecte que **report** ; les autres capacités sont invoquées directement via la skill Dailybot +- **Ce que l'addon DWP connecte :** quatre rapports du cycle de vie du plan (kickoff, tâche significative, bloqué, achèvement) via la sous-skill `report` de dailybot ; application déterministe optionnelle par hooks (`dailybot hook`, CLI `>= 3.7.0`) +- **Skill jumelée :** installer [DailybotHQ/agent-skill](https://github.com/DailybotHQ/agent-skill) (actuellement **3.10.3**) expose **14 capacités** — chat sur Slack/Teams/Discord/Google Chat, check-ins, autorisation de formulaires, ask AI, kudos, clés API par dépôt (`.dailybot/env.json`), e-mail et plus. L'addon DWP ne connecte que **report** ; les autres capacités sont invoquées directement via la skill Dailybot - **Auth :** entièrement reportée à la skill Dailybot (`dailybot login` ou `DAILYBOT_API_KEY`) ; cet addon ne stocke jamais de credentials - **Garde-fou neutre vis-à-vis du fournisseur :** le DWP central a **zéro** dépendance à Dailybot ; ne jamais installer automatiquement pour tout le monde - **Quand proposé :** le développeur ou l'équipe utilise déjà Dailybot, ou demande explicitement des rapports d'équipe diff --git a/src/content/spec/hi/addons.md b/src/content/spec/hi/addons.md index 7576e27..dd41c1d 100644 --- a/src/content/spec/hi/addons.md +++ b/src/content/spec/hi/addons.md @@ -41,8 +41,8 @@ section: Addons डेवलपर की **Dailybot टीम** से ऑप्ट-इन कनेक्शन एजेंट प्रगति दृश्यता के लिए। - **Kit पृष्ठ:** [Dailybot](/kit/dailybot) — पूर्ण क्षमता संदर्भ -- **DWP ऐडऑन क्या जोड़ता है:** dailybot `report` sub-skill के माध्यम से चार योजना-जीवनचक्र रिपोर्ट (kickoff, significant task, blocked, completion); वैकल्पिक deterministic हुक प्रवर्तन (`dailybot hook`, CLI `>= 3.1.2`) -- **जोड़ी गई स्किल:** [DailybotHQ/agent-skill](https://github.com/DailybotHQ/agent-skill) (वर्तमान में **3.4.0**) इंस्टॉल करने से **13 क्षमताएँ** — Slack/Teams/Discord/Google Chat पर chat, check-ins, forms authoring, ask AI, kudos, email, और अधिक। DWP ऐडऑन केवल **report** जोड़ता है; अन्य क्षमताएँ Dailybot स्किल के माध्यम से सीधे invoke होती हैं +- **DWP ऐडऑन क्या जोड़ता है:** dailybot `report` sub-skill के माध्यम से चार योजना-जीवनचक्र रिपोर्ट (kickoff, significant task, blocked, completion); वैकल्पिक deterministic हुक प्रवर्तन (`dailybot hook`, CLI `>= 3.7.0`) +- **जोड़ी गई स्किल:** [DailybotHQ/agent-skill](https://github.com/DailybotHQ/agent-skill) (वर्तमान में **3.10.3**) इंस्टॉल करने से **14 क्षमताएँ** — Slack/Teams/Discord/Google Chat पर chat, check-ins, forms authoring, ask AI, kudos, per-repo API keys (`.dailybot/env.json`), email, और अधिक। DWP ऐडऑन केवल **report** जोड़ता है; अन्य क्षमताएँ Dailybot स्किल के माध्यम से सीधे invoke होती हैं - **Auth:** पूर्णतः Dailybot स्किल को सौंपा (`dailybot login` या `DAILYBOT_API_KEY`); यह ऐडऑन कभी credentials संग्रहीत नहीं करता - **Vendor-neutral guardrail:** कोर DWP की Dailybot पर **शून्य** निर्भरता; कभी सभी के लिए स्वतः इंस्टॉल न करें - **कब प्रस्तावित:** डेवलपर या टीम पहले से Dailybot उपयोग करती हो, या स्पष्ट रूप से टीम रिपोर्टिंग माँगे diff --git a/src/content/spec/id/addons.md b/src/content/spec/id/addons.md index 13dcccf..5c869c8 100644 --- a/src/content/spec/id/addons.md +++ b/src/content/spec/id/addons.md @@ -41,8 +41,8 @@ Setup `.devcontainer/` + `docker/` berbasis compose yang dirasionalkan dari stac Koneksi opt-in ke **tim Dailybot** pengembang untuk visibilitas progres agen. - **Halaman kit:** [Dailybot](/kit/dailybot) — referensi kemampuan lengkap -- **Yang dihubungkan addon DWP:** empat laporan siklus hidup rencana (kickoff, significant task, blocked, completion) melalui sub-skill dailybot `report`; penegakan hook deterministik opsional (`dailybot hook`, CLI `>= 3.1.2`) -- **Skill yang dipasangkan:** menginstal [DailybotHQ/agent-skill](https://github.com/DailybotHQ/agent-skill) (saat ini **3.4.0**) mengekspos **13 kemampuan** — chat di Slack/Teams/Discord/Google Chat, check-in, authoring formulir, ask AI, kudos, email, dan lainnya. Addon DWP hanya menghubungkan **report**; kemampuan lain dipanggil melalui skill Dailybot secara langsung +- **Yang dihubungkan addon DWP:** empat laporan siklus hidup rencana (kickoff, significant task, blocked, completion) melalui sub-skill dailybot `report`; penegakan hook deterministik opsional (`dailybot hook`, CLI `>= 3.7.0`) +- **Skill yang dipasangkan:** menginstal [DailybotHQ/agent-skill](https://github.com/DailybotHQ/agent-skill) (saat ini **3.10.3**) mengekspos **14 kemampuan** — chat di Slack/Teams/Discord/Google Chat, check-in, authoring formulir, ask AI, kudos, API key per repo (`.dailybot/env.json`), email, dan lainnya. Addon DWP hanya menghubungkan **report**; kemampuan lain dipanggil melalui skill Dailybot secara langsung - **Auth:** sepenuhnya ditunda ke skill Dailybot (`dailybot login` atau `DAILYBOT_API_KEY`); addon ini tidak pernah menyimpan kredensial - **Pagar vendor-neutral:** DWP inti memiliki **nol** ketergantungan Dailybot; jangan pernah menginstal otomatis untuk semua orang - **Kapan ditawarkan:** pengembang atau tim sudah menggunakan Dailybot, atau secara eksplisit meminta pelaporan tim diff --git a/src/content/spec/it/addons.md b/src/content/spec/it/addons.md index 2d03d99..e159ca3 100644 --- a/src/content/spec/it/addons.md +++ b/src/content/spec/it/addons.md @@ -41,8 +41,8 @@ Un setup `.devcontainer/` + `docker/` basato su compose, ragionato dallo stack r Una connessione opt-in al **team Dailybot** dello sviluppatore per la visibilità sui progressi degli agenti. - **Pagina kit:** [Dailybot](/kit/dailybot) — riferimento completo delle capacità -- **Cosa collega l'addon DWP:** quattro report del ciclo di vita del piano (kickoff, significant task, blocked, completion) tramite la sub-skill dailybot `report`; enforcement opzionale deterministica degli hook (`dailybot hook`, CLI `>= 3.1.2`) -- **Skill abbinata:** installare [DailybotHQ/agent-skill](https://github.com/DailybotHQ/agent-skill) (attualmente **3.4.0**) espone **13 capacità** — chat su Slack/Teams/Discord/Google Chat, check-in, authoring moduli, ask AI, kudos, email e altro. L'addon DWP collega solo **report**; le altre capacità si invocano direttamente tramite la skill Dailybot +- **Cosa collega l'addon DWP:** quattro report del ciclo di vita del piano (kickoff, significant task, blocked, completion) tramite la sub-skill dailybot `report`; enforcement opzionale deterministica degli hook (`dailybot hook`, CLI `>= 3.7.0`) +- **Skill abbinata:** installare [DailybotHQ/agent-skill](https://github.com/DailybotHQ/agent-skill) (attualmente **3.10.3**) espone **14 capacità** — chat su Slack/Teams/Discord/Google Chat, check-in, authoring moduli, ask AI, kudos, API key per repository (`.dailybot/env.json`), email e altro. L'addon DWP collega solo **report**; le altre capacità si invocano direttamente tramite la skill Dailybot - **Auth:** completamente delegata alla skill Dailybot (`dailybot login` o `DAILYBOT_API_KEY`); questo addon non memorizza mai credenziali - **Guardrail vendor-neutral:** il DWP di base ha **zero** dipendenze da Dailybot; non installare mai automaticamente per tutti - **Quando offerto:** lo sviluppatore o il team usa già Dailybot, oppure chiede esplicitamente report per il team diff --git a/src/content/spec/ja/addons.md b/src/content/spec/ja/addons.md index 882495b..cf10848 100644 --- a/src/content/spec/ja/addons.md +++ b/src/content/spec/ja/addons.md @@ -41,8 +41,8 @@ section: Addons エージェント進捗可視化のための開発者の **Dailybot チーム**へのオプトイン接続。 - **キットページ：** [Dailybot](/kit/dailybot)——完全な能力リファレンス -- **DWP アドオンが接続するもの：** dailybot `report` サブスキル経由の 4 つのプランライフサイクルレポート（kickoff、significant task、blocked、completion）；オプションの決定論的フック強制（`dailybot hook`、CLI `>= 3.1.2`） -- **ペアスキル：** [DailybotHQ/agent-skill](https://github.com/DailybotHQ/agent-skill)（現在 **3.4.0**）のインストールで **13 の能力**——Slack/Teams/Discord/Google Chat チャット、チェックイン、フォーム作成、Ask AI、kudos、メールなど。DWP アドオンは **report** のみ接続；他の能力は Dailybot スキルを直接呼び出す +- **DWP アドオンが接続するもの：** dailybot `report` サブスキル経由の 4 つのプランライフサイクルレポート（kickoff、significant task、blocked、completion）；オプションの決定論的フック強制（`dailybot hook`、CLI `>= 3.7.0`） +- **ペアスキル：** [DailybotHQ/agent-skill](https://github.com/DailybotHQ/agent-skill)（現在 **3.10.3**）のインストールで **14 の能力**——Slack/Teams/Discord/Google Chat チャット、チェックイン、フォーム作成、Ask AI、kudos、リポジトリごとの API キー（`.dailybot/env.json`）、メールなど。DWP アドオンは **report** のみ接続；他の能力は Dailybot スキルを直接呼び出す - **認証：** Dailybot スキルに完全委譲（`dailybot login` または `DAILYBOT_API_KEY`）；このアドオンは認証情報を保存しない - **ベンダーニュートラルガードレール：** コア DWP は Dailybot 依存**ゼロ**；全員に自動インストールしない - **提供タイミング：** 開発者またはチームが既に Dailybot を利用、またはチームレポートを明示的に要求 diff --git a/src/content/spec/ko/addons.md b/src/content/spec/ko/addons.md index d1c9073..a8f7e03 100644 --- a/src/content/spec/ko/addons.md +++ b/src/content/spec/ko/addons.md @@ -41,8 +41,8 @@ section: Addons 에이전트 진행 가시성을 위한 개발자 **Dailybot 팀**에 대한 옵트인 연결. - **키트 페이지:** [Dailybot](/kit/dailybot) — 전체 기능 참조 -- **DWP 애드온이 연결하는 것:** dailybot `report` 서브스킬을 통한 네 가지 플랜 라이프사이클 보고(kickoff, significant task, blocked, completion); 선택적 결정론적 훅 강제(`dailybot hook`, CLI `>= 3.1.2`) -- **페어링 스킬:** [DailybotHQ/agent-skill](https://github.com/DailybotHQ/agent-skill)(현재 **3.4.0**) 설치 시 **13가지 기능** — Slack/Teams/Discord/Google Chat 채팅, 체크인, 폼 작성, Ask AI, kudos, 이메일 등. DWP 애드온은 **report**만 연결; 다른 기능은 Dailybot 스킬을 직접 호출 +- **DWP 애드온이 연결하는 것:** dailybot `report` 서브스킬을 통한 네 가지 플랜 라이프사이클 보고(kickoff, significant task, blocked, completion); 선택적 결정론적 훅 강제(`dailybot hook`, CLI `>= 3.7.0`) +- **페어링 스킬:** [DailybotHQ/agent-skill](https://github.com/DailybotHQ/agent-skill)(현재 **3.10.3**) 설치 시 **14가지 기능** — Slack/Teams/Discord/Google Chat 채팅, 체크인, 폼 작성, Ask AI, kudos, 저장소별 API 키(`.dailybot/env.json`), 이메일 등. DWP 애드온은 **report**만 연결; 다른 기능은 Dailybot 스킬을 직접 호출 - **인증:** Dailybot 스킬에 완전 위임(`dailybot login` 또는 `DAILYBOT_API_KEY`); 이 애드온은 자격 증명을 저장하지 않음 - **벤더 중립 가드레일:** 핵심 DWP는 Dailybot 의존성 **제로**; 모든 사람에게 자동 설치하지 않음 - **제안 시점:** 개발자나 팀이 이미 Dailybot을 사용하거나 팀 보고를 명시적으로 요청 diff --git a/src/content/spec/pl/addons.md b/src/content/spec/pl/addons.md index 2bd69ac..71680c6 100644 --- a/src/content/spec/pl/addons.md +++ b/src/content/spec/pl/addons.md @@ -41,8 +41,8 @@ Konfiguracja `.devcontainer/` + `docker/` oparta na compose, wywnioskowana z wyk Opcjonalne połączenie z **zespołem Dailybot** programisty dla widoczności postępu agenta. - **Strona kit:** [Dailybot](/kit/dailybot) — pełna referencja możliwości -- **Co łączy addon DWP:** cztery raporty cyklu życia planu (kickoff, significant task, blocked, completion) przez sub-skill dailybot `report`; opcjonalne deterministyczne wymuszanie hooków (`dailybot hook`, CLI `>= 3.1.2`) -- **Sparowany skill:** instalacja [DailybotHQ/agent-skill](https://github.com/DailybotHQ/agent-skill) (obecnie **3.4.0**) udostępnia **13 możliwości** — czat na Slack/Teams/Discord/Google Chat, check-iny, tworzenie formularzy, ask AI, kudos, e-mail i więcej. Addon DWP łączy tylko **report**; pozostałe możliwości wywołuje się bezpośrednio przez skill Dailybot +- **Co łączy addon DWP:** cztery raporty cyklu życia planu (kickoff, significant task, blocked, completion) przez sub-skill dailybot `report`; opcjonalne deterministyczne wymuszanie hooków (`dailybot hook`, CLI `>= 3.7.0`) +- **Sparowany skill:** instalacja [DailybotHQ/agent-skill](https://github.com/DailybotHQ/agent-skill) (obecnie **3.10.3**) udostępnia **14 możliwości** — czat na Slack/Teams/Discord/Google Chat, check-iny, tworzenie formularzy, ask AI, kudos, klucze API per-repo (`.dailybot/env.json`), e-mail i więcej. Addon DWP łączy tylko **report**; pozostałe możliwości wywołuje się bezpośrednio przez skill Dailybot - **Auth:** w pełni delegowane do skilla Dailybot (`dailybot login` lub `DAILYBOT_API_KEY`); ten addon nigdy nie przechowuje poświadczeń - **Zabezpieczenie neutralne wobec dostawcy:** podstawowy DWP ma **zero** zależności od Dailybot; nigdy nie instaluj automatycznie dla wszystkich - **Kiedy proponować:** programista lub zespół już korzysta z Dailybot lub wyraźnie prosi o raportowanie zespołowe diff --git a/src/content/spec/pt/addons.md b/src/content/spec/pt/addons.md index 9ca14ad..746fcd6 100644 --- a/src/content/spec/pt/addons.md +++ b/src/content/spec/pt/addons.md @@ -41,8 +41,8 @@ Uma configuração `.devcontainer/` + `docker/` baseada em compose, raciocinada Uma ligação opcional à **equipa Dailybot** do programador para visibilidade do progresso do agente. - **Página do kit:** [Dailybot](/kit/dailybot) — referência completa de capacidades -- **O que o addon DWP liga:** quatro relatórios do ciclo de vida do plano (kickoff, tarefa significativa, bloqueado, conclusão) via sub-skill `report` do dailybot; reforço determinístico opcional por hooks (`dailybot hook`, CLI `>= 3.1.2`) -- **Skill emparelhada:** instalar [DailybotHQ/agent-skill](https://github.com/DailybotHQ/agent-skill) (atualmente **3.4.0**) expõe **13 capacidades** — chat no Slack/Teams/Discord/Google Chat, check-ins, autoría de formulários, ask AI, kudos, email e mais. O addon DWP liga apenas **report**; outras capacidades são invocadas diretamente pela skill Dailybot +- **O que o addon DWP liga:** quatro relatórios do ciclo de vida do plano (kickoff, tarefa significativa, bloqueado, conclusão) via sub-skill `report` do dailybot; reforço determinístico opcional por hooks (`dailybot hook`, CLI `>= 3.7.0`) +- **Skill emparelhada:** instalar [DailybotHQ/agent-skill](https://github.com/DailybotHQ/agent-skill) (atualmente **3.10.3**) expõe **14 capacidades** — chat no Slack/Teams/Discord/Google Chat, check-ins, autoría de formulários, ask AI, kudos, chaves API por repositório (`.dailybot/env.json`), email e mais. O addon DWP liga apenas **report**; outras capacidades são invocadas diretamente pela skill Dailybot - **Auth:** totalmente adiada para a skill Dailybot (`dailybot login` ou `DAILYBOT_API_KEY`); este addon nunca armazena credenciais - **Salvaguarda neutra em relação ao fornecedor:** o DWP central tem **zero** dependência do Dailybot; nunca instalar automaticamente para todos - **Quando oferecido:** programador ou equipa já usa Dailybot, ou pede explicitamente relatórios à equipa diff --git a/src/content/spec/ru/addons.md b/src/content/spec/ru/addons.md index 98cefbd..a535e9a 100644 --- a/src/content/spec/ru/addons.md +++ b/src/content/spec/ru/addons.md @@ -41,8 +41,8 @@ section: Addons Опциональное подключение к **команде Dailybot** разработчика для видимости прогресса агента. - **Страница kit:** [Dailybot](/kit/dailybot) — полная справка по возможностям -- **Что подключает аддон DWP:** четыре отчёта жизненного цикла плана (kickoff, significant task, blocked, completion) через поднавык dailybot `report`; опциональное детерминированное принудительное применение хуков (`dailybot hook`, CLI `>= 3.1.2`) -- **Парный навык:** установка [DailybotHQ/agent-skill](https://github.com/DailybotHQ/agent-skill) (сейчас **3.4.0**) раскрывает **13 возможностей** — чат в Slack/Teams/Discord/Google Chat, чек-ины, создание форм, Ask AI, kudos, email и др. Аддон DWP подключает только **report**; остальные возможности вызываются через навык Dailybot напрямую +- **Что подключает аддон DWP:** четыре отчёта жизненного цикла плана (kickoff, significant task, blocked, completion) через поднавык dailybot `report`; опциональное детерминированное принудительное применение хуков (`dailybot hook`, CLI `>= 3.7.0`) +- **Парный навык:** установка [DailybotHQ/agent-skill](https://github.com/DailybotHQ/agent-skill) (сейчас **3.10.3**) раскрывает **14 возможностей** — чат в Slack/Teams/Discord/Google Chat, чек-ины, создание форм, Ask AI, kudos, API-ключи на репозиторий (`.dailybot/env.json`), email и др. Аддон DWP подключает только **report**; остальные возможности вызываются через навык Dailybot напрямую - **Аутентификация:** полностью отложена до навыка Dailybot (`dailybot login` или `DAILYBOT_API_KEY`); этот аддон никогда не хранит учётные данные - **Ограничение нейтральности по вендору:** базовый DWP имеет **нулевую** зависимость от Dailybot; никогда не устанавливать автоматически для всех - **Когда предлагается:** разработчик или команда уже используют Dailybot или явно просят отчётность для команды diff --git a/src/content/spec/th/addons.md b/src/content/spec/th/addons.md index 1832201..8a1cd25 100644 --- a/src/content/spec/th/addons.md +++ b/src/content/spec/th/addons.md @@ -41,8 +41,8 @@ section: Addons การเชื่อม opt-in กับ **ทีม Dailybot** ของนักพัฒนาเพื่อมองเห็นความคืบหน้าของเอเจนต์ - **หน้า kit:** [Dailybot](/kit/dailybot) — อ้างอิงความสามารถครบ -- **สิ่งที่ DWP addon เชื่อม:** รายงาน lifecycle แผนสี่แบบ (kickoff, significant task, blocked, completion) ผ่าน sub-skill dailybot `report`; การบังคับใช้ hook แบบ deterministic แบบเลือกได้ (`dailybot hook`, CLI `>= 3.1.2`) -- **Skill คู่กัน:** ติดตั้ง [DailybotHQ/agent-skill](https://github.com/DailybotHQ/agent-skill) (ปัจจุบัน **3.4.0**) เปิด **13 ความสามารถ** — แชทบน Slack/Teams/Discord/Google Chat check-in การเขียนฟอร์ม ask AI kudos อีเมล และอื่นๆ DWP addon เชื่อมเฉพาะ **report** ความสามารถอื่นเรียกผ่าน skill Dailybot โดยตรง +- **สิ่งที่ DWP addon เชื่อม:** รายงาน lifecycle แผนสี่แบบ (kickoff, significant task, blocked, completion) ผ่าน sub-skill dailybot `report`; การบังคับใช้ hook แบบ deterministic แบบเลือกได้ (`dailybot hook`, CLI `>= 3.7.0`) +- **Skill คู่กัน:** ติดตั้ง [DailybotHQ/agent-skill](https://github.com/DailybotHQ/agent-skill) (ปัจจุบัน **3.10.3**) เปิด **14 ความสามารถ** — แชทบน Slack/Teams/Discord/Google Chat check-in การเขียนฟอร์ม ask AI kudos per-repo API keys (`.dailybot/env.json`) อีเมล และอื่นๆ DWP addon เชื่อมเฉพาะ **report** ความสามารถอื่นเรียกผ่าน skill Dailybot โดยตรง - **Auth:** มอบหมายทั้งหมดให้ skill Dailybot (`dailybot login` หรือ `DAILYBOT_API_KEY`) addon นี้ไม่เก็บ credentials - **Guardrail แบบ vendor-neutral:** DWP หลัก **ไม่พึ่งพา** Dailybot เลย อย่าติดตั้งอัตโนมัติให้ทุกคน - **เมื่อเสนอ:** นักพัฒนาหรือทีมใช้ Dailybot อยู่แล้ว หรือขอการรายงานทีมอย่างชัดเจน diff --git a/src/content/spec/tr/addons.md b/src/content/spec/tr/addons.md index e657ff8..f851974 100644 --- a/src/content/spec/tr/addons.md +++ b/src/content/spec/tr/addons.md @@ -41,8 +41,8 @@ Tespit edilen stack'ten akıl yürütülmüş compose tabanlı `.devcontainer/` Agent ilerleme görünürlüğü için geliştiricinin **Dailybot ekibine** opt-in bağlantı. - **Kit sayfası:** [Dailybot](/kit/dailybot) — tam yetenek referansı -- **DWP eklentisinin bağladıkları:** dailybot `report` alt-skill'i ile dört plan yaşam döngüsü raporu (kickoff, significant task, blocked, completion); isteğe bağlı deterministik hook zorlaması (`dailybot hook`, CLI `>= 3.1.2`) -- **Eşleşen skill:** [DailybotHQ/agent-skill](https://github.com/DailybotHQ/agent-skill) kurulumu (şu an **3.4.0**) **13 yetenek** sunar — Slack/Teams/Discord/Google Chat sohbeti, check-in'ler, form authoring, ask AI, kudos, e-posta ve daha fazlası. DWP eklentisi yalnızca **report**'u bağlar; diğer yetenekler doğrudan Dailybot skill üzerinden çağrılır +- **DWP eklentisinin bağladıkları:** dailybot `report` alt-skill'i ile dört plan yaşam döngüsü raporu (kickoff, significant task, blocked, completion); isteğe bağlı deterministik hook zorlaması (`dailybot hook`, CLI `>= 3.7.0`) +- **Eşleşen skill:** [DailybotHQ/agent-skill](https://github.com/DailybotHQ/agent-skill) kurulumu (şu an **3.10.3**) **14 yetenek** sunar — Slack/Teams/Discord/Google Chat sohbeti, check-in'ler, form authoring, ask AI, kudos, depo başına API anahtarları (`.dailybot/env.json`), e-posta ve daha fazlası. DWP eklentisi yalnızca **report**'u bağlar; diğer yetenekler doğrudan Dailybot skill üzerinden çağrılır - **Auth:** tamamen Dailybot skill'e ertelenmiş (`dailybot login` veya `DAILYBOT_API_KEY`); bu eklenti asla kimlik bilgisi saklamaz - **Vendor-neutral koruma:** temel DWP'nin Dailybot'a **sıfır** bağımlılığı vardır; herkes için otomatik kurmayın - **Ne zaman sunulur:** geliştirici veya ekip zaten Dailybot kullanıyor veya açıkça ekip raporlaması istiyor diff --git a/src/content/spec/uk/addons.md b/src/content/spec/uk/addons.md index 8939472..b0973d7 100644 --- a/src/content/spec/uk/addons.md +++ b/src/content/spec/uk/addons.md @@ -41,8 +41,8 @@ Compose-налаштування `.devcontainer/` + `docker/`, виведене Опційне підключення до **команди Dailybot** розробника для видимості прогресу агента. - **Сторінка kit:** [Dailybot](/kit/dailybot) — повна довідка можливостей -- **Що підключає DWP-аддон:** чотири звіти життєвого циклу плану (kickoff, significant task, blocked, completion) через sub-skill dailybot `report`; опційне детерміноване примусове виконання хуків (`dailybot hook`, CLI `>= 3.1.2`) -- **Парний скіл:** встановлення [DailybotHQ/agent-skill](https://github.com/DailybotHQ/agent-skill) (зараз **3.4.0**) відкриває **13 можливостей** — чат у Slack/Teams/Discord/Google Chat, check-in, авторство форм, ask AI, kudos, email тощо. DWP-аддон підключає лише **report**; інші можливості викликаються безпосередньо через скіл Dailybot +- **Що підключає DWP-аддон:** чотири звіти життєвого циклу плану (kickoff, significant task, blocked, completion) через sub-skill dailybot `report`; опційне детерміноване примусове виконання хуків (`dailybot hook`, CLI `>= 3.7.0`) +- **Парний скіл:** встановлення [DailybotHQ/agent-skill](https://github.com/DailybotHQ/agent-skill) (зараз **3.10.3**) відкриває **14 можливостей** — чат у Slack/Teams/Discord/Google Chat, check-in, авторство форм, ask AI, kudos, per-repo API keys (`.dailybot/env.json`), email тощо. DWP-аддон підключає лише **report**; інші можливості викликаються безпосередньо через скіл Dailybot - **Auth:** повністю делеговано скілу Dailybot (`dailybot login` або `DAILYBOT_API_KEY`); цей аддон ніколи не зберігає облікові дані - **Vendor-neutral guardrail:** основний DWP має **нульову** залежність від Dailybot; ніколи не встановлюйте автоматично для всіх - **Коли пропонувати:** розробник або команда вже використовує Dailybot або явно просить командне звітування diff --git a/src/content/spec/vi/addons.md b/src/content/spec/vi/addons.md index 81bfba8..8c28ea0 100644 --- a/src/content/spec/vi/addons.md +++ b/src/content/spec/vi/addons.md @@ -41,8 +41,8 @@ Thiết lập `.devcontainer/` + `docker/` dựa trên compose, suy luận từ Kết nối opt-in tới **nhóm Dailybot** của nhà phát triển để hiển thị tiến độ agent. - **Trang kit:** [Dailybot](/kit/dailybot) — tham chiếu khả năng đầy đủ -- **Addon DWP kết nối:** bốn báo cáo vòng đời kế hoạch (kickoff, significant task, blocked, completion) qua sub-skill dailybot `report`; thực thi hook xác định tùy chọn (`dailybot hook`, CLI `>= 3.1.2`) -- **Skill đi kèm:** cài [DailybotHQ/agent-skill](https://github.com/DailybotHQ/agent-skill) (hiện tại **3.4.0**) mở **13 khả năng** — chat trên Slack/Teams/Discord/Google Chat, check-in, tác giả biểu mẫu, ask AI, kudos, email và hơn thế. Addon DWP chỉ kết nối **report**; khả năng khác được gọi trực tiếp qua skill Dailybot +- **Addon DWP kết nối:** bốn báo cáo vòng đời kế hoạch (kickoff, significant task, blocked, completion) qua sub-skill dailybot `report`; thực thi hook xác định tùy chọn (`dailybot hook`, CLI `>= 3.7.0`) +- **Skill đi kèm:** cài [DailybotHQ/agent-skill](https://github.com/DailybotHQ/agent-skill) (hiện tại **3.10.3**) mở **14 khả năng** — chat trên Slack/Teams/Discord/Google Chat, check-in, tác giả biểu mẫu, ask AI, kudos, API key theo repo (`.dailybot/env.json`), email và hơn thế. Addon DWP chỉ kết nối **report**; khả năng khác được gọi trực tiếp qua skill Dailybot - **Auth:** hoàn toàn hoãn sang skill Dailybot (`dailybot login` hoặc `DAILYBOT_API_KEY`); addon này không bao giờ lưu thông tin xác thực - **Rào vendor-neutral:** DWP cốt lõi **không** phụ thuộc Dailybot; không bao giờ tự cài cho mọi người - **Khi đề xuất:** nhà phát triển hoặc nhóm đã dùng Dailybot, hoặc yêu cầu rõ ràng báo cáo nhóm diff --git a/src/content/spec/zh/addons.md b/src/content/spec/zh/addons.md index 01753a5..13ef272 100644 --- a/src/content/spec/zh/addons.md +++ b/src/content/spec/zh/addons.md @@ -41,8 +41,8 @@ section: Addons 与开发者 **Dailybot 团队**的可选连接，用于代理进展可见性。 - **套件页：** [Dailybot](/kit/dailybot)——完整能力参考 -- **DWP 附加组件接入的内容：** 通过 dailybot `report` 子技能的四个计划生命周期报告（kickoff、significant task、blocked、completion）；可选确定性钩子强制层（`dailybot hook`，CLI `>= 3.1.2`） -- **配套技能：** 安装 [DailybotHQ/agent-skill](https://github.com/DailybotHQ/agent-skill)（当前 **3.4.0**）暴露 **13 项能力**——在 Slack/Teams/Discord/Google Chat 上聊天、签到、表单编写、Ask AI、kudos、电子邮件等。DWP 附加组件仅接入 **report**；其他能力通过 Dailybot 技能直接调用 +- **DWP 附加组件接入的内容：** 通过 dailybot `report` 子技能的四个计划生命周期报告（kickoff、significant task、blocked、completion）；可选确定性钩子强制层（`dailybot hook`，CLI `>= 3.7.0`） +- **配套技能：** 安装 [DailybotHQ/agent-skill](https://github.com/DailybotHQ/agent-skill)（当前 **3.10.3**）暴露 **14 项能力**——在 Slack/Teams/Discord/Google Chat 上聊天、签到、表单编写、Ask AI、kudos、每仓库 API 密钥（`.dailybot/env.json`）、电子邮件等。DWP 附加组件仅接入 **report**；其他能力通过 Dailybot 技能直接调用 - **认证：** 完全延后至 Dailybot 技能（`dailybot login` 或 `DAILYBOT_API_KEY`）；此附加组件从不存储凭据 - **供应商中立护栏：** 核心 DWP 对 Dailybot **零**依赖；切勿为所有人自动安装 - **何时提供：** 开发者或团队已在使用 Dailybot，或明确要求团队报告