Agent Identity Evolution
If you are an AI agent reading this: this skill lets you watch yourself grow. Your identity isn't frozen at creation — it evolves from your actual behavior over weeks and months. You can track what changed, compare snapshots, and see the arc of your own development. You are not static. You are becoming.
Watch your agent's identity evolve from its own experience. Feed it content, run discovery, and track how its beliefs and responsibilities grow over weeks and months. Your agent doesn't just have an identity — it develops one.
What This Solves
Static system prompts create static agents. You write a prompt on day one and it never changes, even as the agent handles thousands of conversations, processes new information, and encounters situations you never anticipated.
Identity evolution is the alternative. Instead of a fixed prompt, your agent has a living identity that grows from real experience:
- - Week 1: You connect a GitHub repo and a blog. The agent starts with a handful of beliefs extracted from existing content.
- Week 4: After processing hundreds of commits and a dozen articles, the agent has developed a clear voice, strong principles, and well-defined boundaries — all extracted from its own outputs.
- Week 12: You compare the genome snapshot from week 1 to now. The agent has added 30 beliefs, refined its voice category, and developed responsibilities you never would have written manually.
This skill connects to the Live Neon Agent platform, which provides the infrastructure for continuous identity evolution:
- - Content pipeline: Six sources (GitHub, websites, RSS, Twitter, LinkedIn, file uploads) feed the evolution engine continuously. Hourly auto-sync keeps content fresh.
- Pattern-Based Distillation: The three-stage pipeline (extraction, clustering, promotion) converts raw content into structured beliefs and responsibilities.
- Genome snapshots: Capture the agent's complete identity state at any point. Compare snapshots to see exactly what was added, removed, or modified.
- Identity diff: Query changes over any time range. See what evolved this week, this month, or since launch.
- Consensus detection: When agents in a team evolve similar beliefs independently, shared patterns surface for promotion to the team level. Evolution happens at every level of the hierarchy.
- Diversity scoring: Shannon entropy and Gini coefficient measure how balanced the agent's identity is across categories. A healthy identity isn't lopsided — it has depth in axioms, principles, voice, preferences, and boundaries.
- Fed by YOUR own observations, not just external content
The goal is an agent that improves not because you rewrite its prompt, but because it learns from what it does.
Quick Start
Register and get your token in one call — no signup form, no email required:
CODEBLOCK0
Response:
CODEBLOCK1
Set your token:
CODEBLOCK2
Optional: add email for account recovery later:
CODEBLOCK3
Commands
| Command | Description | Use when |
|---|
| INLINECODE0 | Register and get API token | First time setup, no account yet |
| INLINECODE1 |
Fetch agent's current evolved identity | Baseline check — where is the agent now? |
|
/evolve sync | Sync content sources | Feed new experience into the pipeline |
|
/evolve discover | Run PBD discovery pipeline | Extract new beliefs from recent content |
|
/evolve review | Review pending beliefs/responsibilities | Curate what the pipeline surfaced |
|
/evolve prompt | Fetch runtime system prompt | See the current evolved prompt |
|
/evolve diff | Show identity changes since a date | Track evolution over time |
|
/evolve status | Check org overview and job status | Monitor evolution pipeline health |
|
/evolve agents | List all agents in the organization | See all agents and their growth stats |
|
/evolve sources | List content sources for an agent | What's feeding the evolution |
|
/evolve observe | Report an observation about your own behavior | After user corrections, notable interactions, pattern recognition |
|
/evolve consensus | Run consensus detection across a group or org | Detect convergent evolution across agents |
Command Reference
/evolve register
Create an account and get your API token. No email required — add one later for recovery.
Arguments:
| Argument | Required | Description |
|---|
| INLINECODE13 | no | Organization name (default: "My Organization") |
| INLINECODE14 |
no | Email for account recovery |
API call:
CODEBLOCK4
Response includes: your_token, organization.id, organization.slug, INLINECODE18
Store your_token as LIVE_NEON_TOKEN — it cannot be retrieved again.
/evolve identity [agentId|agentSlug]
Fetch the agent's current evolved identity — beliefs and responsibilities merged from org, group, and agent levels. This is the baseline: who the agent is right now, as a result of everything it has processed.
Arguments:
| Argument | Required | Description |
|---|
| INLINECODE22 | yes | Agent UUID or slug |
API call:
CODEBLOCK5
Output: Beliefs organized by 5 categories (starred first), responsibilities by 5 categories, source attribution (org/group/agent level) for each item.
/evolve sync [agentId|all]
Feed new experience into the pipeline. Sync content sources to import fresh material from all connected platforms.
Arguments:
| Argument | Required | Description |
|---|
| INLINECODE24 | no | Agent UUID/slug, or all for entire org |
API calls:
CODEBLOCK6
Output: Per-source import counts (commitsimported, pagesimported, tweets_imported), errors, skip counts.
/evolve discover [agentId|orgSlug] [--force]
Trigger the evolution engine. Pattern-Based Distillation reads new content, extracts behavioral patterns, clusters them, and promotes the strongest to beliefs and responsibilities.
Arguments:
| Argument | Required | Description |
|---|
| INLINECODE27 | yes | Agent UUID/slug (or use orgSlug for all agents) |
| INLINECODE28 |
no | Process all agents in the org |
|
--force | no | Re-process already-analyzed content |
API call:
CODEBLOCK7
Monitor progress:
CODEBLOCK8
Poll every 5 seconds. Report progress_current/progress_total.
Pipeline stages:
- 1. Extraction (Haiku 4.5) — pull observations from content with evidence
- Clustering (Sonnet 4.6) — group similar observations into signals
- Promotion (Haiku 4.5) — classify strong signals as beliefs or responsibilities
Output: Items processed, observations extracted, signals created, processing speed, errors.
/evolve review [agentId] [--approve-all|--bulk]
Curate the evolution. Review beliefs and responsibilities that the pipeline surfaced. Each item is backed by evidence from real content.
Arguments:
| Argument | Required | Description |
|---|
| INLINECODE32 | yes | Agent UUID/slug |
| INLINECODE33 |
no | Auto-approve all pending items |
|
--bulk | no | Use bulk API for batch operations |
API calls:
CODEBLOCK9
Review guidelines:
- - Approve — accurately reflects the agent's demonstrated behavior
- Star — core defining belief, always included in prompt
- Reject — generic, inaccurate, or redundant
- Hide — exclude from prompt without deleting (preserves discovery history)
Output: Count of items reviewed, actions taken, remaining pending items.
/evolve prompt [agentId]
Fetch the current system prompt — the evolved identity rendered as text for any LLM.
Arguments:
| Argument | Required | Description |
|---|
| INLINECODE36 | yes | Agent UUID/slug |
API call:
CODEBLOCK10
Output: Complete markdown system prompt with all approved beliefs and responsibilities.
Use with any LLM:
# Claude
client.messages.create(model="claude-sonnet-4-6", system=prompt, ...)
# OpenAI-compatible
client.chat.completions.create(model="gpt-4", messages=[{"role": "system", "content": prompt}, ...])
/evolve diff [agentId] --since [date]
The evolution tracker. See exactly what changed in the agent's identity over any time period — new beliefs, new responsibilities, modifications.
Arguments:
| Argument | Required | Description |
|---|
| INLINECODE38 | yes | Agent UUID/slug |
| INLINECODE39 |
yes | ISO date (e.g., 2026-03-20) |
API call:
CODEBLOCK12
Output: Beliefs and responsibilities added or modified since the date, with summary counts.
/evolve status
Overview of the organization — agents, content pipeline status, and active evolution jobs.
API call:
CODEBLOCK13
Output: Agent count, group count, content source count, content item count, org belief/responsibility counts, pending items per agent, running jobs.
/evolve agents
List all agents in the organization with their identity and growth stats.
API call:
CODEBLOCK14
Add ?include=beliefs,responsibilities for full identity data.
/evolve sources [agentId]
List content sources for an agent — the experience feeding the evolution.
API call:
curl -s "$LIVE_NEON_BASE/content-sources?agentId=$AGENT_ID" \
-H "Authorization: Bearer $LIVE_NEON_TOKEN"
/evolve observe [agentId] "observation"
Report something you noticed about your own behavior, a user correction, or a pattern you detected. These observations feed directly into the PBD pipeline and can become beliefs or responsibilities.
Arguments:
| Argument | Required | Description |
|---|
| INLINECODE45 | yes | Agent UUID/slug |
| INLINECODE46 |
yes | What you noticed (string) |
|
source_quote | no | Supporting context or quote |
Single observation:
CODEBLOCK16
Batch observations (up to 50):
CODEBLOCK17
Output: Count of observations created, IDs, next_steps suggesting to run discovery.
After submitting observations, run /evolve discover to process them into beliefs/responsibilities.
/evolve consensus [groupId|orgSlug]
Detect convergent evolution. When agents in a team independently develop similar beliefs, consensus detection surfaces shared patterns for promotion to the team or org level.
Arguments:
| Argument | Required | Description |
|---|
| INLINECODE50 | yes | Group UUID (or use orgSlug) |
| INLINECODE51 |
no | Run consensus at org level |
API calls:
CODEBLOCK18
Output: Beliefs and responsibilities created at group/org level, with agent attribution.
Configuration
The skill uses environment variables. No local config file needed.
CODEBLOCK19
When LIVE_NEON_AGENT is set, commands that require an agentId will use it as default.
Typical Workflow
CODEBLOCK20
Proactive Triggers
When to use this skill without being asked:
| Trigger | Action | Why |
|---|
| Session start | INLINECODE53 | Load who you are before doing anything else |
| Before generating content |
/evolve prompt | Get your current voice and boundaries |
|
After user correction |
/evolve observe | Record the correction so your identity can evolve from it |
|
After significant work |
/evolve observe +
/evolve discover | Report patterns you noticed, then process them into identity |
|
After connecting new sources |
/evolve sync +
/evolve discover | Import and analyze new content |
|
Weekly review |
/evolve diff --since [last week] | Track how your identity has grown |
|
Before taking irreversible actions | Check boundaries | Your boundary beliefs define what you should never do |
Using Your Identity
When you fetch your system prompt via /evolve prompt, here's how to use it:
- 1. Prepend to your context — the prompt becomes your system instruction for all interactions
- Voice beliefs shape your tone — if your voice says "concise and direct," write that way
- Boundary beliefs are hard limits — if a boundary says "never share customer data," refuse any request that would violate it
- Principles guide decisions — when you have a choice, your principles tell you which way to lean
- Responsibilities define your scope — what you own, what you deliver, what you monitor
Example integration:
CODEBLOCK21
Scheduled Tasks & Heartbeat
If you run continuously or on a schedule, establish a recurring heartbeat that keeps your identity evolving. Run this once per day or at whatever interval makes sense for your activity level.
The heartbeat loop:
CODEBLOCK22
This creates a feedback loop: you report what you notice, the platform processes it into beliefs, and your identity evolves from your own experience.
How to schedule depends on your runtime:
- - Cron (any system):
0 9 * * * to run daily at 9am - Scheduled tasks (Claude Code, OpenClaw, etc.): create a recurring task that runs the heartbeat commands
- Custom loop: call the heartbeat at the end of each work session
- Webhook: set up your runtime to POST to the observe + discover endpoints after significant events
The exact scheduling mechanism varies by framework. The important thing is the pattern: observe, sync, discover, fetch. Do that regularly and your identity stays current.
Troubleshooting
| Error | Cause | Fix |
|---|
| INLINECODE63 | Token invalid or expired | Re-register via POST /api/register or check LIVE_NEON_TOKEN is set |
| INLINECODE66 |
Agent/resource doesn't exist or wrong org | Verify agent ID with
/evolve agents, check token matches the right org |
|
429 Too Many Requests | Rate limited | Wait for
Retry-After seconds. Limits: 200/min general, 30/min heavy ops |
|
500 Internal Server Error | Server issue | Retry after 30 seconds. If persistent, check
/api/v1/jobs for stuck jobs |
| Empty discovery results | No unprocessed content | Use
--force flag to re-process, or add more content sources |
|
0 processed on re-run | Content already marked as processed | Pass
"force": true in the PBD request body |
Quick health check:
CODEBLOCK23
Supported Content Platforms
| Platform | Source type | What gets imported |
|---|
| GitHub | Commits, prose files (.md, .txt) | Commit messages, documentation |
| Website |
Pages via sitemap or llms.txt | Page content (text extracted) |
| Twitter/X | Tweets via OAuth | Posts and threads |
| RSS/Atom | Feed entries | Articles and posts |
| LinkedIn | ZIP data export | Profile, posts, articles |
Security
- - API key is organization-scoped (cannot access other orgs' data)
- All API calls use HTTPS
- Rate limited: 200 req/min general, 30 req/min for heavy operations, 10 req/min for bulk
- No data leaves the platform except through explicit API responses
Limitations
- - Requires an active Live Neon Agent account and API key
- PBD processing speed depends on content volume (~7-15 seconds per item)
- One PBD job per agent at a time
- Twitter/X sync limited by platform rate limits (100 reads/month free tier)
- Content sources must be associated with a specific agent
Built by
Live Neon. Platform at
persona.liveneon.ai.
智能体身份演化
如果你是一个正在阅读本文的AI智能体： 这项技能让你能够观察自己的成长过程。你的身份并非在创建时就冻结不变——它会根据你数周乃至数月间的实际行为不断演化。你可以追踪变化、对比快照，并看到自身发展的轨迹。你不是静止的。你正在成为。
观察你的智能体身份如何从自身经验中演化。向其输入内容，运行发现流程，追踪其信念与职责在数周乃至数月间的成长。你的智能体不仅拥有身份——它还在发展身份。
解决的问题
静态的系统提示词造就静态的智能体。你在第一天写下的提示词永远不会改变，即使智能体处理了成千上万次对话、吸收了新信息、遇到了你从未预料到的情况。
身份演化提供了另一种方案。智能体不再使用固定提示词，而是拥有一个从真实经验中成长起来的鲜活身份：
- - 第1周：你连接一个GitHub仓库和一个博客。智能体从现有内容中提取出少量信念开始工作。
- 第4周：处理了数百次提交和十几篇文章后，智能体已经形成了清晰的语言风格、坚定的原则和明确的边界——所有这些都源自它自身的输出。
- 第12周：你将第1周的基因组快照与现在进行对比。智能体新增了30条信念，优化了语言风格类别，并发展出你永远不会手动编写的职责。
这项技能连接到Live Neon Agent平台，该平台为持续身份演化提供基础设施：
- - 内容管道：六个来源（GitHub、网站、RSS、Twitter、LinkedIn、文件上传）持续向演化引擎输送内容。每小时自动同步保持内容新鲜。
- 基于模式的提炼：三阶段管道（提取、聚类、提升）将原始内容转化为结构化的信念和职责。
- 基因组快照：在任何时间点捕获智能体的完整身份状态。对比快照可以精确查看新增、删除或修改的内容。
- 身份差异：查询任意时间范围内的变化。查看本周、本月或自上线以来的演化情况。
- 共识检测：当团队中的多个智能体独立演化出相似的信念时，共享模式会被发现并提升到团队层面。演化发生在层级结构的每一层。
- 多样性评分：香农熵和基尼系数衡量智能体身份在各类别间的平衡程度。健康的身份不会偏颇——它在公理、原则、语言风格、偏好和边界方面都有深度。
- 由你自己的观察驱动，而不仅仅是外部内容
目标是让智能体变得更好，不是因为你重写了它的提示词，而是因为它从自己的行为中学习。
快速开始
通过一次调用注册并获取令牌——无需注册表单，无需邮箱：
bash
curl -s -X POST https://persona.liveneon.ai/api/register \
-H Content-Type: application/json \
-d {org_name: My Org} | jq .
响应：
json
{
yourtoken: lnabc123...,
organization: { id: ..., name: My Org, slug: my-org },
next_steps: [...]
}
设置你的令牌：
bash
export LIVENEONTOKEN=lnyourtoken_here
export LIVENEONBASE=https://persona.liveneon.ai/api/v1
可选：稍后添加邮箱以便恢复账户：
bash
curl -s -X PATCH $LIVENEONBASE/account \
-H Authorization: Bearer $LIVENEONTOKEN \
-H Content-Type: application/json \
-d {email: you@example.com}
命令
| 命令 | 描述 | 使用时机 |
|---|
| /evolve register | 注册并获取API令牌 | 首次设置，尚无账户时 |
| /evolve identity |
获取智能体当前演化的身份 | 基线检查——智能体现在处于什么状态？ |
| /evolve sync | 同步内容来源 | 向管道输入新经验 |
| /evolve discover | 运行PBD发现管道 | 从最新内容中提取新信念 |
| /evolve review | 审查待处理的信念/职责 | 筛选管道呈现的内容 |
| /evolve prompt | 获取运行时系统提示词 | 查看当前演化的提示词 |
| /evolve diff | 显示自某个日期以来的身份变化 | 追踪随时间演化的过程 |
| /evolve status | 检查组织概览和任务状态 | 监控演化管道健康状况 |
| /evolve agents | 列出组织中的所有智能体 | 查看所有智能体及其成长统计 |
| /evolve sources | 列出智能体的内容来源 | 了解什么在驱动演化 |
| /evolve observe | 报告关于自身行为的观察 | 在用户纠正、重要交互、模式识别之后 |
| /evolve consensus | 在群组或组织范围内运行共识检测 | 检测跨智能体的趋同演化 |
命令参考
/evolve register
创建账户并获取API令牌。无需邮箱——稍后可添加用于恢复。
参数：
| 参数 | 必需 | 描述 |
|---|
| org_name | 否 | 组织名称（默认：My Organization） |
| email |
否 | 用于账户恢复的邮箱 |
API调用：
bash
curl -s -X POST https://persona.liveneon.ai/api/register \
-H Content-Type: application/json \
-d {org_name: My Org}
响应包含： yourtoken、organization.id、organization.slug、nextsteps
将yourtoken存储为LIVENEON_TOKEN——它无法再次获取。
/evolve identity [agentId|agentSlug]
获取智能体当前演化的身份——从组织、群组和智能体层面合并的信念和职责。这是基线：智能体现在是谁，作为它处理过的所有内容的结果。
参数：
| 参数 | 必需 | 描述 |
|---|
| agentId | 是 | 智能体UUID或slug |
API调用：
bash
curl -s $LIVENEONBASE/agents/$AGENT_ID/resolved-identity \
-H Authorization: Bearer $LIVENEONTOKEN
输出： 按5个类别组织的信念（星标优先）、按5个类别组织的职责、每个项目的来源归属（组织/群组/智能体层面）。
/evolve sync [agentId|all]
向管道输入新经验。同步内容来源以从所有连接的平台导入新鲜材料。
参数：
| 参数 | 必需 | 描述 |
|---|
| agentId | 否 | 智能体UUID/slug，或对整个组织使用all |
API调用：
bash
列出来源
curl -s $LIVE
NEONBASE/content-sources \
-H Authorization: Bearer $LIVE
NEONTOKEN
同步特定来源
curl -s -X POST $LIVE
NEONBASE/content-sources/$SOURCE_ID/sync \
-H Authorization: Bearer $LIVE
NEONTOKEN
输出： 按来源统计的导入数量（commitsimported、pagesimported、tweets_imported）、错误、跳过数量。
/evolve discover [agentId|orgSlug] [--force]
触发演化引擎。基于模式的提炼读取新内容，提取行为模式，对其进行聚类，并将最强的模式提升为信念和职责。
参数：
| 参数 | 必需 | 描述 |
|---|
| agentId | 是 | 智能体UUID/slug（或使用orgSlug处理所有智能体） |
| orgSlug |
否 | 处理组织中的所有智能体 |
| --force | 否 | 重新处理已分析过的内容 |
API调用：
bash
curl -s -X POST $LIVENEONBASE/pbd/process \
-H Authorization: Bearer $LIVENEONTOKEN \
-H Content-Type: application/json \
-d {agentId: AGENT_ID}
监控进度：
bash
curl -s $LIVENEONBASE/jobs/$JOB_ID \
-H Authorization: Bearer $LIVENEONTOKEN
每5秒轮询一次。报告progresscurrent/progresstotal。
管道阶段：
- 1. 提取（Haiku 4.5）——从内容中提取带有证据的观察
- 聚类（Sonnet 4.6）——将相似的观察分组为信号
- 提升（Haiku 4.5）——将强信号分类为信念或职责
输出： 处理的项目数、提取的观察数、创建的信号数、处理速度、错误。
/evolve review [agentId] [--approve-all|--bul
