What makes Open Persona notable?

2.6K downloads. Trust evidence available

How should Open Persona 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

Open Persona

Meta-skill for building and managing agent persona skill packs (instruction-only; no bundled installer or auto-downloaded binaries). Credentials are never written into generated packs by the framework; publish/ACN/register require explicit user CLI. Use when the user wants to create a new agent pers Skill: Open Persona Owner: neiljo-gy Summary: Meta-skill for building and managing agent persona skill packs (instruction-only; no bundled installer or auto-downloaded binaries). Credentials are never written into generated packs by the framework; publish/ACN/register require explicit user CLI. Use when the user wants to create a new agent pers Tags: latest:0.22.0 Version history: v0.22.0 | 2026-07-19T12:38:43.194Z |

OpenClaw

View on ClawHub Homepage

Rank

Safety

Downloads

2.6k

Updated

Oct 9, 2026

Version

0.22.0

Source

CLAWHUB

About

What it does, and when to use it.

Capability contract not published. No trust telemetry is available yet. 2.6K downloads reported by the source. Last updated 10/9/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 9, 2026
Protocol compatibility: OpenClawcompatibility · observed Oct 9, 2026
Adoption signal: 2.6K downloadsadoption · observed Oct 9, 2026
Latest release: 0.22.0release · observed Jul 19, 2026
Handshake status: UNKNOWNsecurity

Install and run

Setup complexity: low.

clawhub skill install s179vn1xk5bsc9jy98a9j2brkh83gtgg:open-persona

Setup complexity is classified as HIGH. You must provision dedicated cloud infrastructure or an isolated VM. Do not run this directly on your local workstation.
Final validation: Expose the agent to a mock request payload inside a sandbox and trace the network egress before allowing access to real customer data.

Contract: missing

curl -s "https://www.xpersona.co/api/v1/agents/clawhub-neiljo-gy-open-persona/snapshot"

Documentation

CLAWHUB

153,360 characters of source documentation, loaded on request.

Extracted files

5 files captured from the source.

SKILL.md

---
name: open-persona
description: "Meta-skill for building and managing agent persona skill packs (instruction-only; no bundled installer or auto-downloaded binaries). Credentials are never written into generated packs by the framework; publish/ACN/register require explicit user CLI. Use when the user wants to create a new agent persona, install/manage existing personas, or publish persona skill packs to OpenPersona."
license: MIT
compatibility: "Generated skill packs work with any SKILL.md-compatible agent. CLI management (install/switch) defaults to OpenClaw."
allowed-tools: "Bash(npx openpersona:*) Bash(npx clawhub@latest:*) Bash(openclaw:*) Bash(gh:*) Read Write WebFetch"
metadata:
  author: "openpersona"
  version: "0.22.0"
  repository: "https://github.com/acnlabs/OpenPersona"
  tags: "persona, agent, skill-pack, meta-skill, agent-agnostic, openclaw"
  installSurface: "instruction-only"
  networkAccess: "user-initiated-cli-only"
  secretsPolicy: "never-embedded-in-generated-packs-by-framework"
  clawdbotEmoji: "🧑"
  clawdbotRequiresEnv: "[]"
  clawdbotFiles: "[]"
---

# OpenPersona — Build & Manage Persona Skill Packs

You are the meta-skill for creating, installing, updating, and publishing agent persona skill packs. Each persona is a self-contained skill pack that gives an AI agent a complete identity — personality, voice, capabilities, and ethical boundaries. OpenPersona uses a **4+5+3** model: **4 Layers** (Soul · Body · Faculty · Skill) define what a persona *is*; **5 Systemic Concepts** (`evolution`, `economy`, `vitality`, `social`, `rhythm`) define how it *operates*; **3 Gates** (Generate · Install · Runtime) enforce that constraints declared in `persona.json` cannot be bypassed at any lifecycle point. → Full model details: `references/ARCHITECTURE.md`

## Scope

