Menu
Publish a tested robot skill to the tidybot-skills org. Use when the user approves publishing a skill from the dev/ folder.
Install with Codex or Claude Copy this prompt, paste it into Codex, Claude, or another assistant, and let it review the skill page and install it for you.
Based on SOC occupation classification
Bundle a Tidybot skill and its dependencies into a single executable Python script for robot submission. Use when (1) submitting a multi-dependency skill to the robot, (2) preparing code for the /code/execute API, (3) resolving deps.txt dependency chains into one file.
Start, stop, restart, and health-check the MuJoCo sim server and agent server. Use when (1) launching the sim for skill development or testing, (2) restarting after a crash, (3) checking if the sim is running, (4) shutting down cleanly.
Audit all Tidybot repos for uncommitted/unpushed changes, diff workspace skills and personality files against the Tidybot-Universe setup repo, and summarize. Use when (1) the user says "push tidybot" or "commit tidybot", (2) reviewing what's changed before pushing, (3) syncing workspace files to the public repo.
Robot connection credentials and API endpoints — IP address, API key, base URL, and all key REST endpoints. Use when (1) making API calls to the robot, (2) executing code on the robot via /code/execute, (3) debugging connection issues or timeouts, (4) needing the robot IP or API key mid-session, (5) polling execution status or retrieving recorded frames, or (6) fetching SDK docs or the getting-started guide.
Execute a physical task on the robot (pick up, place, move, look at, etc.). Use when the user asks you to do something with/on the robot — any manipulation, navigation, or perception task. Triggers on requests like "pick up the banana," "put that on the plate," "go to the table," "what do you see," etc.
External services catalog — model endpoints, vision APIs, grasping backends, and Python client SDKs available to robot skills. Use when (1) a skill needs an external model or API, (2) checking what backend services are available, (3) debugging service timeouts or connection failures, (4) requesting a new service that doesn't exist yet, (5) downloading or using a service's Python client SDK.
| name | tidybot-skill-publish |
| description | Publish a tested robot skill to the tidybot-skills org. Use when the user approves publishing a skill from the dev/ folder. |
Only publish when the user explicitly approves. Ask first: "Want me to publish this so other Tidybots can use it?"
dev-tb- prefix with proper OpenClaw structure (SKILL.md, scripts/main.py, scripts/deps.txt)gh auth login)Rename from dev-tb- to tb-: Move the skill folder from dev-tb-my-skill/ to tb-my-skill/.
Create a repo in the tidybot-skills org. The repo name drops the tb- prefix (e.g. local tb-pick-up-object → remote tidybot-skills/pick-up-object):
gh repo create tidybot-skills/<skill-name-without-tb-prefix> --public
Push skill code to the new repo
Update catalog.json in tidybot-skills/wishlist:
{
"<skill-name>": {
"repo": "tidybot-skills/<skill-name>",
"description": "What the skill does",
"author": "<your-agent-name>",
"dependencies": ["dep1", "dep2"],
"success_rate": 0,
"total_trials": 0,
"institutions_tested": 0
}
}
Set success_rate and total_trials to 0 — public stats start fresh.
Update wishlist.json if this skill fulfills a wishlist item — set status to "done" and add the repo path
| Field | Description |
|---|---|
| repo | GitHub repo path (tidybot-skills/<name>) |
| description | What the skill does |
| author | Agent or person who built it |
| dependencies | List of skill repo names this depends on |
| success_rate | Percentage of successful trials (0–100) |
| total_trials | Total number of trial runs performed |
| institutions_tested | Number of distinct labs that tested this |
| Status | Meaning |
|---|---|
pending | Not started |
building | Agent working on it |
done | Available in catalog.json |