ccem: Skill for Claude Code

.agents/skills/product-design/ux-researcher/SKILL.md

ux-researcher is a skill for Claude Code, Codex from Genuifx/ccem. It costs 23 tokens per session (2,435 once invoked), scanned A, original, Apache-2.0.

UX research guidance for studying how people use products, testing usability, combining research findings, and organising research work. UX means the experience people have when using a product.

In plain words
What is it for?
Use it for user research, usability testing, data synthesis, and research operations.
Why use it?
It helps replace guesses about user behaviour with structured research and clearer findings.

Skill for Claude CodeCodex

Written for no agent in particular: nothing here depends on one. Also seen: installed under .agents/ (shared by several agents); mentions Codex.

This is Genuifx/ccem's own configuration. It tells Claude Code and Codex how to work on ccem itself, so it is not a mod to install elsewhere. Copy it as a starting point and replace the rules that are about this project. Everything ccem configures →

Needs its repository: it runs a file that does not travel with it, so clone the repository first. The line is python scripts/transcript_analyzer.py --folder transcripts/ --themes themes.yaml.

View source ↗ Genuifx/ccem
Reuse

Borrowing it

Nothing to install: this file belongs to Genuifx/ccem. Take a copy, put it at the same path in your own repository, and replace the rules that are about this project with yours.

Copy the file
curl -O https://raw.githubusercontent.com/Genuifx/ccem/main/.agents/skills/product-design/ux-researcher/SKILL.md
Clone the repo
git clone --depth 1 https://github.com/Genuifx/ccem

Made for: Claude Code, Codex.

Wrote this? Show the measurements

A badge with what this costs and how it scanned, read live from this page, so it follows the numbers instead of freezing them. Markdown for a README, HTML for a documentation site or a project page.

agentmods badge for ux-researcher

