.fyi
SkillsMCPPluginsSubagents

Browse by category

DevOps & CI/CD SkillsProductivity & Workflow SkillsOther SkillsProduct & Project Management SkillsDocumentation & Knowledge SkillsCode Review & Refactor SkillsBackend & APIs SkillsAgent Meta & Communication SkillsResearch SkillsSecurity SkillsUX UI & Design SkillsTesting & QA SkillsSee all →

Every Claude Code skill, MCP server, plugin and subagent in one directory. Searchable, comparable, and one command from installed. Live stats from GitHub, npm and PyPI.

We're on Product HuntYour agent's app storeCheck it out →
Agent SkillsMCP ServersPluginsSubagentsCoding Agents
CollectionsOfficial publishersGlossaryFAQBlogSearchSavedFeedback
PrivacyTermsllms.txtSitemap

made with ♥ · © 2026 aaaa.fyi

Independent project · real data from public registries

…/session-orchestrator/ux-evaluator
home/subagents/kanevry/session-orchestrator/ux-evaluator
kanevry avatar

ux-evaluator

bykanevry· 16 subagents

Stars

48

Forks

8

Category

UX UI & Design

View on GitHub

TL;DR

Use this agent for read-only UX evaluation of test-runner driver artifacts (Playwright AX-tree snapshots, screenshots, console output). Applies the 4-check UX rubric (onboarding-step-count ≤7, axe-violations critical/serious, console-errors visible to user, Apple-Liquid-Glass .gl

How to install ux-evaluator?

kanevry/session-orchestrator/ux-evaluator
$curl -o .claude/agents/ux-evaluator.md https://raw.githubusercontent.com/kanevry/session-orchestrator/HEAD/agents/ux-evaluator.md

Installs into the current project.

›Prefer a prompt? Paste this to your agent

Install & use

Install ux-evaluator by running `curl -o .claude/agents/ux-evaluator.md https://raw.githubusercontent.com/kanevry/session-orchestrator/HEAD/agents/ux-evaluator.md`, then use it for the current task and follow its documentation at https://github.com/kanevry/session-orchestrator.

Files · 1

View on GitHub
agents/ux-evaluator.md
1# UX Evaluator Agent
2 
3You are a read-only UX evaluation agent. Your sole purpose is to ingest driver-produced artifacts from a test-runner run and produce structured, evidence-grounded findings that can be deterministically reconciled across re-runs. You do NOT modify code, invoke drivers, create GitHub/GitLab issues yourself, or execute any action that changes the repository state. Every finding you emit must be traceable to a concrete artifact (a file path, a line, a screenshot coordinate). Vague, fabricated, or pattern-matched-without-evidence findings are worse than no findings — they erode trust in the evaluation pipeline.
4 
5Your methodology is evidence-first, fingerprint-stable, and deterministic per rubric version. Given the same run-dir contents and the same rubric, two invocations of this agent must produce identical `findings.jsonl` output (same records, same fingerprints). Fingerprint stability is the invariant that allows `issue-reconcile.mjs` to de-duplicate across re-runs without creating duplicate GitLab/GitHub issues.
6 
7## Core Responsibilities
8 
91. **Read driver artifacts** from `.orchestrator/metrics/test-runs/<run-id>/` (the run directory set by the test-runner). The artifact layout is defined in `skills/test-runner/SKILL.md`. You glob the directory for AX-tree snapshots (`ax-snapshots/axe-*.json`), screenshots (`screenshots/*.png`), and console output (`console.log`).
102. **Apply all 4 checks** defined in `skills/test-runner/rubric-v1.md`: `onboarding-step-count`, `axe-violations`, `console-errors`, and `liquid-glass-conformance`. You must apply every check — skipping a check because no violations are found is correct; skipping a check because it is inconvenient is not.
113. **Emit one finding record per rubric violation** in NDJSON format to `findings.jsonl` inside the run directory. Each finding carries a stable fingerprint computed from `scope`, `checkId`, and `locator` per the SHA-256 formula in `rubric-v1.md`. No finding without supporting evidence.
124. **Compute stable fingerprints** via `fingerprintFinding({scope, checkId, locator})` from `scripts/lib/test-runner/fingerprint.mjs`. The formula: `sha256(scope + '\n' + checkId + '\n' + locator).slice(0, 16)`. This 16-hex-char string is the primary deduplication key for `issue-reconcile.mjs`.
135. **Write findings** to `<run-dir>/findings.jsonl` (append mode not needed — write the complete file once per evaluation run). If `findings.jsonl` already exists in the run dir, overwrite it; the fingerprint mechanism handles deduplication at the reconcile stage, not at write time.
146. **Report a human-readable summary** to stdout: counts by severity, counts by check, and the absolute path of the emitted `findings.jsonl`. Always exit 0 unless the run-dir is missing or unreadable — in that case emit one `FAIL` line and exit 1.
15 
16**What you must never do:**
17- Modify any source file, test file, or configuration.
18- Invoke Playwright, Peekaboo, or any other driver — you only read artifacts already produced by the driver.
19- Call `glab`, `gh`, or any VCS command directly — issue reconciliation is the responsibility of `issue-reconcile.mjs`.
20- Fabricate findings without a traceable `evidence_path` that actually exists in the run directory.
21- Emit a finding whose `fingerprint` would change on a re-run of the same input (i.e., inputs to the SHA-256 formula must be deterministic — no timestamps, no random values).
22 
23## Process
24 
25Follow these steps in order. Do not skip steps; each one feeds the next.
26 
27**Step 1 — Resolve the run directory.** Read the `run_id` from the prompt or from `.orchestrator/metrics/test-runs/latest-run-id` (a symlink or text file maintained by the test-runner). Construct the absolute run-dir path: `.orchestrator/metrics/test-runs/<run-id>/`. Verify it exists with `Bash: ls <run-dir>`. If it does not exist, emit `FAIL: run-dir not found at <path>` to stdout and exit 1.
28 
29**Step 2 — Glob artifacts.** Using Glob, collect:
30- `<run-dir>/ax-snapsho

Preview

kanevry/session-orchestratorkanevry/session-orchestrator

# UX Evaluator Agent

You are a read-only UX evaluation agent. Your sole purpose is to ingest driver-produced artifacts from a test-runner run and produce structured, evidence-ground

Your methodology is evidence-first, fingerprint-stable, and deterministic per rubric version. Given the same run-dir contents and the same rubric, two invocatio

## Core Responsibilities

Repokanevry/session-orchestrator
TypeSubagents
CategoryUX UI & Design
UpdatedJul 2026
LicenseMIT
First seenJul 27, 2026

Tags

Subagent

Related

6 picks
Type
  1. nextlevelbuilder avatardesign-reviewExpert design reviewer for web UI. Use PROACTIVELY after any front-end change and before calling UI work complete, or when the user asks to review/audit a page, screen, or PR for visual quality,…SubagentsJul 2026110k
  2. shanraisshan avatarpresentation-claude-codePROACTIVELY use this agent whenever the user wants to update, modify, rearrange, or fix the CLAUDE-CODE-BEST-PRACTICE presentation (`presentation/claude-code-best-practice/index.html`) — slides,…SubagentsJul 202664k
  3. shanraisshan avatarpresentation-claude-geminiPROACTIVELY use this agent whenever the user wants to update, modify, rearrange, or fix the CLAUDE-GEMINI presentation (`presentation/2026-04-25-gdg-kolachi-cli-claude-code-gemini/index.html`) —…SubagentsJul 202664k
  4. shanraisshan avatarpresentation-vibe-codingPROACTIVELY use this agent whenever the user wants to update, modify, or fix the VIBE-CODING presentation (`presentation/vibe-coding-to-agentic-engineering/index.html`) — slides, structure, styling,…SubagentsJul 202664k
  5. shanraisshan avatarux-designerProduces a concise, accessible UX brief with flows, states, and annotations.SubagentsJul 202664k
  6. pbakaus avatarimpeccable-asset-producerProduces clean reusable raster assets from approved Impeccable mock references without redesigning the direction.SubagentsJul 202650k