sandbaseai/sandbase-skills / research/talent-sourcing
talent-sourcing
VerifiedSource technical and professional talent by combining LinkedIn profiles, GitHub contributions, and company intelligence. Identifies candidates with specific skills, assesses expertise depth, and provides outreach context for recruiting teams.
Talent Sourcing
Source technical and professional talent by combining LinkedIn profiles, GitHub contributions, and company intelligence. Identifies candidates with specific skills, assesses expertise depth, and provides outreach context for recruiting teams. Read the API map before selecting a capability.
Call SandBase capabilities
Use the capability identifiers below as discovery hints, not MCP tool names. Find the matching endpoint with sandbase_discover(q: "<provider and capability>"); use its returned name in sandbase_inspect(name: "<returned name>"). Read inputSchema, pricing, and execute_as, then call sandbase_run using execute_as.arguments.name and schema-defined arguments. If a run_id is returned, poll sandbase_run_get(run_id: "<returned run_id>") within the task budget until completed or failed; report pending or failed runs without resubmitting them automatically.
Capability identifiers
linkedin_web_v2_user_profilelinkedin_web_v2_search_jobsstrale_github_user_profileapollo_company_enrichagentbody_linkedin_profile
Workflow
- Understand the user's research question, target, and context.
- Resolve each selected capability with
sandbase_discover, then inspect the returnednamewithsandbase_inspectto confirm the schema and pricing. - Follow
execute_aswithsandbase_run; collect async results withsandbase_run_getas described above. - Synthesize findings into a clear, evidence-backed answer.
- Cite sources, note evidence gaps, and separate observations from interpretations.
Guidelines
- Always call
sandbase_inspectbefore using any capability. - Cite sources and preserve attribution (URLs, usernames, dates, metrics).
- Separate factual observations from analysis and recommendations.
- If data is unavailable, note the gap and continue with available evidence.
- Read-only research only. Never take actions on platforms.
Related skills
| Skill | Stars | Updated | Works with | Status | Install |
|---|---|---|---|---|---|
| reverse-engineer-anythingmorluto/reaReverse engineer native, managed, Electron/JavaScript, packaged, firmware, and browser targets with REA, and build agent environments (AgentEnv bundles) of web applications from a live instance or a capture, and of Linux desktop apps with a task from a request. Use shipped-artifact or requested runtime evidence to explain features, compare versions, decompile code, or guide a reconstruction. Skip REA for ordinary source-repository architecture analysis. | Stars: 471k | Updated | Claude CodeCodex | Verified | Install |
| diagnosing-superpowersobra/superpowersUse when a superpowers session went wrong and your human partner wants to know why — repeated work, ignored plans, stumbles, poor results, a skill that didn't fire, "it took too long", "why is it so expensive", "what is it doing" — or wants to build a bug report for the superpowers maintainers, for the current session or a past one identified by id or path, on any harness. | Stars: 322k | Updated | Claude CodeCodex | Verified | Install |
| dispatching-parallel-agentsobra/superpowersUse when facing 2+ independent tasks that can be worked on without shared state or sequential dependencies | Stars: 322k | Updated | Claude CodeCodex | Verified | Install |
| executing-plansobra/superpowersUse when executing an implementation plan in the current session as the implementer yourself — your human partner chose inline execution, or no subagent tool is available | Stars: 322k | Updated | Claude CodeCodex | Verified | Install |