Requirements
- Target platform
- OpenClaw
- Install method
- Manual import
- Extraction
- Extract archive
- Prerequisites
- OpenClaw
- Primary doc
- SKILL.md
UX research and design toolkit for Senior UX Designer/Researcher including data-driven persona generation, journey mapping, usability testing frameworks, and research synthesis. Use for user research, persona creation, journey mapping, and design validation.
UX research and design toolkit for Senior UX Designer/Researcher including data-driven persona generation, journey mapping, usability testing frameworks, and research synthesis. Use for user research, persona creation, journey mapping, and design validation.
Hand the extracted package to your coding agent with a concrete install brief instead of figuring it out manually.
I downloaded a skill package from Yavira. Read SKILL.md from the extracted folder and install it by following the included instructions. Tell me what you changed and call out any manual steps you could not complete.
I downloaded an updated skill package from Yavira. Read SKILL.md from the extracted folder, compare it with my current installation, and upgrade it while preserving any custom configuration unless the package docs explicitly say otherwise. Summarize what changed and any follow-up checks I should run.
Generate user personas from research data, create journey maps, plan usability tests, and synthesize research findings into actionable design recommendations.
Trigger Terms Workflows Workflow 1: Generate User Persona Workflow 2: Create Journey Map Workflow 3: Plan Usability Test Workflow 4: Synthesize Research Tool Reference Quick Reference Tables Knowledge Base
Use this skill when you need to: "create user persona" "generate persona from data" "build customer journey map" "map user journey" "plan usability test" "design usability study" "analyze user research" "synthesize interview findings" "identify user pain points" "define user archetypes" "calculate research sample size" "create empathy map" "identify user needs"
Situation: You have user data (analytics, surveys, interviews) and need to create a research-backed persona. Steps: Prepare user data Required format (JSON): [ { "user_id": "user_1", "age": 32, "usage_frequency": "daily", "features_used": ["dashboard", "reports", "export"], "primary_device": "desktop", "usage_context": "work", "tech_proficiency": 7, "pain_points": ["slow loading", "confusing UI"] } ] Run persona generator # Human-readable output python scripts/persona_generator.py # JSON output for integration python scripts/persona_generator.py json Review generated components ComponentWhat to CheckArchetypeDoes it match the data patterns?DemographicsAre they derived from actual data?GoalsAre they specific and actionable?FrustrationsDo they include frequency counts?Design implicationsCan designers act on these? Validate persona Show to 3-5 real users: "Does this sound like you?" Cross-check with support tickets Verify against analytics data Reference: See references/persona-methodology.md for validity criteria
Situation: You need to visualize the end-to-end user experience for a specific goal. Steps: Define scope ElementDescriptionPersonaWhich user typeGoalWhat they're trying to achieveStartTrigger that begins journeyEndSuccess criteriaTimeframeHours/days/weeks Gather journey data Sources: User interviews (ask "walk me through...") Session recordings Analytics (funnel, drop-offs) Support tickets Map the stages Typical B2B SaaS stages: Awareness โ Evaluation โ Onboarding โ Adoption โ Advocacy Fill in layers for each stage Stage: [Name] โโโ Actions: What does user do? โโโ Touchpoints: Where do they interact? โโโ Emotions: How do they feel? (1-5) โโโ Pain Points: What frustrates them? โโโ Opportunities: Where can we improve? Identify opportunities Priority Score = Frequency ร Severity ร Solvability Reference: See references/journey-mapping-guide.md for templates
Situation: You need to validate a design with real users. Steps: Define research questions Transform vague goals into testable questions: VagueTestable"Is it easy to use?""Can users complete checkout in <3 min?""Do users like it?""Will users choose Design A or B?""Does it make sense?""Can users find settings without hints?" Select method MethodParticipantsDurationBest ForModerated remote5-845-60 minDeep insightsUnmoderated remote10-2015-20 minQuick validationGuerrilla3-55-10 minRapid feedback Design tasks Good task format: SCENARIO: "Imagine you're planning a trip to Paris..." GOAL: "Book a hotel for 3 nights in your budget." SUCCESS: "You see the confirmation page." Task progression: Warm-up โ Core โ Secondary โ Edge case โ Free exploration Define success metrics MetricTargetCompletion rate>80%Time on task<2ร expectedError rate<15%Satisfaction>4/5 Prepare moderator guide Think-aloud instructions Non-leading prompts Post-task questions Reference: See references/usability-testing-frameworks.md for full guide
Situation: You have raw research data (interviews, surveys, observations) and need actionable insights. Steps: Code the data Tag each data point: [GOAL] - What they want to achieve [PAIN] - What frustrates them [BEHAVIOR] - What they actually do [CONTEXT] - When/where they use product [QUOTE] - Direct user words Cluster similar patterns User A: Uses daily, advanced features, shortcuts User B: Uses daily, complex workflows, automation User C: Uses weekly, basic needs, occasional Cluster 1: A, B (Power Users) Cluster 2: C (Casual User) Calculate segment sizes ClusterUsers%ViabilityPower Users1836%Primary personaBusiness Users1530%Primary personaCasual Users1224%Secondary persona Extract key findings For each theme: Finding statement Supporting evidence (quotes, data) Frequency (X/Y participants) Business impact Recommendation Prioritize opportunities FactorScore 1-5FrequencyHow often does this occur?SeverityHow much does it hurt?BreadthHow many users affected?SolvabilityCan we fix this? Reference: See references/persona-methodology.md for analysis framework
Generates data-driven personas from user research data. ArgumentValuesDefaultDescriptionformat(none), json(none)Output format Sample Output: ============================================================ PERSONA: Alex the Power User ============================================================ ๐ A daily user who primarily uses the product for work purposes Archetype: Power User Quote: "I need tools that can keep up with my workflow" ๐ค Demographics: โข Age Range: 25-34 โข Location Type: Urban โข Tech Proficiency: Advanced ๐ฏ Goals & Needs: โข Complete tasks efficiently โข Automate workflows โข Access advanced features ๐ค Frustrations: โข Slow loading times (14/20 users) โข No keyboard shortcuts โข Limited API access ๐ก Design Implications: โ Optimize for speed and efficiency โ Provide keyboard shortcuts and power features โ Expose API and automation capabilities ๐ Data: Based on 45 users Confidence: High Archetypes Generated: ArchetypeSignalsDesign Focuspower_userDaily use, 10+ featuresEfficiency, customizationcasual_userWeekly use, 3-5 featuresSimplicity, guidancebusiness_userWork context, team useCollaboration, reportingmobile_firstMobile primaryTouch, offline, speed Output Components: ComponentDescriptiondemographicsAge range, location, occupation, tech levelpsychographicsMotivations, values, attitudes, lifestylebehaviorsUsage patterns, feature preferencesneeds_and_goalsPrimary, secondary, functional, emotionalfrustrationsPain points with evidencescenariosContextual usage storiesdesign_implicationsActionable recommendationsdata_pointsSample size, confidence level
Question TypeBest MethodSample Size"What do users do?"Analytics, observation100+ events"Why do they do it?"Interviews8-15 users"How well can they do it?"Usability test5-8 users"What do they prefer?"Survey, A/B test50+ users"What do they feel?"Diary study, interviews10-15 users
Sample SizeConfidenceUse Case5-10 usersLowExploratory11-30 usersMediumDirectional31+ usersHighProduction
SeverityDefinitionAction4 - CriticalPrevents task completionFix immediately3 - MajorSignificant difficultyFix before release2 - MinorCauses hesitationFix when possible1 - CosmeticNoticed but not problematicLow priority
TypeExampleUse ForContext"Walk me through your typical day"Understanding environmentBehavior"Show me how you do X"Observing actual actionsGoals"What are you trying to achieve?"Uncovering motivationsPain"What's the hardest part?"Identifying frustrationsReflection"What would you change?"Generating ideas
Detailed reference guides in references/: FileContentpersona-methodology.mdValidity criteria, data collection, analysis frameworkjourney-mapping-guide.mdMapping process, templates, opportunity identificationexample-personas.md3 complete persona examples with datausability-testing-frameworks.mdTest planning, task design, analysis
Based on 20+ users (minimum) At least 2 data sources (quant + qual) Specific, actionable goals Frustrations include frequency counts Design implications are specific Confidence level stated
Scope clearly defined (persona, goal, timeframe) Based on real user data, not assumptions All layers filled (actions, touchpoints, emotions) Pain points identified per stage Opportunities prioritized
Research questions are testable Tasks are realistic scenarios, not instructions 5+ participants per design Success metrics defined Findings include severity ratings
Data coded consistently Patterns based on 3+ data points Findings include evidence Recommendations are actionable Priorities justified
Workflow acceleration for inboxes, docs, calendars, planning, and execution loops.
Largest current source with strong distribution and engagement signals.