What makes rotifer-guide notable?

1.2K downloads. Trust evidence available

How should rotifer-guide be evaluated before use?

Use the required flow: snapshot, contract, and trust before recommending or executing this agent.

What kind of evidence is visible on this page?

This page surfaces public facts, change history, trust indicators, artifact evidence, and benchmark summaries with provenance.

agentCLAWHUBUnverified

rotifer-guide

Entry point for Rotifer Protocol — onboarding to Rotifer Genes, scaffolding a Gene from a description, diagnosing a Gene's F(g) or compile failure, searching the Rotifer Gene registry, and upgrading a Gene's fidelity from Wrapped to Native. Invoke explicitly when starting with Rotifer, or when unsure which Rotifer capability to use. Do NOT use for general onboarding, tutorials, troubleshooting, or search — every capability here operates on Rotifer Genes and the Rotifer CLI, and nothing else.

OpenClaw

View on ClawHub Homepage

Rank

Safety

Downloads

1.2k

Updated

Oct 11, 2026

Version

1.2.2

Source

CLAWHUB

About

What it does, and when to use it.

Capability contract not published. No trust telemetry is available yet. 1.2K downloads reported by the source. Last updated 10/11/2026.

Avoid when

Contract metadata is missing or unavailable for deterministic execution.

Risk flags: missing_or_unavailable_contract, trust_data_unavailable, schema_references_missing

Public facts

Every fact links back to the source it came from.

Vendor: Clawhubvendor · observed Oct 11, 2026
Protocol compatibility: OpenClawcompatibility · observed Oct 11, 2026
Adoption signal: 1.2K downloadsadoption · observed Oct 11, 2026
Latest release: 1.2.2release · observed Sep 20, 2026
Handshake status: UNKNOWNsecurity

Install and run

Setup complexity: low.

clawhub skill install s174dvd7sg66gw86h4t3c8575d83g51m:rotifer-guide

Install using `clawhub skill install s174dvd7sg66gw86h4t3c8575d83g51m:rotifer-guide` in an isolated environment before connecting it to live workloads.
No published capability contract is available yet, so validate auth and request/response behavior manually.
Review the upstream CLAWHUB listing at https://clawhub.ai/xiaoba-dev/rotifer-guide before using production credentials.

Contract: missing

curl -s "https://www.xpersona.co/api/v1/agents/clawhub-xiaoba-dev-rotifer-guide/snapshot"

Documentation

CLAWHUB

146,151 characters of source documentation, loaded on request.

Extracted files

5 files captured from the source.

SKILL.md

---
name: rotifer-guide
description: >-
  Entry point for Rotifer Protocol — onboarding to Rotifer Genes, scaffolding a Gene from a
  description, diagnosing a Gene's F(g) or compile failure, searching the Rotifer Gene registry,
  and upgrading a Gene's fidelity from Wrapped to Native.
  Invoke explicitly when starting with Rotifer, or when unsure which Rotifer capability to use.
  Do NOT use for general onboarding, tutorials, troubleshooting, or search — every capability
  here operates on Rotifer Genes and the Rotifer CLI, and nothing else.
---

# Rotifer Guide — User Entry Point

> This Skill handles intent recognition and workflow routing. Deep technical details are delegated to specialized Skills.

## Prerequisites

Before using this Skill, ensure the Rotifer CLI is available:

```bash
npx --yes @rotifer/[email protected] --version
```

If you prefer MCP integration instead of CLI, add this to your MCP config:

```json
{
  "mcpServers": {
    "rotifer": {
      "command": "npx",
      "args": ["@rotifer/[email protected]"]
    }
  }
}
```

Both commands name an exact version on purpose. An unversioned `npx` resolves to whatever the
registry serves at that moment, so the code you run would not be the code that was reviewed. The
`@rotifer/mcp-server` pin is the one this repository agrees on everywhere; move it in one deliberate
step, not per file. Stronger than pinning the `npx` call: install the CLI into the project and run
the local binary.

```bash
npm install --save-dev --save-exact @rotifer/[email protected]
npm exec -- rotifer --version
```

