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.

62

Quality

73%

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

72%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 highly actionable, well-templated VoC workflow with clear phasing, but it lacks validation checkpoints in its batch process and keeps all content in a single long file rather than progressively disclosing detail.

Suggestions

Add explicit validation checkpoints (e.g., 'Before clustering, confirm feedback from at least 3 sources; if fewer, flag low-confidence themes') to lift workflow clarity above the batch-operation cap.

Move the large output-format and theme-card templates into a referenced file (e.g., references/output-template.md) and keep SKILL.md as a concise overview to improve progressive disclosure.

Trim the 'Built for...' marketing framing and merge the duplicate 'When to Use' and 'Trigger Phrases' lists to tighten conciseness.

DimensionReasoningScore

Conciseness

The bulk is purposeful templates and structure rather than concept explanation, but the 'Built for...' framing paragraph and the redundant 'When to Use' / 'Trigger Phrases' sections could be trimmed.

4 / 5

Actionability

Provides fully specified, copy-ready templates (normalized feedback format, theme card with explicit '3+ customers' thresholds, sentiment overview, and complete output markdown) covering the common cases.

5 / 5

Workflow Clarity

The six phases are clearly sequenced, but there are no explicit validation/verification checkpoints for a batch synthesis operation, which per the rubric caps workflow clarity at 3.

3 / 5

Progressive Disclosure

Sections are well-organized by phase, but the skill is a monolithic 313-line file with large templates (output format, theme card) inlined and no one-level-deep references to split the content.

3 / 5

Total

15

/

20

Passed

Description

75%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 capabilities and input sources with low conflict risk, but it omits any explicit 'when to use' trigger guidance, capping completeness.

Suggestions

Add an explicit 'Use when...' clause with concrete trigger phrases (e.g., 'Use when synthesizing customer feedback, building a VoC report, or clustering NPS/support themes') to lift completeness.

Include a few more natural user synonyms (e.g., 'customer insights', 'feedback report', 'review aggregation') to broaden trigger-term coverage.

DimensionReasoningScore

Specificity

Lists multiple concrete actions ('theme clustering, sentiment analysis, trend detection, and actionable recommendations') and enumerates many specific input sources, giving comprehensive coverage of capabilities.

5 / 5

Completeness

Clearly answers 'what' the skill does but provides no explicit 'Use when...' clause or equivalent trigger guidance, which per the rubric caps completeness at 3.

3 / 5

Trigger Term Quality

Includes natural terms users would say ('customer feedback', 'VoC', 'NPS', 'G2 reviews', 'support tickets') but is missing some common synonyms and variations a user might naturally phrase.

4 / 5

Distinctiveness Conflict Risk

Occupies a clear niche (Voice of Customer synthesis) with distinct source-specific triggers and minimal overlap risk with other skills.

5 / 5

Total

17

/

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