CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

customer-research

When the user wants to conduct, analyze, or synthesize customer research. Use when the user mentions "customer research," "ICP research," "talk to customers," "analyze transcripts," "customer interviews," "survey analysis," "support ticket analysis," "voice of customer," "VOC," "build personas," "customer personas," "jobs to be done," "JTBD," "what do customers say," "what are customers struggling with," "Reddit mining," "G2 reviews," "review mining," "digital watering holes," "community research," "forum research," "competitor reviews," "customer sentiment," or "find out why customers churn/convert/buy." Use for both analyzing existing research assets AND gathering new research from online sources. For writing copy informed by research, see copywriting. For acting on research to improve pages, see cro.

Quality

91%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide
SecuritybySnyk

Low

Low-risk findings worth noting

SKILL.md
Quality
Evals
Security

Quality

Content

88%Weight 40%Scale 1-5

Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.

A strong, well-structured instructional skill: it assumes Claude's intelligence, gives concrete frameworks and templates with explicit quality guardrails, and cleanly defers platform-level detail to a real, clearly-signaled reference file. The only improvement space is trimming/externalizing the long persona template and adding one or two more reference files to slim the main body.

DimensionReasoningScore

Conciseness

The body is dense and imperative throughout — 'Extract: pains, triggers, desired outcomes', 'Don't average across segments' — with no padding explaining concepts Claude already knows. Only minor sections (the full persona template, the per-field extraction table) could be tightened or externalized, which keeps it just below the 'every token earns its place' anchor.

4 / 5

Actionability

It provides copy-paste-ready templates for the synthesis report ('## Top Themes (ranked by frequency × intensity)...') and persona document, a concrete confidence-level table with explicit criteria, a fill-in extraction field table, and specific deliverable options. As an instruction-only skill, the guidance is fully executable with no vague abstraction.

5 / 5

Workflow Clarity

The sequence is explicit: check product-marketing context → establish mode → ask clarifying questions (lead with #1 and #2) → extract → synthesize → offer deliverables. Validation checkpoints are present and explicit ('Label every insight with a confidence level before presenting it', 'Don't create a persona until you have at least 5-10 data points'), matching the top anchor including its checklist-style guardrails section.

5 / 5

Progressive Disclosure

The single reference is well-signaled and one level deep ('read references/source-guides.md for detailed playbooks, search operators, and per-platform extraction tips') and the file exists and delivers what's promised. However, the bundle has only that one file while the body inlines ~90 lines of persona and deliverable templates that could be split out, leaving minor organization gaps versus the anchor-5 structure.

4 / 5

Total

18

/

20

Passed

Description

90%Weight 40%Scale 1-5

Based on the skill's description, can an agent find and select it at the right time? Clear, specific descriptions lead to better discovery.

An exemplary trigger description: comprehensive natural keywords, explicit when-conditions, third-person voice, and boundary hand-offs to adjacent skills. Its one weakness is that the capability statement stays at generic verbs ('conduct, analyze, or synthesize') rather than naming the concrete deliverables the body actually teaches.

Suggestions

Name the concrete outputs in the capability clause — e.g., 'Build research-backed customer personas, VOC quote banks, and jobs-to-be-done maps from interviews, surveys, tickets, and online reviews' — so the what matches the specificity of the when.

Trim near-duplicate trigger entries (e.g., 'customer research' vs. 'community research' vs. 'forum research') to reduce verbosity without losing coverage.

DimensionReasoningScore

Specificity

The what is 'conduct, analyze, or synthesize customer research' plus the two modes ('analyzing existing research assets AND gathering new research from online sources') — domain and 1-2 actions, but the verbs are generic. Concrete outputs the skill actually produces (personas, VOC quote banks, JTBD maps, competitive intel) never appear as capabilities, so it falls short of the 'several specific actions' anchor 4.

3 / 5

Completeness

Both what and when are explicit: the two-mode capability statement ('Use for both analyzing existing research assets AND gathering new research from online sources') plus an explicit 'Use when the user mentions…' clause with concrete trigger phrases — matching the top anchor exactly.

5 / 5

Trigger Term Quality

Comprehensive natural-language coverage with synonyms and acronyms: 'customer research,' 'ICP research,' 'talk to customers,' 'voice of customer,' 'VOC,' 'jobs to be done,' 'JTBD,' 'Reddit mining,' 'G2 reviews,' 'find out why customers churn/convert/buy.' These are phrases a user would actually say; no common variation is missing.

5 / 5

Distinctiveness Conflict Risk

Clear niche with distinct trigger vocabulary and explicit boundary disambiguation ('For writing copy informed by research, see copywriting. For acting on research to improve pages, see cro.'), which minimizes conflict with the adjacent marketing skills.

5 / 5

Total

18

/

20

Passed

Validation

100%

Checks the skill against the spec for correct structure and formatting. All validation checks must pass before discovery and implementation can be scored.

Validation — 16 / 16 Passed

Validation for skill structure

No warnings or errors.

Repository

joshmanders/dotfiles

Path

claude/skills/customer-research/SKILL.md

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.