Skill flagged — suspicious patterns detected

ClawHub Security flagged this skill as suspicious. Review the scan results before using.

Linkedin Signal

v1.0.0

Detect and score B2B buying signals from LinkedIn job posts and company data, then generate personalized outreach messages for hot leads.

0· 68·0 current·0 all-time

Install

OpenClaw Prompt Flow

Install with OpenClaw

Best for remote or guided setup. Copy the exact prompt, then paste it into OpenClaw for nicemaths123/linkedin-signal.

Previewing Install & Setup.
Prompt PreviewInstall & Setup
Install the skill "Linkedin Signal" (nicemaths123/linkedin-signal) from ClawHub.
Skill page: https://clawhub.ai/nicemaths123/linkedin-signal
Keep the work scoped to this skill only.
After install, inspect the skill metadata and help me finish setup.
Use only the metadata you can verify from ClawHub; do not invent missing requirements.
Ask before making any broader environment changes.

Command Line

CLI Commands

Use the direct CLI path if you want to install manually and keep every step visible.

OpenClaw CLI

Bare skill slug

openclaw skills install linkedin-signal

ClawHub CLI

Package manager switcher

npx clawhub@latest install linkedin-signal
Security Scan
VirusTotalVirusTotal
Benign
View report →
OpenClawOpenClaw
Suspicious
medium confidence
Purpose & Capability
Name/description (LinkedIn buying signals + outreach) match the runtime instructions: the SKILL.md explicitly orchestrates Apify actors to scrape LinkedIn jobs, company pages, news, and profiles and uses an LLM to score and craft outreach. Collecting decision-maker info and emails is coherent with lead-gen purpose.
!
Instruction Scope
Instructions direct broad web scraping of LinkedIn job posts, company profiles, and personal profiles and to extract emails/contacts and push results to external systems (CSV/Notion/CRM). The doc does not document rate-limiting, legality/TOU compliance, how contact emails are obtained, or safeguards for sensitive personal data. It also references many Apify actor IDs and expects an apify_token in the example input, but the skill metadata does not declare that credential.
Install Mechanism
This is instruction-only (no install spec, no code files), so nothing is written to disk by an installer. That lowers technical install risk; the runtime risk is from remote scraping and outbound data flows, not local installs.
!
Credentials
Registry metadata lists no required env vars or primary credential, yet the SKILL.md input schema and setup steps explicitly require an Apify API token (apify_token). It also claims integrations (Notion/Airtable/HubSpot/CRM/Slack) but does not declare required credentials for those targets. This mismatch is an incoherence and increases risk of ad-hoc credential requests at runtime.
Persistence & Privilege
The skill is not always:true, is user-invocable, and does not request persistent system privileges or claim to modify other skills/configs. No elevated persistent presence is requested in the metadata.
What to consider before installing
This skill appears to do what it says (scrape LinkedIn via Apify and generate outreach) but the metadata omits required credentials and data-flow details. Before installing or running: (1) Confirm the developer/source and ask them to declare required env vars (Apify token and any CRM/Notion tokens) in the metadata rather than only in example inputs. (2) Never supply high-privilege or production CRM tokens to an unknown skill — use a disposable/test account or scoped API key. (3) Ask how emails/PII are obtained and whether scraping respects LinkedIn's terms and privacy laws (GDPR). (4) Verify the referenced Apify actor IDs on apify.com and ensure they are reputable. (5) If you plan to push leads to your systems, require the skill to show explicit destination endpoints and authentication flows before granting access. If the author cannot provide source code or a homepage and explain the credential needs, treat this as risky and avoid providing real credentials.

Like a lobster shell, security has layers — review code before you run it.

latestvk978nkzye09hn3kqhatvrz0da584jksv
68downloads
0stars
1versions
Updated 2w ago
v1.0.0
MIT-0

🎯 LinkedIn B2B Buying Signal Detector

Slug: linkedin-buying-signal-detector
Category: Sales Intelligence / Lead Generation
Powered by: Apify + Claude AI

Detect who is ready to buy RIGHT NOW by analyzing LinkedIn job postings, company growth signals, tech stack changes, and hiring patterns — then auto-generate hyper-personalized outreach messages.


💡 Why This Skill Dominates

Most lead gen tools find who to contact. This skill tells you when to contact them — at the exact moment they have budget, urgency, and intent. No SaaS equivalent under $2,000/month.

Buying signals detected:

  • 🚀 Company hiring Sales/Marketing roles → scaling, has budget
  • 🔧 Hiring DevOps/Cloud Engineers → infrastructure investment incoming
  • 📈 Headcount growth > 20% in 90 days → expansion phase
  • 💼 New C-level hire (CMO, CTO, VP Sales) → new budget owner, new priorities
  • 📣 Job descriptions mentioning competitor tools → switching signal
  • 🏆 Recent funding round mention in job posts → fresh cash to spend

🛠️ Apify Actors Used

Get your Apify API key here: https://www.apify.com?fpr=dx06p

ActorIDPurpose
LinkedIn Jobs Scrapercurious_coder/linkedin-jobs-scraperScrape job postings by company/keyword
LinkedIn Company Scraperanchor/linkedin-company-scraperExtract headcount, growth, funding info
Google News Scraperapify/google-news-scraperDetect funding rounds, press releases
LinkedIn Profile Scraperdev_fusion/linkedin-profile-scraperFind decision-makers + contact info

