CtrlK
BlogDocsLog inGet started
Tessl Logo

sales-motion-design

When the user wants to choose between PLG and sales-led, design a sales motion, optimize time-to-first-value, or build a value-before-purchase experience. Also use when the user mentions 'PLG,' 'product-led growth,' 'sales-led,' 'sales motion,' 'free trial,' 'freemium,' 'self-serve,' 'demo-first,' 'time-to-first-value,' 'TTFV,' or 'agent-led sales.' This skill covers sales motion selection, value delivery design, and go-to-market motion architecture. Do NOT use for technical implementation, code review, or software architecture.

68

Quality

Does it follow best practices?

Impact

No eval scenarios have been run

SecuritybySnyk

Passed

No known issues

SKILL.md
Quality
Evals
Security

Quality

Content

65%

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

The content is highly actionable with concrete matrices, thresholds, and sequenced playbooks, but it is oversized for a SKILL.md overview, duplicates reference material inline, and is structured as a compendium without explicit workflow validation checkpoints. Leaner main body plus stronger reference signaling would lift the weaker dimensions.

Suggestions

Move the benchmark tables that also appear in references/quick-reference.md (TTFV targets, CAC/LTV ratios, conversion rates) into the reference file, leaving the SKILL.md body as a leaner overview that points to them — this addresses both conciseness and progressive_disclosure.

Promote the reference signal from a single trailing sentence to a clearly flagged 'Reference' section near the top, e.g. '**Benchmarks & cheat sheets**: See [references/quick-reference.md](references/quick-reference.md)', so detailed material is obviously one level deep.

Add an explicit end-to-end workflow with a validation checkpoint — e.g. 'Select motion → set TTFV/metric targets → implement → check red-flag thresholds (PQL-to-close <15%, CAC payback >20mo) → adjust' — to give the multi-step process a validate→fix→retry loop.

DimensionReasoningScore

Conciseness

The body is information-dense rather than fluffy, but at ~460 lines it is very long for a SKILL.md overview, and several benchmark tables (TTFV targets, CAC ratios, conversion rates) duplicate content also present in references/quick-reference.md — it could be tightened by pushing detail into the reference.

2 / 3

Actionability

Provides concrete, specific decision guidance: a price×complexity selection matrix with scoring ('7+ PLG signals = pure PLG. 4-6 = hybrid. 0-3 = sales-led'), explicit PQL triggers, ranked value-before-purchase tactics with conversion lifts, and a 5-step TTFV optimization sequence — fully actionable for an instruction-only skill.

3 / 3

Workflow Clarity

Individual processes are well sequenced with explicit targets (numbered migration paths 'Target: 25%+ PQL-to-close rate', the MAP/ELIMINATE/PRELOAD/GUIDE/MEASURE steps), but the skill reads as a reference compendium of matrices rather than a single end-to-end workflow, and the process steps lack explicit validation checkpoints or a validate→fix→retry loop.

2 / 3

Progressive Disclosure

A one-level-deep reference exists and is well organized, but it is signaled only by a single sentence buried at the very end of the body, and the main file itself carries large benchmark tables that overlap the reference — content that should be separate is inline.

2 / 3

Total

9

/

12

Passed

Description

100%

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, trigger-rich, complete on both what and when, and clearly distinguished from neighboring skills via a negative-scope clause. It matches the strongest anchor on every dimension.

DimensionReasoningScore

Specificity

Lists multiple concrete actions — 'choose between PLG and sales-led, design a sales motion, optimize time-to-first-value, or build a value-before-purchase experience' plus 'sales motion selection, value delivery design, and go-to-market motion architecture' — rather than vague language; voice stays third-person ('When the user wants...').

3 / 3

Completeness

Explicitly answers both what ('This skill covers sales motion selection, value delivery design, and go-to-market motion architecture') and when ('Also use when the user mentions...'), and adds a negative scope ('Do NOT use for technical implementation, code review, or software architecture').

3 / 3

Trigger Term Quality

Covers a broad set of natural terms a user would actually say: 'PLG,' 'product-led growth,' 'sales-led,' 'sales motion,' 'free trial,' 'freemium,' 'self-serve,' 'demo-first,' 'time-to-first-value,' 'TTFV,' and 'agent-led sales.'

3 / 3

Distinctiveness Conflict Risk

Clear GTM/sales-motion niche with distinct triggers and an explicit exclusion clause, making it unlikely to fire for unrelated skills.

3 / 3

Total

12

/

12

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
tech-leads-club/agent-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.