원클릭으로
flow-analysis
Comprehensive user journey analysis with multi-flow comparison
Codex 또는 Claude로 설치 이 Prompt를 복사해 Codex, Claude 또는 다른 어시스턴트에 붙여 넣으면 Skill 페이지를 검토하고 설치를 진행할 수 있습니다.
메뉴
Comprehensive user journey analysis with multi-flow comparison
Codex 또는 Claude로 설치 이 Prompt를 복사해 Codex, Claude 또는 다른 어시스턴트에 붙여 넣으면 Skill 페이지를 검토하고 설치를 진행할 수 있습니다.
SOC 직업 분류 기준
Creates well-structured Claude Skills with proper YAML frontmatter, clear instructions, and supporting files. Activates when the user wants to create a new skill, add capabilities to their AI assistant, encode team preferences, or structure any reusable instruction set. Covers the full lifecycle from intent capture through writing, testing, and refinement.
Shows all available skills, platform support, common workflows, and troubleshooting for the @terrazul/assistant-creator package. Activates when the user asks for help, wants to know what's available, or needs guidance on using the package.
Interactive wizard to set up MCP server credentials in your shell environment (~/.zshenv, ~/.bashrc, etc.). Activates when the user needs to configure API keys, tokens, or environment variables for MCP servers, or after adding new MCP integrations that require authentication.
Searches mcp.so marketplace for MCP servers and configures them for Claude, Codex, or Gemini. Use when user wants to add external tool integrations, find MCP servers, or configure model context protocol.
Converts Claude SKILL.md files to Gemini-compatible format. Use when user wants to use a Claude skill with Gemini CLI, or needs to make skills cross-platform compatible.
Create well-formed Claude agents with proper YAML frontmatter, system prompts, and examples. Use when user wants to create a new agent, customize Claude behavior, or needs help structuring an agent definition.
| name | flow-analysis |
| description | Comprehensive user journey analysis with multi-flow comparison |
Analyze and compare multiple user journeys, identify optimization opportunities, and provide conversion-focused recommendations.
| Flow | Key Metrics | Common Issues |
|---|---|---|
| Signup | Completion rate, time | Too many fields, unclear value |
| Login | Success rate, errors | Password requirements, 2FA friction |
| Checkout | Conversion, abandonment | Guest checkout, payment trust |
| Onboarding | Completion, skip rate | Too long, no progress indicator |
| Search | Results quality, filters | No results, poor relevance |
Document each flow:
For each step, capture:
Evaluate each step:
| Factor | Score 1-5 | Description |
|---|---|---|
| Discoverability | [X] | Can users find next action? |
| Clarity | [X] | Are instructions clear? |
| Efficiency | [X] | Minimum steps possible? |
| Error handling | [X] | Are errors recoverable? |
| Feedback | [X] | Is progress communicated? |
Compare flows side-by-side:
Prioritize by:
# Flow Analysis Report
**Flows Analyzed**: [List]
**Date**: [Date]
**Application Type**: [Type]
## Executive Summary
| Flow | Steps | Time | Friction Score | Completion % |
|------|-------|------|----------------|--------------|
| Signup v1 | 5 | 2m 30s | 2.8 | 65% |
| Signup v2 | 3 | 1m 15s | 1.9 | 82% |
**Recommendation**: [Key finding]
## Flow Comparison
### Signup Flow Analysis
#### Version 1 (Current)
```mermaid
graph TD
A[Start] --> B[Step 1: Email]
B --> C[Step 2: Password]
C --> D[Step 3: Profile]
D --> E[Step 4: Preferences]
E --> F[Complete]
Metrics:
graph TD
A[Start] --> B[Step 1: Email + Password]
B --> C[Step 2: Verify]
C --> D[Complete]
Metrics:
| Step | V1 | V2 | Improvement |
|---|---|---|---|
| Fields to complete | 8 | 4 | -50% |
| Required clicks | 12 | 6 | -50% |
| Error opportunities | 5 | 2 | -60% |
| Validation feedback | Delayed | Real-time | +Quality |
| Step | Friction | Issue | Impact |
|---|---|---|---|
| Step 3 | 4.2 | Profile photo required | 32% drop-off |
| Step 4 | 3.8 | Too many preferences | 18% drop-off |
| Issue | Solution | Expected Impact |
|---|---|---|
| Profile photo | Make optional | +15% completion |
| Preferences | Move to later | +10% completion |
| Practice | V1 | V2 | Best Practice |
|---|---|---|---|
| Social login | No | Yes | Yes |
| Progress indicator | No | Yes | Yes |
| Password visibility | No | Yes | Yes |
| Inline validation | No | Yes | Yes |
| Guest option | N/A | N/A | Depends |
| Point | V1 % | V2 % | Improvement |
|---|---|---|---|
| Start → Step 1 | 15% | 10% | +5% |
| Step 1 → Step 2 | 12% | 8% | +4% |
| Step 2 → Complete | 8% | 5% | +3% |
| Total Drop-off | 35% | 23% | +12% |
Test: Social login prominence
Test: Field count
| Metric | Our Site | Competitor A | Competitor B | Best |
|---|---|---|---|---|
| Signup steps | 5 | 3 | 4 | 3 |
| Time to complete | 2m 30s | 1m 00s | 1m 45s | 1m |
| Social options | 0 | 3 | 2 | 3+ |
| Guest checkout | No | Yes | Yes | Yes |
## Example Usage
Use the flow-analysis skill to:
## Best Practices
1. **Map before optimizing** - Understand current state
2. **Measure everything** - Data over assumptions
3. **Test incrementally** - One change at a time
4. **Consider segments** - Mobile vs desktop, new vs returning
5. **Balance speed and quality** - Don't sacrifice trust for speed