CtrlK
BlogDocsLog inGet started
Tessl Logo

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," "PMF survey," "product/market fit survey," "customer interview questions," "interview outreach," "Sales Safari," or "find out why customers churn/convert/buy." Use for analyzing existing research assets, mining online sources, AND running primary research (interviews and surveys). For writing copy informed by research, see copywriting. For acting on research to improve pages, see cro.

72

Quality

89%

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

78%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 well-organized, actionable skill body that splits heavy detail into two clearly signaled reference files and provides concrete frameworks, templates, and guardrails. It is efficient and earns most of its tokens, with only minor tightening and feedback-loop gaps keeping it from the top anchors.

Suggestions

Tighten the Mode 2 quick-decision guide and persona anti-patterns into tighter bullet form to trim a few tokens.

Add an explicit validate→fix→retry loop for the synthesis step (e.g., re-check confidence levels against the minimum-viable-sample rule before finalizing personas) to push workflow clarity to 5.

Surface one or two concrete executable details from the reference files inline (e.g., the 40% PMF benchmark already present) so the body is more self-contained for the most common cases.

DimensionReasoningScore

Conciseness

Largely efficient and earns its tokens with domain-specific frameworks, tables, and templates rather than explaining concepts Claude already knows; a few prose passages (e.g., the persona anti-patterns and quick-decision guide) could be tightened slightly.

4 / 5

Actionability

Highly actionable for an instruction-only skill: concrete extraction frameworks, a copy-paste synthesis template, a persona structure template, per-ICP source tables, and confidence criteria; minor gaps come from deferring some detail to the reference files.

4 / 5

Workflow Clarity

Clear three-mode sequencing with an explicit "mine before you ask" ordering, numbered extraction and synthesis steps, and quality guardrails (confidence labeling, sample-bias checks); not a 5 because there are no explicit validate→fix→retry feedback loops, though the task is non-destructive so the destructive cap does not apply.

4 / 5

Progressive Disclosure

Well-structured overview that keeps the full interview/survey playbook and per-platform source detail in two real, one-level-deep reference files (references/interviews-and-surveys.md, references/source-guides.md), each clearly signaled inline.

5 / 5

Total

17

/

20

Passed

Description

100%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.

A strong, well-constructed description that clearly defines what the skill does and when to invoke it, with comprehensive natural trigger terms and explicit hand-off boundaries to adjacent skills. Third-person voice is used throughout, incurring no penalty.

DimensionReasoningScore

Specificity

Lists multiple concrete actions — "conduct, analyze, or synthesize customer research," "analyzing existing research assets, mining online sources, AND running primary research (interviews and surveys)" — with comprehensive coverage of the skill's scope.

5 / 5

Completeness

Explicitly answers both what (conduct/analyze/synthesize research across three modes) and when ("Use when the user mentions…") with concrete trigger phrases, satisfying the top anchor.

5 / 5

Trigger Term Quality

Exhaustive list of natural trigger phrases users would actually say ("talk to customers," "Reddit mining," "G2 reviews," "Sales Safari") including synonyms and acronyms (VOC/voice of customer, JTBD/jobs to be done, PMF/product-market fit).

5 / 5

Distinctiveness Conflict Risk

Clear customer-research niche with distinct triggers and explicit boundary routing ("For writing copy informed by research, see copywriting. For acting on research to improve pages, see cro"), minimizing conflict risk.

5 / 5

Total

20

/

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.

Validation16 / 16 Passed

Validation for skill structure

No warnings or errors.

Repository
coreyhaines31/marketingskills
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.