Import Persona from Paperclip
Convert a Paperclip agent directory into a WoterClip persona. Maps Paperclip's agent structure (SOUL.md, AGENTS.md, HEARTBEAT.md, TOOLS.md) to WoterClip's persona structure (SOUL.md, TOOLS.md, config.yaml).
Prerequisites
.woterclip/config.yaml must exist (run /woterclip-init first)
- User must provide the path to the Paperclip agent directory
File Mapping
| Paperclip File |
WoterClip Target |
What to Import |
SOUL.md |
SOUL.md |
Copy as-is — identity, posture, voice |
HEARTBEAT.md |
Append to SOUL.md |
Only the role-specific responsibilities section (bottom). Skip the generic heartbeat procedure (top) — replaced by the plugin's heartbeat skill |
AGENTS.md |
config.yaml + SOUL.md |
Safety rules → append to SOUL.md Boundaries section. Workspace paths → drop. Memory refs → drop |
TOOLS.md |
TOOLS.md |
Copy, replacing Paperclip API references with Linear MCP equivalents |
life/, memory/ |
Skip |
Claude Code has built-in memory |
Import Procedure
Step 1: Read Source
Ask the user for the Paperclip agent directory path. Read all files present:
SOUL.md (required)
AGENTS.md (optional)
HEARTBEAT.md (optional)
TOOLS.md (optional)
If SOUL.md doesn't exist, stop — this is not a valid Paperclip agent directory.
Step 2: Ask for Persona Details
Ask the user:
- Persona name — e.g., "Backend Engineer" (pre-fill from SOUL.md if obvious)
- Linear label — e.g.,
backend (must be unique)
- Role type —
engineer, orchestrator, analyst, or custom
- Model —
opus, sonnet, or haiku (suggest based on role)
- Escalates to — default:
ceo
Step 3: Transform SOUL.md
- Start with the Paperclip
SOUL.md content
- From
HEARTBEAT.md: extract the role-specific section (usually the bottom half, after the generic heartbeat steps). Append as a "## Working Style" or "## Role Responsibilities" section
- From
AGENTS.md: extract safety rules and boundaries. Append to the "## Boundaries" section
- Add a WoterClip-specific "## Quality Checklist" section if not present
- Drop any Paperclip-specific references (workspace paths, PARA memory, budget tracking)
Step 4: Transform TOOLS.md
- Start with the Paperclip
TOOLS.md content
- Replace Paperclip API references:
paperclip skill → mcp__claude_ai_Linear__* (Linear MCP tools)
para-memory-files → drop (replaced by Claude Code built-in memory)
- Paperclip API calls (
POST /checkout, PATCH /api/issues) → Linear MCP equivalents
- Add a "## Required" section listing
mcp__claude_ai_Linear and any other tool prefixes
- If AGENTS.md references playbooks, note them for manual migration
Step 5: Generate config.yaml
Create the persona config:
name: <Name>
role: <role>
label: <label>
escalates_to: <escalates_to>
required_tools:
- mcp__claude_ai_Linear
# additional tools based on TOOLS.md
runtime:
model: <model>
thinking_effort: <high for opus, medium otherwise>
max_turns: <300 for opus, 200 for sonnet, 100 for haiku>
enable_chrome: false
timeout: 0
extra_args: []
Step 6: Write Files
- Create
.woterclip/personas/<label>/
- Write
SOUL.md, TOOLS.md, config.yaml
- Update
.woterclip/config.yaml to add the persona to the personas map
- Create the Linear label if it doesn't exist
Step 7: Summary
Imported: <Name> (from <source-path>)
Label: <label>
Model: <model>
Files created:
✓ .woterclip/personas/<label>/SOUL.md
✓ .woterclip/personas/<label>/TOOLS.md
✓ .woterclip/personas/<label>/config.yaml
What was imported:
✓ SOUL.md — identity and posture
✓ HEARTBEAT.md — role responsibilities (appended to SOUL.md)
✓ AGENTS.md — safety rules (appended to Boundaries)
✓ TOOLS.md — tool list (Paperclip refs replaced)
What was NOT imported:
✗ Budget tracking (no WoterClip equivalent)
✗ PARA memory (replaced by Claude Code built-in memory)
✗ Approval workflows (not in v1)
Review SOUL.md and customize for this project's specific needs.
1---2name: persona-import3description: This skill should be used when the user asks to "import a paperclip agent", "convert paperclip to woterclip", "migrate from paperclip", "import persona from paperclip", or wants to convert existing Paperclip agent directories into WoterClip persona format.4---5# Import Persona from Paperclip67Convert a Paperclip agent directory into a WoterClip persona. Maps Paperclip's agent structure (SOUL.md, AGENTS.md, HEARTBEAT.md, TOOLS.md) to WoterClip's persona structure (SOUL.md, TOOLS.md, config.yaml).89## Prerequisites1011- `.woterclip/config.yaml` must exist (run `/woterclip-init` first)12- User must provide the path to the Paperclip agent directory1314## File Mapping1516| Paperclip File | WoterClip Target | What to Import |17|----------------|-----------------|----------------|18| `SOUL.md` | `SOUL.md` | Copy as-is — identity, posture, voice |19| `HEARTBEAT.md` | Append to `SOUL.md` | Only the role-specific responsibilities section (bottom). Skip the generic heartbeat procedure (top) — replaced by the plugin's heartbeat skill |20| `AGENTS.md` | `config.yaml` + `SOUL.md` | Safety rules → append to SOUL.md Boundaries section. Workspace paths → drop. Memory refs → drop |21| `TOOLS.md` | `TOOLS.md` | Copy, replacing Paperclip API references with Linear MCP equivalents |22| `life/`, `memory/` | Skip | Claude Code has built-in memory |2324## Import Procedure2526### Step 1: Read Source2728Ask the user for the Paperclip agent directory path. Read all files present:29- `SOUL.md` (required)30- `AGENTS.md` (optional)31- `HEARTBEAT.md` (optional)32- `TOOLS.md` (optional)3334If `SOUL.md` doesn't exist, stop — this is not a valid Paperclip agent directory.3536### Step 2: Ask for Persona Details3738Ask the user:391. **Persona name** — e.g., "Backend Engineer" (pre-fill from SOUL.md if obvious)402. **Linear label** — e.g., `backend` (must be unique)413. **Role type** — `engineer`, `orchestrator`, `analyst`, or custom424. **Model** — `opus`, `sonnet`, or `haiku` (suggest based on role)435. **Escalates to** — default: `ceo`4445### Step 3: Transform SOUL.md46471. Start with the Paperclip `SOUL.md` content482. From `HEARTBEAT.md`: extract the role-specific section (usually the bottom half, after the generic heartbeat steps). Append as a "## Working Style" or "## Role Responsibilities" section493. From `AGENTS.md`: extract safety rules and boundaries. Append to the "## Boundaries" section504. Add a WoterClip-specific "## Quality Checklist" section if not present515. Drop any Paperclip-specific references (workspace paths, PARA memory, budget tracking)5253### Step 4: Transform TOOLS.md54551. Start with the Paperclip `TOOLS.md` content562. Replace Paperclip API references:57 - `paperclip` skill → `mcp__claude_ai_Linear__*` (Linear MCP tools)58 - `para-memory-files` → drop (replaced by Claude Code built-in memory)59 - Paperclip API calls (`POST /checkout`, `PATCH /api/issues`) → Linear MCP equivalents603. Add a "## Required" section listing `mcp__claude_ai_Linear` and any other tool prefixes614. If AGENTS.md references playbooks, note them for manual migration6263### Step 5: Generate config.yaml6465Create the persona config:6667```yaml68name: <Name>69role: <role>70label: <label>71escalates_to: <escalates_to>7273required_tools:74 - mcp__claude_ai_Linear75 # additional tools based on TOOLS.md7677runtime:78 model: <model>79 thinking_effort: <high for opus, medium otherwise>80 max_turns: <300 for opus, 200 for sonnet, 100 for haiku>81 enable_chrome: false82 timeout: 083 extra_args: []84```8586### Step 6: Write Files87881. Create `.woterclip/personas/<label>/`892. Write `SOUL.md`, `TOOLS.md`, `config.yaml`903. Update `.woterclip/config.yaml` to add the persona to the `personas` map914. Create the Linear label if it doesn't exist9293### Step 7: Summary9495```96Imported: <Name> (from <source-path>)97 Label: <label>98 Model: <model>99100Files created:101 ✓ .woterclip/personas/<label>/SOUL.md102 ✓ .woterclip/personas/<label>/TOOLS.md103 ✓ .woterclip/personas/<label>/config.yaml104105What was imported:106 ✓ SOUL.md — identity and posture107 ✓ HEARTBEAT.md — role responsibilities (appended to SOUL.md)108 ✓ AGENTS.md — safety rules (appended to Boundaries)109 ✓ TOOLS.md — tool list (Paperclip refs replaced)110111What was NOT imported:112 ✗ Budget tracking (no WoterClip equivalent)113 ✗ PARA memory (replaced by Claude Code built-in memory)114 ✗ Approval workflows (not in v1)115116Review SOUL.md and customize for this project's specific needs.117```