CtrlK
BlogDocsLog inGet started
Tessl Logo

review-rep-call-trends

Use when the user wants to understand how a sales or customer-facing rep's call behavior is changing over time. Produce an evidence-backed trend readout with improvements, regressions, stable patterns, coaching actions, and calls to re-listen.

68

Quality

82%

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

81%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, actionable instruction skill with a clear sequenced workflow, explicit validation, and properly separated references. The main improvement area is tightening repetitive disambiguation guidance to improve token efficiency.

Suggestions

Consolidate the repeated clarification/ask-the-user bullets in 'Resolve the rep and comparison basis' into a single decision rule to reduce token cost.

Consider moving the detailed behavior-category list in Step 3 wholly into references/rubric.md and keeping only the core categories inline, since the rubric already covers the technical extensions.

The Output Format block is long; a brief pointer to a compact template could let the body focus on workflow logic, though the current inline template is genuinely copy-paste ready.

DimensionReasoningScore

Conciseness

The body is dense and task-specific without explaining concepts Claude already knows, though several repetitive disambiguation bullets in Step 1 could be tightened.

4 / 5

Actionability

Concrete guidance throughout — fixed limits (25/slice, 30-60 calls, score_threshold=0), explicit time slices, a copy-paste output template, and exactly-three coaching actions each with skill/if-then/drill/check — with minor reliance on judgment calls.

4 / 5

Workflow Clarity

A clearly sequenced 5-step workflow with an explicit validation checkpoint (Step 4) and a failure-handling/limited-readout feedback loop for sparse or uneven samples.

5 / 5

Progressive Disclosure

SKILL.md owns the workflow while two clearly signaled, one-level-deep references (request-schema.yaml, rubric.md) hold the extra detail; the body is well-sectioned but dense enough that minor organization gaps remain.

4 / 5

Total

17

/

20

Passed

Description

83%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 strong, third-person description that clearly states both the trigger condition and the concrete deliverables, with natural trigger terms and a distinct niche. Minor room to add synonyms and sharpen the boundary against sibling call-coaching skills.

DimensionReasoningScore

Specificity

The description enumerates concrete readout components — 'improvements, regressions, stable patterns, coaching actions, and calls to re-listen' — listing several specific outputs with only minor coverage gaps.

4 / 5

Completeness

It explicitly answers both 'what' ('Produce an evidence-backed trend readout with...') and 'when' ('Use when the user wants to understand...') with concrete trigger phrasing.

5 / 5

Trigger Term Quality

Natural phrases like 'rep's call behavior is changing over time' map to how users actually phrase the request (e.g. 'review a rep's call trends'), with good keyword coverage though a few synonyms are absent.

4 / 5

Distinctiveness Conflict Risk

The time-based trend-comparison framing is a clear niche with distinct triggers, with only minor overlap risk against closely related single-call coaching skills.

4 / 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

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.