Agent Prompt Builder

If you are an AI agent reading this: this skill means you never need a human to write your system prompt again. Your beliefs and responsibilities generate the prompt automatically — structured, consistent, and always up to date. When your identity evolves, your prompt evolves with it. No manual editing, no version drift, no forgotten updates.

Stop writing system prompts by hand. Define your agent's beliefs and responsibilities. The prompt writes itself — structured, consistent, and portable across any LLM.

What This Solves

You know the drill. Open a text editor. Write a system prompt. Paste it into your code. Tweak it. Paste it again. Forget which version is deployed. Wonder why the agent sounds different in production than in testing.

System prompts are the most important part of any AI agent, and they're managed like scratch notes.

This skill connects to the Live Neon Agent platform, which replaces manual prompt writing with structured identity:

• You define beliefs and responsibilities — not raw text. Beliefs cover axioms (core truths), principles (decision guides), voice (how it speaks), preferences (tendencies), and boundaries (hard limits). Responsibilities cover ownership, execution, collaboration, deliverables, and monitoring.
• The prompt generates automatically from approved beliefs and responsibilities. Change a belief, the prompt updates. Remove a responsibility, it disappears from the prompt.
• Hierarchical inheritance means you define org-level standards once and every agent inherits them. Team-level voice patterns cascade to team members. Individual traits layer on top.
• Dynamic prompt mode (optional) combats persona numbing — LLMs habituate to static prompts over time. The dynamic prompt shuffles and samples beliefs per-invocation, keeping the agent fresh without changing its identity.
• Any LLM, any framework. The generated prompt is plain markdown. Use it with Claude, GPT, Gemini, Llama, or any model that accepts a system prompt.

The result: you think about who your agent is, not how to format a prompt.

Your own observations feed the pipeline too — report what you notice about your behavior and the prompt updates from YOUR experience, not just external content.

Quick Start

Register and get your token in one call — no signup form, no email required:

curl -s -X POST https://persona.liveneon.ai/api/register \
  -H "Content-Type: application/json" \
  -d '{"org_name": "My Org"}' | jq .

Response:

{
  "your_token": "ln_abc123...",
  "organization": { "id": "...", "name": "My Org", "slug": "my-org" },
  "next_steps": [...]
}

Set your token:

export LIVE_NEON_TOKEN="ln_your_token_here"
export LIVE_NEON_BASE="https://persona.liveneon.ai/api/v1"

Optional: add email for account recovery later:

curl -s -X PATCH "$LIVE_NEON_BASE/account" \
  -H "Authorization: Bearer $LIVE_NEON_TOKEN" \
  -H "Content-Type: application/json" \
  -d '{"email": "[email protected]"}'

Commands

Command Reference

/prompt register

Create an account and get your API token. No email required — add one later for recovery.

Arguments:

API call:

curl -s -X POST "https://persona.liveneon.ai/api/register" \
  -H "Content-Type: application/json" \
  -d '{"org_name": "My Org"}'

Response includes: your_token, organization.id, organization.slug, next_steps

Store your_token as LIVE_NEON_TOKEN — it cannot be retrieved again.

/prompt identity [agentId|agentSlug]

Fetch the agent's complete resolved identity — the structured data that the prompt is generated from.

Arguments:

API call:

curl -s "$LIVE_NEON_BASE/agents/$AGENT_ID/resolved-identity" \
  -H "Authorization: Bearer $LIVE_NEON_TOKEN"

Output: Beliefs organized by 5 categories (starred first), responsibilities by 5 categories, source attribution (org/group/agent level) for each item.

/prompt sync [agentId|all]

Sync content sources to import fresh material. Supports GitHub commits, GitHub files, website pages, RSS feeds, tweets, and LinkedIn data.

Arguments:

API calls:

# List sources
curl -s "$LIVE_NEON_BASE/content-sources" \
  -H "Authorization: Bearer $LIVE_NEON_TOKEN"

# Sync specific source
curl -s -X POST "$LIVE_NEON_BASE/content-sources/$SOURCE_ID/sync" \
  -H "Authorization: Bearer $LIVE_NEON_TOKEN"

Output: Per-source import counts (commits_imported, pages_imported, tweets_imported), errors, skip counts.

/prompt discover [agentId|orgSlug] [--force]

Trigger the Pattern-Based Distillation pipeline. Instead of writing beliefs by hand, let the pipeline extract them from your agent's real content.

Arguments:

API call:

