labs-graduation
Skill395k starsChanged todayMITView on GitHub
Move a feature out of Control UI Labs, either on by default or still off by default. Use when asked to promote, graduate or ship a Labs feature.
1 other project uses a version of this.
Adopted by
Steady: 0 new projects took it in the last 4 weeks, none the 4 weeks before.thin data
Most recently taken up by
- openclaw/openclawword for word, first seen Nov 15, 2026
Who's talking about moltbot/clawdbot
- SkillCurb“Clawdbot The NEW AI TOOL with Insane Results (Local Install)”YouTube · Jan 29, 2026 · 272 views
- LifeHacks_06“The Clawdbot Scandal: How 60,000 GitHub Stars Led to a $16M Crypto Scam & Forced Rebrand”YouTube · Jan 27, 2026 · 8 views
- amankhan1.substack.com“How to Get Clawdbot/Moltbot/OpenClaw Set Up in an Afternoon”the web · Feb 20, 2026
- medium.com“My First Three Days with Clawdbot (now Moltbot)”the web · Feb 20, 2026
- linkedin.com“Clawdbot Review: Powerful but Security Concerns”the web · Feb 20, 2026
The biggest 5 of 10 mentions linking to the repository that our crawl found. Each line is their own headline.
See all 10
Talked about on the web and YouTube (10 times).
On the web · 8
- Feb 20, 2026How to Get Clawdbot/Moltbot/OpenClaw Set Up in an Afternoon — amankhan1.substack.com
- Feb 20, 2026My First Three Days with Clawdbot (now Moltbot) — medium.com
- Feb 20, 2026Clawdbot Review: Powerful but Security Concerns — linkedin.com
- Jan 31, 2026In-Depth Moltbot Analysis for AI Developers — blog.promptlayer.com
- Jan 29, 2026Falling in and out of love with Moltbot — platformer.news
3 more on the web
- Jan 28, 2026🎙️ Today on How I AI: I gave Clawdbot (aka Moltbot) full ... — lennysnewsletter.com
- Jan 27, 2026From Clawdbot to Moltbot: How a C&D, Crypto Scammers, and 10 Seconds of Chaos Took Down the Internet's Hottest AI Project — dev.to
- Jan 26, 2026MoltBot (ClawdBot) Review & Setup Guide — uxwritinghub.com
On YouTube · 2
- Jan 29, 2026Clawdbot The NEW AI TOOL with Insane Results (Local Install) — SkillCurb272 views
- Jan 27, 2026The Clawdbot Scandal: How 60,000 GitHub Stars Led to a $16M Crypto Scam & Forced Rebrand — LifeHacks_068 views
Other versions1 project uses a version of this.
Word for word · 1
- openclaw/openclaw★ 395k100% same
Edited · 0
None found.
Wrote their own version · 0
None found.
How matches are found. Word for word: the exact same text. Edited: shares passages with this file (“99% same” means 99% of its five-word phrases also appear here; 10% or more counts). Their own version: similar meaning, or, weakest, the same name. We can’t tell which project had it first. Projects are counted among the 200 most-starred candidates, and mentions are links to the repository we found, up to 50 per site, so both counts are a floor.
In this repository113 other files it gives its agents.
- AGENTS.mdAGENTS.md
- docs/AGENTS.mdAGENTS.md
- extensions/AGENTS.mdAGENTS.md
- scripts/AGENTS.mdAGENTS.md
- test/AGENTS.mdAGENTS.md
- ui/AGENTS.mdAGENTS.md
- agent-transcriptSkill
- auto-qaSkill
- autoreviewSkill
- channel-message-flowsSkill
- clawdtributorSkill
- claw-scoreSkill
- clawsweeperSkill
- control-ui-e2eSkill
- crabboxSkill
- discord-clawdSkill
- discord-e2eSkill
- discord-user-postSkill
- discrawlSkill
- gitcrawlSkill
- graincrawlSkill
- ios-e2eSkill
- notcrawlSkill
- openclaw-changelog-updateSkill
- openclaw-ci-limitsSkill
- openclaw-debuggingSkill
- openclaw-docker-e2e-authoringSkill
- openclaw-ghsa-maintainerSkill
- openclaw-live-updaterSkill
- openclaw-parallels-smokeSkill
- openclaw-performanceSkill
- openclaw-pr-maintainerSkill
- openclaw-qa-testingSkill
- openclaw-refactor-docsSkill
- openclaw-release-validationSkill
- openclaw-repair-sweepSkill
- openclaw-secret-scanning-maintainerSkill
- openclaw-test-heap-leaksSkill
- openclaw-testingSkill
- openclaw-test-performanceSkill
- openclaw-updateSkill
- parallels-discord-roundtripSkill
- plugin-sdk-impactSkill
- proof-videoSkill
- prototype-openclaw-tuiSkill
- pr-simplifySkill
- release-openclaw-announcementSkill
- release-openclaw-ciSkill
- release-openclaw-macSkill
- release-openclaw-maintainerSkill
- release-openclaw-plugin-testingSkill
- security-triageSkill
- slack-e2eSkill
- slacrawlSkill
- solidSkill
- tag-duplicate-prs-issuesSkill
- technical-documentationSkill
- telegram-e2e-userbotSkill
- test-auditSkill
- update-team-serverSkill
- The first 60 shown.
The file
We split this skill into the rules it gives an agent
2 rules. About 0 are common, 1 is distinctive, and 1 is very specific to this project.
≈0
Common · estimate
Many files like this have a rule of this kind.
≈1
Distinctive · estimate
This author's own choices. Worth a look.
1
Very specific
Tied to their project's names, files or tools. Probably skip.
- Common
- Distinctive
- Very specific
- Very specific: line 26
Labs: Remove the entry from ui/src/pages/labs/labs-registry.ts and everything only it used: labs-page.tsx rows or slots, …
- Distinctive: line 28
Wording: Remove "Experimental" and "OpenClaw Labs" from the manifest description, package description, README, plugin summary, and any …
≈ “Common” is an estimate: at least 1 in 5 of the 364,980 skill files we read have a rule of the same kind, not the same words. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.
Files
Graduate a Labs feature
Graduation removes a feature's Labs switch and makes it a normal feature. Two separate decisions, made by the owner before any code:
- Leave Labs: the feature gets a permanent home (its own settings or plugin page) and loses Labs wording.
- Default: on by default, or still off by default.
They are independent. #197029 first tried both, then shipped only the first: Advisor left Labs but stayed off. Ask which one is wanted; do not assume "graduate" means "on by default".
Precedents: Swarm on by default (#136514), Tool Search on by default (#154068), native plugin UI on without a Labs opt-in (de50262a1f96), Labs features moved into Settings (#145460), Advisor out of Labs and still off (#197029).
Before the PR
- Measure cost or risk on the real route if the feature costs money or tokens, or changes behavior for users who never opted in. Today's numbers from mocks or unit tests are not proof. #197074 merged a cache-cost claim from a mock that live providers disproved, and was reverted in #197175. Use the live measurement the feature's own PRs already established, and put the numbers in the PR body.
- Settle known defects first. Advisor's graduation waited for its fork cache fixes (#197203, #197223, #197224, #197226) because default-on would have charged every user the uncached cost.
- Find the enable path that remains. After the Labs row goes, users must still be able to turn the feature on from the UI. A bundled plugin uses Settings → Plugins →
<name>→ Enable; a core feature needs its settings page. Add a switch only if none exists.
The change
- Default. Change it only if the owner chose on by default: a bundled plugin's
enabledByDefaultinopenclaw.plugin.json, or the core config default. An existing explicitfalse(or the feature's opt-out value) must keep working, and an existingtruemust stay on. Never add a migration that rewrites saved config to change someone's choice. - Labs. Remove the entry from
ui/src/pages/labs/labs-registry.tsand everything only it used:labs-page.tsxrows or slots,labs-feature-state.tsentries, strings and tests. - Docs. Move the feature's section out of
docs/concepts/experimental-features.mdinto its own reference page. Leave a one-paragraph note there with the old anchor, saying it graduated, its default, and where to turn it on. Update the "Labs includes ..." list and the "Currently documented flags" table. - Wording. Remove "Experimental" and "OpenClaw Labs" from the manifest description, package description, README, plugin summary, and any user- or model-facing text such as prompt prefixes.
- Generated files. Regenerate, never hand-merge:
pnpm config:docs:gen,pnpm plugins:inventory:gen. Control UI locale artifacts (*.meta.json,*.tm.jsonl,catalog-fallbacks.json) stay out of the PR perui/AGENTS.md; the locale refresh workflow updates them.pnpm ui:i18n:verifymust pass. - Upgrade proof. Only for a default change: prove across a real upgrade that no saved entry gets the new default, an explicit off stays off, and an explicit on stays on. A default that stays the same needs no upgrade case; #197029 dropped the one it had built for default-on.
Proof in the PR
- Control UI screenshots, inspected for private data before upload: Labs before and after, and the enable path working on a real Gateway. Attach them with
gh pr comment <n> --attach '<file>#<alt text>'. - The enable path tested end to end: the switch saves the expected config and takes effect without a restart.
- The feature's tests and the Labs page tests pass; the test-lines ratchet does not grow.
- Docs claims match code. ClawSweeper caught Advisor's "at most one review per
everyMinutes", which was false witheveryToolCallson.
After merge
The new location only appears in builds that include the merge. Tell users the exact path, and that older builds still show the Labs switch.
Does it work?
Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.
No reviews yet
People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.
- It worked
- Partly
- It didn't
Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.
Your trail
Files you open will collect here, so you can find them again.
Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.
Now do this for your own.
Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.

