search

Routes people-search queries to local DuckDB or Powerset backends with reviewed retrieval pipelines.

1|1|Updated Apr 28, 2026
One-click install
npx skills add https://github.com/powerset-co/powerpacks --skill search-powerset-co
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: search
Source: https://github.com/powerset-co/powerpacks/tree/main/packs/search/skills/search
Command: npx skills add https://github.com/powerset-co/powerpacks --skill search-powerset-co

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve? Recruiters and hiring teams need a single entry point that decides where and how deeply to search for candidates across local contact indexes and hosted Powerset networks, without manually choosing backends, writing queries, or managing search runs. ## Core Features & Use Cases - Intelligent Routing: Records a decision.json that routes each query by surface (people, company, SQL, contacts), backend (local DuckDB or Powerset TurboPuffer/Postgres), depth (fast or deep), and mode (interactive or auto). - Fast Search Pipelines: Runs prepare-and-execute flows over local DuckDB indexes or hosted TurboPuffer retrieval with LLM filtering and reranking, including a deterministic direct-lookup fast path for names, emails, and LinkedIn URLs. - Deep JD Search: Turns a pasted job description or job-posting URL into a result-driven pond loop with human scoring in a web viewer, model-crafted follow-up queries, and a final shortlist.csv. - Use Case: Paste a senior backend engineer job posting and get a reviewed, multi-round candidate shortlist from your Powerset network, with every query and filter confirmed before any spend. ## Quick Start Ask the agent to search for candidates, for example: search for senior software engineers in San Francisco using my Powerset network.

Frequently Asked Questions about search

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I search for candidates from a job description?▼

Paste the JD text or provide the job-posting URL and the skill records a deep-mode decision, generates one broad query for your review, then runs iterative search ponds. Results appear in a local web viewer where you score candidates, ending with a shortlist.csv.

How do I search my local network instead of Powerset?▼

Say 'local', 'offline', or 'my imported network' in the query and the router selects the local DuckDB backend. It uses the database at POWERPACKS_LOCAL_SEARCH_DB or .powerpacks/search-index/local-search.duckdb, with no TurboPuffer or Postgres calls.

What is the difference between fast and deep search modes?▼

Fast mode runs one expansion, retrieval, and rerank pass for ordinary people searches. Deep mode handles JDs and shortlist requests with a result-driven loop of up to four ponds, human scoring in a viewer, and model-crafted follow-up queries.

Can I look up a specific person by name or LinkedIn URL?▼

Yes, bare identifiers like a name, email, phone, Twitter handle, or LinkedIn URL trigger a direct DuckDB lookup instead of the full pipeline. It matches against profile columns and returns compact results without any LLM stages.

What happens if OPENAI_API_KEY is missing during a local search?▼

Local searches run LLM filtering and reranking by default, which require OPENAI_API_KEY. If the key is missing, rerun with the --search-only flag to skip the model stages instead of failing the search.

When should I not use this search skill?▼

Do not use it for Sales Navigator or LinkedIn lead retrieval, which are outside its retrieval boundary. Company-only lookups, cross-row SQL logic, and contact-field filtering are routed to their own dedicated surfaces instead.