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.
90
88%
Does it follow best practices?
Impact
Pending
No eval scenarios have been run
Passed
No known issues
Quality
Discovery
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.
This is a strong skill description that clearly defines its domain (GTM strategy and sales motion design), provides extensive natural trigger terms covering common variations and acronyms, and explicitly states both when to use and when not to use the skill. The negative boundary clause is a particularly effective addition for reducing false positive matches.
| Dimension | Reasoning | Score |
|---|---|---|
Specificity | Lists multiple specific concrete actions: 'choose between PLG and sales-led,' 'design a sales motion,' 'optimize time-to-first-value,' 'build a value-before-purchase experience.' Also specifies coverage areas: 'sales motion selection, value delivery design, and go-to-market motion architecture.' | 3 / 3 |
Completeness | Clearly answers both 'what' (sales motion selection, value delivery design, GTM motion architecture) and 'when' with explicit trigger guidance ('When the user wants to...' and 'Also use when the user mentions...'). Additionally includes negative boundaries ('Do NOT use for technical implementation, code review, or software architecture'). | 3 / 3 |
Trigger Term Quality | Excellent coverage of natural trigger terms including both acronyms and full forms: 'PLG,' 'product-led growth,' 'sales-led,' 'sales motion,' 'free trial,' 'freemium,' 'self-serve,' 'demo-first,' 'time-to-first-value,' 'TTFV,' 'agent-led sales.' These are terms users would naturally use when discussing go-to-market strategy. | 3 / 3 |
Distinctiveness Conflict Risk | Occupies a clear niche in go-to-market strategy and sales motion design with highly specific trigger terms. The explicit exclusion of technical implementation, code review, and software architecture further reduces conflict risk with engineering-focused skills. | 3 / 3 |
Total | 12 / 12 Passed |
Implementation
77%Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.
This is a strong, highly actionable skill with excellent decision frameworks, concrete benchmarks, and clear workflows for sales motion design. Its main weakness is length—at 400+ lines, it pushes the boundaries of what should live in a single SKILL.md file, with several detailed reference sections that could be offloaded to separate files. The content quality is high throughout, with specific numbers, clear decision criteria, and practical examples.
Suggestions
Move detailed benchmark tables (CAC benchmarks, industry trial rates, agent-led discovery metrics) to a separate references file and link to them, keeping only the most critical decision-driving numbers inline.
Consider splitting motion archetypes (Section 2) into a separate MOTIONS.md reference file, keeping only the selection matrix and brief summaries in the main SKILL.md.
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The skill is comprehensive and mostly efficient, but at ~400+ lines it includes some content that could be trimmed or offloaded to reference files. The benchmarks tables and detailed archetype descriptions are valuable but border on excessive for a SKILL.md overview. Some sections like the agent-led discovery section are quite detailed for what could be a reference file. | 2 / 3 |
Actionability | Highly actionable with concrete decision frameworks (the 2x2 matrix, scoring system with 7+ PLG signals), specific benchmarks with numbers, clear PQL trigger examples, team composition by ARR stage, and step-by-step migration paths. The examples section shows concrete input/output patterns for common user requests. | 3 / 3 |
Workflow Clarity | Multi-step processes are clearly sequenced throughout: the TTFV optimization steps (MAP→ELIMINATE→PRELOAD→GUIDE→MEASURE), motion migration paths with numbered steps and success targets, hybrid motion structure with clear flow diagram, and stage-specific playbooks. Validation checkpoints are present (e.g., 'Target: 25%+ PQL-to-close rate', 'Only viable with tight ICP', signal thresholds for when to add sales). | 3 / 3 |
Progressive Disclosure | The skill references `references/quick-reference.md` and related skills at the end, which is good. However, the main body is quite long and monolithic—sections like detailed benchmarks tables, agent-led discovery details, and industry-specific trial rates could be offloaded to reference files. The content that is inline would benefit from being split into separate reference documents with clear pointers. | 2 / 3 |
Total | 10 / 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.
Validation — 11 / 11 Passed
Validation for skill structure
No warnings or errors.
81e7e0d
Table of Contents
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.