# Dailybot Custom Form Template > 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. - **Type:** Skill - **Install:** `agentstack add skill-dailybothq-agent-skill-custom-template` - **Verified:** Yes — security-reviewed for prompt injection and unsafe behavior - **Seller:** [DailybotHQ](https://agentstack.voostack.com/s/dailybothq) - **Installs:** 0 - **Category:** [Agent Skills](https://agentstack.voostack.com/c/agent-skills) - **Latest version:** 0.1.0 - **License:** MIT - **Upstream author:** [DailybotHQ](https://github.com/DailybotHQ) - **Source:** https://github.com/DailybotHQ/agent-skill/tree/main/skills/dailybot/forms/_custom-template ## Install ```sh agentstack add skill-dailybothq-agent-skill-custom-template ``` Requires the [AgentStack CLI](https://agentstack.voostack.com/docs/cli). Works with Claude Code, Cursor, and any MCP-compatible agent. ## About # Custom Form Skill — Starter Template > [!IMPORTANT] > **Do not use this file in place.** It lives inside the universal Dailybot skill pack (`.agents/skills/dailybot/`) only as a reference. **Copy it** to your own repo as: > > ```text > .agents/skills/dailybot-custom//SKILL.md > ``` > > The universal Dailybot skill pack is **managed by `skills-lock.json`** and rewritten on every upgrade. Anything you place inside `.agents/skills/dailybot/` will be overwritten. Anything under `.agents/skills/dailybot-custom/` is **customer-owned** and the installer never touches it. That separation is the entire point — keep the line clean. --- ## When the universal skill loads this custom file The universal `dailybot-forms` skill resolves a per-form custom skill by reading `.dailybot/profile.json` in the repo root and looking up the current form under `vars.custom_form_skills`: ```json { "vars": { "custom_form_skills": { "by_uuid": { "": ".agents/skills/dailybot-custom/" }, "by_slug": { "": ".agents/skills/dailybot-custom/" } } } } ``` When either lookup matches, the universal skill stops and loads this file. Everything below this point is your custom workflow logic — write it for the specific form this skill targets. --- ## 1 — Auth User-scoped Bearer token (`dailybot login`). This is identical to the universal forms skill — see [`../../shared/auth.md`](../../shared/auth.md). If the developer doesn't have a session, fall back to the universal skill's auth steps; don't reinvent them here. --- ## 2 — State machine reference (fill in) Document the workflow this form uses. Read it from `dailybot form get --json` once and pin the canonical version here so future-you doesn't have to re-derive it. ``` draft → review "Send for review" review → released "Mark released" review → draft "Back to draft" released → (final, sticky unless allow_reopen_from_final_state=true) ``` Keep this in sync with the server-side workflow. The server is the source of truth for `allowed_transitions`; this section is documentation only. --- ## 3 — Per-state required fields Some forms expect specific questions to be answered before moving forward. Document the contract per state: | State | Required answers before transitioning out | |-------|-------------------------------------------| | `draft` | service name, release notes | | `review` | reviewer list, regression-test status | | `released` | release URL, channel-routing target | The custom skill should validate these locally **before** invoking the CLI's `transition` command, so the developer sees a clear "you need to fill X first" instead of a server-side audience error. --- ## 4 — Default values & autofill If the form has fields the agent can fill from session context, document the source mapping: | Form question | Source | |---------------|--------| | `service_name` | repo name from `.dailybot/profile.json` → `default_metadata.repo` | | `released_by` | logged-in user from `dailybot status --auth --json` | | `branch` | `git rev-parse --abbrev-ref HEAD` | Always confirm the autofilled values with the developer before submitting. --- ## 5 — Channel routing reminders If a transition triggers a side-effect (post to Slack, page on-call, email stakeholders), document it here so the agent surfaces the side-effect during the confirmation prompt: > "Moving this response to `released` will notify `#releases` in Slack and email the stakeholders list. Confirm? (yes / cancel)" The server owns the actual notifications — this section is about what to tell the developer in the confirmation prompt. --- ## 6 — Recovery flows What does the agent do when: - The latest response is in a final state but the developer says "I need to re-open" → guide them to a new response (or, if they own the form, suggest `allow_reopen_from_final_state=true`). - The developer's audience does not include the requested transition (`form_response_change_state_forbidden`) → tell them who can do it; do not retry. - A required field is missing → list the gaps, ask the developer to fill them, then re-attempt the transition. --- ## 7 — Reference implementation A complete reference implementation of this template lives as a custom skill at `.agents/skills/dailybot-custom//SKILL.md` in the consuming repo (a customer- or team-owned namespace, separate from this skill pack). Such a skill demonstrates per-state validation, autofill from repo metadata, and channel-routing reminders end-to-end. --- ## 8 — Keep customizations under `dailybot-custom/` | OK | Not OK | |----|--------| | `.agents/skills/dailybot-custom/coderelease-form/SKILL.md` | `.agents/skills/dailybot/forms/coderelease-form/SKILL.md` | | `.agents/skills/dailybot-custom/onboarding-survey/SKILL.md` | Editing the universal `.agents/skills/dailybot/forms/SKILL.md` directly | | Registering your skill in `.dailybot/profile.json` → `vars.custom_form_skills` | Hardcoding form UUIDs into the universal skill | If you find yourself wanting to edit the universal `dailybot-forms` skill to handle one specific form, stop and author a custom skill here instead. That's the contract the resolver exists to make safe. ## Source & license This open-source skill is cataloged on AgentStack and links to its original source — we do not rehost the code. - **Author:** [DailybotHQ](https://github.com/DailybotHQ) - **Source:** [DailybotHQ/agent-skill](https://github.com/DailybotHQ/agent-skill) - **License:** MIT Install and usage instructions live in the source repository linked above. ## Pricing - **Free** — Free ## Security capabilities Automated source analysis of v0.1.0 — what this tool can access: - **Network access:** no - **Filesystem access:** no - **Shell / process execution:** no - **Environment & secrets:** no - **Dynamic code execution:** no *"Yes" means the capability is present in the source — more access means more to trust, not that it is unsafe.* ## Versions - **0.1.0** — security scan: passed — Imported from the upstream source. ## Links - Listing page: https://agentstack.voostack.com/l/skill-dailybothq-agent-skill-custom-template - Seller: https://agentstack.voostack.com/s/dailybothq - Browse the marketplace: https://agentstack.voostack.com/browse --- Listed on AgentStack — the marketplace for AI agent skills and MCP servers. Every listing is security-reviewed. Creators keep 70%.