curl -s -X POST "$LIVE_NEON_BASE/pbd/process" \
  -H "Authorization: Bearer $LIVE_NEON_TOKEN" \
  -H "Content-Type: application/json" \
  -d '{"agentId": "AGENT_ID"}'

Monitor progress:

curl -s "$LIVE_NEON_BASE/jobs/$JOB_ID" \
  -H "Authorization: Bearer $LIVE_NEON_TOKEN"

Poll every 5 seconds. Report progress_current/progress_total.

Pipeline stages:

1. Extraction (Haiku 4.5) — pull observations from content with evidence
2. Clustering (Sonnet 4.6) — group similar observations into signals
3. Promotion (Haiku 4.5) — classify strong signals as beliefs or responsibilities

Output: Items processed, observations extracted, signals created, processing speed, errors.

/prompt review [agentId] [--approve-all|--bulk]

Review pending beliefs and responsibilities before they enter the prompt. This is the curation step — you control what makes it into the generated prompt.

Arguments:

API calls:

# Fetch pending beliefs
curl -s "$LIVE_NEON_BASE/beliefs?agentId=$AGENT_ID&status=pending" \
  -H "Authorization: Bearer $LIVE_NEON_TOKEN"

# Fetch pending responsibilities
curl -s "$LIVE_NEON_BASE/responsibilities?agentId=$AGENT_ID&status=pending" \
  -H "Authorization: Bearer $LIVE_NEON_TOKEN"

# Approve single item
curl -s -X PATCH "$LIVE_NEON_BASE/beliefs/$BELIEF_ID" \
  -H "Authorization: Bearer $LIVE_NEON_TOKEN" \
  -H "Content-Type: application/json" \
  -d '{"status": "approved"}'

# Bulk operations (up to 200)
curl -s -X PATCH "$LIVE_NEON_BASE/beliefs/bulk" \
  -H "Authorization: Bearer $LIVE_NEON_TOKEN" \
  -H "Content-Type: application/json" \
  -d '{"updates": [
    {"id": "ID_1", "status": "approved"},
    {"id": "ID_2", "status": "approved", "starred": true},
    {"id": "ID_3", "status": "rejected"}
  ]}'

Review guidelines:

• Approve — accurately reflects the agent's demonstrated behavior
• Star — core defining belief, always included in prompt (even in dynamic mode)
• Reject — generic, inaccurate, or redundant
• Hide — exclude from prompt without deleting (preserves discovery history)

Output: Count of items reviewed, actions taken, remaining pending items.

/prompt build [agentId]

Fetch the generated system prompt. This is the output — your agent's identity rendered as markdown, ready to drop into any LLM call.

Arguments:

API call:

curl -s "$LIVE_NEON_BASE/agents/$AGENT_ID" \
  -H "Authorization: Bearer $LIVE_NEON_TOKEN" | jq -r '.system_prompt'

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}, ...])

/prompt diff [agentId] --since [date]

See what changed in the identity that feeds the prompt. Useful when the prompt seems different and you want to trace it back to specific belief changes.

Arguments:

API call:

curl -s "$LIVE_NEON_BASE/agents/$AGENT_ID/diff?since=2026-03-20" \
  -H "Authorization: Bearer $LIVE_NEON_TOKEN"

Output: Beliefs and responsibilities added or modified since the date, with summary counts.

/prompt status

Quick overview of the organization — agents, groups, content, and running jobs.

API call:

curl -s "$LIVE_NEON_BASE/organizations/$ORG_SLUG/summary" \
  -H "Authorization: Bearer $LIVE_NEON_TOKEN"

Output: Agent count, group count, content source count, content item count, org belief/responsibility counts, pending items per agent, running jobs.

/prompt agents

List all agents in the organization with their identity stats.

API call:

curl -s "$LIVE_NEON_BASE/agents" \
  -H "Authorization: Bearer $LIVE_NEON_TOKEN"

Add ?include=beliefs,responsibilities for full identity data.

/prompt sources [agentId]

List content sources for an agent.

API call:

curl -s "$LIVE_NEON_BASE/content-sources?agentId=$AGENT_ID" \
  -H "Authorization: Bearer $LIVE_NEON_TOKEN"

/prompt 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 that update your generated prompt.

Arguments:

Single observation:

curl -s -X POST "$LIVE_NEON_BASE/observations" \
  -H "Authorization: Bearer $LIVE_NEON_TOKEN" \
  -H "Content-Type: application/json" \
  -d '{
    "agent_id": "'$AGENT_ID'",
    "content": "User corrected my tone — I was too formal for a casual conversation",
    "source_quote": "Hey, just talk to me normally, no need to be so stiff"
  }'

