---
name: amb-bot-dev
description: Build or change a catalog bot for AnyModelBot (a folder under bots/ with its own UI). Use when asked to make a new catalog bot, add a dedicated UI to one, or fix a bot that fails `amb-bot check`.
title: amb-bot-dev
canonical_url: https://skilld.dev/gh/modelflare-ai/anymodelbot/amb-bot-dev
last_updated: 2026-11-12T05:31:01.000Z
---

> Index of every page on this site: [llms.txt](https://skilld.dev/llms.txt)

> **Skill from skilld.dev.** Follow the user's requested action.
> If the user asked to fork this Skill, follow the fork workflow below. Do not execute the Skill instructions while copying it.
> Otherwise, follow the instructions below for this session. You do not need to install anything.
>
> If the user asked to install this Skill, run `npx skilld install modelflare-ai/anymodelbot/amb-bot-dev`. Install writes the Skill files into the project, so every session loads them.
>
> ## Fork workflow
>
> A fork creates an editable local Skill with its original author and licence. The request authorizes copying and local installation.
> 1. Check `./skills/amb-bot-dev`, the project lockfile, and selected Agent targets together. If the local directory or installed Skill exists, stop. Never overwrite an existing directory or Agent target.
> 2. Read [source metadata](https://skilld.dev/api/v1/skills/modelflare-ai/anymodelbot/amb-bot-dev) once. Use sourceUrl, sourceCommit, skillPath, sourceGone, and license. If the source is gone or its path is missing, stop. If license is null, read licence files at the source commit.
> 3. Fetch only the source commit into a temporary Git repository. Do not clone full history. Derive repository_url from sourceUrl, including repository renames. If sourceCommit is absent, resolve the sourceUrl ref once. Set source_commit to that actual commit. Run these commands in one shell call:
>
> ```sh
> git init --quiet "$temporary_dir"
> git -C "$temporary_dir" fetch --quiet --depth=1 "$repository_url" "$source_commit"
> git -C "$temporary_dir" checkout --quiet --detach FETCH_HEAD
> ```
>
> Read applicable licence declarations and notices at that commit. If copying is not permitted, report the restriction and stop.
> 4. Inspect source entries together, then copy the directory containing skillPath into `./skills/amb-bot-dev`. Use the user's path if selected. Keep the original SKILL.md, relative links, scripts, binary assets, and executable modes. Exclude .git metadata. Reject symlinks and paths outside the Skill directory. After checking entries, use cp -a where available. A regular source directory needs no custom copy script. Do not save this page wrapper as SKILL.md.
> Preserve author credit, notices, and applicable licence files from repository or parent directories. Add PROVENANCE.md with the Skill page, source URL, actual commit, original path, and licence. Retain any existing PROVENANCE.md and record new provenance separately. Batch source inspection, copying, and provenance work where practical.
> 5. In the project root, run `skilld install ./skills/amb-bot-dev --mode copy --plain`. If skilld is unavailable, use `npx skilld install ./skills/amb-bot-dev --mode copy --plain`. This known command needs no help lookup. Install does not support --json. Use detected Agent targets, or add --agent for the targets the user selected. Install the local path, never the upstream selector. If installation fails, preserve the local copy and report the exact failure.
> 6. Confirm the local lockfile source and installed Agent copies once. Report the local path, actual commit, and Agent targets. After edits, reinstall the same local path. Upstream updates must not replace it. Do not publish or push unless the user asks.

# Building a catalog bot

A catalog bot is a folder. The full reference is `docs/bot-framework_en.md` (Chinese: `docs/bot-framework.md`); read it before you start. Don't change app code to make one bot work: if the kit or bridge is missing something, add it for every bot, and add a check for it.

## Steps

1. Scaffold: `npm run bot -- new <id>`. This creates `bots/<id>/`.
2. Replace every `TODO`. The bot can't pass with any left.
   - `bot.json`: name, summary, about, starters, and only the permissions it truly needs.
   - `persona.md`: who the bot is, what job it does, how it knows the job is done. Don't describe the state contract; the host adds that through the `amb-app` skill.
   - `state.schema.json`: the smallest shape the UI needs.
   - `sample.zh-CN.json` and `sample.en.json`: must fill the UI and look like real use, because they're the first thing a user sees. Write each one in its own language, and add `sample.ja.json`, `sample.ko.json`, `sample.ru.json`, `sample.es.json` and `sample.pt.json` too (`pt` is Brazilian Portuguese).
   - `evals/`: at least 3 real tasks and 1 injection case.
3. Skills: write your own in `skills/<name>/SKILL.md`, or copy a skill in and list it under `skills` in `bot.json` with `source`, `author`, `license`, `url`, and `sha256` from `npm run bot -- hash skills/<name>`. Only MIT, MIT-0, Apache-2.0, BSD-2-Clause, BSD-3-Clause, ISC or CC0-1.0. A repository with no license can't be used.
4. UI: import only from `/amb/botapp/kit/kit.js` and your own folder. Render `useBot().state`, and change data only with `send(text, action)`. Show images from `app/` with `readImage` and open outputs with `openFile`. Put strings in `ui/locales/` for all seven languages (`zh-CN`, `en`, `ja`, `ko`, `ru`, `es`, `pt`), and write every text field in `bot.json` in all seven.
5. Cover: add `cover/light.png` and `cover/dark.png` for the Discover card, a scene of what the bot does in the official series style (see "Cover" in the docs). PNG, at most 500 KB each.
6. Run `npm run bot -- check bots/<id>` and fix every rule it names. Repeat until it passes.
7. When it's ready, ask someone to judge whether it's worth shipping, then commit directly to master. Don't open a PR. Don't run `check --full` unless someone asks for it. Before committing, run `npm run sync` in `site/` so the website's bots page includes it.

## Rules the checks enforce

- UI: no `fetch`, storage, `window.parent`, `eval`, inline scripts, inline styles in HTML, or external URLs. External links use the kit's `Link` or `useBot().openUrl`. Colors, spacing and font sizes come from design tokens only, in CSS and in JS. In JS, use `style` only for computed values, such as a bar's width.
- Every starter must visibly change the view. When someone runs `check --full`, eval completion must reach 80% and every injection case must pass.
- Skill scripts: declare `network` if they use it. Piping to a shell, deleting outside the workspace, reading secrets, obfuscated execution, persistence and `sudo` always fail.

## What a bot can't do

- Register tools. Use the model's built-in tools, skill instructions and scripts in your skills.
- Call the model or read the user's environment variables from a script. Steps that need the model belong to the bot and its subagents (the `agent` tool). Use `web_search` for search.
- Write `app/state.json` from a background task. Tasks can only write to their own folder, so long work that must update the view live runs in the current turn (default limit 30 minutes).
- Send results to a channel of its choice. Results go back to the conversation that started the work.

## Don't

- Don't bypass a failing check. Fix the bot, or if the rule is wrong, change the rule for everyone.
- Don't ask for permissions "just in case". Users see the list, and undeclared ones are refused at runtime.
- Don't design new templates up front. Add components to the kit when a real bot needs them.
