Individual skill
make-bot-ui
Build a small operator UI over an agent/webhook backend. Use when buttons or controls should trigger an agent workflow.
skills/make-bot-ui/SKILL.md
Source commit 79595c97d47b5400034fb985e67f1a00389a81af
What was checked
- Matches the observed repository HEAD
- Yes
- Scanner rules are current
- Yes
- Repository scan complete
- No
- Skill scan complete
- No
- Observed behavior
- Instructions only
- Last checked
- Nov 6, 2026
These are observations at the recorded commit, not a guarantee of safety. Review the source before running it.
Install this skill
Choose an agent in your Stack or copy a command below. Commands fetch the pinned commit and copy only this skill directory. Existing destinations are refused. Copying a command does not install anything.
An install command is unavailable: current rules, complete repository and skill scans, an eligible behavior level and a permitted license are required.
Repository context
- Repository stars (not skill ratings)
- 21
- Repository last updated
- Nov 1, 2026
- License
- MIT
Observed agent integration: No specific integration evidence. Standard SKILL.md installation does not imply verified compatibility.
- agent-skills Repository topic
- ai-agents Repository topic
- claude-code Repository topic
- codex Repository topic
- coding-agents Repository topic
- cursor Repository topic
- pstack Repository topic
- cline Repository topic
- copilot Repository topic
- gemini Repository topic
- design Derived category
- operations Derived category
- design-interface Derived category
Files and excerpt
File metadata and permitted, redacted excerpts come from the recorded scan. Source links are pinned to that commit.
Browse files
SKILL.mdcore · 692 bytes
Read excerpt
# Make Bot UI
1. Define the operator actions, payload schema, authentication boundary, and observable completion state before UI code.
2. Keep secrets server-side. Treat webhook URLs/tokens as credentials.
3. Implement the thinnest UI that exposes state, errors, retries, and idempotent request IDs.
4. Make every action safe under duplicate delivery or refresh.
5. Verify one full round trip through the real backend when `observe`/network access exists. Otherwise ship a deterministic local mock plus an explicit integration gap.