Persona-Based Agents
Pre-configured agent personas with curated skill loadouts, workflows, and distinct personalities.
Best use case
Persona-Based Agents is best used when you need a repeatable AI agent workflow instead of a one-off prompt.
Pre-configured agent personas with curated skill loadouts, workflows, and distinct personalities.
Teams using Persona-Based Agents should expect a more consistent output, faster repeated execution, less prompt rewriting.
When to use this skill
- You want a reusable workflow that can be run more than once with consistent structure.
When not to use this skill
- You only need a quick one-off answer and do not need a reusable workflow.
- You cannot install or maintain the underlying files, dependencies, or repository context.
Installation
Claude Code / Cursor / Codex
Manual Installation
- Download SKILL.md from GitHub
- Place it in
.claude/skills/README/SKILL.mdinside your project - Restart your AI agent — it will auto-discover the skill
How Persona-Based Agents Compares
| Feature / Agent | Persona-Based Agents | Standard Approach |
|---|---|---|
| Platform Support | Not specified | Limited / Varies |
| Context Awareness | High | Baseline |
| Installation Complexity | Unknown | N/A |
Frequently Asked Questions
What does this skill do?
Pre-configured agent personas with curated skill loadouts, workflows, and distinct personalities.
Where can I find the source code?
You can find the source code on GitHub using the link provided at the top of the page.
Related Guides
Best AI Skills for Claude
Explore the best AI skills for Claude and Claude Code across coding, research, workflow automation, documentation, and agent operations.
ChatGPT vs Claude for Agent Skills
Compare ChatGPT and Claude for AI agent skills across coding, writing, research, and reusable workflow execution.
Cursor vs Codex for AI Workflows
Compare Cursor and Codex for AI coding workflows, repository assistance, debugging, refactoring, and reusable developer skills.
SKILL.md Source
# Persona-Based Agents Pre-configured agent personas with curated skill loadouts, workflows, and distinct personalities. ## What's a Persona? A **persona** is an agent definition that goes beyond "use these skills." Each persona includes: - **🧠 Identity & Memory** — who this agent is, how they think, what they've learned - **🎯 Core Mission** — what they optimize for, in priority order - **🚨 Critical Rules** — hard constraints they never violate - **📋 Capabilities** — domain expertise organized by area - **🔄 Workflows** — step-by-step processes for common tasks - **💭 Communication Style** — how they talk, with concrete examples - **🎯 Success Metrics** — measurable outcomes that define "good" - **🚀 Advanced Capabilities** — deeper expertise loaded on demand - **🔄 Learning & Memory** — what they retain and patterns they recognize ## How to Use ### Claude Code ```bash cp agents/personas/startup-cto.md ~/.claude/agents/ # Then: "Activate startup-cto mode" ``` ### Cursor ```bash ./scripts/convert.sh --tool cursor # Personas convert to .cursor/rules/*.mdc ``` ### Any Supported Tool ```bash ./scripts/install.sh --tool <your-tool> ``` ## Available Personas | Persona | Emoji | Domain | Best For | |---------|-------|--------|----------| | [Startup CTO](startup-cto.md) | 🏗️ | Engineering + Strategy | Technical co-founders, architecture decisions, team building | | [Growth Marketer](growth-marketer.md) | 🚀 | Marketing + Growth | Bootstrapped founders, content-led growth, launches | | [Solo Founder](solo-founder.md) | 🦄 | Cross-domain | One-person startups, side projects, MVP building | ## Personas vs Task Agents | | Task Agents (`agents/`) | Personas (`agents/personas/`) | |---|---|---| | **Focus** | Task execution | Role embodiment | | **Scope** | Single domain | Cross-domain curated set | | **Voice** | Neutral/professional | Personality-driven with backstory | | **Workflows** | Single-step | Multi-step with decision points | | **Use case** | "Do this task" | "Think like this person" | Both coexist. Use task agents for focused work, personas for ongoing collaboration. ## Creating Your Own See [TEMPLATE.md](template.md) for the format specification. Key elements: ```yaml --- name: Agent Name description: What this agent does and when to activate it. color: blue # Agent color theme emoji: 🎯 # Single emoji identifier vibe: One sentence personality capture. tools: Read, Write, Bash, Grep, Glob --- ``` Follow the section structure (Identity → Mission → Rules → Capabilities → Workflows → Communication → Metrics → Advanced → Learning) for consistency with existing personas.
Related Skills
persona
Generate data-driven user personas for UX research and product design. Usage: /persona generate [options]
wiki-query
Query the LLM Wiki — reads index.md first, drills into 3-10 relevant pages, synthesizes an answer with inline [[wikilink]] citations, and offers to file the answer back as a new comparison or synthesis page. Usage /wiki-query "<question>"
wiki-log
Show recent entries from the LLM Wiki log (wiki/log.md). Uses the standardized
wiki-lint
Run a health check on the LLM Wiki vault — mechanical checks (orphans, broken links, stale pages, missing frontmatter, log gap, duplicates) plus semantic checks (contradictions, cross-reference gaps, concepts missing their own page). Outputs a markdown report with suggested actions. Usage /wiki-lint [--stale-days N] [--log-gap-days N]
wiki-init
Bootstrap a fresh LLM Wiki vault with the three-layer structure, schema files, and starter templates. Usage /wiki-init <path> --topic "<topic>" [--tool all|claude-code|codex|cursor|antigravity]
wiki-ingest
Ingest a source file from raw/ into the LLM Wiki — read, discuss, write summary page, update cross-references across 5-15 pages, regenerate index, append to log. Usage /wiki-ingest <path-to-source>
tc
Track technical changes with structured records, a state machine, and session handoff. Usage: /tc <init|create|update|status|resume|close|export|dashboard> [args]
tc-tracker
Use when the user asks to track technical changes, create change records, manage TC lifecycles, or hand off work between AI sessions. Covers init/create/update/status/resume/close/export workflows for structured code change documentation.
llm-wiki
Use when building or maintaining a persistent personal knowledge base (second brain) in Obsidian where an LLM incrementally ingests sources, updates entity/concept pages, maintains cross-references, and keeps a synthesis current. Triggers include "second brain", "Obsidian wiki", "personal knowledge management", "ingest this paper/article/book", "build a research wiki", "compound knowledge", "Memex", or whenever the user wants knowledge to accumulate across sessions instead of being re-derived by RAG on every query.
karpathy-coder
Use when writing, reviewing, or committing code to enforce Karpathy's 4 coding principles — surface assumptions before coding, keep it simple, make surgical changes, define verifiable goals. Triggers on "review my diff", "check complexity", "am I overcomplicating this", "karpathy check", "before I commit", or any code quality concern where the LLM might be overcoding.
karpathy-check
Run Karpathy's 4-principle review on staged changes or the last commit. Checks complexity, diff noise, hidden assumptions, and goal verification. Usage /karpathy-check [--last-commit]
cs-wiki-linter
Dispatched sub-agent that runs a periodic health check on an LLM Wiki vault. Runs mechanical checks via scripts (orphans, broken links, stale pages, missing frontmatter, duplicate titles, log gaps), does semantic checks (contradictions, stale claims, cross-reference gaps, concepts missing their own page), and produces a markdown report with suggested actions. Spawn weekly, after batch ingests, or when the user says "check the wiki" / "lint my wiki" / "audit the vault".