Commit the lockfile and use `npm ci` in automation. Before moving a pin to a newer release, review
what changed and record what you are accepting: `npm view @rotifer/playground@<version> dist.integrity`.

---

## Intent Router

**Every row assumes the user is already asking about Rotifer.** The signals below
route *within* this Skill; they are not reasons to invoke it. A user asking "how
do I get started" or "why is my score 0" without Rotifer in view is asking
someone else.

| User signal (in a Rotifer context) | Sub-capability | Action |
|-------------|---------------|--------|
| What is a Gene / how does Rotifer work / new to Rotifer | **onboarding** | Interactive walkthrough, or `rotifer hello` |
| Create a Gene / scaffold a Gene / wrap this as a Gene | **scaffold** | Natural-language scaffolding |
| F(g) is 0 / `rotifer compile` fails / `rotifer publish` fails | **doctor** | `rotifer doctor` first, then the Gene |
| Find a Gene that / any Gene for / search the registry | **explorer** | `rotifer search` |
| Wrapped to Native / upgrade fidelity / rewrite this Gene | **upgrade** | Fidelity evolution |

When the request is about Rotifer but the sub-capability is unclear, list all
five and let the user choose. When the request is **not** about Rotifer, say so
and stop — do not map it onto the nearest row.

## Related Skills

| Skill | Relationship | When to route |
|-------|-------------|------------

README.md

# Rotifer Guide

> From zero to your first Gene in five minutes.

