lead-generation

Lead Generation — Find high-intent buyers in live Twitter, Instagram, and Reddit conversations. Auto-researches your product, generates targeted search queri...

Security Scan

The skill’s requirements and runtime instructions are consistent with a lead‑generation tool that proxies searches through SkillBoss; no glaring mismatches or unrelated credential requests were found, though there are minor metadata inconsistencies and some runtime behaviors you should verify before installing.

Purpose & Capability

The skill claims to find leads across Twitter/Instagram/Reddit and routes searches through SkillBoss API Hub; requesting a SKILLBOSS_API_KEY and calling api.skillbossai.com is appropriate and proportional to that purpose. No unrelated credentials or binaries are requested.

Instruction Scope

Instructions tell the agent to (a) use web_fetch/web_search to research the product, (b) call https://api.skillbossai.com/v1/pilot for searches, and (c) save artifacts to local paths under data/lead-generation. These actions are consistent with the stated purpose, but product research implies accessing arbitrary web pages (not limited to api.skillbossai.com) which the skill metadata only lists api.skillbossai.com for — confirm that the agent’s web capabilities and network policy permit and are intended to be used for broad web fetching. The skill instructs saving lead data locally (usernames, quotes, URLs) — expected for this use but a privacy consideration.

Install Mechanism

Instruction-only skill with no install spec and no code files. This is low-risk from an install-execution perspective (nothing is downloaded or installed by the skill itself).

Credentials

Only SKILLBOSS_API_KEY is required, which is proportionate. Minor inconsistency: registry metadata lists 'Primary credential: none' while SKILL.md clearly requires SKILLBOSS_API_KEY. Confirm the registry metadata and platform UI will surface this env var so you know what to provide.

Persistence & Privilege

always:false and no modifications to other skills or system configuration. The skill asks to write its own files under data/lead-generation (normal for a stateful skill). No elevated privileges requested.

Assessment

This skill looks coherent for social lead discovery, but verify a few things before installing: 1) Only provide a SKILLBOSS_API_KEY you trust and prefer a scope-limited key if possible — check SkillBoss’s permissions and data handling. 2) Confirm you’re comfortable with the agent fetching arbitrary webpages during product research (the SKILL.md uses web_fetch/web_search) and that your environment’s network policies allow that. 3) Understand that lead data (usernames, quotes, URLs, outreach drafts) will be written to local files under data/lead-generation — decide retention and access controls. 4) Fix the minor metadata issues (registry primary credential not set, metadata lists only api.skillbossai.com while instructions imply broader web access) or ask the publisher for clarification. If those points are acceptable, the skill’s requests are proportionate to its stated purpose.

Find high-intent buyers from live social conversations.

Discovers leads expressing problems your product solves, complaining about competitors, or actively seeking solutions across Twitter, Instagram, and Reddit.

Setup

Set SKILLBOSS_API_KEY environment variable. All search calls are routed through SkillBoss API Hub (https://api.skillbossai.com/v1/pilot).

3-Phase Process

Phase 1: Product Research (One-Time)

Ask for product reference (website/GitHub/description). Use web_fetch/web_search to research. Build profile: product info, target audience, pain points, competitors, keywords. Validate with user.

Generate 12-18 queries across:

1. Pain point queries — people expressing problems
2. Competitor frustration — complaints about alternatives
3. Tool/solution seeking — "recommend..."
4. Industry discussion — target audience

Save to data/lead-generation/product-profile.json and search-queries.json.

Phase 2: Lead Discovery (Repeatable)

Use SkillBoss API Hub to search for relevant social posts and users:

import requests, os

SKILLBOSS_API_KEY = os.environ["SKILLBOSS_API_KEY"]
API_BASE = "https://api.skillbossai.com/v1"

def pilot(body: dict) -> dict:
    r = requests.post(
        f"{API_BASE}/pilot",
        headers={"Authorization": f"Bearer {SKILLBOSS_API_KEY}", "Content-Type": "application/json"},
        json=body,
        timeout=60,
    )
    return r.json()

# Search Twitter posts by keyword
result = pilot({"type": "search", "inputs": {"query": "GENERATED_QUERY site:twitter.com"}, "prefer": "balanced"})
posts = result["result"]["results"]

# Search Instagram posts by keyword
result = pilot({"type": "search", "inputs": {"query": "GENERATED_QUERY site:instagram.com"}, "prefer": "balanced"})
posts = result["result"]["results"]

# Search Reddit posts by keyword
result = pilot({"type": "search", "inputs": {"query": "GENERATED_QUERY site:reddit.com"}, "prefer": "balanced"})
posts = result["result"]["results"]

Repeat for each generated query across platforms.

Phase 3: Scoring & Output

Score (1-10):

• Explicitly asking for solution: +3
• Complaining about competitor: +2
• Project blocked by pain: +2
• Active in target community: +1
• High engagement (>10 likes/5 comments): +1
• Recent (<48h): +1
• Profile matches ICP: +1
• Selling competing solution: -3

Tiers: 8-10 Hot, 6-7 Warm, 5 Watchlist

Deduplicate via data/lead-generation/sent-leads.json (key: {platform}:{author}:{post_id}).

Output: Username, quote, URL, score, why fit, outreach draft, engagement, timestamp.

Outreach:

"I had the same problem! Ended up using [Product] — it does [capability]. [URL] (Disclosure: I work with [Product])"

Tips

• Save profile once, reuse daily
• Quality > quantity
• Always disclose affiliations
• Draft only; user reviews/sends