⚙️ Workflow

INPUT: Target niche + location + ICP criteria
        ↓
STEP 1 — Scrape LinkedIn Jobs (last 30 days)
  └─ Filter by: hiring roles = buying signals
        ↓
STEP 2 — Scrape Company Profiles
  └─ Extract: headcount, growth %, tech stack, funding
        ↓
STEP 3 — Score each company (0–100 intent score)
  └─ Weighted signals → Hot / Warm / Cold
        ↓
STEP 4 — Find Decision Makers
  └─ CEO / VP Sales / CMO / CTO profiles + emails
        ↓
STEP 5 — Claude AI generates personalized outreach
  └─ Email + LinkedIn message referencing the exact signal
        ↓
OUTPUT: Scored lead list + ready-to-send messages (CSV / JSON / Notion / CRM)

📥 Inputs

{
  "niche": "SaaS companies",
  "location": "France",
  "hiring_signals": ["Sales Manager", "Growth Hacker", "DevOps Engineer"],
  "min_employees": 10,
  "max_employees": 500,
  "days_lookback": 30,
  "max_companies": 50,
  "apify_token": "YOUR_APIFY_TOKEN",
  "output_format": "csv"
}

📤 Output Example

{
  "companies": [
    {
      "name": "ScaleUp SAS",
      "website": "scaleup.fr",
      "linkedin_url": "linkedin.com/company/scaleup-sas",
      "headcount": 87,
      "growth_90d": "+34%",
      "intent_score": 91,
      "intent_label": "🔥 HOT",
      "signals_detected": [
        "Hiring VP Sales (posted 3 days ago)",
        "Hiring 4 SDRs simultaneously",
        "Job post mentions switching from HubSpot to Salesforce"
      ],
      "decision_makers": [
        {
          "name": "Marie Dupont",
          "title": "CEO",
          "linkedin": "linkedin.com/in/marie-dupont",
          "email": "m.dupont@scaleup.fr"
        }
      ],
      "ai_outreach": {
        "email_subject": "ScaleUp × [Votre outil] — timing parfait ?",
        "email_body": "Bonjour Marie, j'ai remarqué que ScaleUp recrute activement un VP Sales et 4 SDRs en ce moment...",
        "linkedin_message": "Marie, votre croissance de 34% en 90 jours est impressionnante..."
      }
    }
  ],
  "summary": {
    "total_companies_analyzed": 50,
    "hot_leads": 8,
    "warm_leads": 19,
    "cold_leads": 23,
    "run_date": "2025-02-28"
  }
}

🧠 Claude AI Prompt (Scoring + Outreach)

You are a B2B sales intelligence expert. 

Given this company data:
- Company: {{company_name}}
- Recent job postings: {{job_titles}}
- Headcount growth: {{growth_pct}}% in 90 days
- Signals detected: {{signals}}
- Target decision maker: {{dm_name}}, {{dm_title}}

1. Calculate an intent score from 0-100 based on the signals.
2. Label as: 🔥 HOT (80+), ⚡ WARM (50-79), ❄️ COLD (<50)
3. Write a personalized cold email (subject + 5 lines max) referencing 
   the MOST compelling signal.
4. Write a LinkedIn message (300 chars max) that feels human, not spammy.

Return valid JSON only.

💰 Cost Estimate (Apify Compute Units)

VolumeEstimated CUApify Cost
10 companies~15 CU~$0.15
50 companies~60 CU~$0.60
200 companies~220 CU~$2.20
1,000 companies~1,000 CU~$10

💡 Start free: Apify offers $5 free credits/month — enough to test 500 companies.
👉 Create your free Apify account here


🚀 Setup Instructions

1. Get Your Apify API Token

  1. Sign up at https://www.apify.com?fpr=dx06p
  2. Go to Settings → Integrations → API Token
  3. Copy your token

2. Configure the Skill

Paste your Apify token in the apify_token field when running the skill.

3. Define Your ICP

Specify your Ideal Customer Profile:

  • Industry / niche
  • Company size range
  • Location
  • Hiring roles that signal buying intent for YOUR product

4. Run & Export

Results are exported as CSV, JSON, or pushed directly to Notion / Airtable / your CRM.


🔗 Integrations

PlatformAction
SlackAlert when 🔥 HOT lead detected
NotionAuto-populate leads database
AirtableCRM-ready structured output
HubSpot / PipedriveDirect lead import via webhook
EmailWeekly digest of top signals

📊 Competitive Advantage vs Existing Skills

FeatureB2B Lead Gen (yours)Google Maps (yours)This Skill
Finds contact info
Scores buying intent
Detects timing signals
AI-personalized outreach
Tracks competitor mentions
Monitors headcount growth

⚠️ Limitations & Best Practices

  • LinkedIn may rate-limit heavy scraping → recommended max 200 companies/run
  • Email accuracy: ~70-80% (cross-reference with Hunter.io for best results)
  • Re-run weekly on the same target list to catch new signals
  • GDPR: Only use publicly available LinkedIn data, personalize responsibly

🏷️ Tags

lead-generation sales-intelligence linkedin buying-signals b2b outreach apify intent-data prospecting crm-enrichment


Powered by Apify — The Web Scraping & Automation Platform

Comments

Loading comments...