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 answering both what the skill does and when to use it. The explicit exclusion clause adds helpful disambiguation. The main weakness is that the specific capabilities could be more granular—listing concrete deliverables like 'write LinkedIn connection request messages' or 'create content calendars for social selling' would strengthen specificity.
Suggestions
Add more concrete, specific actions/deliverables (e.g., 'write LinkedIn connection request templates, create DM follow-up sequences, audit LinkedIn profiles for sales optimization') to improve specificity from domain-level to action-level.
| 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' exclusion 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 in this domain. | 3 / 3 |
Distinctiveness Conflict Risk | Very distinct niche focused specifically on LinkedIn/social media selling with clear boundaries. The explicit exclusion of technical implementation, code review, and software architecture further reduces conflict risk 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.
This skill is exceptionally actionable with clear workflows, concrete templates, and specific benchmarks that make it immediately usable. However, it is severely over-scoped and verbose—attempting to cover profile optimization, Sales Navigator, content strategy, DM sequences, automation tools, metrics, multi-platform selling, thought leadership, employee advocacy, and algorithm mechanics all in one file. The lack of progressive disclosure means this consumes enormous context window space, much of which covers knowledge Claude already possesses or could be split into referenced sub-files.
Suggestions
Split into a concise SKILL.md overview (profile optimization + DM sequence core) with references to separate files: SALES-NAVIGATOR.md, AUTOMATION-TOOLS.md, MULTI-PLATFORM.md, EMPLOYEE-ADVOCACY.md, ALGORITHM.md
Remove explanatory content Claude already knows: Boolean search syntax, what SSI stands for, general platform descriptions, and statistics that don't change behavior (e.g., '92% of marketers maintaining or increasing video investment')
Cut the tool comparison table and platform-specific algorithm details into referenced files, keeping only a one-line recommendation per use case in the main skill
Reduce the 'Questions to Ask' section—many overlap with the 'Before Starting' section, creating redundancy
| 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, 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 specific day-by-day timing with a clear stop condition ('After 3 unanswered follow-ups'), and the daily/weekly routines provide structured workflows. The troubleshooting section adds error recovery guidance. | 3 / 3 |
Progressive Disclosure | This is a monolithic wall of content with no references to external files. All 10 major sections are inline, making the skill extremely long. Content like tool comparisons, algorithm details, employee advocacy programs, and multi-platform strategy should be in separate referenced files. The 'Related Skills' section at the end references other skills but doesn't offload any of this skill's own content. | 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.
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.