CtrlK
BlogDocsLog inGet started
Tessl Logo

analyze-feedback

Synthesizes customer feedback into actionable themes including feature requests, bugs, pain points, and praise. Use when planning product roadmap, understanding user sentiment, investigating specific issues, or preparing voice-of-customer reports.

75

Quality

Does it follow best practices?

Impact

No eval scenarios have been run

SecuritybySnyk

Advisory

Suggest reviewing before use

SKILL.md
Quality
Evals
Security

Quality

Content

87%

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

A concise, highly actionable skill body with concrete Amplitude tool calls and a clear output template. Its main weakness is workflow clarity: the sequence is clear but lacks validation checkpoints or error-recovery guidance for edge cases like empty results.

Suggestions

Add validation checkpoints between steps — e.g. after `get_feedback_sources` and `get_feedback_insights`, verify data was returned before proceeding, and if a theme is empty expand the date range or filter set.

Include an explicit error-recovery/feedback loop (e.g. 'If no insights match, broaden `types` or widen the date range, then re-run') to lift workflow clarity toward the level-3 anchor.

Fix the 'Inlcude' typo in the Prioritized Recommendations bullet so the guidance is copy-clean.

DimensionReasoningScore

Conciseness

The body is lean — concrete tool calls, filter value lists, and a compact output template — and assumes Claude's competence without explaining concepts Claude already knows, fitting the 'every token earns its place' anchor rather than the padded level-2 example.

3 / 3

Actionability

Provides specific executable tool calls (e.g. `Amplitude:get_feedback_insights` with filter values `request`, `complaint`, `lovedFeature`, `bug`, `painPoint`) plus a copy-ready output structure with `[p0]`-`[p3]` priorities, matching the fully-executable anchor.

3 / 3

Workflow Clarity

The five steps are clearly sequenced, but there are no validation checkpoints or feedback loops (e.g. verify sources returned data, handle empty insights by widening filters), matching 'steps listed but validation gaps; checkpoints missing or implicit' rather than the level-3 anchor requiring explicit validation steps.

2 / 3

Progressive Disclosure

No bundle files exist and the ~50-line skill is self-contained with well-organized section headers (Instructions steps + Best Practices), so the 'under 50 lines, no external references needed, well-organized sections' guideline yields a 3.

3 / 3

Total

11

/

12

Passed

Description

100%

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 well-crafted description: it states a concrete capability, includes an explicit 'Use when' trigger clause with natural phrasing, and occupies a distinct voice-of-customer niche. No meaningful gaps relative to the rubric anchors.

DimensionReasoningScore

Specificity

Lists concrete deliverables — 'feature requests, bugs, pain points, and praise' — and a concrete action ('Synthesizes customer feedback into actionable themes'), matching the multiple-specific-actions anchor rather than the thinner 'names domain and some actions' level.

3 / 3

Completeness

Explicitly answers both what ('Synthesizes customer feedback into actionable themes...') and when via an explicit 'Use when...' clause, satisfying the level-3 anchor; it is not the level-2 case where 'when' is only implied.

3 / 3

Trigger Term Quality

Natural terms a user would say are well covered — 'customer feedback', 'user sentiment', 'product roadmap', 'voice-of-customer reports' — going beyond the sparse single-keyword anchor at level 2.

3 / 3

Distinctiveness Conflict Risk

The voice-of-customer / feedback-analysis niche has distinct triggers (roadmap planning, sentiment, VoC reports) unlikely to collide with other skills, matching the clear-niche anchor.

3 / 3

Total

12

/

12

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
amplitude/builder-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.