CtrlK
BlogDocsLog inGet started
Tessl Logo

draft-objection-response

Use when drafting a bounded reply to a supplied prospect objection after contact-specific outreach gates are known.

60

Quality

70%

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/draft-objection-response/SKILL.md
SKILL.md
Quality
Evals
Security

Quality

Content

78%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.

The body is a lean, well-structured instruction-only skill with explicit gating, terminal states, and a quality checklist that make it highly actionable. Adding a worked output example and an explicit error-recovery loop would push workflow clarity and actionability to full marks.

DimensionReasoningScore

Conciseness

Terse imperative steps with no concept-explanation padding and a clear assumption of Claude's competence, though the guardrails and quality check slightly restate workflow constraints and could be trimmed.

4 / 5

Actionability

Concrete, executable instruction-only guidance with explicit terminal states ('STOP', 'NEEDS VERIFICATION'), named gates, labeled output fields, and proof-gap handling, but no fully worked output example for the common case.

4 / 5

Workflow Clarity

A clear 7-step sequence with explicit validation checkpoints (gates in step 2, readiness labeling in step 7) and a final quality-check checklist, though it lacks an explicit validate-fix-retry feedback loop.

4 / 5

Progressive Disclosure

A single-purpose skill under ~50 lines with no need for external references, organized into clear sections (Purpose, Required inputs, Workflow, Output format, Guardrails, Quality check, Example invocation), meeting the simple-skill exception for a top score.

5 / 5

Total

17

/

20

Passed

Description

62%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.

The description clearly targets a specific compliance-gated sales workflow and supplies an explicit 'Use when' trigger, but it bundles what and when into a single clause and relies on narrow, somewhat jargon-laden trigger terms. Expanding to a few concrete actions and more natural synonyms would raise it.

Suggestions

List 1-2 more concrete actions (e.g., 'surface proof gaps', 'gate drafting on opt-out status') to move specificity from a single action toward comprehensive coverage.

Add natural trigger synonyms users actually say (e.g., 'prospect pushback', 'sales objection', 'reply to a no') beyond 'prospect objection'.

Separate the 'what' and 'when' into distinct clauses so the trigger conditions read as concrete, standalone phrases rather than a precondition tacked onto the action.

DimensionReasoningScore

Specificity

Names the objection-response domain and one concrete action ('drafting a bounded reply'), but does not list several actions, matching the '1-2 concrete actions, not comprehensive' anchor.

3 / 5

Completeness

Both 'what' (draft a bounded reply to a prospect objection) and 'when' (Use when... after gates are known) are present in one combined clause, but the 'when' leans on the 'what' rather than standing as concrete separate triggers.

4 / 5

Trigger Term Quality

Natural terms like 'draft', 'objection', 'reply', and 'prospect objection' appear, but coverage is narrow and the gating phrase 'after contact-specific outreach gates are known' is jargon users would not naturally say.

3 / 5

Distinctiveness Conflict Risk

The sales-compliance objection-reply niche is narrow with distinct triggers, though minor overlap remains with general reply-drafting skills.

4 / 5

Total

14

/

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.