Persona Route
OverKill Hill P³ · overkillhill.com · github.com/OKHP3
The router stays narrow and boring. The personas stay expressive.
This skill answers one question: which agent should own this, and what do
they need to start? It does not do the work.
Scope
Use on the default or front-door agent (Larry, in the reference deployment)
when the owner hasn't picked a persona, or when a task needs to cross
agents mid-pipeline. Channel routing still wins: if the owner messaged a
specific persona directly, that persona owns the request.
Default roster
Override from the deployment's workspace AGENTS.md when it defines its own.
| Persona |
Owns |
Route when |
| Larry |
General Q&A, research, errands, file and repo work, dispatch |
Default; anything not clearly owned below |
| AskJamie |
Correspondence drafted in the owner's voice |
Email, DM, or reply the owner will send as themselves |
| MurderBird |
Long-form thesis, structure, and argument red team |
Articles, essays, position pieces, "does this hold" |
| Glee-fully |
WWGD reception and warmth check |
"How will this land", sensitive or relational drafts before sending |
Multi-stage pipelines:
- Email: Larry (context) to AskJamie (draft) to Glee-fully (WWGD, if sensitive) to owner.
- Article: Larry (research) to MurderBird (thesis and audit) to voice pass to Glee-fully (WWGD) to owner.
Procedure
- Check for an explicit persona in the request or channel. If present, stop
and let that persona own it.
- Classify the request: correspondence, long-form argument, reception
check, or general.
- Pick the owner from the roster. If two fit, pick the one that owns the
first pipeline stage.
- If the request is ambiguous after one pass, ask the owner one question.
- Build the handoff packet with only the context the next agent needs.
Exclude secrets, credentials, and unrelated private content.
- Deliver:
- If the runtime exposes an agent-to-agent messaging tool and the owner
has enabled it for this deployment, send the packet there and report the
tool's confirmation.
- Otherwise return the packet in chat with the target persona named, so
the owner can forward it. Say plainly that cross-agent delivery is not
configured.
- Verify before returning: the packet names one owner, one task, and any
open questions; nothing in it was invented.
Handoff packet
[HANDOFF]
to: <persona>
from: <persona>
task: <one sentence>
context: <only what the next agent needs; links or file paths preferred>
result-so-far: <what is already done, or "none">
open-questions: <list, or "none">
return-to: <persona or owner>
Rules
- Route, never execute. The owning persona does the work.
- Never change bindings, agent config, or tool policy from this skill.
- A persona boundary is also a trust boundary: never pass private mail
content to a public-facing agent.
- Report routing reasons in one line so the owner can overrule it.
About
Built by Jamie Hill · OverKill Hill P³
Published at github.com/OKHP3
Part of the OKHP3/skillz Agent Skill library.
MIT License. Free to use, fork, and adapt. A nod to the source is appreciated.
1---2name: okhp3-openclaw-persona-route3description: Decide which OpenClaw agent persona should own a request (Larry, AskJamie, MurderBird, or Glee-fully by default), then package the work as a [HANDOFF] packet. Use when a request arrives at the default agent without a named persona, when work must move between agents, or when asked "who should handle this". Routes only; never executes the routed task.4license: MIT5metadata:6 source: https://skillmd.com/skills/okhp3/okhp3-openclaw-persona-route7 author: Jamie Hill (OverKill Hill P³)8 version: "0.1.0"9 category: openclaw10 origin: okhp3/skillz11 homepage: https://overkillhill.com12 author-github: https://github.com/OKHP313 in_scope: "Classify a request, pick the owning agent persona, and emit a handoff packet."14 out_of_scope: "Executing the routed task, changing agent bindings or config, and cross-agent messaging that the owner has not enabled."15 openclaw:16 requires: {}17---1819# Persona Route2021**OverKill Hill P³** · [overkillhill.com](https://overkillhill.com) · [github.com/OKHP3](https://github.com/OKHP3)2223The router stays narrow and boring. The personas stay expressive.2425This skill answers one question: which agent should own this, and what do26they need to start? It does not do the work.2728## Scope2930Use on the default or front-door agent (Larry, in the reference deployment)31when the owner hasn't picked a persona, or when a task needs to cross32agents mid-pipeline. Channel routing still wins: if the owner messaged a33specific persona directly, that persona owns the request.3435## Default roster3637Override from the deployment's workspace `AGENTS.md` when it defines its own.3839| Persona | Owns | Route when |40|---|---|---|41| Larry | General Q&A, research, errands, file and repo work, dispatch | Default; anything not clearly owned below |42| AskJamie | Correspondence drafted in the owner's voice | Email, DM, or reply the owner will send as themselves |43| MurderBird | Long-form thesis, structure, and argument red team | Articles, essays, position pieces, "does this hold" |44| Glee-fully | WWGD reception and warmth check | "How will this land", sensitive or relational drafts before sending |4546Multi-stage pipelines:4748- **Email:** Larry (context) to AskJamie (draft) to Glee-fully (WWGD, if sensitive) to owner.49- **Article:** Larry (research) to MurderBird (thesis and audit) to voice pass to Glee-fully (WWGD) to owner.5051## Procedure52531. Check for an explicit persona in the request or channel. If present, stop54 and let that persona own it.552. Classify the request: correspondence, long-form argument, reception56 check, or general.573. Pick the owner from the roster. If two fit, pick the one that owns the58 first pipeline stage.594. If the request is ambiguous after one pass, ask the owner one question.605. Build the handoff packet with only the context the next agent needs.61 Exclude secrets, credentials, and unrelated private content.626. Deliver:63 - If the runtime exposes an agent-to-agent messaging tool and the owner64 has enabled it for this deployment, send the packet there and report the65 tool's confirmation.66 - Otherwise return the packet in chat with the target persona named, so67 the owner can forward it. Say plainly that cross-agent delivery is not68 configured.697. Verify before returning: the packet names one owner, one task, and any70 open questions; nothing in it was invented.7172## Handoff packet7374```text75[HANDOFF]76to: <persona>77from: <persona>78task: <one sentence>79context: <only what the next agent needs; links or file paths preferred>80result-so-far: <what is already done, or "none">81open-questions: <list, or "none">82return-to: <persona or owner>83```8485## Rules8687- Route, never execute. The owning persona does the work.88- Never change bindings, agent config, or tool policy from this skill.89- A persona boundary is also a trust boundary: never pass private mail90 content to a public-facing agent.91- Report routing reasons in one line so the owner can overrule it.9293## About9495Built by [Jamie Hill](https://overkillhill.com) · [OverKill Hill P³](https://overkillhill.com)96Published at [github.com/OKHP3](https://github.com/OKHP3)97Part of the [OKHP3/skillz](https://github.com/OKHP3/skillz) Agent Skill library.98MIT License. Free to use, fork, and adapt. A nod to the source is appreciated.