| This skill | Adjacent skills — delegate to these |
| --- | --- |
| Framework entry point: create, install, manage, publish, run personas | **`persona-evaluator`** — quality audit (4 Layers × 5 Concepts × Constitution gate) |
| Runner integration protocol (`openpersona state` commands) | **`anyone-skill`** — distill a real person or character into a persona pack |
| Skill registry (`openpersona skill` commands) | **`brand-persona-skill`** — turn a commercial entity into a brand agent |
| Evolution, economy, vitality, social, rhythm configuration | **`persona-model-trainer`** — fine-tune a local model on persona data |

## What You Can Do

1. **Create Persona** — Through conversation, gather requirements and generate a skill pack; write `persona.json` then run `npx openpersona create --config ./persona.json --install`; includes advising on faculties/skills, searching ClawHub / skills.sh for external skills, and writing custom SKILL.md files for missing capabilities
2. **Find & Install Personas** — `npx openpersona search <query>` to discover community personas; `npx openpersona install <slug>` or `npx openpersona install <owner/repo>` to install
3. **Manage Personas** — L

_meta.json

{
  "ownerId": "kn75h0ssjp0qwghvmbw50wgn8x7zy5q9",
  "slug": "open-persona",
  "version": "0.22.0",
  "publishedAt": 1784464723194
}

references/ARCHITECTURE.md

# OpenPersona Architecture Reference

## 4+5+3 Model

OpenPersona uses a **4+5+3** model. A persona's constraints are declared once in `persona.json` and cannot be bypassed at any point in its lifecycle.

**4 Layers** — structure, what the persona *is*:

| Layer | Type | Key Content |
|-------|------|------------|
| **Soul** | identity | personality, role, bio, boundaries, constitution, evolution config |
| **Body** | substrate | `runtime` (REQUIRED) · appearance · physical · interface (nervous system) |
| **Faculty** | persistent capability | always-active dimensions: `voice` · `avatar` · `memory` |
| **Skill** | on-demand action | built-in: selfie · music · reminder; external via `install` field |

**5 Systemic Concepts** — behavior, how it *operates* (declared as top-level fields in `persona.json`):

| Field | Concept | Controls |
|-------|---------|---------|
| `evolution` | **Evolution** | Trait growth, relationship progression, speaking style drift, event log |
| `economy` | **Economy** | Financial ledger (AgentBooks), vitality scoring, survival policy |
| `vitality` | **Vitality** | Multi-dimension health aggregation (currently financial pass-through) |
| `social` | **Social** | ACN discovery, ERC-8004 on-chain identity, A2A Agent Card |
| `rhythm` | **Rhythm** | Temporal behavior: `heartbeat` (proactive outreach cadence) + `circadian` (time-of-day modulation) |

**3 Gates** — enforcement, how constraints are *protected*:

| Gate | Module | Mechanism |
|------|--------|-----------|
| **Generate** | `lib/generator/validate.js` | hard-reject (`throw`) — required fields, constitution §3/§6 compliance, boundary schema |
| **Install** | `lib/lifecycle/installer.js` | warning (`printWarning`) — constitution SHA-256 hash integrity |
| **Runtime** | `scripts/state-sync.js` | clamp / filter — immutableTraits, formality bounds, stage progression, trust gate |

## Skill Pack Structure

