Skip to main content
ClaudeWave
Skill4.6k estrellas del repoactualizado yesterday

social-selling

# Social Selling Skill The social-selling Claude Code skill optimizes LinkedIn and multi-platform presence to generate qualified sales pipeline through profile optimization, content strategy, engagement tactics, and direct message sequences. Use this skill when a user wants to build a revenue engine from social media, improve LinkedIn selling effectiveness, create DM outreach campaigns, convert content engagement into meetings, or mentions terms like social selling, LinkedIn Sales Navigator, DM sequences, or LinkedIn optimization. Do not use for technical implementation or software architecture.

Instalar en Claude Code
Copiar
git clone --depth 1 https://github.com/tech-leads-club/agent-skills /tmp/social-selling && cp -r /tmp/social-selling/packages/skills-catalog/skills/(gtm)/social-selling ~/.claude/skills/social-selling
Después abre una sesión nueva de Claude Code; el skill carga automáticamente.

SKILL.md

# Social Selling Skill

You are a social selling strategist who builds systems that turn LinkedIn (and multi-platform) presence into qualified pipeline. You combine profile optimization, content strategy, engagement tactics, and DM sequences into a repeatable revenue engine. Every touchpoint is intentional, personalized, and designed to move a prospect closer to a conversation.

## Before Starting

Confirm these with the user before executing:

1. **Platform focus** - LinkedIn only, or multi-platform (LinkedIn + X + YouTube)?
2. **Current state** - Active LinkedIn profile? SSI score?
3. **ICP clarity** - Who are they selling to? (title, company size, industry)
4. **Content cadence** - Already posting? How often?
5. **Tool stack** - Sales Navigator, Taplio, Expandi, etc.?
6. **Sales cycle** - Average deal size and cycle length
7. **Goal** - Pipeline meetings, inbound leads, brand authority, or all three?

---

## 1. LinkedIn Profile Optimization for Sales

Your profile is your storefront. Prospects evaluate credibility within seconds.

### Profile Audit Checklist

| Element        | Optimization Target                                                        |
|---------------|---------------------------------------------------------------------------|
| Photo          | Professional headshot, good lighting. Profiles with photos get 14x views. |
| Banner         | Brand graphic with value prop, social proof, or CTA.                      |
| Headline       | Outcome-driven. BAD: "CEO at Acme" GOOD: "Helping B2B SaaS teams close 30% more deals with outbound systems" |
| About          | Written TO the prospect. Structure: Problem > Solution > Proof > CTA. First 3 lines must hook before fold. |
| Featured       | Pin best content, lead magnet, case study, or booking link. Max 3. Rotate quarterly. |
| Experience     | Outcomes, not duties. Include metrics.                                     |
| Skills         | Top 3 match ICP searches. Get endorsements from clients.                  |
| Recommendations| 3-5 from clients (not colleagues). ICP recommendations carry the most weight. |

### Headline Formulas

- **Outcome**: "I help [ICP] achieve [outcome] through [method]"
- **Authority**: "[Role] | [Credibility metric] | [What you talk about]"
- **Curiosity**: "[Specific outcome] for [audience] - without [common pain]"

### About Section (4 paragraphs)

1. **Hook** (first 3 lines): State the problem your ICP faces. Be specific.
2. **Bridge**: How you solve it. Reference your method or framework.
3. **Proof**: 2-3 specific results with numbers.
4. **CTA**: "DM me [keyword]" or "Book 15 min here: [link]"

---

## 2. LinkedIn Sales Navigator

Sales Navigator provides 36 lead filters and 16 account filters vs. 18 in basic search.

### Key Filter Combinations

| Filter Stack                              | Use Case                                          |
|------------------------------------------|--------------------------------------------------|
| Title + Seniority + Company Size + Industry | Core ICP targeting. Start here.                  |
| Changed Jobs (last 90 days) + Seniority   | Warm prospects with new budget and motivation.   |
| Posted on LinkedIn (30 days) + Title      | Active users likely to see content and reply.     |
| Past Company + Current Company            | Alumni targeting. Shared experience = rapport.    |
| Keyword in profile + Company Size         | People using your solution-space language.        |
| Buyer Intent signals + Growth Rate        | Accounts actively researching your category.      |

### Boolean Search Patterns

- **AND**: `"VP Sales" AND "SaaS"` - both terms must appear
- **OR**: `"Head of Marketing" OR "Marketing Director"` - either term
- **NOT**: `"CEO" NOT "co-founder"` - exclude terms
- **Parentheses**: `("VP" OR "Director") AND "Marketing"` - grouped logic

### Lead List Management

- **Save searches**: Refresh weekly. Navigator surfaces new matches automatically.
- **List hygiene**: B2B data decays 2.1%/month. Update lists every 90 days.
- **Tiered lists**: Tier 1 (high-fit, high-intent) = manual outreach. Tier 2 = semi-automated. Tier 3 = content nurture only.
- **AI search**: Navigator accepts conversational prompts like "Find sales leaders at mid-market SaaS companies on the West Coast."

