Gabriel Operator

View saved version →

---
name: persona-builder
description: Interview the user and author a local Gabriel AI Persona draft covering page copy, list schema, pipeline stages, optional team-agent graph, and optional review-only workflow. Use when the user wants to design a new persona in files they control. Produces local drafts only and does not publish, provision, authenticate, or call remote services.
---

# Persona Builder

Design one Gabriel AI Persona as local draft files for human review.

This public skill covers the same draft files as `digital-twin-page`,
`list-builder`, `pipeline-builder`, and `team-agents`. It does not create live
Gabriel resources. Live create, git bind, and publish stay in Gabriel Operator
after the user reviews these files.

## Public authoring boundary

- Work only in the repository the user explicitly selects.
- Write local draft files only. Do not commit, push, publish, deploy, or run.
- Do not request, infer, copy, or store passwords, API keys, access tokens, cookies, or session data.
- Do not call remote APIs, open Gabriel Operator in a browser, or sync live records.
- Do not add real personal, confidential, financial, or authentication data.
- Use placeholder ids such as `page_example`. Do not invent production database ids.
- If the user asks to provision, publish, or authenticate, refuse and point them to Gabriel Operator.

## Interview

Collect, propose, confirm, then write files. Do not dump empty JSON and stop.

1. Ask what the persona does if the user did not already describe it.
2. Propose a title, short description, visibility (`private` default), list columns, pipeline stages, and whether a team-agent graph or a review-only workflow is needed.
3. Confirm the proposal.
4. Write the files below.
5. Summarize the files changed and note that live create/publish is a separate user action.

## Canonical files

```text
assets/chat-config.json
assets/list.json
assets/pipeline.json
assets/team-agent.json
assets/task-orchestration.json
assets/workflow.json
```

Write `chat-config.json`, `list.json`, and `pipeline.json` for every new persona.
Write team-agent and workflow files only when the confirmed proposal includes them.
Preserve unknown fields and stable ids when a file already exists.

## Page copy (`assets/chat-config.json`)

Supported fields only: `pageProfile.title`, `pageProfile.description`,
`pageProfile.longDescription`, `pageProfile.profilePicture`,
`pageProfile.bannerImage`, `pageProfile.bannerType`, `pageProfile.tags`,
`pageProfile.category`, `pageProfile.subcategory`, `publishedConfig.name`,
`publishedConfig.firstMessage`, `publishedConfig.systemPrompt`.

Keep conversational instructions clear and non-deceptive. Do not claim tools,
connectors, or live data this draft cannot provide.

```json
{
  "schemaVersion": 1,
  "pageId": "page_example",
  "publishedConfig": {
    "name": "Assistant",
    "firstMessage": "How can I help?",
    "systemPrompt": "Answer using the material supplied by the user."
  },
  "pageProfile": {
    "title": "Assistant",
    "description": "A helpful digital twin",
    "tags": []
  },
  "updatedAt": 0
}
```

## List schema (`assets/list.json`)

Edit schema only. Do not import or write live records. Column types: `text`,
`number`, `boolean`, `date`, `select`. Use `options` only on `select` columns.

Additional lists, if requested, go in `assets/lists/<slug>.json` with the same shape.

```json
{
  "schemaVersion": 1,
  "listId": "list_example",
  "list": {
    "id": "list_example",
    "name": "Example List",
    "description": "Review-only list schema",
    "collectionId": "collection_example",
    "columns": [
      {
        "key": "title",
        "label": "Title",
        "type": "text",
        "required": true
      }
    ]
  },
  "commitMessage": "Draft list schema"
}
```

## Pipeline (`assets/pipeline.json`)

One pipeline is one state-machine draft. Stages are metadata. Transitions are
allowed moves. Do not run the machine or modify live records.

```json
{
  "schemaV

Preview of the first 4,000 characters. Read full instructions →

Referenced files: 1 — file references are metadata, not package contents.