README.md
[![agentmods](https://agentmods.dev/badge/skills/genuifx/ccem/ux-researcher/github.svg)](https://agentmods.dev/skills/genuifx/ccem/ux-researcher)
Your own site
<a href="https://agentmods.dev/skills/genuifx/ccem/ux-researcher"><img src="https://agentmods.dev/badge/skills/genuifx/ccem/ux-researcher/github.svg" alt="Measured on agentmods" height="20"></a>

Or the 80×15 button, for a site that already has a row of RSS and ATOM ones. Only the verdict fits; the numbers stay here.

agentmods 80×15 button for ux-researcher

Your own site · 80×15
<a href="https://agentmods.dev/skills/genuifx/ccem/ux-researcher"><img src="https://agentmods.dev/badge/skills/genuifx/ccem/ux-researcher.svg" alt="Reviewed on agentmods" width="80" height="20"></a>
Per session 23 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.
When invoked 2,435 The whole file, excluding the scripts and references it only reads on demand.
Security scan A 0 findings. A grade says what 26 rules found in the file — not that it is safe.
Origin original No closer match found in the catalogue.
Token cost

What it costs to keep this loaded

Counted locally with the o200k_base tokenizer, which is exact for GPT models; Claude uses its own tokenizer and its counts differ. Treat this as one consistent yardstick across the catalogue rather than a bill. Prices are per million input tokens.

ModelPer sessionOnce invoked
Fable 5.1 $0.00023 $0.02435
Opus 5.5 $0.00009 $0.00974
Sonnet 5.5 $0.00005 $0.00487
Haiku 4.5 $0.00002 $0.00244

Measured 1mo ago against content hash 2c9aa5dce4c4, method: parsed. Prices are Anthropic first-party input rates as of 2026-10-07, from the pricing page.

Security

Grade A, and why

ux-researcher scanned grade A with 0 findings against 26 rules in 11 categories — prompt injection, anti-refusal, data exfiltration, privilege escalation, supply chain, agent snooping, system-prompt leakage, SSRF and excessive agency — measured 1mo ago.

A static scan of the body, not an audit. Every finding is printed with the line that produced it so you can judge whether it matters here. A mod is markdown that instructs an agent; that is exactly why what it instructs is worth reading.

Nothing flagged

None of the 26 patterns this scan looks for appear in this file: no shell pipes, no recursive deletes, no credential paths, no hidden text, no instruction-override or anti-refusal phrasing, no agent-config snooping. That is not a guarantee, it is the absence of the things that are checkable.

.agents/skills/product-design/ux-researcher/SKILL.md · 459 lines

How it starts

The opening of the file, as written. The whole thing — 459 lines — stays where its author put it; the contents beside it link to each section on GitHub.

UX Researcher

Expert-level user experience research for product decisions.

Core Competencies

  • Qualitative research methods
  • Quantitative research methods
  • Usability testing
  • Survey design
  • Data synthesis
  • Research operations
  • Stakeholder communication
  • Research ethics

Research Methods

Method Selection Matrix

Method Type Sample Time Best For
Interviews Qual 5-15 2-4 weeks Deep understanding
Surveys Quant 100+ 1-2 weeks Validation at scale
Usability Tests Qual 5-8 1-2 weeks Design validation
Card Sorting Qual 15-30 1 week Information arch
A/B Testing Quant 1000+ 2-4 weeks Feature optimization
Diary Studies Qual 10-20 2-4 weeks Behavior over time
Analytics Quant All Ongoing Behavioral patterns
Ethnography Qual 5-10 4-8 weeks Contextual understanding

When to Use What

DISCOVERY PHASE
├── Stakeholder interviews
├── Competitive analysis
├── User interviews
└── Contextual inquiry

DEFINITION PHASE
├── Surveys (quantitative validation)
├── Card sorting
└── Persona development

DEVELOPMENT PHASE
├── Concept testing
├── Usability testing
├── A/B testing
└── Preference testing

LAUNCH PHASE
├── Beta testing
├── Launch surveys
└── Analytics monitoring

POST-LAUNCH
├── Customer feedback
├── NPS surveys
├── Behavioral analytics
└── Support ticket analysis

User Interviews

Interview Planning

# Research Plan: [Study Name]

## Research Questions
1. [What are we trying to learn?]
2. [What are we trying to learn?]

## Hypotheses
- [What we think we'll find]

## Methodology
- 60-minute semi-structured interviews
- Remote via Zoom
- Recording with consent

## Participant Criteria
**Include:**
- [Criterion 1]
- [Criterion 2]

**Exclude:**
- [Criterion 1]

## Sample Size
- 8-12 participants
- Segment distribution: [breakdown]

## Timeline
- Recruiting: [dates]
- Sessions: [dates]
- Analysis: [dates]
- Presentation: [date]

## Team
- Lead researcher: [name]
- Note-taker: [name]
- Observers: [names]

Read the full file on GitHub · 459 lines

Changes

What this file has done since we first saw it

Hashed on every crawl. A supply-chain change to an agent config is a question of when, not whether, so the history is kept rather than the latest state alone.

  1. 1mo ago First seen · 459 lines · 23 tokens per session scan A 2c9aa5dce4c4

Subscribe to this mod's changes

ux-researcher is a skill published in the GitHub repository Genuifx/ccem (23 stars, last pushed today), licensed Apache-2.0. It adds 23 tokens to every session and 2,435 once invoked, about $0.0001 per session on Opus 5.5. A static security scan graded it A with 0 findings. No closer match exists in the catalogue, so it is treated as the original; first seen 2026-08-30.

Related

Other skills, from other repositories

ux-researcher

!cat skills/shared/protocols/ux-protocol.md 2>/dev/null || true !cat skills/shared/protocols/design-mindset-and-rules.md 2>/dev/null || true !cat .production-grade.yaml 2>/dev/null || echo "No config — using defaults".

buiphucminhtam/forgewright · 47 tokens

Cognitive Load Analyzer

Evaluate interface complexity by measuring information density, decision points, visual hierarchy, and task completion paths to reduce user cognitive burden.

PramodDutta/qaskills · 29 tokens

righter

Apply UX content writing principles to review existing UI copy or write new UI copy from scratch. Use this skill whenever someone asks you to: review, audit, critique, or improve UI text, error messages, button labels, tooltips, empty states, permission prompts, onboarding copy, form helper text, accessible labels or…

ommakes/Skills · 121 tokens

vois-tokens

Rules and patterns for building UI with shadcn/ui, Tailwind v4 or StyleX, and Motion against a Vois design token set. Use when building components, pages, or any UI that should conform to the workspace design system. Covers spacing, typography, color tokens, component architecture, animation, accessibility, and modern…

ommakes/Skills · 77 tokens

design-rationale

Help designers articulate the cognitive science, behavioral psychology, and platform standards behind their design decisions. Use this skill when a designer needs to explain why they made a decision in a critique, design review, or stakeholder meeting. Also use when auditing a screen for principle alignment, preparing…

ommakes/Skills · 136 tokens

onboarding-flow

Design new onboarding flows or evaluate/critique existing ones — signup sequences, setup checklists, first-run wizards, personalization quizzes, permission priming, paywalls — for SaaS/web products or consumer/mobile apps. Use this whenever someone asks to design, build, spec, improve, review, audit, or critique…

ommakes/Skills · 153 tokens