CtrlK
BlogDocsLog inGet started
Tessl Logo

voice-of-customer-synthesizer

Aggregate customer feedback from multiple sources — support tickets, NPS comments, Slack messages, G2 reviews, call transcripts, survey responses — into a unified VoC report with theme clustering, sentiment analysis, trend detection, and actionable recommendations for product, marketing, and CS teams. Chains review-site-scraper for public review data.

56

Quality

70%

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

Fix and improve this skill with Tessl

tessl review fix ./skills/research/composites/voice-of-customer-synthesizer/SKILL.md
SKILL.md
Quality
Evals
Security

Quality

Content

57%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-structured, genuinely actionable synthesis workflow with concrete templates and search commands. Its weaknesses are the absence of any validation checkpoints in the phase sequence, a large inlined output template with no reference files, and redundant sections (trigger phrases duplicated, narrative padding) that spend tokens without adding guidance.

Suggestions

Add validation checkpoints between phases, e.g. after Phase 1 confirm every provided source was normalized and item counts reconcile before clustering, and after Phase 2 verify representative quotes are verbatim from source data.

Move the Phase 5 output-format template (and optionally the theme template) to references/report-template.md and reference it one level deep, keeping SKILL.md as an overview.

Delete the duplicate "Trigger Phrases" section (it repeats "When to Use") and trim the "Built for" narrative and Cost table to reclaim tokens.

DimensionReasoningScore

Conciseness

The body is mostly templates and tables that earn their tokens, but includes unnecessary fat: the "Built for" startup narrative paragraph, a Cost table of rough estimates, and a "Trigger Phrases" section that duplicates the "When to Use" list verbatim in intent. Mostly efficient but could be tightened; not score 4 because the duplication and narrative padding are clearly trimmable.

3 / 5

Actionability

Concrete, executable guidance throughout: a normalization format (SOURCE | DATE | CUSTOMER | …), ready-to-run search strings ("[product name]" feedback OR review OR "switched to"), a full theme-card template, and a complete output report skeleton with a save path. Minor gaps — no concrete handling instructions for the listed CSV inputs — keep it below fully copy-paste-ready coverage.

4 / 5

Workflow Clarity

Phases 0–5 are clearly sequenced with labeled sub-steps, but there are no validation checkpoints anywhere (e.g., confirm all sources were parsed before clustering, verify quotes are verbatim, check theme counts against item counts). This matches the anchor "sequence present but checkpoints missing or implicit"; not score 4 because checkpoints are absent rather than having minor gaps.

3 / 5

Progressive Disclosure

Good section structure, but the ~90-line Phase 5 output-format template is inlined in SKILL.md with no references/ directory or any external files — content that clearly belongs in a separate reference file. No nested references exist (nothing to get lost in), so it sits above score 2, but with zero progressive disclosure and inlinable bulk content it fits the "some structure, content that should be separate is inline" anchor.

3 / 5

Total

13

/

20

Passed

Description

71%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 specific, well-scoped description that names concrete actions and many real feedback sources. Its main weakness is the absence of any 'when to use' trigger guidance, which caps completeness, and the "VoC" abbreviation is used without the spelled-out phrase users might say.

Suggestions

Add an explicit trigger clause, e.g. "Use when the user asks what customers are saying, wants customer feedback synthesized across channels, or requests a VoC/voice-of-customer report."

Spell out "voice of customer (VoC)" at first use so the description matches both the natural phrase and the abbreviation.

Include one or two natural trigger phrasings users actually say ("synthesize customer feedback", "customer feedback report") in the description itself rather than only in the body.

DimensionReasoningScore

Specificity

"Aggregate customer feedback… into a unified VoC report with theme clustering, sentiment analysis, trend detection, and actionable recommendations" lists multiple concrete actions and names ten concrete source types (support tickets, NPS comments, Slack messages, G2 reviews, call transcripts, survey responses). Comprehensive and specific; not score 4 because coverage of the skill's capabilities is complete rather than having minor gaps.

5 / 5

Completeness

The "what" is clear and detailed, but there is no "Use when…" clause or equivalent explicit trigger guidance — the description never states when Claude should invoke it. Per the rubric guideline, a missing 'Use when' clause caps completeness at 3; not score 2 because the "what" is unambiguous and comprehensive.

3 / 5

Trigger Term Quality

Strong natural terms users would say — "customer feedback", "support tickets", "NPS comments", "reviews", "sentiment" — plus named sources. Missing common phrasings like "what are customers saying", "voice of customer" spelled out (only the jargon "VoC" appears), and "survey" variants are partially covered.

4 / 5

Distinctiveness Conflict Risk

"Unified VoC report" with named sources and chained review-site-scraper carves a clear niche distinct from generic sentiment-analysis or scraping skills. Minor overlap risk with standalone sentiment-analysis or survey-analysis skills; not score 5 because "aggregate feedback… sentiment analysis" could compete with those adjacent skills.

4 / 5

Total

16

/

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.

Validation — 15 / 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
gooseworks-ai/goose-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.