CtrlK
BlogDocsLog inGet started
Tessl Logo

customer-research

Conduct, analyze, and synthesize customer research including surveys, interviews, and community mining to build personas and uncover jobs-to-be-done.

59

Quality

68%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide

SecuritybySnyk

Passed

No findings from the security scan

Fix and improve this skill with Tessl

tessl review fix ./plugins/AI-Agents-Safe-Coding-Skills/skills/customer-research/SKILL.md

The canonical home for this skill is customer-research in administrakt0r/AI-Agents-Safe-Coding-Skills

SKILL.md
Quality
Evals
Security

Quality

Content

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

The content is well-structured and actionable with clear sequenced workflows, validation/confidence checkpoints, and excellent progressive disclosure via a real one-level-deep reference. It is mostly concise and executable, with only minor trimming opportunities in the templated sections.

DimensionReasoningScore

Conciseness

The body is mostly efficient and avoids over-explaining concepts Claude already knows, though a few sections (e.g., the lengthy persona template, repeated confidence tables) could be tightened; sits above 3 (mostly efficient) but not quite the lean 5-anchor.

4 / 5

Actionability

Provides concrete extraction frameworks, structured templates, specific field tables, and named source/search-operator examples a user can act on, with only minor gaps (no executable code, which is fine for an instruction-only skill); matches the 'mostly executable guidance' 4-anchor.

4 / 5

Workflow Clarity

Multi-step processes are clearly sequenced (Mode 1 extraction then synthesis, Mode 2 source selection then extraction then synthesis) with quality guardrails and confidence validation checkpoints; just shy of the 5-anchor's explicit feedback loops, but well above the 3-anchor with implicit checkpoints.

4 / 5

Progressive Disclosure

SKILL.md is a clear overview that offloads the deep platform playbooks to a single well-signaled one-level-deep reference ('read references/source-guides.md'), and that file is confirmed to exist and is appropriately structured, matching the 5-anchor of clear overview with well-signaled one-level-deep references.

5 / 5

Total

17

/

20

Passed

Description

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

The description is specific and third-person with several concrete actions and relevant domain keywords, but it lacks any 'Use when...' trigger clause, which caps completeness at 3 and leaves trigger-term coverage incomplete. Adding an explicit when-to-use clause with natural trigger phrases would lift the two capped dimensions.

Suggestions

Append an explicit trigger clause, e.g. 'Use when the user mentions customer research, ICP research, analyzing transcripts, survey analysis, voice of customer, building personas, or jobs-to-be-done.'

Add natural keyword synonyms users actually say (e.g., 'user research', 'ICP', 'VOC', 'review mining') to broaden trigger-term coverage.

Keep the concrete actions but consider tightening 'conduct, analyze, and synthesize' into sharper verbs to avoid the slight generic feel.

DimensionReasoningScore

Specificity

Lists several concrete actions ('conduct, analyze, and synthesize', 'build personas', 'uncover jobs-to-be-done') across multiple named source types (surveys, interviews, community mining), but some phrasing remains slightly generic; falls above the 3-anchor (1-2 actions) but below the fully comprehensive 5-anchor.

4 / 5

Completeness

Has a clear 'what' (conduct/analyze/synthesize research, build personas, uncover JTBD) but no 'Use when...' clause or equivalent explicit trigger guidance, so per the judging guidelines completeness is capped at 3.

3 / 5

Trigger Term Quality

Contains relevant domain keywords ('surveys', 'interviews', 'personas', 'jobs-to-be-done', 'customer research') that a user might naturally say, but is missing common variation/synonym phrases and lacks an explicit trigger context; matches the 3-anchor of 'some relevant keywords but missing common variations'.

3 / 5

Distinctiveness Conflict Risk

The persona-building and JTBD focus with community-mining framing carves a mostly distinct niche with only minor overlap risk against adjacent marketing skills; sits between 3 (some overlap) and 5 (clear niche), closer to 4.

4 / 5

Total

14

/

20

Passed

Validation

93%

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

Validation15 / 16 Passed

Validation for skill structure

CriteriaDescriptionResult

frontmatter_unknown_keys

Unknown frontmatter key(s) found; consider removing or moving to metadata

Warning

Total

15

/

16

Passed

Repository
administrakt0r/AI-Agents-Safe-Coding-Skills
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.