powerset-set

Lists Powerset sets and sets the default set scope for local Powerpacks search.

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

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? When working with multiple Powerset sets, local Powerpacks search primitives need to know which set to scope queries against. This Skill lets you inspect the sets accessible to your Powerset account and persist a default set ID locally so every search inherits the correct scope without repeated manual configuration. ## Core Features & Use Cases - List accessible sets: Calls the Powerset Search MCP list_sets tool to show all sets available to the logged-in user, including person, member, and Sales Navigator account counts. - Show the active default: Reads POWERPACKS_DEFAULT_SET_ID (or the legacy POWERSET_DEFAULT_SET_ID) from the local .env and matches it against MCP results. - Set the default by ID or name: Resolves a user-provided set name or UUID against MCP results and upserts a single POWERPACKS_DEFAULT_SET_ID line in the local ignored .env file. - Use Case: After joining a new recruiting project, run $powerset sets use engineering-candidates so all subsequent local network searches are scoped to that set automatically. ## Quick Start Ask your agent to use the powerset-set skill to list your Powerset sets and set the default set to the one named after your current recruiting project.

Frequently Asked Questions about powerset-set

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

FAQPage Schema
How do I set the default Powerset set for local search?▼

Run the skill with a set name or UUID, such as `$powerset sets use <id|name>`. It resolves the value against the MCP `list_sets` result and upserts `POWERPACKS_DEFAULT_SET_ID` into the local `.env` file.

How do I list all Powerset sets accessible to my account?▼

The skill calls the Powerset Search MCP `list_sets` tool directly to return every set available to the logged-in user. It does not use local SQL or `set_scope.py` for normal set retrieval.

Does changing the default set modify server-side set membership?▼

No. The skill only manages local set scope by writing `POWERPACKS_DEFAULT_SET_ID` to the local `.env` file. It does not upload contacts, run searches, or mutate server-side set membership.

What happens if POWERPACKS_DEFAULT_SET_ID is not set?▼

The skill falls back to checking the legacy `POWERSET_DEFAULT_SET_ID` variable, which search primitives still accept as an alias. If neither is set, no default set scope is applied to local searches.

Why does the skill require the Powerset Search MCP?▼

Set listing and name resolution are owned by the remote Powerset Search MCP, so the skill verifies MCP registration with `mcp_install.py status` before use. The local repo only owns the default choice stored in `.env`.