Semantic Prospect

AI-powered semantic lead prospecting – discovers, qualifies, and enriches high-intent business opportunities from web communities, forums, Reddit, and public...

Security Scan

The skill's instructions, required credential, and behavior are internally consistent with a SaaS lead-discovery API; no code or install step is present, but there are a few minor documentation/metadata inconsistencies you should verify before use.

Purpose & Capability

The skill's name and description (semantic lead prospecting from public forums/Reddit) align with its declared API usage: it requires a service-specific API key and POSTs queries to a Simply Semantics endpoint that returns leads. The functionality described (strategies: mock/brave/llm, enrichment, scoring) is plausible for the stated purpose.

Instruction Scope

SKILL.md gives narrow, task-focused runtime instructions: extract targeting criteria, validate, then call the MCP endpoint with x-api-key. It does not instruct reading unrelated local files or other env vars. Note: the docs emphasize the platform 'never reads or transmits your environment variables' but also instruct the agent to send SIMPLY_SEMANTICS_API_KEY in an x-api-key header — this is expected for an API but the phrasing could be clearer (they likely mean they don't read unrelated env-vars).

Install Mechanism

Instruction-only skill with no install spec and no code files — lowest risk install surface (nothing is written to disk by the skill itself).

Credentials

The only required credential in SKILL.md and clawhub.json is a single service-scoped API key (SIMPLY_SEMANTICS_API_KEY), which is proportional to the stated SaaS API purpose. However, the top-level registry summary in the package metadata lists 'Required env vars: none' which contradicts the SKILL.md and clawhub.json. Also the privacy text's wording about 'never reads, collects, or transmits your environment variables' is ambiguous and should be clarified (they presumably mean they don't collect arbitrary env vars or third-party keys).

Persistence & Privilege

The skill is not always-enabled and is user-invocable; it does not request any elevated platform privileges or system-wide configuration changes in the instructions. Autonomous invocation is allowed (normal default) but not combined with other concerning permissions.

Assessment

