/user-persona-creation
Create detailed user personas based on research and data. Develop realistic representations of target users to guide product decisions and ensure user-centered design.
$ npx -y skills add nicepkg/auto-company --skill user-persona-creation --agent claude-codeHow it fires
How this skill gets triggered: by you, by Claude, or both.
- Fires itselfAuto-invocation. Claude auto-loads it when your prompt matches the work.Auto-invocation is when the right skill fires by itself at the right moment, driven by a FLOW.md router and a hook, instead of you invoking it by name. It is the difference between a skill being installed and a skill actually getting used.Read the full definition →
- You can call itInvoke it directly when you want it.
- Slash command
/user-persona-creation
Context preview
The summary Claude sees to decide when to auto-load this skill.
Create detailed user personas based on research and data. Develop realistic representations of target users to guide product decisions and ensure user-centered design.
SKILL.md
user-persona-creation.SKILL.mdname: user-persona-creation
description: Create detailed user personas based on research and data. Develop realistic representations of target users to guide product decisions and ensure user-centered design.
User Persona Creation
Overview
User personas synthesize research into realistic user profiles that guide design, development, and marketing decisions.
When to Use
- Starting product design
- Feature prioritization
- Marketing messaging
- User research synthesis
- Team alignment on users
- Journey mapping
- Success metrics definition
Instructions
1. **Research & Data Collection**
# Gather data for persona development
class PersonaResearch:
def conduct_interviews(self, target_sample_size=12):
"""Interview target users"""
interview_guide = {
'demographics': [
'Age, gender, location',
'Job title, industry, company size',
'Experience level, education',
'Salary range, purchasing power'
],
'goals': [
'What are you trying to achieve?',
'What's most important to you?',
'What does success look like?'
],
'pain_points': [
'What frustrates you about current solutions?',
'What takes too long or is complicated?',
'What prevents you from achieving goals?'
],
'behaviors': [
'How do you currently solve this problem?',
'What tools do you use?',
'How do you learn about new solutions?'
],
'preferences': [
'How do you prefer to communicate?',
'What communication channels do you use?',
'When are you most responsive?'
]
}
return {
'sample_size': target_sample_size,
'interview_guide': interview_guide,
'output': 'Interview transcripts, notes, recordings'
}
def analyze_survey_data(self, survey_data):
"""Synthesize survey responses"""
return {
'demographics': self.segment_demographics(survey_data),
'pain_points': self.extract_pain_points(survey_data),
'goals': self.identify_goals(survey_data),
'needs': self.map_needs(survey_data),
'frequency_distribution': self.calculate_frequencies(survey_data)
}
def analyze_user_data(self):
"""Use product analytics data"""
return {
'feature_usage': 'Which features are most used',
'user_segments': 'Behavioral groupings',
'conversion_paths': 'How users achieve goals',
'churn_patterns': 'Why users leave',
'usage_frequency': 'Active vs inactive users'
}
def synthesize_data(self, interview_data, survey_data, usage_data):
"""Combine all data sources"""
return {
'primary_personas': self.identify_primary_personas(interview_data),
'secondary_personas': self.identify_secondary_personas(survey_data),
'persona_groups': self.cluster_similar_users(usage_data),
'confidence_level': 'Based on data sources and sample size'
}2. **Persona Template**
User Persona: Premium SaaS Buyer
---
## Demographics
Name: Sarah Chen
Age: 34
Location: San Francisco, CA
Job Title: VP Product Management
Company: Series B SaaS startup (50 employees)
Experience: 8 years in product management
Education: MBA from Stanford, BS in Computer Science
Income: $180K salary + 0.5% equity
---
## Professional Context
Industry: B2B SaaS (Project Management)
Company Size: 50-200 employees
Budget Authority: Can approve purchases up to $50K
Buying Process: 60% solo decisions, 40% committee
Evaluation Time: 4-6 weeks average
---
## Goals & Motivations
Primary Goals:
1. Improve team productivity by 25%
2. Reduce project delivery time by 30%
3. Increase visibility into project status
4. Improve team collaboration across remote locations
Success Definition:
- Team using tool daily
- 20% reduction in status meetings
- Faster decision-making
- Higher team satisfaction
---
## Pain Points
Current Challenges:
- Existing tool is slow and outdated
- Poor mobile experience
- Limited reporting capabilities
- Difficult to customize for company needs
- Vendor is unresponsive to feature requests
Frustrations:
- Wasting time in status update meetings
- Lack of real-time visibility into project health
- Can't easily identify bottlenecks
- Integration with other tools is difficult
---
## Behaviors & Preferences
Daily Tools:
- Slack: Constant communication
- Google Workspace: Document collaboration
- Jira: Technical work tracking
- Spreadsheets: Status reporting (workaround)
Work Patterns:
- Typically works 8am-6pm Pacific
- Checks email every 15 minutes
- In meetings 50% of day
- Works 20% of time outside office hours
Information Gathering:
- Reads G2/Capterra reviews: High trust
- Asks for peer recommendations: Very influential
- Requests demos: Hands-on evaluation
- Wants to see case studies: Similar companies
Decision Drivers:
- ROI and measurable impact: 40%
- User adoption potential: 30%
- Ease of implementation: 20%
- Price: 10%
---
## Technology Comfort
Tech Savviness: High (uses 15+ tools daily)
Mobile Usage: 40% of work on mobile
Prefers: Intuitive UI, minimal training
Adoption Speed: Fast (new tools in 1-2 weeks)
Integration Importance: Very high
---
## Customer Journey
Awareness: Product recommendations from peers
Consideration: Reviews, demos, talk to customers
Decision: Cost-benefit analysis, team input
Onboarding: Expects self-service + minimal support
Ongoing: Wants regular feature updates, responsive support
---
## Communication Preferences
Prefers: Email and Slack (avoid calls)
Re
Read more
name: user-persona-creation description: Create detailed user personas based on research and data. Develop realistic representations of target users to guide product decisions and ensure user-centered design.
User Persona Creation
Overview
User personas synthesize research into realistic user profiles that guide design, development, and marketing decisions.
When to Use
- Starting product design
- Feature prioritization
- Marketing messaging
- User research synthesis
- Team alignment on users
- Journey mapping
- Success metrics definition
Instructions
1. **Research & Data Collection**
# Gather data for persona development
class PersonaResearch:
def conduct_interviews(self, target_sample_size=12):
"""Interview target users"""
interview_guide = {
'demographics': [
'Age, gender, location',
'Job title, industry, company size',
'Experience level, education',
'Salary range, purchasing power'
],
'goals': [
'What are you trying to achieve?',
'What's most important to you?',
'What does success look like?'
],
'pain_points': [
'What frustrates you about current solutions?',
'What takes too long or is complicated?',
'What prevents you from achieving goals?'
],
'behaviors': [
'How do you currently solve this problem?',
'What tools do you use?',
'How do you learn about new solutions?'
],
'preferences': [
'How do you prefer to communicate?',
'What communication channels do you use?',
'When are you most responsive?'
]
}
return {
'sample_size': target_sample_size,
'interview_guide': interview_guide,
'output': 'Interview transcripts, notes, recordings'
}
def analyze_survey_data(self, survey_data):
"""Synthesize survey responses"""
return {
'demographics': self.segment_demographics(survey_data),
'pain_points': self.extract_pain_points(survey_data),
'goals': self.identify_goals(survey_data),
'needs': self.map_needs(survey_data),
'frequency_distribution': self.calculate_frequencies(survey_data)
}
def analyze_user_data(self):
"""Use product analytics data"""
return {
'feature_usage': 'Which features are most used',
'user_segments': 'Behavioral groupings',
'conversion_paths': 'How users achieve goals',
'churn_patterns': 'Why users leave',
'usage_frequency': 'Active vs inactive users'
}
def synthesize_data(self, interview_data, survey_data, usage_data):
"""Combine all data sources"""
return {
'primary_personas': self.identify_primary_personas(interview_data),
'secondary_personas': self.identify_secondary_personas(survey_data),
'persona_groups': self.cluster_similar_users(usage_data),
'confidence_level': 'Based on data sources and sample size'
}2. **Persona Template**
User Persona: Premium SaaS Buyer --- ## Demographics Name: Sarah Chen Age: 34 Location: San Francisco, CA Job Title: VP Product Management Company: Series B SaaS startup (50 employees) Experience: 8 years in product management Education: MBA from Stanford, BS in Computer Science Income: $180K salary + 0.5% equity --- ## Professional Context Industry: B2B SaaS (Project Management) Company Size: 50-200 employees Budget Authority: Can approve purchases up to $50K Buying Process: 60% solo decisions, 40% committee Evaluation Time: 4-6 weeks average --- ## Goals & Motivations Primary Goals: 1. Improve team productivity by 25% 2. Reduce project delivery time by 30% 3. Increase visibility into project status 4. Improve team collaboration across remote locations Success Definition: - Team using tool daily - 20% reduction in status meetings - Faster decision-making - Higher team satisfaction --- ## Pain Points Current Challenges: - Existing tool is slow and outdated - Poor mobile experience - Limited reporting capabilities - Difficult to customize for company needs - Vendor is unresponsive to feature requests Frustrations: - Wasting time in status update meetings - Lack of real-time visibility into project health - Can't easily identify bottlenecks - Integration with other tools is difficult --- ## Behaviors & Preferences Daily Tools: - Slack: Constant communication - Google Workspace: Document collaboration - Jira: Technical work tracking - Spreadsheets: Status reporting (workaround) Work Patterns: - Typically works 8am-6pm Pacific - Checks email every 15 minutes - In meetings 50% of day - Works 20% of time outside office hours Information Gathering: - Reads G2/Capterra reviews: High trust - Asks for peer recommendations: Very influential - Requests demos: Hands-on evaluation - Wants to see case studies: Similar companies Decision Drivers: - ROI and measurable impact: 40% - User adoption potential: 30% - Ease of implementation: 20% - Price: 10% --- ## Technology Comfort Tech Savviness: High (uses 15+ tools daily) Mobile Usage: 40% of work on mobile Prefers: Intuitive UI, minimal training Adoption Speed: Fast (new tools in 1-2 weeks) Integration Importance: Very high --- ## Customer Journey Awareness: Product recommendations from peers Consideration: Reviews, demos, talk to customers Decision: Cost-benefit analysis, team input Onboarding: Expects self-service + minimal support Ongoing: Wants regular feature updates, responsive support --- ## Communication Preferences Prefers: Email and Slack (avoid calls) Re
全自主 AI 公司,24/7 不停歇运行 14 个 AI Agent,每个都是该领域世界顶级专家的思维分身。 自主构思产品、做决策、写代码、部署上线、搞营销。没有人类参与。 基于 Claude Code Agent Teams 驱动。 ⚠️ 实验项目 — 还在测试中,能跑但不一定稳定。目前仅支持 macOS。
Other skills on auto-company.
- /agent-browser
Browser automation CLI for AI agents. Use when the user needs to interact with websites, including navigating pages, filling forms, clicking buttons, taking screenshots, extracting data, testing web apps, or automating any browser task. Triggers include requests to "open a
Open skill - /code-review-security
Security-focused code review checklist and automated scanning patterns. Use when reviewing pull requests for security issues, auditing authentication/authorization code, checking for OWASP Top 10 vulnerabilities, or validating input sanitization. Covers SQL injection prevention,
Open skill - /cold-email-sequence-generator
Generate personalized cold email sequences (7-14 emails) with A/B test subject lines, follow-up timing recommendations, and integrated social proof. Creates multi-touch campaigns optimized for response rates. Use when users need outbound email campaigns, sales sequences, or lead
Open skill - /community-led-growth
Expert in community-led growth (CLG) - leveraging user communities to drive acquisition, retention, and expansion. Covers building developer communities, user groups, ambassador programs, and turning customers into advocates. Knows the difference between community as a feature
Open skill - /competitive-intelligence-analyst
Use this skill when users need to analyze competitors, monitor market movements, benchmark features/pricing, identify market gaps, or understand competitive positioning. Activates for "what are competitors doing," market analysis, or differentiation strategy.
Open skill - /content-strategy
When the user wants to plan a content strategy, decide what content to create, or figure out what topics to cover. Also use when the user mentions "content strategy," "what should I write about," "content ideas," "blog strategy," "topic clusters," or "content planning." For
Open skill

