CtrlK
BlogDocsLog inGet started
Tessl Logo

get-rep-call-feedback

Use when the user wants evidence-backed coaching for one rep's calls, especially by comparing the rep with peer examples to identify repeatable best practices, specific upgrade moments, and practical next-call language.

64

Quality

76%

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 ./packages/opencode/src/skill/builtin/.bundle/sales/workflows/get-rep-call-feedback/SKILL.md
SKILL.md
Quality
Evals
Security

Quality

Content

85%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-structured coaching workflow with explicit thresholds, a complete output contract, and clean one-level reference loading. The only real weakness is repetition — several policies (no scorecards, don't assume a target) are stated two or three times across sections.

Suggestions

Consolidate the no-scorecard/no-ranking guidance, which currently appears in Workflow step 4, 'Next steps to avoid', and Modes, into a single Rules bullet.

Merge the two near-duplicate opening bullets in 'Resolve the target and comparison set' that both instruct not to assume a target rep or feedback mode.

Trim the Context-Gathering Intake section to one sentence (or fold it into Rules), since it adds little beyond naming a preferred input tool.

DimensionReasoningScore

Conciseness

Mostly efficient policy content, but with real redundancy: the no-scorecard rule appears in Workflow step 4, 'Next steps to avoid', and implicitly in Modes; the first two bullets of 'Resolve the target' repeat the same don't-assume-a-target guidance; and the Context-Gathering Intake section adds little beyond naming a preferred input tool. Fits 'mostly efficient but could be tightened'; not 4 because several sections restate the same constraint.

3 / 5

Actionability

For an instruction-only skill this is copy-paste-ready: exact thresholds ('at least 15 target calls and at least 15 peer calls', 'three to eight observed moments', 'five to ten stealable peer moments', 'no more than 25 quoted words'), explicit defaults (trailing 30/60-day windows), a complete output template with per-section formats, and enumerated next-step options.

5 / 5

Workflow Clarity

A clear four-step sequence with explicit validation checkpoints and feedback loops: 'make at most three narrow source reads... and confirm any inferred anchor', 'If targets are not met after a bounded pass, produce a limited feedback memo, state the shortfall, and name the next search', plus a Failure Handling section and a Coverage/Confidence output section that force recovery paths rather than leaving them implicit.

5 / 5

Progressive Disclosure

The body owns the core loop and output format, and each of the four reference files — all verified to exist, one level deep — is linked with a conditional purpose ('Use... when date-window conversion, attendee-filter limitations, threshold fallback, or sparse-result recovery needs more detail'). Navigation is easy and nothing that belongs in a reference is inlined.

5 / 5

Total

18

/

20

Passed

Description

67%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 well-formed description with an explicit 'Use when' clause, third-person framing, and a distinctive peer-comparison niche. Its main gap is trigger-term coverage: the natural phrase 'call feedback' (used throughout the skill's own examples) never appears.

Suggestions

Add the natural user phrasing 'call feedback' or 'feedback on a rep's calls' to the description, since the skill's own example prompts lead with that wording.

Include 1-2 more trigger variations such as 'sales call coaching' or 'review my recent calls' to broaden keyword coverage.

Consider naming the concrete deliverable (a coaching readout with stealable peer moves and specific upgrade moments) instead of the abstract phrase 'evidence-backed coaching'.

DimensionReasoningScore

Specificity

Names several concrete actions — 'comparing the rep with peer examples', 'identify repeatable best practices, specific upgrade moments, and practical next-call language' — but phrases like 'evidence-backed coaching' stay somewhat abstract, so coverage is good rather than comprehensive.

4 / 5

Completeness

Explicitly answers both: what ('comparing the rep with peer examples to identify repeatable best practices, specific upgrade moments, and practical next-call language') and when ('Use when the user wants evidence-backed coaching for one rep's calls'). The 'when' could carry more concrete trigger phrases to reach a 5.

4 / 5

Trigger Term Quality

Relevant keywords are present ('coaching', 'rep's calls', 'peer examples', 'best practices') but the most natural user phrasing for this task — 'call feedback', 'review my calls' — is missing; the skill's own example prompts lead with 'feedback'. Fits 'some relevant keywords but missing common variations or synonyms' better than the level above, where only a few natural terms would be missing.

3 / 5

Distinctiveness Conflict Risk

A clear niche — rep-level call coaching via peer benchmarking — with distinct triggers; only minor overlap risk with adjacent sales skills such as scorecard or manager-note generation, which it explicitly disclaims elsewhere.

4 / 5

Total

15

/

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

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.