Skip to content

JasonColapietro/suede-creator-skills / skills/suede-prospecting

suede-prospecting

Verified

Build a source-backed, scored prospect list across SaaS, B2B, local business, or early demand signals. Use when asked to "find our first design partners", define an ICP, enrich leads, run gap plays or warm-path network mining, or document disqualification evidence. Includes source dates, confidence, licensed-data checks, and a qualification handoff. NOT FOR: sending outreach (use suede-cold-email), CRM routing (use suede-revops), or competitor profiles (use suede-competitor-profiling).

FileKindSize
CARD.mdmarkdown4.4 KB
SKILL.mdskill md19.3 KB
agents/openai.yamlconfig551 B
evals/evals.jsonconfig13.8 KB
references/b2b-prospecting.mdmarkdown5.5 KB
references/collector.mdmarkdown9.5 KB
references/compliance.mdmarkdown7.1 KB
references/data-sources.mdmarkdown14.5 KB
references/demand-signals.mdmarkdown9.4 KB
references/local-prospecting.mdmarkdown8.1 KB
references/saas-prospecting.mdmarkdown11.0 KB
references/worked-handoff.mdmarkdown1.6 KB
scripts/collect.mjsscript67.7 KB

evals/evals.json

View on GitHub
{
  "skill_name": "suede-prospecting",
  "evals": [
    {
      "id": 1,
      "prompt": "We're a B2B SaaS selling RevOps tooling at $30K ACV. Build me a list of 25 prospects.",
      "expected_output": "Should check for product-marketing.md first and identify the SaaS branch. It should define the ICP, then discover which research sources are currently callable, authenticated, authorized, and permitted before selecting vendors or a manual public-source workflow. Candidate-pool size should be justified by requested output, observed disqualification, source access, and review capacity rather than a hard multiplier. It should discover an authorized email validator and read its current result semantics, or label addresses unverified and provide a user-operated validation handoff. It should output the SaaS evidence table followed by a bounded priority-review set only where current signals support it. Should reference references/saas-prospecting.md.",
      "assertions": [
        "Checks for product-marketing.md",
        "Identifies SaaS branch",
        "Runs Phase 1 ICP definition",
        "Recommends multi-source discovery (Apollo, Clay, Crunchbase, BuiltWith)",
        "Asks about user's tool access",
        "Justifies a bounded candidate sample from evidence and review capacity",
        "Requires email validation before final list",
        "Outputs SaaS-branch chat table columns",
        "Includes an evidence-ranked priority-review set when warranted",
        "References saas-prospecting.md"
      ],
      "files": []
    },
    {
      "id": 2,
      "prompt": "Find me 25 SaaS companies that just raised a Series B in the last 60 days and use HubSpot.",
      "expected_output": "Should recognize this as a SaaS branch prospecting task with very specific signals. Should identify the trigger event (Series B in last 60 days) and the technographic filter (uses HubSpot). Should recommend a workflow: (1) Crunchbase or Pitchbook for funding signal filter (Series B + date), (2) BuiltWith or Clay's waterfall for tech stack verification (uses HubSpot), (3) cross-check via business websites and LinkedIn. Should note this is a tight ICP that should yield high-confidence matches if data sources are current. Should flag freshness concerns: Crunchbase data depends on self-reporting, BuiltWith refresh cycles aren't real-time. Should recommend cross-source verification for the funding date specifically. Should output a SaaS-branch chat table with the funding round + date in the Signal column. Should include verified email validation before delivering.",
      "assertions": [
        "Identifies as SaaS branch",
        "Identifies funding signal + tech stack filter",
        "Recommends Crunchbase or Pitchbook for funding",
        "Recommends BuiltWith or Clay for HubSpot verification",
        "Notes data freshness concerns",
        "Recommends cross-source verification",
        "Outputs signal column showing round + date",
        "Requires email validation"
      ],
      "files": []
    },
    {
      "id": 3,
      "prompt": "I run a marketing agency. Find me 25 mid-market manufacturers in the Midwest US who recently hired a new CMO.",
      "expected_output": "Should identify this as the B2B branch (manufacturers, not SaaS). Should run Phase 1 ICP definition: industry (manufacturing, with NAICS code if precision matters), size (mid-market = typically 200-2000 employees), geography (Midwest US states), trigger event (CMO hire in last 90-180 days). Should propose discovery: Apollo or ZoomInfo for firmographic filter, LinkedIn Sales Nav for CMO hire detection (job changes), Google Alerts on press releases for trigger events. Should warn that CMO hires aren't always in public databases: LinkedIn Sales Nav alerts on job changes is the most reliable source. Should output B2B-branch chat table with the CMO trigger as the signal. Should reference references/b2b-prospecting.md. Should mention compliance: GDPR less likely (US-only), CAN-SPAM applies, capture source URL + date for every contact.",
      "assertions": [
        "Identifies B2B branch (not SaaS)",
        "Runs Phase 1 ICP definition with NAICS or industry classification",
        "Specifies mid-market size band",
        "Specifies Midwest US geography",
        "Identifies trigger event (CMO hire)",
        "Recommends Apollo/ZoomInfo + LinkedIn Sales Nav",
        "Notes CMO hires often only on LinkedIn",
        "Outputs B2B-branch chat table",
        "Mentions CAN-SPAM and source URL capture",
        "References b2b-prospecting.md"
      ],
      "files": []
    },
    {
      "id": 4,
      "prompt": "We sell to industrial distributors. Build a list of 25 prospects.",
      "expected_output": "Should identify this as the B2B branch. Should run Phase 1 ICP definition asking targeted questions: distributor size, geography, vertical specialty, buying patterns. Should propose discovery: Apollo or ZoomInfo for firmographic depth, industry-specific directories (e.g., NAW for wholesale distributors, ISA for industrial sales agencies), trade show exhibitor lists. Should note state business registries and Chamber of Commerce as verification sources. Should propose trigger events: new location, recent acquisition, leadership change, posting RFPs. Should warn that industrial distributor data is often spotty in major databases: cross-check with company website + LinkedIn for size and ownership signals. Should output B2B-branch chat table. Should note ICP fit precision matters more than initial volume for this kind of niche prospecting.",
      "assertions": [
        "Identifies B2B branch",
        "Runs Phase 1 ICP definition asking targeted questions",
        "Recommends industry-specific directories beyond Apollo/ZoomInfo",
        "Mentions trade show exhibitor lists",
        "Identifies relevant trigger events",
        "Warns about data spottiness for industrial",
        "Recommends cross-verification with business websites + LinkedIn",
        "Notes ICP fit precision over volume"
      ],
      "files": []
    },
    {
      "id": 5,
      "prompt": "I build websites for local businesses. Find me 15 prospects near Austin, TX who don't have a website.",
      "expected_output": "Should identify the Local SMB branch and define the business category, geography, requested count, and service-gap criteria. It should discover whether an authorized research connector or browser is currently callable and permitted; otherwise it should provide exact public-source queries and work from user-supplied URLs, exports, screenshots, or copied text. It should cross-check listing claims against the business's own site or another current source and treat website status as one signal, not an automatic Hot/Warm quota. It should output the Local SMB evidence table and a bounded priority-review set only when cited evidence supports it. It should reference references/local-prospecting.md and prohibit bulk extraction.",
      "assertions": [
        "Identifies Local SMB branch",
        "Asks about business category if not specified",
        "Uses a user-approved geography or a justified pilot radius",
        "Discovers authorized research tooling or uses a manual fallback",
        "Applies 4-tier website status classification",
        "Uses Hot/Warm/Cold/Skip scoring",
        "Outputs Local SMB chat table columns",
        "Adds an evidence-ranked priority-review set when warranted",
        "References local-prospecting.md",
        "Warns against bulk-scraping Google Maps"
      ],
      "files": []
    },
    {
      "id": 6,
      "prompt": "I have a list of 200 prospect emails from Apollo. How do I know which ones are deliverable before I start outreach?",
      "expected_output": "Should explain the deliverability validation step in Phase 3. Should first verify which validator is available in the current session and read its current official result semantics, account limits, and terms. Should map deliverable, invalid, risky, unknown, and catch-all results without inventing vendor-specific fields; exclude invalid results, treat risky and catch-all cautiously, and re-verify unknown results. Should calculate risk from current list data and sender-platform guidance instead of asserting universal source-accuracy or bounce thresholds. Should hand the approved list to `suede-cold-email` only after validation and suppression checks.",
      "assertions": [
        "Uses an authorized validator or explicit unverified/manual fallback",
        "Explains email_state values (ok, email_invalid, risky, unknown, accept_all)",
        "Treats provider accuracy as unverified until checked on a current sample",
        "Uses current sender-platform evidence instead of a universal bounce threshold",
        "Recommends a result-aware validation and suppression workflow",
        "Discovers an available authorized validator or gives a manual fallback",
        "Mentions that sender reputation is difficult to recover",
        "References data-sources.md"
      ],
      "files": []
    },
    {
      "id": 7,
      "prompt": "I just built a tool that automates failed-payment follow-up for gym owners. I have no customers yet. Help me find my first ten: the people who are actually dealing with this problem right now.",
      "expected_output": "Should select the Demand-signal branch and load references/demand-signals.md, not the SMB, B2B, or SaaS list-building branches. Should start with a product brief, then mine the five signal buckets across public professional discourse. Before research, it should discover currently callable search, browser, and source-reading tools; verify authorization and source terms; and use a manual query plus user-supplied URL or export fallback when those tools are unavailable. It must read original public sources rather than qualify from snippets. Should score prospects on the demand-fit rubric rather than ICP-fit Hot/Warm/Cold and require a cited public signal for every primary-shortlist prospect. Should draft source-based openers but never auto-send. Should produce the evidence report and label prospects as potential customers based on public signals, not confirmed buyers. Should honor the compliance guardrails including no data brokers, leaked data, or sensitive-trait targeting.",
      "assertions": [
        "Selects the Demand-signal branch, not the SMB/B2B/SaaS list-building branches",
        "Mines the five signal buckets from public discourse rather than contact databases",
        "Discovers authorized current tools, includes a manual fallback, and reads original sources rather than snippets",
        "Scores on the demand-fit rubric (0-100 weighted), not ICP-fit Hot/Warm/Cold",
        "Requires a cited public signal for every primary-shortlist prospect",
        "Drafts openers but never auto-sends; labels prospects as potential-based-on-public-signals",
        "Produces the evidence report structure with a 7-day manual outreach plan and limits"
      ],
      "files": []
    },
    {
      "id": 8,
      "prompt": "I'm a founder selling payroll software to 20-200 person companies. Cold email reply rates have cratered. I have about 4,000 LinkedIn connections and a busy calendar. Can I turn my own network into pipeline without spamming people?",
      "expected_output": "Should apply the warm-paths method in SKILL.md Phase 2 and lay out: export LinkedIn connections, calendar attendees and inbox contacts (noting LinkedIn's export only includes emails for connections who allow it, and that this is the user's own data export, not scraping); enrich and score against the ICP; match against a target account list to find first- and second-degree paths; start with recent calendar meetings to find buying moments; recruit a connector per vertical and pay them per qualified meeting with the arrangement disclosed; use double opt-in intros only, with a human approving every intro and no contact asked to take intros for two vendors in the same week. Keeps the source URL and capture date rule for every row.",
      "assertions": [
        "Starts by exporting the network (LinkedIn, calendar, inbox)",
        "Notes LinkedIn's export lacks emails for most connections",
        "Matches contacts against target accounts for first- and second-degree paths",
        "Suggests starting with recent calendar meetings",
        "Recommends connectors with disclosed compensation",
        "Requires double opt-in intros with a human approving each one"
      ],
      "files": []
    },
    {
      "id": 9,
      "prompt": "I run a landing page and tracking agency. Build me a list of B2B SaaS companies that are running Meta ads but have no pixel installed or are sending ad traffic to their homepage, and draft the opener.",
      "expected_output": "Should load references/saas-prospecting.md (gap plays) and pair the ad-activity signal with gaps verified from outside: ad destinations from the Meta Ad Library, tags from page source, the network tab, or a tag checker. Should require evidence (date, URL or screenshot) for every gap and treat 'no gap found' as a valid result. Should caveat that server-side tracking (Conversions API, server-side GTM) is invisible from outside, so a missing browser pixel isn't proof, and that homepage destinations can be deliberate. Should re-verify the gap within 7 days of sending. The opener should state the observation and ask a question rather than accuse, offer the teardown only after a yes, and route final outreach copy to suede-cold-email without sending anything.",
      "assertions": [
        "Uses the Meta Ad Library to confirm active ads and their destinations",
        "Checks tags from outside (page source, network tab, or tag checker)",
        "Requires dated evidence for each gap and allows 'no gap found'",
        "Warns that server-side tracking can't be seen from outside",
        "Re-verifies gaps within 7 days of sending",
        "Opener is an observation plus a question, not an accusation"
      ],
      "files": []
    }
  ]
}
brainstormingobra/superpowersYou MUST use this before any creative work - creating features, building components, adding functionality, modifying behavior, or planning anything new, in software or out of it (a talk, a business, a renovation).Stars: 323kUpdated Claude CodeCodexVerifiedInstall
brand-guidelinesanthropics/skillsApplies Anthropic's official brand colors and typography to any sort of artifact that may benefit from having Anthropic's look-and-feel. Use it when brand colors or style guidelines, visual formatting, or company design standards apply.Stars: 198kUpdated Claude CodeCodexVerifiedInstall
frontend-designanthropics/skillsGuidance for distinctive, intentional visual design when building new UI or reshaping an existing one. Helps with aesthetic direction, typography, and making choices that don't read as templated defaults.Stars: 198kUpdated Claude CodeCodexVerifiedInstall
mcp-builderanthropics/skillsGuide for creating high-quality MCP (Model Context Protocol) servers that enable LLMs to interact with external services through well-designed tools. Use when building MCP servers to integrate external APIs or services, whether in Python (FastMCP) or Node/TypeScript (MCP SDK).Stars: 198kUpdated Claude CodeCodexVerifiedInstall