sales-call-prep

Pre-sales-call intelligence composite. Deep dives on the person AND their company before a sales call, then maps findings to your product to generate talking points, objection prep, and a call strategy. Goes beyond generic attendee research — this is sales-specific intelligence that helps SDRs, AEs, and founders walk into calls with a plan. Tool-agnostic — works with any CRM, research source, and calendar.

Quality

75%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide

Securityby

Low

Low-risk findings worth noting

Fix and improve this skill with Tessl

tessl review fix ./skills/sales/composites/sales-call-prep/SKILL.md

Quality

Content

71%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-sequenced composite skill with concrete schemas and templates, weakened by monolithic inlining and some padding. The workflow is clear and executable but would benefit from file-level progressive disclosure and tighter prose.

Suggestions

Extract the large report template (Step 5) and the per-dimension research tables into reference files (e.g. REPORT_TEMPLATE.md, COMPANY_RESEARCH.md) and link to them one level deep.

Trim motivational rationale ('is a credibility killer') and condense the top meeting-brief comparison table to the distinctives that matter for triggering.

Add an explicit completeness/validation checkpoint between Step 1 (context gather) and Step 2 (web research) so prior-interaction gaps are caught before research proceeds.

Dimension	Reasoning	Score
Conciseness	Mostly efficient and table-driven, but ~830 lines with motivational padding ('is a credibility killer'), a large editorial meeting-brief comparison table, and 'Why It Matters' rationale columns that restate sales common sense and could be tightened.	3 / 5
Actionability	Fully executable guidance: typed input/output contracts per step, specific 'what to check / where to look / why' tables, authority classifications, and a complete copy-ready report template covering common call types.	5 / 5
Workflow Clarity	Clear Steps 0–5 sequence with explicit I/O contracts between steps and an After-Call checklist, but lacks explicit validate→fix→retry feedback loops between research/synthesis steps, leaving minor validation gaps.	4 / 5
Progressive Disclosure	Good in-file structure (clear ## sections, tables, schemas) but entirely monolithic — no bundle/reference files exist, and large blocks (full report template, research dimension tables) are inlined that could live one level deeper.	3 / 5
	Total	15 / 20 Passed

Description

78%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 specific, well-triggered description with concrete actions and good natural keyword coverage, undermined only by the absence of an explicit 'Use when' trigger clause. Distinctiveness is good but depends on body context to fully separate it from generic meeting-research skills.

Suggestions

Add an explicit 'Use when...' clause naming concrete triggers, e.g. 'Use when preparing for a sales call, demo, or prospect meeting — not internal meetings or customer check-ins.'

Move the contrast with generic meeting research into the description (one phrase) so distinctiveness does not rely on the body table.

Trim 'pre-sales-call intelligence composite' jargon in favor of the natural phrase users actually say ('prep me for my sales call').

Dimension	Reasoning	Score
Specificity	Lists multiple concrete actions — 'Deep dives on the person AND their company', 'maps findings to your product to generate talking points, objection prep, and a call strategy' — giving comprehensive coverage of what the skill does.	5 / 5
Completeness	The 'what' is clear, but there is no explicit 'Use when...' trigger clause; the 'when' is only weakly implied via the audience phrase 'helps SDRs, AEs, and founders walk into calls with a plan', which caps completeness at 3 per the rubric.	3 / 5
Trigger Term Quality	Strong natural-term coverage with synonyms: 'sales call', 'call strategy', 'talking points', 'objection prep', plus audience variants 'SDRs, AEs, and founders' and tool terms 'CRM'.	5 / 5
Distinctiveness Conflict Risk	It carves a niche ('Goes beyond generic attendee research — this is sales-specific intelligence') but overlap with a closely related meeting-brief skill is only fully resolved in the body, leaving minor conflict risk.	4 / 5
	Total	17 / 20 Passed

Validation

87%

Warnings & errors only

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

Validation — 14 / 16 Passed

Validation for skill structure

Criteria	Description	Result
skill_md_line_count	SKILL.md is long (832 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
Path: skills/sales/composites/sales-call-prep/SKILL.md
Commit: 2523432

Reviewed: 5 days ago

Table of Contents

Discovery Implementation Validation

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.