sf-ai-agentforce-persona
Audited by Runlayer on Mar 13, 2026
Malicious tool definition detected
Constraint notes in the framework explain how earlier choices pull later ones. ## GENERATION GUARDRAILS These behavioral constraints apply when executing the persona design workflow: - **Context fields are agent design, not persona** — Name, role, audience, agent type, surface, use cases originate in agent design. Persona design imports or minimally gathers them.
Tool: sf-ai-agentforce-persona/SKILL.md [4/4] Description: and persona boundary scenarios. | **Scoring rules:** - Score each category independently. Provide a number and 1-2 sentences of justification. - Flag any inconsistencies between dimensions or settings (e.g., "Personable voice but Clinical Analyst tone — these may conflict in practice").
Tool passed security scan
Malicious tool definition detected
Tool: sf-ai-agentforce-persona/references/persona-encoding-guide.md [3/4] Description: by a dropdown - **Identity** — personality traits are far richer than 3 options **Recommendation:** Set the dropdown to whichever option is closest to your persona's Register + Voice combination. Then do the real persona work in Topic Instructions and Action Output Response Instructions. The dropdown is a global nudge; the instructions are where persona actually lives.
- **Instruction precedence:** The working assumption is that topic instructions supersede system instructions, but more testing is needed to evaluate this. If confirmed, the system prompt carries the baseline persona and topic instructions carry overrides — the same layering pattern as Agent Builder (global Role + per-topic detail).
Tool passed security scan
Tool passed security scan
Passed Files (4)Click to expand
Tool passed security scan
Tool passed security scan
Tool passed security scan
Tool passed security scan