CtrlK
BlogDocsLog inGet started
Tessl Logo

prepare-sales-handoff

Use when preparing a reviewable sales handoff brief from supplied account, contact, and interaction records for a next owner.

62

Quality

72%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide

SecuritybySnyk

Passed

No findings from the security scan

Fix and improve this skill with Tessl

tessl review fix ./skills/prepare-sales-handoff/SKILL.md
SKILL.md
Quality
Evals
Security

Quality

Content

75%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, lean, and highly actionable instruction skill: it sequences a concrete workflow with an explicit safety gate, a copy-paste output template, and guardrails, and is correctly framed as non-destructive draft-only work. It is a touch short of top marks only for mild thematic redundancy, the lack of a fully worked example, and no progressive-disclosure references.

Suggestions

Add one short fully-populated worked example (e.g. fill the output template for the Avery Lin / Meridian Forge case referenced in 'Example invocation') so the output format is unambiguously copy-paste ready.

Consolidate the repeated 'do not invent qualification / budget / authority' guidance so the constraint appears authoritatively once in Guardrails and is only referenced elsewhere, trimming redundancy.

If the gating rules in step 6 grow further, split them into a short references/ file (e.g. NEXT_STEP_GATES.md) and signal it from the workflow to exercise true progressive disclosure.

DimensionReasoningScore

Conciseness

The body is lean and directive with no concept explanations Claude already knows and no filler; the only redundancy is the 'do not invent qualification' theme recurring across Purpose, Workflow, and Guardrails, which is minor but trimmable, keeping it at anchor 4 rather than 5.

4 / 5

Actionability

It provides a concrete 7-step workflow, a copy-paste output-format template with labeled fields, and precise gating rules with explicit conditions; the one gap is the absence of a fully populated worked example, so it is mostly-but-not-fully copy-paste ready.

4 / 5

Workflow Clarity

Steps are clearly sequenced with an explicit eligibility/opt-out gate (step 6) and a final 'Quality check' checklist; because the skill is explicitly non-destructive ('DRAFT ONLY', 'Actions taken: None') the destructive/batch cap does not apply, and the missing validate-fix-retry loop is not a real gap for a draft skill.

4 / 5

Progressive Disclosure

No bundle files exist and none are needed; the skill is self-contained and well-sectioned into clear headers (Purpose, Required inputs, Workflow, Output format, Guardrails, Quality check, Example invocation) with easy navigation, but at ~65 lines it marginally exceeds the simple-skill threshold and demonstrates no actual reference disclosure, so it sits at anchor 4.

4 / 5

Total

16

/

20

Passed

Description

70%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, concrete description with an explicit 'Use when' trigger and a well-scoped niche; its main limitation is that it frames a single composite action rather than enumerating several discrete capabilities. It is clearly distinguishable and unlikely to fire for the wrong skill.

Suggestions

Enumerate 1-2 more discrete actions the skill performs (e.g. 'compile a sourced interaction chronology and stakeholder map') to lift specificity from a single composite action to several concrete capabilities.

Add a couple of natural trigger synonyms users might say, such as 'deal handoff', 'account transition', or 'opportunity hand-off', to broaden trigger-term coverage.

Optionally add a second trigger clause (e.g. 'Use when ... or when the user asks to hand off an account to a new owner') to give the 'when' more than one concrete trigger situation.

DimensionReasoningScore

Specificity

Names the domain ('sales handoff brief') and one concrete composite action ('preparing a reviewable ... brief from supplied ... records') with specific inputs and recipient, but it is a single action rather than the several discrete actions the anchor-4 example requires.

3 / 5

Completeness

It explicitly answers both 'what' (prepare a reviewable sales handoff brief from records for a next owner) and 'when' via an explicit 'Use when ...' clause; the 'when' is concrete but a single restated situation rather than multiple natural trigger phrasings, so it sits at anchor 4 rather than 5.

4 / 5

Trigger Term Quality

Natural terms a user would say are present ('sales handoff', 'account ... contact ... interaction records', 'next owner'), with good coverage; a few synonyms (e.g. 'deal handoff', 'account transition') are missing, keeping it just below comprehensive.

4 / 5

Distinctiveness Conflict Risk

It carves a clear niche (sales handoff brief preparation from supplied records) with distinct triggers and minimal conflict risk, with only minor overlap against general sales or account-management skills.

4 / 5

Total

15

/

20

Passed

Validation

100%

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

Validation16 / 16 Passed

Validation for skill structure

No warnings or errors.

Repository
llaskin/AI-SDR-Skill-Pack
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.