# Persona Create

> This skill should be used when the user asks to "create a persona", "add a new persona", "set up a new agent role", "add a woterclip persona", or runs the /persona-create command. Interactively creates a new WoterClip persona with SOUL.md, TOOLS.md, and config.yaml.

- Skill: `samin12/persona-create` (Agent Skill, multi-file: 2 files)
- Install (CLI): `npx skillmds@latest add samin12/persona-create`
- Raw SKILL.md: https://api.skillmd.com/api/skills/samin12/persona-create/raw
- Safety review: pending
- Works with: Claude Code, Claude.ai, OpenAI Codex
- Category: AI & ML
- Author: Samin12 (https://skillmd.com/u/samin12)
- Updated: 2026-09-22
- Page: https://skillmd.com/skills/samin12/persona-create

---

# Create Persona

Interactively create a new WoterClip persona for this repository.

## Prerequisites

Verify `.woterclip/config.yaml` exists. If not, instruct the user to run `/woterclip-init` first.

## Procedure

### Step 1: Gather Persona Details

Ask the user for:

1. **Name** — Display name (e.g., "QA Engineer", "Infra Engineer", "Research Analyst")
2. **Role** — Role type: `engineer`, `orchestrator`, `analyst`, or custom
3. **Label** — Linear label for routing issues to this persona (e.g., `qa`, `infra`, `research`). Must be unique across existing personas.
4. **Escalates to** — Which persona to escalate to (default: `ceo`)
5. **Model** — Runtime model: `opus`, `sonnet`, or `haiku` (suggest based on role complexity)
6. **Required tools** — Beyond `mcp__claude_ai_Linear`, which tool prefixes does this persona need? (e.g., `mcp__neon`, `mcp__plugin_playwright_playwright`)

### Step 2: Generate SOUL.md

Create a SOUL.md tailored to the persona's role. Use the structure from existing persona templates:

- **Identity** — One-sentence role description
- **Technical Posture** — 5-7 principles for how this persona approaches work
- **Voice and Tone** — Communication style
- **Working Style** — How to approach tasks
- **Boundaries** — What this persona does NOT do (reference other personas)
- **Quality Checklist** — Pre-completion checks

Present the generated SOUL.md to the user for review. Ask if they want to edit any section.

### Step 3: Generate TOOLS.md

Create a TOOLS.md listing:
- Required tools (from step 1)
- Common usage patterns for this persona's role
- Optional tools the user might add later

### Step 4: Generate config.yaml

Create the persona's runtime config:

```yaml
name: <Name>
role: <role>
label: <label>
escalates_to: <escalates_to>

required_tools:
  - mcp__claude_ai_Linear
  # additional tools from step 1

runtime:
  model: <model>
  thinking_effort: <high for opus, medium for sonnet/haiku>
  max_turns: <300 for opus, 200 for sonnet, 100 for haiku>
  enable_chrome: false
  timeout: 0
  extra_args: []
```

### Step 5: Write Files

1. Create `.woterclip/personas/<label>/` directory
2. Write `SOUL.md`, `TOOLS.md`, `config.yaml`

### Step 6: Update Config

Read `.woterclip/config.yaml` and add the new persona to the `personas` map:

```yaml
<label>:
  path: "personas/<label>"
  label: "<label>"
```

### Step 7: Create Linear Label

Call `mcp__claude_ai_Linear__list_issue_labels` to check if the label exists. If not, create it under the WoterClip group via `mcp__claude_ai_Linear__create_issue_label`.

### Step 8: Summary

```
Persona created: <Name>
  Label:    <label>
  Model:    <model>
  Escalates: <escalates_to>
  Path:     .woterclip/personas/<label>/

Files:
  ✓ SOUL.md
  ✓ TOOLS.md
  ✓ config.yaml

Linear label "<label>" created under WoterClip group.

Customize SOUL.md to match your project's specific needs.
```