prospect

anthropics/knowledge-work-plugins · updated Apr 8, 2026

MDX-style export adds YAML metadata + attribution linking explainx.ai and this canonical listing URL.

$npx skills add https://github.com/anthropics/knowledge-work-plugins --skill prospect
0 commentsdiscussion
summary

Go from an ICP description to a ranked, enriched lead list in one shot. The user describes their ideal customer via "$ARGUMENTS".

skill.md

Prospect

Go from an ICP description to a ranked, enriched lead list in one shot. The user describes their ideal customer via "$ARGUMENTS".

Examples

  • /apollo:prospect VP of Engineering at Series B+ SaaS companies in the US, 200-1000 employees
  • /apollo:prospect heads of marketing at e-commerce companies in Europe
  • /apollo:prospect CTOs at fintech startups, 50-500 employees, New York
  • /apollo:prospect procurement managers at manufacturing companies with 1000+ employees
  • /apollo:prospect SDR leaders at companies using Salesforce and Outreach

Step 1 — Parse the ICP

Extract structured filters from the natural language description in "$ARGUMENTS":

Company filters:

  • Industry/vertical keywords → q_organization_keyword_tags
  • Employee count ranges → organization_num_employees_ranges
  • Company locations → organization_locations
  • Specific domains → q_organization_domains_list

Person filters:

  • Job titles → person_titles
  • Seniority levels → person_seniorities
  • Person locations → person_locations

If the ICP is vague, ask 1-2 clarifying questions before proceeding. At minimum, you need a title/role and an industry or company size.

Step 2 — Search for Companies

Use mcp__claude_ai_Apollo_MCP__apollo_mixed_companies_search with the company filters:

  • q_organization_keyword_tags for industry/vertical
  • organization_num_employees_ranges for size
  • organization_locations for geography
  • Set per_page to 25

Step 3 — Enrich Top Companies

Use mcp__claude_ai_Apollo_MCP__apollo_organizations_bulk_enrich with the domains from the top 10 results. This reveals revenue, funding, headcount, and firmographic data to help rank companies.

Step 4 — Find Decision Makers

Use mcp__claude_ai_Apollo_MCP__apollo_mixed_people_api_search with:

  • person_titles and person_seniorities from the ICP
  • q_organization_domains_list scoped to the enriched company domains
  • per_page set to 25

Step 5 — Enrich Top Leads

Credit warning: Tell the user exactly how many credits will be consumed before proceeding.

Use mcp__claude_ai_Apollo_MCP__apollo_people_bulk_match to enrich up to 10 leads per call with:

  • first_name, last_name, domain for each person
  • reveal_personal_emails set to true

If more than 10 leads, batch into multiple calls.

Step 6 — Present the Lead Table

Show results in a ranked table:

Leads matching: [ICP Summary]

# Name Title Company Employees Revenue Email Phone ICP Fit

ICP Fit scoring:

  • Strong — title, seniority, company size, and industry all match
  • Good — 3 of 4 criteria match
  • Partial — 2 of 4 criteria match

Summary: Found X leads across Y companies. Z credits consumed.

Step 7 — Offer Next Actions

Ask the user:

  1. Save all to Apollo — Bulk-create contacts via mcp__claude_ai_Apollo_MCP__apollo_contacts_create with run_dedupe: true for each lead
  2. Load into a sequence — Ask which sequence and run the sequence-load flow for these contacts
  3. Deep-dive a company — Run /apollo:company-intel on any company from the list
  4. Refine the search — Adjust filters and re-run
  5. Export — Format leads as a CSV-style table for easy copy-paste
how to use prospect

How to use prospect on Cursor

AI-first code editor with Composer

1

Prerequisites

Before installing skills in Cursor, ensure your development environment meets these requirements:

  • Cursor installed and configured on your development machine
  • Node.js version 16.0+ with npm package manager (verify with node --version)
  • Active project directory or workspace where you want to add prospect
2

Execute installation command

Execute the skills CLI command in your project's root directory to begin installation:

$npx skills add https://github.com/anthropics/knowledge-work-plugins --skill prospect

The skills CLI fetches prospect from GitHub repository anthropics/knowledge-work-plugins and configures it for Cursor.

3

Select Cursor when prompted

The CLI will show a list of available agents. Use arrow keys to navigate and space to select Cursor:

◆ Which agents do you want to install to?
│ ── Universal (.agents/skills) ── always included ────
│ • Amp
│ • Antigravity
│ • Cline
│ • Codex
│ ●Cursor(selected)
│ • Cursor
│ • Windsurf
4

Verify installation

Confirm successful installation by checking the skill directory location:

.cursor/skills/prospect

Reload or restart Cursor to activate prospect. Access the skill through slash commands (e.g., /prospect) or your agent's skill management interface.

Security & Verification Notice

We perform automated surface-level scans (Gen AI Scanner, Socket, Snyk) during installation. These checks detect common vulnerabilities but do not guarantee complete security. Always review skill source code and verify the publisher's reputation before production use.

Skills execute code in your development environment. Always verify the publisher's identity, review recent commits, and test in isolated environments before production deployment.

List & Monetize Your Skill

