When the user wants to sell through social media, optimize LinkedIn for sales, build DM sequences, or convert content engagement into pipeline. Also use when the user mentions 'social selling,' 'LinkedIn selling,' 'LinkedIn DMs,' 'social prospecting,' 'LinkedIn Sales Navigator,' 'DM sequences,' 'LinkedIn outreach,' 'social pipeline,' or 'LinkedIn optimization.' This skill covers social selling strategy from profile optimization through DM-to-deal conversion. Do NOT use for technical implementation, code review, or software architecture.
78
72%
Does it follow best practices?
Impact
Pending
No eval scenarios have been run
Passed
No known issues
Optimize this skill with Tessl
npx tessl skill review --optimize ./packages/skills-catalog/skills/(gtm)/social-selling/SKILL.mdQuality
Discovery
89%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 with excellent trigger term coverage and clear completeness, explicitly stating both what the skill does and when to use it. The main weakness is that the specific capabilities could be more granular—listing concrete actions like 'write connection request messages,' 'audit LinkedIn profiles,' or 'design multi-touch DM sequences' would strengthen specificity. The inclusion of negative boundaries is a nice touch that further reduces conflict risk.
Suggestions
Add more concrete, specific actions to improve specificity, e.g., 'audit LinkedIn profiles, write connection request messages, design multi-touch DM sequences, craft engagement comments, build social proof strategies.'
| Dimension | Reasoning | Score |
|---|---|---|
Specificity | The description names the domain (social selling, LinkedIn) and mentions some actions like 'optimize LinkedIn for sales,' 'build DM sequences,' 'convert content engagement into pipeline,' and 'profile optimization through DM-to-deal conversion,' but these are more high-level categories than concrete specific actions like the level-3 examples show. | 2 / 3 |
Completeness | Clearly answers both 'what' (social selling strategy from profile optimization through DM-to-deal conversion) and 'when' (explicit 'Use when' triggers and a list of trigger terms). Also includes a helpful 'Do NOT use' boundary clause. | 3 / 3 |
Trigger Term Quality | Excellent coverage of natural trigger terms users would say: 'social selling,' 'LinkedIn selling,' 'LinkedIn DMs,' 'social prospecting,' 'LinkedIn Sales Navigator,' 'DM sequences,' 'LinkedIn outreach,' 'social pipeline,' 'LinkedIn optimization.' These are terms users would naturally use when seeking help with this topic. | 3 / 3 |
Distinctiveness Conflict Risk | Very distinct niche focused specifically on LinkedIn/social media selling with clear boundaries. The 'Do NOT use for technical implementation, code review, or software architecture' clause further reduces conflict risk. Unlikely to overlap with other skills. | 3 / 3 |
Total | 11 / 12 Passed |
Implementation
55%Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.
The skill is highly actionable with excellent concrete templates, benchmarks, and workflows, but it is far too long and monolithic for a SKILL.md file. It tries to be a comprehensive social selling encyclopedia rather than a lean overview with pointers to detailed resources. The content quality is strong but the delivery format undermines token efficiency and progressive disclosure.
Suggestions
Split into a concise SKILL.md overview (Sections 1-4 summarized) with detailed content in referenced files like SALES-NAVIGATOR.md, DM-TEMPLATES.md, AUTOMATION-TOOLS.md, MULTI-PLATFORM.md, and ALGORITHM.md
Remove explanations of concepts Claude already knows (e.g., what Boolean operators do, what PDF carousels are, basic LinkedIn features) and statistics that don't directly inform action
Trim the tool comparison and metrics sections to essential recommendations only, moving detailed comparisons to a referenced file
Consolidate the 'Questions to Ask' and 'Before Starting' sections which overlap significantly
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | At ~400+ lines, this skill is extremely verbose. It explains concepts Claude already knows (what Boolean search is, what PDF carousels are, basic LinkedIn features), includes extensive statistics and benchmarks that pad the content, and covers far too much ground. Sections like algorithm tips, employee advocacy, and multi-platform strategy could be separate referenced files. Many tables restate common knowledge. | 1 / 3 |
Actionability | The skill provides highly concrete, actionable guidance: specific DM templates with exact wording, daily/weekly routines with time allocations, exact filter combinations for Sales Navigator, headline formulas, automation safety limits with specific numbers, and clear benchmarks. A user could immediately execute on nearly every section. | 3 / 3 |
Workflow Clarity | The 4-stage flow (Post → Engage → DM → Call) is clearly sequenced with explicit gates (e.g., 'Only DM after engaging 2-3 times'). The DM sequence has a clear day-by-day architecture with a defined stop condition ('After 3 unanswered follow-ups - move to content nurture'). The daily and weekly routines provide clear time-boxed workflows. The 'Before Starting' checklist ensures prerequisites are confirmed. | 3 / 3 |
Progressive Disclosure | This is a monolithic wall of content with 10 major sections all inline. There are no references to separate files for detailed content like tool comparisons, DM templates, algorithm details, or employee advocacy programs. The 'Related Skills' section at the end references other skills but the body itself should split substantial sections (e.g., Sales Navigator details, automation tools, multi-platform strategy) into referenced documents. | 1 / 3 |
Total | 8 / 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.
906a57d
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.