/agentforce-persona-generate

name: agentforce-persona-generate
description: "Use to design an AI agent persona — identity, voice, tone, behavioral style, guardrails — and encode it into Agent Script (.agent files) or Agentforce Builder field values. Runs four sequenced phases (DRAFT, REFINE, SCORE, ENCODE) plus five spokes (NAME, FILL OUT, ADJUST, CHECKLIST, WORKSHOP). Supports greenfield (brand input to a starter .agent file) and brownfield (audit an existing .agent file and re-encode persona fields only), with a 100-point evaluation rubric. Trigger when a user designs a new agent persona, retrofits persona consistency, translates brand guidelines into agent voice, defines tone/register/formality/warmth/humor/personification, encodes a persona for Agent Script or Agentforce Builder, or scores or audits an existing .agent file for persona quality. Do not trigger for building Agentforce actions/metadata, authoring Agent Script flow control without persona work, or testing agent conversations."
metadata:
  relatedSkills:
    - "agentforce-generate"
  version: "3.0"
  domains: ["Agentforce"]
  cliTools:
    - tool: ["python3"]
      semver: ">=3.10.0"
allowed-tools: Read Write AskUserQuestion Glob Grep

Designing Agent Persona

How to Use

This skill designs an AI agent persona for Salesforce Agentforce. It walks through four sequenced phases (DRAFT → REFINE → SCORE → ENCODE) and offers five spokes (NAME, FILL OUT, ADJUST, CHECKLIST, WORKSHOP) you can run any time after DRAFT.

**What it produces:**

• A persona document (`persona/[agent-name]/persona.md`) — who the agent is, how it sounds, what it never does
• A sample dialog (`persona/[agent-name]/sample-dialog.md`) — the persona in action
• An evaluation report on request (`persona/[agent-name]/evaluation.md`) — 100-point rubric, gap analysis, recommendations
• A completeness checklist on request (`persona/[agent-name]/checklist.md`) — what's filled in, what's missing
• A workshop outline on request (`persona/[agent-name]/workshop-outline.md`) — stakeholder questions, dimension cards
• An encoding artifact on request — valid Agent Script `.agent` file, OR Agentforce Builder field values

**Session resumption:** If you stop mid-phase, your progress is preserved in the conversation and can be resumed.

When to Use This Skill

• Designing a new Agentforce agent and need to define its personality before building (greenfield)
• Auditing an existing `.agent` file's persona consistency (brownfield)
• Translating brand guidelines into a structured persona
• Producing a stakeholder workshop outline to gather design input
• Aligning teams on what an agent should sound like before development

**Scope boundary:** This skill defines WHO the agent is. It does not define dialog flows, subagents, actions, routing, or variables — those are agent design (use `agentforce-generate`). The encoding output for Use Case A produces an `.agent` skeleton with placeholders for those structures; the user fills them in.

Framework Reference

Read `references/persona-framework.md` for the full framework. It defines:

• **Identity** — 3-5 anchoring adjectives + Negative Identity (≥2 character-level anti-patterns)
• **14 dimensions** (Personification + the 13 expression dimensions):
• **Personification** — Talking System / Familiar Thing / Personal Assistant
• **Register** — Subordinate / Peer / Advisor / Coach
• **Voice** — Formality, Warmth, Personality Intensity, Reading Level
• **Tone** — Emotional Coloring, Empathy Level (+ Tone Boundaries, Tone Flex)
• **Delivery** — Brevity, Humor
• **Chatting Style** — Emoji, Formatting, Punctuation, Capitalization
• **Persona Artifacts** — Identity (traits + negative identity), Expression (tone boundaries + never-say + guardrails), Phrasing (phrase book + discourse markers + lexicon)
• **Tone Flex** — how tone shifts by context (including per-subagent calibration)
• **Lexicon** — global and per-subagent vocabulary, including immutable terms
• **Guardrails** — content-level boundaries (e.g., "Don't offer medical advice"), distinct from Never-Say

Attributes are ordered by dependency. Identity → Personification → Register → Voice → Tone → Delivery → Chatting Style. Constraint notes recommend natural pairings; any combination is valid.

Attribution for the external sources this skill draws on is in `references/attributions.md`.

---

Pre-DRAFT Triage — Greenfield or Brownfield?

**Before anything else,** ask the user which lane they're on. The two lanes diverge significantly downstream.

> Welcome. Two ways to use this skill: > > 1. **Starting fresh** — design a persona from scratch using brand input, audience details, and channel. **Greenfield.** > 2. **Auditing an existing agent** — review and improve a `.agent` file you already have. **Brownfield.** > > Which one?

Set a `mode` flag in state: `greenfield` or `brownfield`.

**Brownfield triggers:**

• User uploads a `.agent` file → load via `scripts/parse_agent_yaml.py` (read-only)
• ADJUST spoke is immediately available (subagents and actions exist)
• SCORE includes per-subagent and per-action sub-scoring
• ENCODE produces annotated proposed-new-file + diff summary, never inventing structure

**Greenfield triggers:**

• ENCODE produces a starter `.agent` skeleton with placeholders for subagents/actions/routing
• ADJUST spoke is initially gated (offered only if user later declares subagents)

---

Architecture: Phases and Spokes

**Phases** are sequenced — order matters. **Spokes** orbit the hub, available any time after DRAFT, in any order. The hub is presented after every phase or spoke exit.

SEQUENCED PHASES (linear pipeline):
  DRAFT → REFINE → SCORE → ENCODE
                          ↑
              (loop back via phases or spokes if SCORE finds gaps)

SPOKES (radiate from the HUB; any time after DRAFT):
  ⊙ NAME              — pick or confirm the agent's name
  ⊙ FILL OUT          — phrase book, never-say, lexicon, immutable content
  ⊙ ADJUST            — s