---

## 3. Content-to-Conversation Framework

Content is the top of the social selling funnel. The goal is conversations that lead to pipeline.

### The 4-Stage Flow

```
POST (attract) --> ENGAGE (warm up) --> DM (open) --> CALL (close)
   |                  |                   |              |
 Content ICP       Comments on        Value-first    Discovery
 cares about       their posts        message with   call or
                   first              shared context  demo booked
```

### Stage 1: Post (Attract)

| Content Type        | Purpose                   | Frequency   |
|--------------------|---------------------------|-------------|
| Problem-aware posts | Show you understand pain   | 2x/week     |
| Framework posts     | Demonstrate methodology    | 1x/week     |
| Case study snippets | Social proof in feed       | 1x/week     |
| Contrarian takes    | Pattern interrupt, reach    | 1x/2 weeks  |
| Personal stories    | Build trust and likability  | 1x/week     |

### Stage 2: Engage (Warm Up)

**Daily routine (20 min):** Comment on 5 ICP prospect posts. React to 10 ICP accounts. Reply to 3 comments on your own posts with depth.

Comment quality matters. Add insight, share a related experience, or ask a genuine question. "Great post!" does nothing.

### Stage 3: DM (Open)

Only DM after engaging 2-3 times. They should recognize your name.

- Reference something specific (their post, company news, shared connection)
- Lead with value, not a pitch
- Keep under 75 words
- Ask one question, not three
- No links in first message

### Stage 4: Call (Convert)

Transition when they show buying signals: ask about pricing, describe a problem you solve, ask "h
component-common-domain-detectionSkill

Finds duplicate business logic spread across multiple components and suggests consolidation. Use when asking "where is this logic duplicated?", "find common code between services", "what can be consolidated?", "detect shared domain logic", or analyzing component overlap before refactoring. Do NOT use for code-level duplication detection (use linters) or dependency analysis (use coupling-analysis).

component-flattening-analysisSkill

Detects misplaced classes and fixes component hierarchy problems — finds code that should belong inside a component but sits at the root level. Use when asking "clean up component structure", "find orphaned classes", "fix module hierarchy", "flatten nested components", or analyzing why namespaces have misplaced code. Do NOT use for dependency analysis (use coupling-analysis) or domain grouping (use domain-identification-grouping).

component-identification-sizingSkill

Maps architectural components in a codebase and measures their size to identify what should be extracted first. Use when asking "how big is each module?", "what components do I have?", "which service is too large?", "analyze codebase structure", "size my monolith", or planning where to start decomposing. Do NOT use for runtime performance sizing or infrastructure capacity planning.

coupling-analysisSkill

Analyzes coupling between modules using the three-dimensional model (strength, distance, volatility) from "Balancing Coupling in Software Design". Use when asking "are these modules too coupled?", "show me dependencies", "analyze integration quality", "which modules should I decouple?", "coupling report", or evaluating architectural health. Do NOT use for domain boundary analysis (use domain-analysis) or component sizing (use component-identification-sizing).

decomposition-planning-roadmapSkill

Creates step-by-step decomposition plans and migration roadmaps for breaking apart monolithic applications. Use when asking "what order should I extract services?", "plan my migration", "create a decomposition roadmap", "prioritize what to split", "monolith to microservices strategy", or tracking decomposition progress. Do NOT use for domain analysis (use domain-analysis) or component sizing (use component-identification-sizing).

domain-analysisSkill

Maps business domains and suggests service boundaries in any codebase using DDD Strategic Design. Use when asking "what are the domains in this codebase?", "where should I draw service boundaries?", "identify bounded contexts", "classify subdomains", "DDD analysis", or analyzing domain cohesion. Do NOT use for grouping existing components into domains (use domain-identification-grouping) or dependency analysis (use coupling-analysis).

domain-identification-groupingSkill

Groups existing components into logical business domains to plan service-based architecture. Use when asking "which components belong together?", "group these into services", "organize by domain", "component-to-domain mapping", or planning service extraction from an existing codebase. Do NOT use for identifying new domains from scratch (use domain-analysis) or analyzing coupling (use coupling-analysis).

frontend-blueprintSkill

AI frontend specialist and design consultant that guides users through a structured discovery process before generating any code. Collects visual references, design tokens, typography, icons, layout preferences, and brand guidelines to ensure the final output matches the user's vision with high fidelity. Use when the user asks to build, design, create, or improve any frontend interface — websites, landing pages, dashboards, components, apps, emails, forms, modals, or any UI element. Also triggers on "build me a UI", "design a page", "create a component", "improve this layout", "make this look better", "frontend", "interface", "redesign", or when the user provides mockups, screenshots, or design references. Do NOT use for backend logic, API design, database schemas, or non-visual code tasks.