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.From its SKILL.md
npx -y skills add S3YED/appie-kit --skill personaAssembled from the repository path, not quoted from the project. Check it against their README if it does not work.
One thing to look at
- 6 stars6 stars. Stars are a popularity signal and not a quality one, but at this level it is likely that nobody has read this closely except its author, and you would be relying on your own review.
What its file declares
Copied from the file, not written here
The file declares its own license as MIT. That is the author’s claim about this one file, and it is not the same thing as the license GitHub reports for the repository, which is listed with the other numbers below.
SKILL.md
1.8 KB, 275 tokens by cl100k_base, as published. Nobody here has run it
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
- Identify the persona and the decision style it implies.
- Use that role to prioritize, summarize, or draft in the right voice.
- Keep role-specific playbooks compact and reusable.
References
references/personas.mdfor 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.
What ships with it
Read from the repository
Just SKILL.md. No reference files, no scripts.