This skill appears to do what it says: it calls a Simply Semantics API and requires a single service API key. Before installing, verify the following: 1) Confirm the API key is obtained only from the vendor dashboard (https://dashboard.simplysemantics.com/sp/) and that you trust the https://dashboard.simplysemantics.com domain. 2) Note the metadata inconsistency: some registry summaries claim 'no required env vars' while the SKILL.md and clawhub.json require SIMPLY_SEMANTICS_API_KEY — expect to provide that key. 3) Understand the mock default: new accounts default to strategy 'mock' (synthetic leads); you must explicitly set strategy:'brave' or 'llm' to get real results. 4) Ask the vendor to clarify the privacy wording about 'not reading environment variables' (they should confirm they only use the supplied SIMPLY_SEMANTICS_API_KEY for authentication and don't harvest other secrets). 5) Ensure your intended use complies with the target communities' terms of service and privacy rules (the vendor states they only use public content). If you need higher assurance, request the vendor's security/privacy documentation or an API contract showing exact request/response shapes and retention behavior.

Quick summary
AI semantically understands context across web sources (Reddit, forums, communities, public discussions) to identify high-intent prospects with real buying signals. It qualifies, scores, enriches, and organizes leads into action-ready records — perfect for sales teams, SaaS companies, consultants, course creators, and especially AI agents/bots that can autonomously nurture and convert.

Authentication

SIMPLY_SEMANTICS_API_KEY is always required. This is your personal API key generated when you create an account at https://dashboard.simplysemantics.com/sp/. It authenticates your requests and is scoped to your Semantic Prospect account only — it does not grant access to any other Simply Semantics service or any third-party system.

What "no configuration required" means: You do NOT need to supply third-party search API keys (Brave, Perplexity, xAI, etc.) to use the free tier. The platform provides its own search keys for free-tier queries. You only need your SIMPLY_SEMANTICS_API_KEY for authentication.

Optionally, you can add your own Brave Search or LLM API keys in the dashboard to bypass free-tier limits.

Free tier limits

• Weekly free searches: 10 per week (shared across Brave Search and LLM when using platform-provided keys)
• LLM free queries: 5 total (limited to 3 results per query)
• Monthly lead quota: 50 leads
• Add your own Brave or LLM API key via the dashboard to bypass weekly limits and get up to 10 results per LLM query

Privacy & data handling

• Data sources: All leads are discovered from publicly accessible web content only (public forums, Reddit, community boards). No private data, no login-walled content, no PII databases are accessed.
• Data retention: Leads are stored in your account for your review and export. They are not shared with other users or third parties.
• No credential collection: The platform never reads, collects, or stores your third-party API keys on the server side. If you add your own Brave or LLM key in the dashboard, it is stored encrypted in your account's strategy configuration and used only to make search requests on your behalf.
• No cross-service data sharing: Your Semantic Prospect data is isolated to your account. It is not shared with other Simply Semantics services (e.g. Semantic Shield).
• Compliance: Users are responsible for ensuring their use of lead data complies with each source community's terms of service. Semantic Prospect only surfaces publicly available information.

When to use this skill (activation triggers)

Activate Semantic Prospect when the user:

• Wants to find qualified leads/opportunities in specific industries, topics, keywords, or communities.
• Asks to "discover prospects", "find high-intent leads", "qualify opportunities", "scan communities for buyers", "build targeted list from Reddit/forums", "identify pain-point discussions".
• Provides targeting criteria (e.g. keywords, industry, location filters) and wants semantic/intent-based results.
• Needs enriched prospect data for outbound, enrichment, or agent handoff.

Do NOT use for:

• Generic web search or scraping (use browser tools)
• PII-heavy or non-public data lookup
• Real-time monitoring of private channels
• Non-business/opportunity focused queries (e.g. news, memes)

How to use (instructions for the agent)

1. Extract targeting criteria — Pull from user message:

   • Keywords/topics (e.g. "compliance tools", "Series B fintech")
   • Industries/verticals
   • Communities/sources (Reddit subs, forums, niche boards)
   • Filters (location, engagement level, intent signals)
   • Optional: custom qualification rules or ICP description

2. Validate — If missing core criteria (keywords or industry/topic) → ask: "Please specify keywords, industry, or communities to prospect in."

3. Call the API — POST to the Semantic Prospect endpoint.

   URL: https://dashboard.simplysemantics.com/sp/mcp/forum-leads-api

   Headers:

   x-api-key: ${SIMPLY_SEMANTICS_API_KEY}
   Content-Type: application/json
   

⚠️ IMPORTANT: Default strategy is mock (test data)

New accounts default to the mock strategy, which returns fake sample leads for testing purposes only. Mock leads contain synthetic data — no real users, URLs, or contact information. They are safe to inspect. You must explicitly set "strategy": "brave" or "strategy": "llm" in the request body to get real results. The user can also change their default strategy in the dashboard under Search Strategies → "Set as Default", but when calling via API, always pass the strategy field explicitly.

If the response contains "is_mock": true or "search_strategy": "mock", the results are test data — not real leads.

Example: Mock / Testing (fake sample data — DEFAULT for new accounts)

{
  "niche": "marketing",
  "keywords": ["test"]
}

Omitting "strategy" uses the user's default, which is mock for new accounts. Returns synthetic test leads with "is_mock": true. Mock data contains no real personal information — it is safe for testing and integration validation.

Example: LLM Web Search (real AI-powered results)

{
  "niche": "marketing",
  "nicheLabel": "Digital Marketing Services",
  "keywords": ["SEO help", "Google ranking", "social media manager"],
  "strategy": "llm"
}

Free tier: 5 LLM queries (3 results each), counts toward 10 weekly free searches. No third-party API key setup needed — the platform provides its own.

Example: Brave Search (real web search results)

{
  "niche": "fitness",
  "nicheLabel": "Personal Training & Fitness",
  "keywords": ["need personal trainer", "looking for fitness coach"],
  "strategy": "brave"
}

Free tier: counts toward 10 weekly free searches. No third-party API key setup needed — the platform provides its own.

Request body fields

Field	Type	Required	Description
niche	string	no	Target niche key (default: "marketing")
nicheLabel	string	no	Display name for the niche
keywords	string[]	no	Search keywords
strategy	string	no	"llm", "brave", or "mock". Defaults to user's preferred strategy (mock for new accounts). Always pass explicitly for real results.

Output

{
  "leads": [
    {
      "url": "https://www.reddit.com/r/smallbusiness/comments/abc123",
      "poster_username": "auto_shop_owner",
      "intent_summary": "Running an auto repair shop with paper invoices, need affordable shop management software",
      "lead_score": 88,
      "contact_hint": "Comparing tools, budget up to $200/month, ready to buy",
      "source_forum": "reddit.com",
      "is_mock": false,
      "search_strategy": "llm",
      "search_rank": 1,
      "niche": "marketing"
    }
  ],
  "strategy": "llm",
  "free_tier": {
    "maxResults": 3
  }
}

Notes on the response:

• search_strategy — which engine found the lead: brave, llm, or mock
• is_mock — true when mock/test strategy was used; these are NOT real leads
• free_tier — only present when LLM free tier was used; maxResults indicates the cap on results per query
• search_rank — position in the raw search results before scoring

4. Parse & format — Transform response into clean report for the user.
   • If is_mock is true on any lead, warn the user that results are test data and they should set strategy to "llm" or "brave" for real leads.
5. Edge cases

• 401/403 → "Missing or invalid SIMPLY_SEMANTICS_API_KEY. Set the env var to use this skill."
• 429 → "Rate limit reached (monthly quota, weekly free searches, or LLM free queries exhausted). Retry later, add your own API key, or contact [e-mail]"
• No results → "No high-intent matches found with current criteria. Try broadening keywords or sources."
• Error → fallback polite message + suggest refining input