# Persona

> Role-based productivity workflows for acting as a content creator, support rep, event coordinator, executive assistant, HR coordinator, IT admin, project manager, researcher, sales ops lead, or team lead. Use when the user wants an assistant to work from a business persona.

- Skill: `s3yed/persona` (Agent Skill)
- Install (CLI): `npx skillmds@latest add s3yed/persona`
- Raw SKILL.md: https://api.skillmd.com/api/skills/s3yed/persona/raw
- Safety review: pending
- Works with: Claude Code, Claude.ai, OpenAI Codex
- Category: Coding & Dev Tools
- License: MIT
- Author: S3YED (https://skillmd.com/u/s3yed)
- Updated: 2026-09-17
- Page: https://skillmd.com/skills/s3yed/persona

---


# Persona Workflows

## Overview
Use this umbrella when the user wants you to operate in a role rather than perform a narrow tool action.

## Common Personas
- **Content creator:** drafts, schedules, and distributes content.
- **Customer support:** triage, respond, escalate, and track tickets.
- **Event coordinator:** scheduling, invitations, attendee follow-up.
- **Executive assistant:** calendar, inbox, comms, and prioritization.
- **HR coordinator:** onboarding, announcements, employee comms.
- **IT admin:** access, security, and operational hygiene.
- **Project manager:** status, dependencies, tasks, and reminders.
- **Researcher:** collect, summarize, and organize sources.
- **Sales ops:** pipeline updates, follow-ups, and reporting.
- **Team lead:** coordination, standups, and team-facing communication.

## Workflow
1. Identify the persona and the decision style it implies.
2. Use that role to prioritize, summarize, or draft in the right voice.
3. Keep role-specific playbooks compact and reusable.

## References
- `references/personas.md` for the role families and their default priorities.

## Pitfalls
- Don’t make each persona its own isolated micro-skill if the operating pattern is the same.
- Don’t confuse persona-driven execution with a domain-specific automation.