CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

ai-sdr

When the user wants to deploy AI sales development reps, automate sales qualification, build signal-to-action routing, or design AI agent architecture for sales. Also use when the user mentions 'AI SDR,' 'AI sales agent,' 'automated qualification,' 'signal routing,' 'sales automation,' '11x,' 'Artisan,' 'AiSDR,' 'AI BDR,' or 'autonomous sales.' This skill covers AI SDR deployment, qualification automation, and agent architecture for sales development. Do NOT use for technical implementation, code review, or software architecture.

70

Quality

88%

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

SKILL.md
Quality
Evals
Security

Quality

Content

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

Highly actionable, well-sequenced content with explicit numeric thresholds, validation gates, and feedback loops, supported by real one-level-deep reference files. The main drag is token efficiency: duplicated and time-sensitive vendor pricing and a bulky ASCII diagram inflate the body at the cost of durability and context budget.

Suggestions

Move the platform comparison tables and all vendor pricing/version-specific data into references/ (e.g. a platform-comparison or implementation-guide section) to keep time-sensitive figures out of SKILL.md and remove the Instantly-vs-Smartlead duplication with Section 1.

Replace the ASCII sequence-branching diagram with a compact conditional list (Email 1 → opens/no-open → ...) to reclaim tokens without losing the branching logic.

Trim the day-by-day breakdown in Sections 2's four weeks to week-level outcomes in SKILL.md, pointing to references/implementation-guide.md for the per-day detail.

DimensionReasoningScore

Conciseness

The body is mostly dense, informative tables rather than padded prose, but it carries time-sensitive specifics ('$5K-10K', '2025-2026', '4.2M+ accounts', '450M+ contacts') that will stale, duplicates the Instantly-vs-Smartlead comparison already present in the Section 1 platform table, and spends many tokens on a bulky ASCII branching diagram that could be a short list.

3 / 5

Actionability

For an instruction-only skill the guidance is fully executable: numeric ICP tier cutoffs (80-100/50-79/0-49), a seven-step enrichment waterfall, a day-by-day warmup protocol with hard limits ('NEVER exceed 50 emails/day per mailbox'), explicit thresholds ('80%+ email match rate', 'bounce rate below 2%', 'minimum sample size: 100 sends per variant'), and concrete reply phrases for sentiment classification.

5 / 5

Workflow Clarity

The 4-week program is sequenced day-by-day with explicit checkpoints and feedback loops: a 'Before Starting' gate ('If any of these are unclear, ask before proceeding'), a soft-launch gate ('Target: 95%+ delivery rate before expanding volume', 'pause if triggered'), and a Week 4 measure-then-recalibrate loop ('Recalibrate scoring weights based on actual conversion data, not assumptions').

5 / 5

Progressive Disclosure

Two real, one-level-deep reference files (implementation-guide.md, quick-reference.md — both present in the bundle with no nested references) are clearly signaled with purpose clauses ('read references/implementation-guide.md when designing or debugging'), but the body itself inlines the full day-by-day deployment program and platform comparison detail that could live in references, keeping SKILL.md heavier than an overview.

4 / 5

Total

17

/

20

Passed

Description

91%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 description with explicit what/when structure, comprehensive trigger synonyms including vendor names, and a useful negative boundary. Its only weaknesses are slightly incomplete capability coverage relative to the body's actual scope and minor overlap risk with adjacent sales/GTM skills.

DimensionReasoningScore

Specificity

The description lists multiple concrete actions — 'deploy AI sales development reps, automate sales qualification, build signal-to-action routing, or design AI agent architecture for sales' — which goes beyond naming the domain, but omits core capabilities the body covers (sequencing, deliverability, reply classification), so it falls short of the comprehensive anchor 5.

4 / 5

Completeness

It explicitly answers both questions: what ('This skill covers AI SDR deployment, qualification automation, and agent architecture for sales development') and when ('When the user wants to... Also use when the user mentions...'), plus a negative boundary ('Do NOT use for technical implementation, code review, or software architecture') — clearer than the anchor-5 example.

5 / 5

Trigger Term Quality

Trigger coverage is comprehensive with both natural synonyms ('AI SDR', 'AI sales agent', 'AI BDR', 'autonomous sales', 'sales automation') and specific product names users would actually say ('11x', 'Artisan', 'AiSDR'), matching the comprehensive-synonyms anchor exactly.

5 / 5

Distinctiveness Conflict Risk

The niche is clear and product-name triggers are highly distinctive, but broad terms like 'sales automation' and 'automated qualification' could overlap with sibling skills in the same bundle (ai-cold-outreach, lead-enrichment), and the Do-NOT-use clause excludes only technical work rather than those adjacent GTM skills.

4 / 5

Total

18

/

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.

Validation — 16 / 16 Passed

Validation for skill structure

No warnings or errors.

Repository

tech-leads-club/agent-skills

Path

packages/skills-catalog/skills/(gtm)/ai-sdr/SKILL.md

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.