Surface passive technical experts by the depth of the answers they give, not the resumes they wrote
https://apidirect.io/mcp?token=YOUR_API_KEY
Find me passive experts who clearly know how to solve {problem} and check they are credible, established accounts
reddit-deep-expertise-sourcer.
Any agent can also call get_skill(skill_id="reddit-deep-expertise-sourcer") to pull these steps on demand.
The best engineers rarely job-hunt, but they answer hard questions in public. Mining the top comments on a deep technical problem reveals demonstrated competence, and user vetting filters down to credible, established accounts worth a cold approach.
Who it's for: Technical recruiters and founders hunting passive senior or specialist talent
| Input | Required | Description | Example |
|---|---|---|---|
problem |
Yes | A deep, specific technical problem only a real expert would answer well | debugging Kubernetes etcd quorum loss |
skill_area |
No | Broader skill area to widen the expert pool and spot recurring names | Kubernetes |
search_reddit_comments(query={problem}, sort_by=top, get_sentiment=true)
Gather the most upvoted, substantive answers to the hard problem and note the authors who show first-hand expertise.
search_reddit_comments(query={skill_area}, sort_by=top)
Widen to the broader skill area to spot authors who recur across multiple deep threads, signaling genuine depth.
search_reddit_users(query=<comment_author>)
Vet each recurring author's karma and account age to keep only established, credible experts and drop throwaway accounts.
This is exactly what the MCP returns to your agent (via the reddit-deep-expertise-sourcer prompt or get_skill tool), with your inputs filled in.
SKILL: Reddit Deep-Expertise Sourcer
The best engineers rarely job-hunt, but they answer hard questions in public. Mining the top comments on a deep technical problem reveals demonstrated competence, and user vetting filters down to credible, established accounts worth a cold approach.
You are running this skill on API Direct via its MCP tools. Execute the steps below yourself by calling the named tools in order — values in <angle brackets> come from a previous step. Then deliver the result described at the end.
INPUTS:
- problem (required): <problem — ASK THE USER>
- skill_area (optional): (optional — e.g. Kubernetes)
STEPS:
1. Tool `search_reddit_comments` — search_reddit_comments(query=<problem>, sort_by=top, get_sentiment=true)
Gather the most upvoted, substantive answers to the hard problem and note the authors who show first-hand expertise.
2. Tool `search_reddit_comments` — search_reddit_comments(query=<skill_area>, sort_by=top)
Widen to the broader skill area to spot authors who recur across multiple deep threads, signaling genuine depth.
3. Tool `search_reddit_users` — search_reddit_users(query=<comment_author>)
Vet each recurring author's karma and account age to keep only established, credible experts and drop throwaway accounts.
DELIVER: A vetted list of passive subject-matter experts who publicly solve <problem>-class issues, ranked by demonstrated depth and account credibility.
Note: each underlying tool call is billed at its normal endpoint price; get_sentiment adds a small per-page surcharge. Page through results as needed but stop once you have enough to deliver the outcome.
List a named competitor's employees by seniority — via their personal posts, not the company page.
Catch freshly laid-off talent within days of the announcement, before every other recruiter circles back
Find portfolio-grade designers, photographers and editors and pull their public email in one pass