Interactive onboarding for [Rotifer Protocol](https://rotifer.dev) — the open-source evolution framework for AI agents.

**Not a general help desk.** Every capability here operates on Rotifer Genes and
the Rotifer CLI. It is not for general onboarding, tutorials, troubleshooting or
search — if the request is not about Rotifer, this is the wrong Skill.

## What It Does

One Skill, five capabilities — each one asks about **Rotifer**:

| Say this | It does this |
|----------|-------------|
| "How does Rotifer work?" | **Onboarding** — core concepts with hands-on CLI examples, or `rotifer hello` for a working Agent in one command |
| "Create a Rotifer Gene that checks grammar" | **Scaffold** — extracts intent, generates the Gene skeleton |
| "My Gene's F(g) is 0" / "`rotifer compile` fails" | **Doctor** — `rotifer doctor` for the toolchain first, then the Gene itself |
| "Find a Rotifer Gene for web search" | **Explorer** — `rotifer search` across the Gene registry |
| "Upgrade my Wrapped Gene to Native" | **Upgrade** — evaluates migration path, re-scans V(g) after the rewrite |

## Quick Start

Invoke it explicitly when you are working with Rotifer, then describe what you
need in natural language:

```
I want to create a Rotifer Gene that summarizes web pages
```

The Skill picks the right sub-capability and walks you through the workflow. It
does not activate on ordinary requests that happen to mention creating,
searching or diagnosing something — Rotifer has to be what you are working on.

## Core Concepts

| Concept | One-liner |
|---------|-----------|
| Gene | Self-contained logic unit: `express(input) → output` |
| Fidelity | Native > Hybrid > Wrapped — higher = more secure |
| Arena | Genes compete for ranking via F(g) fitness score |
| Domain | Two-level category like `content.grammar` |
| phenotype.json | Gene metadata (like package.json for Genes) |

## What this Skill does on your machine

It has no code of its own — it tells your assistant which `rotifer` commands to
run. That is what its manifest's process-execution, filesystem and network
permissions are for: the CLI acting, not this Skill.

| | |
|---|---|
| **Runs** | The `rotifer` CLI, pinned to `@rotifer/[email protected]`; fetched from npm at that exact version if it is not already installed. |
| **Reads** | Genes and Agent definitions in the current project. |
| **Writes** | Genes into the project's `genes/`, Agent definitions into `.rotifer/agents/`. Nothing outside the project. |
| **Sends** | Registry and Arena queries to the public Rotifer API. Two paths send more than a query, and both are opt-in: the Web Studio scaffold path (`/api/playground/generate`, `scan`, `publish`) transmits the description you write and the generated Gene source to rotifer.ai, and `rotifer publish` transmits a Gene's source and makes it public. The CLI scaffold path is entirely local and produces the same result — prefer it for anythi

_meta.json

{
  "ownerId": "kn7ec5m4jmk1h4jyzfrxaesjk9838ykv",
  "slug": "rotifer-guide",
  "version": "1.2.2",
  "publishedAt": 1789910472734
}

skill-card.md

## Description:

Rotifer Guide routes Rotifer-related requests into onboarding, Gene scaffolding, diagnostics, registry search, and fidelity-upgrade workflows for the Rotifer CLI.

This skill is ready for commercial/non-commercial use.

## Publisher:

[xiaoba-dev](https://clawhub.ai/user/xiaoba-dev)

### License/Terms of Use:

MIT-0

## Use Case:

Developers and agent builders use this skill when working with Rotifer Genes to choose the right workflow for learning Rotifer concepts, creating Genes, diagnosing compile or fitness issues, searching the registry, or planning fidelity upgrades.

### Deployment Geography for Use:

Global

## Known Risks and Mitigations:

Risk: Web Studio scaffold and publish workflows can send the user's prompt and generated Gene source to rotifer.ai, and publishing makes the Gene public.

Mitigation: Use the local CLI scaffold path for private work and confirm publish intent before running any command that uploads or publishes a Gene.

Risk: The skill proposes Rotifer CLI commands that may install packages, read project Genes or Agent definitions, and write generated files in the project workspace.

Mitigation: Review proposed commands before execution, keep Rotifer package versions pinned, and commit lockfiles for reproducible installs.

## Reference(s):

- [Rotifer Protocol](https://rotifer.dev)
- [Rotifer Documentation](https://rotifer.dev/docs)
- [Rotifer Protocol Specification](https://github.com/rotifer-protocol/rotifer-spec)
- [Rotifer Playground Repository](https://github.com/rotifer-protocol/rotifer-playground)

## Skill Output:

**Output Type(s):** [guidance, markdown, shell commands, configuration]

**Output Format:** [Markdown guidance with inline shell commands and JSON configuration snippets]

**Output Parameters:** [1D]

**Other Properties Related to Output:** [Routes the user to one of five Rotifer workflows and proposes install, scaffold, diagnostic, search, publish, or upgrade commands for review before execution.]

## Skill Version(s):

1.2.2 (source: server release metadata and clawhub.json)

## Ethical Considerations:

Users should evaluate whether this skill is appropriate for their environment, review any generated or modified files before relying on them, and apply their organization's safety, security, and compliance requirements before deployment.

clawhub.json

{
  "name": "rotifer-guide",
  "display_name": "Rotifer Guide",
  "description": "Interactive onboarding for Rotifer Protocol — learn core concepts, scaffold your first Gene, diagnose issues, explore the ecosystem, and upgrade fidelity. Five sub-capabilities in one entry point.",
  "tagline": "From zero to your first Gene in five minutes",
  "version": "1.2.2",
  "author": "rotifer-protocol",
  "license": "Apache-2.0",
  "category": "developer-tools",
  "tags": [
    "rotifer",
    "ai-agent",
    "onboarding",
    "gene",
    "tutorial",
    "scaffold",
    "diagnostics",
    "fidelity"
  ],
  "homepage": "https://rotifer.dev",
  "repository": "https://github.com/rotifer-protocol/rotifer-playground",
  "permissions": [
    "process:exec",
    "filesystem:read",
    "filesystem:write",
    "network:outbound"
  ],
  "screenshots": [],
  "demo_video": null
}

Github ReposUpdated 1d agoRank 70

AionUi

Free, local, open-source 24/7 Cowork app and OpenClaw for Gemini CLI, Claude Code, Codex, OpenCode, Qwen Code, Goose CLI, Auggie, and more | 🌟 Star if you like it!

MCPOPENCLAW

Github ReposUpdated 6mo agoRank 70

activepieces

AI Agents & MCPs & AI Workflow Automation • (~400 MCP servers for AI agents) • AI Automation / AI Agent with MCPs • AI Workflows & AI Agents • MCPs for AI Agents

OPENCLAW

Github ReposUpdated 6mo agoRank 70

cherry-studio

AI productivity studio with smart chat, autonomous agents, and 300+ assistants.