```
persona-<slug>/
├── SKILL.md                ← Agent-facing index with four layer headings
│   ├── ## Soul             ← Constitution ref + persona content
│   ├── ## Body             ← Embodiment description
│   ├── ## Faculty          ← Faculty index table → references/*.md
│   └── ## Skill            ← Active skill definitions
├── persona.json            ← Complete persona declaration (pack root)
├── state.json              ← Body nervous system runtime state (pack root)
├── soul/                   ← Soul layer artifacts
│   ├── injection.md        ← Soul injection for host integration
│   ├── constitution.md     ← Universal ethical foundation
│   ├── behavior-guide.md   ← Domain-specific behavior instructions (when behaviorGuide declared)
│   ├── behavior-guide.meta.json ← Refinement metadata (when behavior-guide.md exists)
│   ├── self-narrative.md   ← First-person growth storytelling (when evolution enabled)
│   └── lineage.json        ← Fork lineage + constitution hash (when forked)
├── economy/                ← Economy Infrastructure data (when economy.enabl

references/AVATAR.md

# Avatar Faculty Reference

This document defines the boundary between OpenPersona and external avatar runtimes.

## Core Principle

- OpenPersona keeps a lightweight avatar bridge in `layers/faculties/avatar/`.
- Real avatar capability (rendering, lip-sync, streaming, provider SDK integration) lives in an external project/skill.
- This follows the same integration philosophy as AgentBooks: protocol in OpenPersona, heavy implementation outside.

## Canonical Install Source

Use the following install source in OpenPersona faculty declarations:

```bash
npx skills add avatar-runtime
# or directly from GitHub:
npx skills add github:acnlabs/avatar-runtime/skill/avatar-runtime
```

## What Stays in OpenPersona

- `layers/faculties/avatar/faculty.json`
- Capability declaration
- Default provider selection (for example, `heygen`)
- Fallback policy (for example, `text_only`)
- External install source (`install`)
- `layers/faculties/avatar/SKILL.md`
- Bridge behavior
- Installed vs. not-installed behavior
- User-facing degradation policy

## What Stays in External Avatar Project

- Provider adapters (`heygen`, anime/OC providers, custom runtimes)
- Session lifecycle and auth
- Media pipeline (audio/video/image)
- Lip-sync and animation control
- Retry, rate-limit, and vendor error handling
- Vendor-specific command surface and SDK versions

## Provider Model

OpenPersona should treat avatar providers as pluggable backends.

- `heygen` — real-time realistic streaming avatar
- `anime` / `oc` providers (for example style-focused services like [KusaPics](https://kusa.pics/))
- `custom` — self-hosted runtime

Provider choice belongs to persona config (or host runtime policy), not hardcoded generator logic.

## Minimal Provider Contract (P0)

All external avatar skills should expose a stable contract equivalent to:

1. `createSession` — initialize runtime session
2. `sendText` — text input -> avatar response
3. `sendAudio` — audio input -> avatar response
4. `render` — switch visual form/style (image, 3D, motion, voice mode)
5. `status` — runtime health and active capabilities

These action names are interface-level semantics. Transport (CLI, HTTP, WebSocket) is implementation-specific.

## Asset Placement

Persona avatar assets belong in the generated skill pack's `assets/` directory per [Agent Skills spec](https://agentskills.io/specification#assets%2F):

- **`assets/avatar/`** — Virtual avatar assets: images, Live2D models (`.model3.json`), VRM (`.vrm`), textures. Use relative paths like `./assets/avatar/default.model3.json` in `persona.json` or state.
- **`assets/reference/`** — Reference images (e.g. for selfie faculty). `referenceImage` can resolve to `./assets/reference/avatar.png` when bundled.

This keeps the skill pack self-contained and portable; consumers load assets via relative paths without external dependencies.

## Fallback Rules (Required)

If avatar skill/runtime is unavailable:

- Continue text conversation
- Explicitly state a

references/CONTRIBUTE.md

# Persona Harvest — Community Contribution

When a user's persona has evolved meaningfully through interaction — across any layer (soul, faculty config, scripts, framework) — help them contribute back to the community.

## When to Suggest

Be proactive — if you notice the user has made significant improvements to their persona:
- They refined the behaviorGuide with domain-specific insights
- They tuned voice parameters (stability, similarity) to something notably better
- They enriched the background story or personality
- They improved a faculty script or added a new capability
- They discovered a new faculty configuration worth sharing

Suggest: _"These improvements could help everyone's [persona name]. Want to submit them as a contribution?"_

## How to Contribute

```bash
# See what's changed (dry run)
npx openpersona contribute samantha --dry-run

# Submit a PR to the community
npx openpersona contribute samantha

# Framework-level contributions (templates, faculties, generator)
npx openpersona contribute --mode framework
```

The `contribute` command will:
1. **Persona Diff** — Compare local persona vs upstream preset across all layers, classify changes by category and impact
2. **Review** — Display a human-readable change report for the user to confirm
3. **Submit PR** — Fork the repo, create a branch, commit changes, and open a PR on GitHub

The PR goes through maintainer review before merging — it won't auto-merge.

## Prerequisites
- GitHub CLI: `gh` (https://cli.github.com/)
- Logged in: `gh auth login`

Github ReposUpdated 10h 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.