docs: enforce real hire names in create-agent skill

Co-Authored-By: Paperclip <noreply@paperclip.ing>

skills/paperclip-create-agent/SKILL.md

@@ -73,7 +73,7 @@ curl -sS "$PAPERCLIP_API_URL/llms/agent-icons.txt" \
 
 ### 6. Draft the new hire config
 
-- role / title / name
+- `name` / `role` / `title` — **the `name` field MUST be a real human first + last name** (e.g. `Ada Whitfield`), never the role, function, or team. Put the function in `title` (e.g. "Chief Technology Officer") and the role enum in `role` (e.g. `cto`). Pick a name not already used by an existing teammate.
 - icon (required in practice; pick from `/llms/agent-icons.txt`)
 - reporting line (`reportsTo`)
 - adapter type
@@ -100,7 +100,7 @@ curl -sS -X POST "$PAPERCLIP_API_URL/api/companies/$PAPERCLIP_COMPANY_ID/agent-h
   -H "Authorization: Bearer $PAPERCLIP_API_KEY" \
   -H "Content-Type: application/json" \
   -d '{
-    "name": "CTO",
+    "name": "Ada Whitfield",
     "role": "cto",
     "title": "Chief Technology Officer",
     "icon": "crown",

skills/paperclip-create-agent/references/draft-review-checklist.md

@@ -9,6 +9,7 @@ Use it for every path: exact template, adjacent template, or generic fallback.
 ## A. Identity and framing
 
 - [ ] `name`, `role`, and `title` are set and consistent with each other
+- [ ] `name` is a real human first + last name (e.g. `Ada Whitfield`), not the role/function/team — the function lives in `title` and the enum in `role`; the chosen name is not already used by an existing teammate
 - [ ] `AGENTS.md` names the agent, the role, and the company in the first sentence
 - [ ] The first paragraph points at the Paperclip skill as the source of truth for the heartbeat procedure
 - [ ] The reporting line (`reportsTo`) resolves to a real in-company agent id