CtrlK
BlogDocsLog inGet started
Tessl Logo

sales-coaching

AI sales coach composite. Analyzes all available sales data — email campaigns, call recordings/transcripts, reply patterns, pipeline outcomes — to identify what the user does well, where they struggle, and how to improve. Finds patterns in top-performing emails, winning call techniques, successful objection handles, and deal progression. Produces personalized coaching recommendations based on their specific product, market, and selling style. Tool-agnostic.

58

Quality

68%

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/sales/composites/sales-coaching/SKILL.md
SKILL.md
Quality
Evals
Security

Quality

Content

77%

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

The body is a well-sequenced, highly actionable coaching workflow with clear checkpoints and concrete schemas. Its main weaknesses are verbosity (overlapping report templates across steps) and a monolithic single-file structure that should be split into reference files.

Suggestions

Deduplicate the coaching report template between Step 5 (personalized_playbook) and Step 6 (report structure) — keep one canonical template and reference it from the other.

Extract the large output-contract schemas and per-role skill-dimension tables into reference files under references/ (e.g. SCHEMAS.md, SKILL_DIMENSIONS.md) and link to them from SKILL.md to improve progressive disclosure.

Tighten the placeholder tables (winner_vs_loser, sentiment_trend, winning_vs_losing) which repeat similar column structures across steps.

DimensionReasoningScore

Conciseness

The body is verbose and redundant — the coaching report template is rendered in both Step 5 (personalized_playbook) and Step 6 (report structure) with heavy overlap, and many placeholder tables repeat structure — yet it does not condescend by explaining concepts Claude already knows. Not score 3 because it could be tightened substantially; not score 1 because the content is structured domain-specific guidance rather than padded with basic explanations.

2 / 3

Actionability

For an instruction-only skill the guidance is highly concrete and copy-paste-ready: exact metric formulas ("Word count (you) / word count (prospect)"), numeric thresholds ("10-15 questions", "40-50% talk"), full input/output contracts, letter-grade rubrics, and a complete report template. Matches the anchor for specific, executable guidance.

3 / 3

Workflow Clarity

Steps 0-6 are clearly sequenced, each with a Purpose, Input Contract, Output Contract, and explicit Human Checkpoints acting as validation gates (e.g. "Proceed with analysis? (Y/n)"), plus a data-availability adaptation table. This is an analysis/coaching workflow, not a destructive or batch operation, so the validation cap does not apply.

3 / 3

Progressive Disclosure

The skill is a single ~900-line monolithic file with no bundle files; it is well-sectioned but content that would benefit from being split (the large output-contract schemas, the report template, the per-role skill-dimension tables) is all inline. Not score 3 because it far exceeds the under-50-lines simple-skill allowance; not score 1 because organization is clear, not a wall of text.

2 / 3

Total

10

/

12

Passed

Description

60%

Based on the skill's description, can an agent find and select it at the right time? Clear, specific descriptions lead to better discovery.

The description is specific and action-oriented about what the composite does, but it is missing an explicit "Use when…" trigger clause and the natural user-spoken phrases that would cue auto-loading. It also does not differentiate itself from sibling sales composites within the description itself.

Suggestions

Add an explicit "Use when…" clause with natural trigger phrases users would say, e.g. "Use when the user says 'coach me on my sales', 'how can I sell better', 'why am I losing deals', or wants to diagnose their personal selling performance."

Surface 2-3 natural trigger terms ("sales coaching", "improve my selling", "review my calls/emails") directly in the description so the skill is cued by how users actually talk.

Add a one-line distinctiveness note in the description (e.g. "coaches the seller, unlike sequence-performance which analyzes campaigns") to reduce conflict risk with sibling composites.

DimensionReasoningScore

Specificity

The description lists multiple concrete actions — "Analyzes all available sales data — email campaigns, call recordings/transcripts, reply patterns, pipeline outcomes", "Finds patterns in top-performing emails, winning call techniques, successful objection handles", and "Produces personalized coaching recommendations" — matching the anchor that names several specific actions rather than a single vague one.

3 / 3

Completeness

It clearly answers what the skill does (analyze sales data, find patterns, produce coaching) but has no "Use when…" clause or equivalent explicit trigger guidance — the judging guideline caps completeness at 2 in that case. Not score 1 because the "what" is strong; not score 3 because "when" is only implied, not explicit.

2 / 3

Trigger Term Quality

It contains relevant domain keywords ("sales coach", "coaching recommendations", "email campaigns", "call recordings") but omits the natural trigger phrases a user would actually say (e.g. "coach me", "help me sell better", "why am I losing deals"), which only appear in the body. Not score 3 because common variations users would speak are missing; not score 1 because several relevant keywords are present.

2 / 3

Distinctiveness Conflict Risk

It carves a personal-coaching niche ("coaching recommendations based on their specific product, market, and selling style") but does not differentiate itself from the sibling `sequence-performance` composite within the description — that distinction lives only in the body. Somewhat specific but could still overlap with similar sales-analysis skills.

2 / 3

Total

9

/

12

Passed

Validation

87%

Checks the skill against the spec for correct structure and formatting. All validation checks must pass before discovery and implementation can be scored.

Validation14 / 16 Passed

Validation for skill structure

CriteriaDescriptionResult

skill_md_line_count

SKILL.md is long (909 lines); consider splitting into references/ and linking

Warning

frontmatter_unknown_keys

Unknown frontmatter key(s) found; consider removing or moving to metadata

Warning

Total

14

/

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.