Menu
Generate consistent, well-formatted reports from UX evaluation findings
Install with Codex or Claude Copy this prompt, paste it into Codex, Claude, or another assistant, and let it review the skill page and install it for you.
Based on SOC occupation classification
| name | report-generator |
| description | Generate consistent, well-formatted reports from UX evaluation findings |
Ensure consistent, professional report formatting across all UX evaluation types. This skill standardizes output format, severity scales, and report structure.
All reports follow this structure:
# [Report Type] Report
## Metadata
- URL, date, evaluator, scope
## Executive Summary
- Overall score/status
- Key metrics
- Top 3-5 findings
- Critical actions
## Detailed Findings
- Organized by category
- Each with: severity, location, evidence, fix
## Priority Matrix
- Impact vs effort analysis
- Quick wins highlighted
## Recommendations
- Immediate, short-term, long-term
- Estimated effort
## Appendix
- Screenshots
- Methodology
- References
All evaluations use this scale:
| Severity | Label | Definition | Priority |
|---|---|---|---|
| 0 | Not an issue | No problem found | None |
| 1 | Cosmetic | Minor issue | Low - fix if time |
| 2 | Minor | Causes inconvenience | Medium - schedule fix |
| 3 | Major | Significant problem | High - fix soon |
| 4 | Critical | Catastrophic issue | Urgent - fix now |
| Source Scale | Severity 4 | Severity 3 | Severity 2 | Severity 1 |
|---|---|---|---|---|
| WCAG | Critical | Serious | Moderate | Minor |
| Friction | Score 5 | Score 4 | Score 3 | Score 1-2 |
| Nielsen | Catastrophe | Major | Minor | Cosmetic |
# UX Heuristics Evaluation Report
**URL**: [Target]
**Date**: [Date]
**Evaluation Type**: Nielsen's 10 Usability Heuristics
## Executive Summary
**Overall UX Score**: [X/100]
| Severity | Count |
|----------|-------|
| Critical (4) | X |
| Major (3) | X |
| Minor (2) | X |
| Cosmetic (1) | X |
### Heuristic Scores
| Heuristic | Score | Issues |
|-----------|-------|--------|
| H1: Visibility | X/5 | Y |
| ... | ... | ... |
### Top Issues
1. [Issue] - Severity [X]
2. [Issue] - Severity [X]
3. [Issue] - Severity [X]
## Detailed Findings
### H1: Visibility of System Status
**Score**: X/5
#### Issue H1.1: [Title]
- **Severity**: [0-4]
- **Location**: [Element/page]
- **Description**: [What the issue is]
- **Evidence**: [Screenshot ref]
- **Recommendation**: [How to fix]
[Continue for each issue...]
## Priority Matrix
[Impact vs Effort grid]
## Recommendations
### Immediate (This week)
1. [Fix] - Effort: [Low/Med/High]
### Short-term (This month)
1. [Fix] - Effort: [Low/Med/High]
### Long-term (Quarter)
1. [Fix] - Effort: [Low/Med/High]
# WCAG [Level] Accessibility Audit Report
**URL**: [Target]
**Date**: [Date]
**Conformance Target**: Level [A/AA/AAA]
## Executive Summary
**Compliance Status**: [Compliant/Partial/Non-Compliant]
| Criteria | Passed | Failed | N/A |
|----------|--------|--------|-----|
| Level A | X | X | X |
| Level AA | X | X | X |
### Critical Issues
1. [Issue] - Criterion [X.X.X]
2. [Issue] - Criterion [X.X.X]
## Issues by Principle
| Principle | Severity 4 | Severity 3 | Severity 2 | Severity 1 |
|-----------|------------|------------|------------|------------|
| Perceivable | X | X | X | X |
| Operable | X | X | X | X |
| Understandable | X | X | X | X |
| Robust | X | X | X | X |
## Detailed Findings
### Perceivable
#### Issue P.1: [Title]
- **Criterion**: [X.X.X Name]
- **Level**: [A/AA/AAA]
- **Severity**: [0-4]
- **Location**: [Element]
- **Impact**: [Who affected]
- **Current**: [State now]
- **Required**: [What should be]
- **Code Fix**:
```html
<!-- Before -->
...
<!-- After -->
...
[Continue...]
[Timeline with fixes]
### Flow Report
```markdown
# User Flow Test Report
**Flow**: [Name]
**URL**: [Target]
**Date**: [Date]
## Executive Summary
| Metric | Value |
|--------|-------|
| Status | [Pass/Partial/Fail] |
| Steps | X |
| Duration | Xm Xs |
| Friction Points | X |
| Predicted Completion | X% |
### Key Findings
1. [Finding]
2. [Finding]
3. [Finding]
## Flow Visualization
[Mermaid diagram]
## Step Analysis
### Step 1: [Name]
| Metric | Value |
|--------|-------|
| Duration | Xs |
| Friction Score | [1-5] |
**Issues**:
#### Issue 1.1: [Title]
- **Severity**: [0-4]
- **Type**: [Discoverability/Clarity/Efficiency/Error]
- **Description**: [Details]
- **Impact**: [User impact]
- **Recommendation**: [Fix]
[Continue...]
## Friction Summary
| Priority | Issues |
|----------|--------|
| High (4-5) | X |
| Moderate (3) | X |
| Low (1-2) | X |
## Recommendations
[Prioritized list]
Human-readable reports for documentation and sharing.
Structured data for tooling and integration:
{
"metadata": {
"url": "https://example.com",
"date": "2025-01-15",
"type": "heuristics",
"evaluator": "UX Researcher"
},
"summary": {
"score": 72,
"issues": {
"critical": 1,
"major": 4,
"minor": 8,
"cosmetic": 3
}
},
"findings": [
{
"id": "H1.1",
"heuristic": "Visibility of System Status",
"severity": 3,
"title": "No loading indicator",
"location": ".submit-btn",
"description": "...",
"recommendation": "..."
}
],
"recommendations": {
"immediate": [...],
"shortTerm": [...],
"longTerm": [...]
}
}
Use the report-generator skill to format the heuristics findings into a comprehensive report with executive summary and priority matrix.
Use the report-generator skill to create a unified report combining:
- Heuristics evaluation findings
- Accessibility audit results
- Flow test analysis
Generate both markdown and JSON outputs.
Use the report-generator skill to create a 1-page executive summary of the audit findings for stakeholder presentation.
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.