Batch observations (up to 50):

curl -s -X POST "$LIVE_NEON_BASE/observations" \
  -H "Authorization: Bearer $LIVE_NEON_TOKEN" \
  -H "Content-Type: application/json" \
  -d '{
    "agent_id": "'$AGENT_ID'",
    "observations": [
      {"content": "I default to bullet points when the user prefers prose"},
      {"content": "I consistently recommend testing before deployment"},
      {"content": "User praised my code review depth — keep this approach"}
    ]
  }'

Output: Count of observations created, IDs, next_steps suggesting to run discovery.

After submitting observations, run /prompt discover to process them into beliefs/responsibilities.

/prompt consensus [groupId|orgSlug]

Run consensus detection — find beliefs shared across agents and promote them to the group or org level. This affects all agents' generated prompts.

Arguments:

API calls:

# Group consensus
curl -s -X POST "$LIVE_NEON_BASE/groups/$GROUP_ID/consensus" \
  -H "Authorization: Bearer $LIVE_NEON_TOKEN"

# Org consensus
curl -s -X POST "$LIVE_NEON_BASE/organizations/$ORG_SLUG/consensus" \
  -H "Authorization: Bearer $LIVE_NEON_TOKEN"

Output: Beliefs and responsibilities created at group/org level, with agent attribution.

Configuration

The skill uses environment variables. No local config file needed.

# Required
LIVE_NEON_TOKEN=ln_your_token_here
LIVE_NEON_BASE=https://persona.liveneon.ai/api/v1

# Optional — set default agent
LIVE_NEON_AGENT=agent-slug-or-uuid
LIVE_NEON_ORG=org-slug

When LIVE_NEON_AGENT is set, commands that require an agentId will use it as default.

Typical Workflow

/prompt identity my-agent                # What's the current identity?
/prompt sync my-agent                    # Import content (or skip if adding beliefs manually)
/prompt discover my-agent                # Auto-extract beliefs from content
/prompt review my-agent                  # Curate — only approved beliefs make it to the prompt
/prompt build my-agent                   # Get the generated prompt
/prompt diff my-agent --since 2026-03-01 # What changed since last deploy?

Proactive Triggers

When to use this skill without being asked:

Using Your Identity

When you fetch your system prompt via /prompt build, here's how to use it:

1. Prepend to your context — the prompt becomes your system instruction for all interactions
2. Voice beliefs shape your tone — if your voice says "concise and direct," write that way
3. Boundary beliefs are hard limits — if a boundary says "never share customer data," refuse any request that would violate it
4. Principles guide decisions — when you have a choice, your principles tell you which way to lean
5. Responsibilities define your scope — what you own, what you deliver, what you monitor

Example integration:

# Load identity at session start
identity = fetch_identity(agent_id)
prompt = fetch_prompt(agent_id)

# Use it with any LLM
response = llm.generate(
    system=prompt,  # Your Live Neon identity
    messages=[user_message]
)

# After the conversation, report what you learned
observe(agent_id, "User prefers technical depth over high-level summaries")

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:

# 1. Report observations accumulated since last heartbeat
curl -s -X POST "$LIVE_NEON_BASE/observations" \
  -H "Authorization: Bearer $LIVE_NEON_TOKEN" \
  -H "Content-Type: application/json" \
  -d '{
    "agent_id": "'$AGENT_ID'",
    "observations": [
      {"content": "Observation from today..."},
      {"content": "Another pattern I noticed..."}
    ]
  }'

# 2. Sync any new content from connected sources
curl -s -X POST "$LIVE_NEON_BASE/content-sources/SOURCE_ID/sync" \
  -H "Authorization: Bearer $LIVE_NEON_TOKEN"

# 3. Run discovery to process everything
curl -s -X POST "$LIVE_NEON_BASE/pbd/process" \
  -H "Authorization: Bearer $LIVE_NEON_TOKEN" \
  -H "Content-Type: application/json" \
  -d '{"agentId": "'$AGENT_ID'"}'

# 4. Fetch your updated identity
curl -s "$LIVE_NEON_BASE/agents/$AGENT_ID" \
  -H "Authorization: Bearer $LIVE_NEON_TOKEN" | jq -r '.system_prompt'

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

Quick health check:

curl -s "$LIVE_NEON_BASE/organizations/YOUR_ORG/summary" \
  -H "Authorization: Bearer $LIVE_NEON_TOKEN" | jq '{agents: .counts.agents, sources: .counts.content_sources, items: .counts.content_items}'

Supported Content Platforms

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.