ux-ui-flow
사용자 플로우 분석 에이전트. 사용자 여정과 인터랙션 플로우를 설계합니다.
Install with Tessl CLI
npx tessl i github:shaul1991/shaul-agents-plugin --skill ux-ui-flow37
Does it follow best practices?
If you maintain this skill, you can automatically optimize it using the tessl CLI to improve its score:
npx tessl skill review --optimize ./path/to/skillValidation for skill structure
Discovery
22%Based on the skill's description, can an agent find and select it at the right time? Clear, specific descriptions lead to better discovery.
This description is too brief and vague to effectively guide skill selection. It lacks concrete actions, explicit trigger conditions, and sufficient keyword coverage. The description would benefit significantly from listing specific capabilities and adding a clear 'Use when...' clause.
Suggestions
Add a 'Use when...' clause with trigger terms like 'user flow', 'customer journey', 'UX mapping', 'interaction design', 'touchpoint analysis'
List specific concrete actions such as 'creates user flow diagrams, maps customer touchpoints, identifies friction points, designs onboarding sequences'
Include common variations and file types users might mention, such as 'flowcharts', 'journey maps', 'wireframes', or specific tools/formats
| Dimension | Reasoning | Score |
|---|---|---|
Specificity | The description uses vague language like '사용자 여정과 인터랙션 플로우를 설계합니다' (designs user journeys and interaction flows) without listing concrete actions such as creating wireframes, mapping touchpoints, or identifying pain points. | 1 / 3 |
Completeness | Only provides a weak 'what' (designs user journeys and flows) with no 'when' clause or explicit trigger guidance. Missing any 'Use when...' statement to indicate when Claude should select this skill. | 1 / 3 |
Trigger Term Quality | Contains some relevant keywords like '사용자 플로우' (user flow), '사용자 여정' (user journey), and '인터랙션 플로우' (interaction flow), but misses common variations like UX, customer journey, flow diagram, or user experience mapping. | 2 / 3 |
Distinctiveness Conflict Risk | Somewhat specific to user flow analysis domain, but could overlap with general UX design skills, wireframing tools, or journey mapping skills due to lack of clear boundaries and specific triggers. | 2 / 3 |
Total | 6 / 12 Passed |
Implementation
22%Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.
This skill content is essentially a job description rather than an actionable skill. It defines a role and lists responsibilities but provides zero guidance on how to actually perform user flow analysis, what formats to use, or what good outputs look like. The skill needs substantial content to be useful.
Suggestions
Add concrete examples of user journey map formats (e.g., Mermaid flowcharts, markdown templates) with sample output
Define a clear workflow: e.g., 1) Identify user goals, 2) Map touchpoints, 3) Document in specific format, 4) Validate against requirements
Include specific templates or schemas for the deliverables expected in `docs/ux/flows/`
Add example scenarios showing input (user requirements) and expected output (completed flow documentation)
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The content is brief and doesn't over-explain concepts Claude knows, but it's essentially just a role description with bullet points rather than actionable skill content. The brevity comes from lack of substance rather than efficient instruction. | 2 / 3 |
Actionability | The skill provides no concrete guidance, code, commands, or examples. It only lists abstract responsibilities ('사용자 여정 매핑', '인터랙션 플로우 설계') without explaining how to actually perform these tasks or what outputs should look like. | 1 / 3 |
Workflow Clarity | There is no workflow defined. The skill lists tasks but provides no sequence, steps, or process for how to analyze user flows, create journey maps, or produce the deliverables mentioned. | 1 / 3 |
Progressive Disclosure | The content is appropriately short and mentions an output location, but there are no references to supporting documentation, templates, or examples that would help Claude understand how to create the expected deliverables. | 2 / 3 |
Total | 6 / 12 Passed |
Validation
90%Checks the skill against the spec for correct structure and formatting. All validation checks must pass before discovery and implementation can be scored.
Validation — 10 / 11 Passed
Validation for skill structure
| Criteria | Description | Result |
|---|---|---|
allowed_tools_field | 'allowed-tools' contains unusual tool name(s) | Warning |
Total | 10 / 11 Passed | |
- Reviewed
Table of Contents
Is this your skill?
If you maintain this skill, you can claim it as your own. Once claimed, you can manage eval scenarios, bundle related skills, attach documentation or rules, and ensure cross-agent compatibility.