Submit your Claude Code skill and start earning

GET_STARTED →

Use Cases

User Story & Requirements Generation

Create detailed user stories, acceptance criteria, and feature specs

Example

Generate user stories for 'password reset feature' with acceptance criteria, edge cases, and test scenarios

Reduce spec writing time by 50%, ensure comprehensive coverage

Competitive Analysis

Research competitors, compare features, identify gaps

Example

Analyze 5 competitor products, create feature comparison matrix, suggest differentiation opportunities

Complete competitive research in 2 hours instead of 2 days

Roadmap Prioritization

Evaluate features using frameworks (RICE, ICE, Kano) and create prioritized backlogs

Example

Score 20 feature ideas using RICE framework, generate prioritized roadmap with rationale

Make data-driven prioritization decisions faster

Stakeholder Communication

Draft PRDs, status updates, and stakeholder presentations

Example

Create executive summary of Q3 roadmap, monthly progress report, feature launch announcement

Save 3-5 hours/week on communication overhead

Implementation Guide

Prerequisites

  • Claude Desktop or compatible AI client
  • Access to product documentation and roadmap tools (Jira, Notion, etc.)
  • Understanding of product management frameworks (RICE, Jobs-to-be-Done, etc.)
  • Stakeholder contact information and communication channels

Time Estimate

30-60 minutes to see productivity improvements

Installation Steps

  1. 1.Install product management skill
  2. 2.Start with user story generation for known feature
  3. 3.Progress to competitive analysis: research 2-3 competitors
  4. 4.Use for roadmap prioritization: apply RICE/ICE scoring
  5. 5.Draft stakeholder communications and refine based on feedback
  6. 6.Build template library for recurring PM tasks
  7. 7.Share effective prompts with product team

Common Pitfalls

  • Not validating competitive research—verify facts before sharing
  • Accepting user stories without involving engineering team
  • Over-relying on frameworks without qualitative judgment
  • Not customizing outputs to company culture and communication style
  • Skipping stakeholder validation of generated requirements

Best Practices

✓ Do

  • +Validate research and competitive analysis with real data
  • +Collaborate with engineering when generating technical requirements
  • +Customize frameworks and templates to your company context
  • +Use skill for first drafts, refine with stakeholder input
  • +Document successful prompt patterns for PM tasks
  • +Combine AI efficiency with human judgment and intuition

✗ Don't

  • Don't publish competitive analysis without fact-checking
  • Don't finalize user stories without engineering review
  • Don't make prioritization decisions solely on AI scoring
  • Don't skip customer validation of generated requirements
  • Don't ignore company-specific context and culture

💡 Pro Tips

  • Provide context: company goals, constraints, customer feedback
  • Ask for alternatives: 'Show 3 ways to prioritize this roadmap'
  • Request stakeholder-specific formatting: 'Executive summary vs. engineering spec'
  • Use skill for 70% generation + 30% customization to company needs

When to Use This

✓ Use When

Use for user story writing, competitive research, roadmap prioritization, stakeholder communication, and PRD drafting. Best for reducing repetitive documentation and research work.

✗ Avoid When

Avoid for strategic product vision (requires deep customer empathy), pricing decisions (needs market and financial expertise), or when face-to-face customer discovery is more valuable than speed.

Learning Path

  1. 1Basic: user stories, feature specs, status updates
  2. 2Intermediate: competitive analysis, prioritization frameworks, PRDs
  3. 3Advanced: product strategy, go-to-market planning, OKR setting
  4. 4Expert: product vision, market positioning, business model innovation

Discussion

Product Hunt–style comments (not star reviews)
  • No comments yet — start the thread.
general reviews

Ratings

4.571 reviews
  • Carlos Smith· Dec 28, 2024

    Useful defaults in prospect — fewer surprises than typical one-off scripts, and it plays nicely with `npx skills` flows.

  • Ava Sharma· Dec 24, 2024

    Registry listing for prospect matched our evaluation — installs cleanly and behaves as described in the markdown.

  • Mateo Ndlovu· Dec 20, 2024

    Registry listing for prospect matched our evaluation — installs cleanly and behaves as described in the markdown.

  • Carlos Johnson· Dec 16, 2024

    Keeps context tight: prospect is the kind of skill you can hand to a new teammate without a long onboarding doc.

  • Shikha Mishra· Dec 12, 2024

    prospect reduced setup friction for our internal harness; good balance of opinion and flexibility.

  • Arya Gupta· Dec 8, 2024

    We added prospect from the explainx registry; install was straightforward and the SKILL.md answered most questions upfront.

  • Carlos Brown· Dec 8, 2024

    prospect reduced setup friction for our internal harness; good balance of opinion and flexibility.

  • Meera Martin· Dec 4, 2024

    Solid pick for teams standardizing on skills: prospect is focused, and the summary matches what you get after install.

  • Daniel Jackson· Nov 27, 2024

    Solid pick for teams standardizing on skills: prospect is focused, and the summary matches what you get after install.

  • Ava Srinivasan· Nov 23, 2024

    We added prospect from the explainx registry; install was straightforward and the SKILL.md answered most questions upfront.

showing 1-10 of 71

1 / 8