CtrlK
BlogDocsLog inGet started
Tessl Logo

find-customer-quotes

Use when the user wants verbatim customer or prospect quotes, voice-of-customer evidence, theme validation, objection evidence, product-friction examples, or support for a product area, use case, or sales narrative. Retrieve from transcripts, call notes, supplied transcript-like recordings or exports, and other grounded call material using explicit speaker-confidence and provenance rules.

74

Quality

92%

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

85%

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

A well-structured, actionable extraction skill with a clear gated workflow and appropriate one-level-deep reference disclosure. Its main weakness is redundancy in the intake/clarification section, where option lists and gating sentences are repeated.

Suggestions

Collapse the duplicated clarification option lists (bare invocation vs. broad request) into one parameterized list to remove repeated bullets and the repeated 'Do not search transcript evidence or draft a quote set until the user selects one' sentence.

Consolidate the threshold guidance scattered across steps 2 and 4 (relevance 0.7 -> 0.6, 20-40 expansion, confidence >= 0.8, theme relevance down to ~0.65) into a single compact thresholds reference to reduce repetition.

Trim the repeated scope/filter reminders in step 1 (the account/segment bounded-pass guidance restates rules already covered by the clarification gate).

DimensionReasoningScore

Conciseness

The body assumes Claude's intelligence (no basic concept explanations) but carries redundancy: the clarification option lists are repeated for the bare-invocation and broad-request cases, and the gating sentence 'Do not search transcript evidence or draft a quote set until the user selects one' appears multiple times, so it could be tightened.

2 / 3

Actionability

Provides highly concrete, executable guidance for an instruction-only skill — explicit thresholds (customer_confidence >= 0.8, theme_relevance >= 0.75), named fields (speaker_role_guess, customer_confidence), search sizing (10-15 then 20-40), a copy-ready Markdown output template, and default counts (five quotes, one per call).

3 / 3

Workflow Clarity

A clearly numbered five-step sequence (Resolve scope, Search, Extract, Verify/rank, Deduplicate) with explicit gating checkpoints ('Do not search... until the user selects one', 'report 0/[target] when none pass threshold') and sparse-results retry logic providing a feedback loop.

3 / 3

Progressive Disclosure

SKILL.md acts as the overview and signals a single one-level-deep reference — [references/extraction-and-output.md] — for the detailed extraction/ranking/JSON rules, and that referenced file exists in the bundle, matching the well-signaled one-level-deep anchor.

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 strong, specific description with an explicit 'Use when...' trigger, concrete retrieval/provenance actions, and a well-scoped niche that distinguishes it from call-analytics or posting skills. It is somewhat long, but each clause supports a distinct trigger or capability.

DimensionReasoningScore

Specificity

Lists multiple concrete operations — 'Retrieve from transcripts, call notes, supplied transcript-like recordings or exports' and 'using explicit speaker-confidence and provenance rules' — naming the domain and the distinct actions performed, matching the 'multiple specific concrete actions' anchor.

3 / 3

Completeness

Explicitly answers both: what ('Retrieve... using explicit speaker-confidence and provenance rules') and when ('Use when the user wants verbatim customer or prospect quotes...'), satisfying the explicit-trigger anchor.

3 / 3

Trigger Term Quality

Covers natural terms a user in this domain would say — 'verbatim customer or prospect quotes', 'voice-of-customer evidence', 'objection evidence', 'product-friction examples' — giving broad coverage of likely phrasings rather than jargon.

3 / 3

Distinctiveness Conflict Risk

Occupies a clear niche — verbatim customer-language extraction from transcript-like evidence with provenance — with distinct triggers unlikely to fire for adjacent analytics or posting skills.

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

relative_links

Relative link issues: 2 suspicious

Warning

Total

15

/

16

Passed

Repository
XiaomiMiMo/MiMo-Code
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.