Skip to main content
skill CX Codex

amb-bot-dev — Claude Code skill: what it does, how to install

amb-bot-dev is a Claude Code skill that scaffolds and edits catalog bots for AnyModelBot. It activates when building a bot, adding a dedicated UI, or fixing issues flagged by amb-bot check.

MIT ★ 4,967 updated 2026-11-16

Install into Claude Code · Skills CLI (Vercel) All methods and platforms ↓
npx skills add modelflare-ai/AnyModelBot --skill amb-bot-dev -a claude-code
Open on GitHub

What amb-bot-dev does

The skill guides the creation and modification of AnyModelBot catalog bots inside bots/<id>/. It scaffolds directories with npm run bot -- new <id>, then fills in bot.json, persona.md, state.schema.json, and sample data across seven supported languages. Every bot also requires test scenarios in evals/, with at least three realistic tasks and one prompt injection case.

Bot interfaces import components strictly from /amb/botapp/kit/kit.js, rendering useBot().state and sending updates via send(text, action). Automated validation blocks fetch, browser storage, eval, inline styles, and external URLs. Verification runs through npm run bot -- check bots/<id>. Bot scripts cannot register custom tools or read user environment variables directly.

What it helps with

  • scaffold a new AnyModelBot catalog bot folder
  • build a restricted bot UI with kit.js components
  • add localized sample files and injection tests in evals
  • resolve validation failures reported by amb-bot check

Example prompts for the agent

  • Create a new catalog bot with id translator
  • Add a kit.js UI for the bot in bots/my-bot
  • Fix errors flagged by npm run bot -- check bots/my-bot

How to install amb-bot-dev

1Skills CLI (Vercel)

npx skills add modelflare-ai/AnyModelBot --skill amb-bot-dev -a claude-code

2Manually: put the files in place

~/.claude/skills/amb-bot-dev/SKILL.md

Copy the whole skill folder; for one project use .claude/skills/amb-bot-dev/

Step by step, with commands for each platform: How to install skills in Claude Code: five ways

Questions about amb-bot-dev

How to install amb-bot-dev in Claude Code?

Run npx skills add modelflare-ai/AnyModelBot --skill amb-bot-dev -a claude-code. You can also place the file directly at ~/.claude/skills/amb-bot-dev/SKILL.md.

What does amb-bot-dev do?

It provides development rules for AnyModelBot catalog items, including folder scaffolding, UI restrictions, and test cases. It ensures the bot complies with the framework check before shipping.

What is required to run amb-bot-dev?

You need Node.js and an AnyModelBot workspace with working npm run bot commands.

Source text

SKILL.md · MIT
---
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`.
---

# 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.

© modelflare-ai · MIT · modelflare-ai/AnyModelBot

Similar skills

All skills for Agent setup: memory, context, orchestration →

From the same set3

Project sponsors

Companies that keep this analytics open