chore(skills): sync vendored dailybot skill pack to v3.13.0

.agents/docs/COMMANDS_REFERENCE.md

@@ -58,7 +58,7 @@ Project-scoped slash commands curated for `dailybot-cli` work. Each routes to a
 
 ## Dailybot agent skill pack (vendored)
 
-The full pack lives under [`../skills/dailybot/`](../skills/dailybot/) (router + 9 sub-skills). The router auto-routes by intent — read [`../skills/dailybot/SKILL.md`](../skills/dailybot/SKILL.md) and let it pick the right sub-skill. Each sub-skill is independently invocable; the full list lives in [`skills_agents_catalog.md`](skills_agents_catalog.md).
+The full pack lives under [`../skills/dailybot/`](../skills/dailybot/) (router + sixteen sub-skills, including labels + featured). The router auto-routes by intent — read [`../skills/dailybot/SKILL.md`](../skills/dailybot/SKILL.md) and let it pick the right sub-skill. Each sub-skill is independently invocable; the full list lives in [`skills_agents_catalog.md`](skills_agents_catalog.md).
 
 ---
 

.agents/docs/skills_agents_catalog.md

@@ -18,7 +18,7 @@ Slash commands. Invoked as `/<name>` (Claude Code) or `#<name>` (Codex/Cursor/Ge
 
 ### Dailybot agent skill pack (vendored from [`DailybotHQ/agent-skill`](https://github.com/DailybotHQ/agent-skill))
 
-The full pack lives under [`.agents/skills/dailybot/`](../skills/dailybot/) (router + fourteen sub-skills; vendored at **v3.11.0**). Every sub-skill requires `dailybot-cli >= 3.8.0` — the pack baseline. The router auto-routes by intent — read [`skills/dailybot/SKILL.md`](../skills/dailybot/SKILL.md) and let it pick the right sub-skill. Direct sub-skill entry points:
+The full pack lives under [`.agents/skills/dailybot/`](../skills/dailybot/) (router + sixteen sub-skills; vendored at **v3.13.0**). Every sub-skill requires `dailybot-cli >= 3.9.0` — the pack baseline. The router auto-routes by intent — read [`skills/dailybot/SKILL.md`](../skills/dailybot/SKILL.md) and let it pick the right sub-skill. Direct sub-skill entry points:
 
 | Slug | Procedure | Use when |
 |------|-----------|----------|
@@ -35,6 +35,8 @@ The full pack lives under [`.agents/skills/dailybot/`](../skills/dailybot/) (rou
 | `dailybot-conversation` | [`skills/dailybot/conversation/SKILL.md`](../skills/dailybot/conversation/SKILL.md) | Opening (or idempotently reusing) a Slack group DM with the bot + named teammates, then optionally posting a report (`conversation open -u … -m …`; Slack only, org-admin only) |
 | `dailybot-ask` | [`skills/dailybot/ask/SKILL.md`](../skills/dailybot/ask/SKILL.md) | Asking the Dailybot AI a one-shot, headless question |
 | `dailybot-workflow` | [`skills/dailybot/workflow/SKILL.md`](../skills/dailybot/workflow/SKILL.md) | Listing / reading / triggering org workflows — `workflow list` (incl. `--filter api_trigger`) / `workflow get` / `workflow trigger` (plan-gated) |
+| `dailybot-labels` | [`skills/dailybot/labels/SKILL.md`](../skills/dailybot/labels/SKILL.md) | Organization Labels — create/list/update/archive/delete and assign (or batch) to forms, check-ins, and workflows/automations (web chip-picker parity; `dailybot-cli >= 3.9.0`) |
+| `dailybot-featured` | [`skills/dailybot/featured/SKILL.md`](../skills/dailybot/featured/SKILL.md) | Private per-user Featured stars on forms, automations, and check-ins (not org Labels; `dailybot-cli >= 3.9.0`) |
 | `dailybot-env` | [`skills/dailybot/env/SKILL.md`](../skills/dailybot/env/SKILL.md) | Managing per-repo API keys in the opt-in, gitignored `.dailybot/env.json` (`env add/use/show/list/remove/off/on`) — be "logged into different orgs in different repos" |
 
 ### Deep Work Plan skill pack (vendored from [`DailybotHQ/deepworkplan-skill`](https://github.com/DailybotHQ/deepworkplan-skill))

.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, sending as a user's identity, and interactive buttons with approval flows, workflow triggers, modals, and callbacks), 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/trigger 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, list/read workflows, and trigger API-triggerable workflows with optional payloads — 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 — pack baseline `>= 3.8.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.11.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, sending as a user's identity, and interactive buttons with approval flows, workflow triggers, modals, and callbacks), open (or reuse) a Slack group DM with the bot and post a report to it, ask the Dailybot AI a question headlessly, **browse/read/trigger the workspace** (`me` / `org` / `user get`, kudos browsing, workflows), **manage organization Labels** (`dailybot label` CRUD + assign/batch on forms, check-ins, workflows) and **private Featured stars**, and **manage per-repo API keys** through `.dailybot/env.json` (pack baseline `dailybot-cli >= 3.9.0`). Routes to the right sub-skill based on intent. Use when the developer mentions Dailybot or wants to interact with their team.
+version: "3.13.0"
 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,7 @@ 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.8.0` — the skill-pack baseline for
+   `dailybot --version` (minimum `>= 3.9.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
@@ -51,7 +51,7 @@ machine — permissions, consent guarantees, and a self-audit you can run — is
 
 ## What it does
 
-Fourteen coordinated capabilities, with smart routing between them:
+Sixteen coordinated capabilities, with smart routing between them:
 
 | Capability | Sub-skill | When it fires |
 |------------|-----------|---------------|
@@ -67,9 +67,10 @@ Fourteen coordinated capabilities, with smart routing between them:
 | **Teams** | `dailybot-teams` | List teams, inspect members, resolve a team name → UUID (used as a resolver by other skills) — **plus account context**: `dailybot me` (who am I / role), `dailybot org` (which org), and `dailybot user get` (one user's profile) |
 | **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 or trigger** the org's workflows — `workflow list` (paginated/searchable, with `--filter api_trigger`), `workflow get`, and `workflow trigger` (fire an API-triggerable workflow with an optional JSON payload). Creating/editing workflows is web-app only. Plan-gated |
-| **Labels** | `dailybot-labels` | Create org Labels and assign them to forms, check-ins, and workflows (`label assign` / `label batch`) — same chip picker as the web app |
 | **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`. Pack baseline (`>= 3.8.0`) |
+| **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`. Pack baseline (`>= 3.9.0`) |
+| **Organization Labels** | `dailybot-labels` | Full org Labels lifecycle (`dailybot label entitlement/list/get/create/update/archive/delete/assign/batch`) — shared taxonomy for forms, check-ins, and workflows/automations; web chip-picker parity. Requires CLI `>= 3.9.0` |
+| **Featured stars** | `dailybot-featured` | Private per-user stars on Forms, Automations, Check-ins (`dailybot featured …`) |
 
 ## Install
 
@@ -87,7 +88,7 @@ reporting, ships **inside this skill** — follow **[Start here (first run)](#st
 
 ## Required Dailybot CLI version
 
-> **Baseline: `dailybot-cli >= 3.8.0`** for **every** sub-skill in the pack —
+> **Baseline: `dailybot-cli >= 3.9.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.
@@ -105,26 +106,25 @@ reporting, ships **inside this skill** — follow **[Start here (first run)](#st
 
 ### Why this minimum
 
-`3.8.0` is the release that shipped the interactive-button contract on
-`dailybot chat send` / `update` (`--buttons`, approval / workflow-button
-flags, modals, callbacks) and `dailybot workflow trigger` (plus
-`workflow list --filter api_trigger`). It also includes everything earlier
-floors already covered: `.dailybot/env.json` per-repo credentials (from
-3.7.0), reporting, hooks, forms and check-in authoring, kudos, teams,
-`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.8.0, ask the developer to run
-`dailybot upgrade` (or `pip install --upgrade 'dailybot-cli>=3.8.0'`)
+`3.9.0` is the release that shipped **organization Labels** (`dailybot label`
+CRUD + `assign` / `batch`) and **Featured** stars (`dailybot featured`), and
+it includes everything from `3.8.0`: the interactive-button contract on
+`dailybot chat send` / `update`, `dailybot workflow trigger`,
+`.dailybot/env.json` per-repo credentials, reporting, hooks, forms and
+check-in authoring, kudos, teams, `ask`, shared list query flags, and
+machine-readable error codes. Pinning one single floor keeps agent behavior
+predictable — no per-sub-skill version matrix.
+
+If `dailybot --version` reports below 3.9.0, ask the developer to run
+`dailybot upgrade` (or `pip install --upgrade 'dailybot-cli>=3.9.0'`)
 before using any sub-skill.
 
 ### Checking the installed version
 
 ```bash
 # Single-line, scriptable
 dailybot --version
-# → dailybot 3.8.0 (Python 3.12.4)
+# → dailybot 3.9.0 (Python 3.12.4)
 
 # Multi-line panel: version, Python runtime, install path, release notes link
 dailybot version
@@ -144,15 +144,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 the pack baseline (`dailybot-cli >= 3.8.0`),
+If the developer is below the pack baseline (`dailybot-cli >= 3.9.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.8.0'` (the pack baseline) |
+| pip      | `pip install 'dailybot-cli>=3.9.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` |
@@ -177,7 +177,7 @@ 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.8.0` pack baseline (the installer scripts, `pip`, and Homebrew all
+pin the `3.9.0` pack baseline (the installer scripts, `pip`, and Homebrew all
 accept a version pin):
 
 | Channel | Pin a version |
@@ -245,6 +245,8 @@ the full step-by-step workflow.
 | "browse kudos", "kudos I received / gave", "org kudos stats", "who's on the wall of fame?" | **Kudos** → read [`kudos/SKILL.md`](kudos/SKILL.md) § Browsing kudos |
 | "add a label to a form / check-in / workflow", "tag this standup with Sprint", "assign organization labels" | **Labels** → read [`labels/SKILL.md`](labels/SKILL.md) |
 | "list my workflows", "show workflows", "what's in workflow X?" | **Workflows** → read [`workflow/SKILL.md`](workflow/SKILL.md) |
+| "list organization labels", "create a label", "archive label X", "labels entitlement" | **Labels** → read [`labels/SKILL.md`](labels/SKILL.md) |
+| "star this form", "featured check-ins", "unfeature automation", "list my starred forms" | **Featured** → read [`featured/SKILL.md`](featured/SKILL.md) |
 | "trigger the deploy workflow", "fire automation X", "run workflow `<uuid>`", "trigger workflow with payload" | **Workflows** → read [`workflow/SKILL.md`](workflow/SKILL.md) § Step 4 (Trigger) |
 | "which channels can Dailybot post to?", "list report channels", "I need a channel UUID for the form / check-in" | **Channels** → read [`channels/SKILL.md`](channels/SKILL.md) |
 | "send a Slack message", "DM someone in chat", "post the deploy report to a channel (with a thread)", "edit that chat message I just sent", "ping the Engineering team in chat" | **Chat** → read [`chat/SKILL.md`](chat/SKILL.md) |

.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 "<question>"` 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.11.0"
+version: "3.13.0"
 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.8.0`** (the skill-pack baseline) — the `dailybot ask`
+> **Requires `dailybot-cli >= 3.9.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.8.0`):
+Confirm the command exists (`dailybot-cli >= 3.9.0`):
 
 ```bash
 dailybot ask --help 2>&1 | head -1

.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.11.0"
+version: "3.13.0"
 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.8.0`** (the skill-pack baseline). The `dailybot channels list`
+> **Requires `dailybot-cli >= 3.9.0`** (the skill-pack baseline). The `dailybot channels list`
 > command is available at this floor. If `dailybot --version` reports below
-> 3.8.0, ask the developer to run `dailybot upgrade`. See
+> 3.9.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